None of the changes we made should/could have affected your server this way.
If you totally stop nginx, is anything listening on 80?
sudo systemctl stop nginx
nginx -t
sudo ss -tlnp | grep ":80"LISTEN 0 128 :80 : users:((“nginx”,pid=25991,fd=6),(“nginx”,pid=25990,fd=6),(“nginx”,pid=25989,fd=6),(“nginx”,pid=25988,fd=6),(“nginx”,pid=25976,fd=6))
LISTEN 0 128 :::80 ::: users:((“nginx”,pid=25991,fd=7),(“nginx”,pid=25990,fd=7),(“nginx”,pid=25989,fd=7),(“nginx”,pid=25988,fd=7),(“nginx”,pid=25976,fd=7))
The odd thing is that my sites are still functioning when they should be stopped.
So nginx isn’t stopping, eh. That’s unusual.
Are you using some kind of special management stack like Bitnami or something to manage nginx, not via systemd?
You could try kill -9 the processes or something, but atm I’m not in a position to give good advice without understanding how your server was setup.
I am not. Well, shoot. Hmmm.
Welp. I got it to stop listening and start back up.
Back to square one.
I think I fixed it. I believe Certbot added an additional server block to that site and it was messing things up.
Thanks so much for your help man!
Woot!
When I ran
$ sudo certbot renew --dry-run
That seemed to work great.
So, I think all is well!
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.