I'm having some issues getting Swag to work correctly and I don't even know where to start. Let's Encrypt was obviously depreciated, but it worked until a few days ago when it failed to renew. I tried the Let's Encrypt -> Swag migration and had all sorts of issues. So I started all over again and installed Swag from scratch.

My problem is that even though my certificates renewed, I just get the "Welcome to your SWAG instance" page and never make it to either of my apps (Emby or Bitwarden) when I'm on the same network or not using the custom .conf files from the Let's Encrypt install, but when I'm outside my LAN, I get the ERR_CONNECTION_REFUSED message when using the .conf files. So I'm thinking this is an issue with the .conf files, but I'm not sure how to fix them.

I see this error in the log, but I'm not sure what it means.

2025/08/13 07:56:44 [emerg] 941#941: "resolver" directive is duplicate in /config/nginx/proxy-confs/bitwarden.subdomain.conf:7

2025/08/13 07:56:45 [emerg] 950#950: "resolver" directive is duplicate in /config/nginx/proxy-confs/bitwarden.subdomain.conf:7

=========================================================

I copied over all the settings from my Let's Encrypt instance.

Network Type: Custom : proxynet

Console Shell Command: Shell
Privileged: On

WebUI: 1443
Port 80: 180

Port 443: 1443
Validation: http
DNSPLUGIN: cloudflare
ONLY_SUMDOMAINS: true
Staging: false

==========================================================

I also copied my .config files from my old Let's Encrypt folder and put them in the proxy-confs folder.

resolver 127.0.0.11 valid=30s;

upstream bitwarden {

server bitwardenrs:80;

}

server {

listen 443 ssl;

server_name bitwarden.*;

include /config/nginx/ssl.conf;

client_max_body_size 128M;

location / {

proxy_pass http://bitwarden;

proxy_set_header Host $host;

proxy_set_header X-Real-IP $remote_addr;

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

proxy_set_header X-Forwarded-Proto $scheme;

}

location /notifications/hub {

proxy_pass http://bitwarden;

proxy_set_header Upgrade $http_upgrade;

proxy_set_header Connection "upgrade";

}

location /notifications/hub/negotiate {

proxy_pass http://bitwarden;

}

}

==========================================================

I could really use some help because at this point, everything is completely broken. Thank you!

Edited August 13, 2025Aug 13 by Spyderturbo007

One of the many reasons I moved to nginx proxy manager and haven't looked back

1 hour ago, Michael_P said:

One of the many reasons I moved to nginx proxy manager and haven't looked back

Wow, it took literally 10 minutes to get that working. It's about 1000x easier than Swag. Looks like I can go ahead and blow away Swag.

Thank you so much for your help!