HTTPS nginx config

Ask the Community Password Manager
1

Hello,

for whatever reason (nothing changed) my bitwarden installation on my local server is not accessable anymore.
I own my domain bitwarden.mydomain.de and this is forwarded to my routers dyndns
all traffice on 443 and 80 are redirected to my server
on this server i have 3 docker container running
1.) SWAG
2.) Nextcloud
3.) bitwarden
each in a seperate container. Nextcloud is accessible but bitwarden not.

here the error log:

2022/12/06 12:01:54 [error] 300#300: 1 bitwarden could not be resolved (3: Host not found), client: 92.117.255.219, server: bitwarden., request: “GET /favicon.ico HTTP/2.0”, host: “bitwarden.mydomain”, referrer: “https:/bitwarden.mydomain.de/”
2022/12/06 12:01:54 [error] 300#300: 1 bitwarden could not be resolved (3: Host not found), client: 92.117.255.219, server: bitwarden., request: “GET /favicon.ico HTTP/2.0”, host: “bitwarden.mydomain”, referrer: “https:/bitwarden.mydomain.de/”
2022/12/06 12:02:07 [error] 300#300: 1 bitwarden could not be resolved (3: Host not found), client: 92.117.255.219, server: bitwarden., request: “GET / HTTP/2.0”, host: “bitwarden.mydomain”
2022/12/06 12:02:07 [error] 300#300: 1 bitwarden could not be resolved (3: Host not found), client: 92.117.255.219, server: bitwarden., request: “GET / HTTP/2.0”, host: “bitwarden.mydomain”
2022/12/06 12:02:07 [error] 300#300: 1 bitwarden could not be resolved (3: Host not found), client: 92.117.255.219, server: bitwarden., request: “GET /favicon.ico HTTP/2.0”, host: “bitwarden.mydomain”, referrer: “https:/bitwarden.mydomain/”
2022/12/06 12:02:07 [error] 300#300: 1 bitwarden could not be resolved (3: Host not found), client: 92.117.255.219, server: bitwarden., request: “GET /favicon.ico HTTP/2.0”, host: "bitwarden.mydomain, referrer: “https:/bitwarden.mydomain”

and there the nginx conf:

server {
listen 443 ssl;
listen [::]:443 ssl;

server_name bitwarden.*;

include /config/nginx/ssl.conf;

client_max_body_size 128M;

location / {
    include /config/nginx/proxy.conf;
    include /config/nginx/resolver.conf;
    set $upstream_app bitwarden;
    set $upstream_port 80;
    set $upstream_proto http;
    proxy_pass $upstream_proto://$upstream_app:$upstream_port;
}

location /admin {
    include /config/nginx/proxy.conf;
    include /config/nginx/resolver.conf;
    set $upstream_app bitwarden;
    set $upstream_port 80;
    set $upstream_proto http;
    proxy_pass $upstream_proto://$upstream_app:$upstream_port;
}

location /notifications/hub {
    include /config/nginx/proxy.conf;
    include /config/nginx/resolver.conf;
    set $upstream_app bitwarden;
    set $upstream_port 3012;
    set $upstream_proto http;
    proxy_pass $upstream_proto://$upstream_app:$upstream_port;
}

location /notifications/hub/negotiate {
    include /config/nginx/proxy.conf;
    include /config/nginx/resolver.conf;
    set $upstream_app bitwarden;
    set $upstream_port 80;
    set $upstream_proto http;
    proxy_pass $upstream_proto://$upstream_app:$upstream_port;
}

}

Thanks for your help

2

here the docker config:

image
image1168×145 7.68 KB

3

Hello @Surfer2010 and welcome to the community,

Sorry to hear you are having issues with your install.
Going from your docker config you provided, it seems that you are running Vaultwarden which is an unofficial 3rd party Bitwarden server, and is not affiliated with the official Bitwarden team.

For further support I gladly welcome you to reach out to support over at the Vaultwarden forums where someone from the community I’m sure will be glad to assist further with your issue.

More info about the differences can be found, in the Vaultwarden wiki or here.
I also have a quick write up on another post you can review.