I tried this migration about a year ago, had issues and rolled it back.  I forgot all about it until today.  I thought I'd give it another go and I still can't get it to work.  I followed the Spaceinvader One video and used the second option.

 

1. Disable letsencrypt

2. Install swag

3. Copy over *.conf files

4. Copy over dns-conf files

5. Profit

 

Unfortunately, everything breaks when I turn on swag. All my subdomains give the following error.

 

Secure Connection Failed

An error occurred during a connection to emby.mydomain.com. PR_END_OF_FILE_ERROR

Error code: PR_END_OF_FILE_ERROR

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.

 

I see this line being repeated over and over and over again in the logs, but it's specific to bitwarden.  I don't see anything for the other subdomains, but they don't work either.

 

nginx: [emerg] "resolver" directive is duplicate in /config/nginx/proxy-confs/bitwarden.subdomain.conf:7

 

If I stop swag and start letsencrypt everything starts working again.

 

Thank you!

Try clearing your browser cache after you have started swag.

Very often the former (and now invalid) certificate is stored in your cache and of course, it does not match the one that swag created.

 

 

Unfortunately that didn't work.  Everything breaks for some reason when using swag and I'm completely lost.

maybe you should take a closer look at that nginx conf file at line 7?

Sounds like there is a duplicate entry and therefor nginx refuses to start (and if ONE subdomain fails due to config problems, nginx wont start and therefor ALL of them are not accessible)

 

 

I copied over the bitwarden.subdomain.conf file from the Let's Encrypt folder so they are the same.  Here is line #7, but it really doesn't mean anything to me.

 

resolver 127.0.0.11 valid=30s;

 

This is the entire file and I don't see anything that's duplicated.  Thanks for the help!

 

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;
  }
}

It doesn't necessarily mean it's duplicate in that file. It means that somewhere there is a duplicate, probably you have it in the resolver.conf file. So just delete line 7 in bitwarden.subdomain.conf and you're good to go.

Edited December 4, 20223 yr by strike

Yep, delete it or comment it out.

 

But it points to 127.0.0.11... this usually does not exist. So there must be another package to  supply the resolver. Or does bitwarden himself hook up this way?

 

Anyway get rid of that line for now and see if the rest is working again, then you still can go after bitwarden.