Closed evakq8r closed 3 years ago
Fixed myself... turns out the configs between SWAG and NPM are defined slightly differently.
In SWAG, the bitwarden-nginx port is pointed to 8080, however in NPM it needed to be pointed to my custom port that was defined during the docker-compose...
Now it works without issue!
Host: Unraid 6.9.1 Containers affected: NginxProxyManager and bitwarden-nginx
Hi there,
I've recently migrated my reverse proxy from linuxserver/swag to jlesage/nginx-proxy-manager, and have managed to get all existing containers to work... except Bitwarden.
I'm using the official Bitwarden install rather than bitwardenrs as I had several issues setting up the rs version. I've used the Protected Endpoint.conf file in the ibracorp/authelia setup instructions and populated the relevant fields. I can get to Authelia, authenticate, then redirected to the Bitwarden instance, but trying to log in just throws 'unexpected error'. If I move the proxy manager from NPM back to SWAG, Bitwarden works fine... which makes me think it's a config setting in NPM that's causing Bitwarden to fail.
linuxserver/swag file for Bitwarden:
jlesage/nginx-proxy-manager file for NPM:
I've also tried posting the same issue here: https://forums.unraid.net/topic/76460-support-djoss-nginx-proxy-manager/?do=findComment&comment=961466, but haven't got any bites as yet.
I'm hoping it's something obvious, but I cannot for the life of me work out why this works with SWAG and not with NPM with identical configs. I've even transplanted the SWAG config into NPM under the Advanced Tab, as well as stripping down the config to the bare minimum (without Authelia) and it still fails.
Any help would be appreciated. Thanks!