Originally created by @minatsuki on GitHub (Apr 20, 2022).
Use the 1.24 container behind a reserve proxy with the subfolder reverse proxy config from here. The container will run fine when set the DOMAIN section with subfolder in config.json until restart. After restart, access through the proxy / without proxy all shows 404.
After delete the DOMAIN section in config, all work fine again. The problem also occurs when set url with "-e DOMAIN".
Originally created by @minatsuki on GitHub (Apr 20, 2022).
Use the 1.24 container behind a reserve proxy with the subfolder reverse proxy config from [here](https://github.com/dani-garcia/vaultwarden/wiki/Proxy-examples). The container will run fine when set the DOMAIN section with subfolder in config.json until restart. After restart, access through the proxy / without proxy all shows 404.
After delete the DOMAIN section in config, all work fine again. The problem also occurs when set url with "-e DOMAIN".
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @minatsuki on GitHub (Apr 20, 2022).
Use the 1.24 container behind a reserve proxy with the subfolder reverse proxy config from here. The container will run fine when set the DOMAIN section with subfolder in config.json until restart. After restart, access through the proxy / without proxy all shows 404
.
After delete the DOMAIN section in config, all work fine again. The problem also occurs when set url with "-e DOMAIN".