Patb

yes, that is correct. I can't connect to http://192.168.2.242:8080/vnc.html?autoconnect=true here is the advanced configuration

I'm still trying to make this work without any success. I decided to try to make it work with Chromium just to try to get it working and then I would go from there. Here is my configuration for Chromium I've been trying for days to get this resolved and I can't understand what I'm doing wrong.

I am trying to get OpenVPN-Client working and I can't seem to get the port passthrough to work. As can be seen, I am not using the default port for SABnzbd (8081 vs 8080). When I make the changes to pass it through it seems to no longer take my port mapping into account and seems to use the defaults (notice 8080 instead of 8081 below) even though I didn't change the port when I changed the network type. Any advice or assistance would be appreciated. Thanks

ok, this is strange, I renamed the container to bitwarden (lower case b) and it now works... Thanks

They are both in a network called "proxynet" and I verified that the names match. Still no success.

Follow up to my post from yesterday. Still getting a 502 Bad Gateway for Bitwarden. I forced update on both Letsencrypt and Bitwarden and still nothing. I am able to connect by using the IP address (in my case: http://192.168.2.242:8343/#/) but this is of limited value as I need to be able to connect to bitwarden remotely. I tried to change the bitwarden in the configuration file to upper case B with no change. Below is the conf I'm using for Bitwarden, I have no problems with any other servers at this time. # make sure that your dns has a cname set for bitwarden and that your bitwarden container is not using a base url server { listen 443 ssl; listen [::]:443 ssl; server_name bitwarden.*; include /config/nginx/ssl.conf; client_max_body_size 128M; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_bitwarden bitwarden; proxy_pass http://$upstream_bitwarden:80; } location /notifications/hub { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_bitwarden bitwarden; proxy_pass http://$upstream_bitwarden:80; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; } location /notifications/hub/negotiate { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_bitwarden bitwarden; proxy_pass http://$upstream_bitwarden:80; } } As stated above, I continue to get the following errors when I try to connect 2019/07/18 22:25:47 [error] 380#380: *1 bitwarden could not be resolved (3: Host not found), client: 192.168.2.1, server: bitwarden.*, request: "GET /favicon.ico HTTP/2.0", host: "bitwarden.XXX.com", referrer: "https://bitwarden.XXX.com/"

I'm starting to loose my mind. I had this working before but my unraid BTRFS cache drive was corrupted and I'm not able to get my bitwarden working with letsencrypt anymore. I'm using the default configuration in letsencrypt and I didn't do anything special with Bitwarden but I keep getting 502 Bad Gateway. I get the following error in the nginx error.log 2019/07/17 22:00:59 [error] 371#371: *2 bitwarden could not be resolved (3: Host not found), client: 192.168.2.1, server: bitwarden.*, request: "GET /favicon.ico HTTP/2.0", host: "bitwarden.xxx.com", referrer: "https://bitwarden.xxx.com/" I have both letsencrypt and bitwarden on the same network "proxynet". I have other services like NextCloud and phpmyadmin set up and working correctly but I can't seem to get bitwarden to work anymore. Thanks.