Hi, I have done nslookup, dig, and checked whatsmydns.net. Across the board it shows as being attached to my server’s IP. I run a script that works flawlessly for other domains, but fails out for this one.
Can’t figure it out. Can anyone help me to find more information, please. Which logs can I check to get this resolved? If I try to resolve the domain in my browser, it jumps to https. My script first sets up a nginx config file for port 80, then issues a cert, then adjusts the nginx config to listen on port 443, and port 80 only to redirect to https.
This isn’t making sense to me! The configuration file has no port 443 in it, and yet I’m being redirected. If I look in /etc/letsencrypt/live, there’s no folder for this specific domain. I see no reason why a bleed over would be happening from another nginx vhost config file when all others are specific to their respective domain.
Any ideas? Does this issue sound related, or are they separate?
I use this command:
/opt/letsencrypt/letsencrypt-auto certonly -a webroot --webroot-path=/var/www/users/thedomain/public -d thedomain.xyz