VKzHs*KzAnpAxp*QdBW8

unRaid 6.7.2 First time unRaid user, currently on a test key however I've always wanted to host bitwarden myself. I've been watching and following this guide from u/spaceinvaderone however while he uses Nextcloud and sonarr as an example, I'm using bitwarden. Most things go to plan, Let's encrypt give my domain my own cert (Although I already own a wildcard so it would be good to just use that one if I can? however when I go to bitwarden.mydomain.com I get the ngix landing page for Let's encrypt which falls under appdata\letsencrypt\www\index.html It appears while everything works correctly with Let's Encrypt and the domain, it is not forwarding the domain to the correct port of bitwarden. I tried to edit the /appdata/letsencrypt/nginx/proxy-confs/bitwarden.subdomain.conf file with: server { listen 443; 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 / { include /config/nginx/proxy.conf; proxy_pass http://172.20.55.109:8080; } location /notifications/hub { include /config/nginx/proxy.conf; proxy_pass http://172.20.55.109:8080; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; } location /notifications/hub/negotiate { include /config/nginx/proxy.conf; proxy_pass http://172.20.55.109:8080; } } without luck, even after rebooting both the Let's Encrypt docker and also the server itself, this page shows up externally on my mobile when connected via LTE so the pfsense rules are working as they should, something isn't forwarding correctly. Can anyone see what's going wrong here? This happens with both nextcloud AND bitwarden, therefore it seems there is an issue with ngix within Let's Encrypt. Thinking there was an issue, I reinstalled unRaid however ran into the same issue. 1.webp 2.webp 3.webp 4.webp