Rebooted VPS, now websites are not working?

[sahsanu]

All ok.

You could try to reboot again but before doing that, show the output of these commands:

systemctl restart nginx ; sleep 5 ; ls -l /run/nginx.pid  ; systemctl status nginx --no-pager -l

[lavishsphere]

@sahsanu

systemctl restart nginx ; sleep 5 ; ls -l /run/nginx.pid  ; systemctl status nginx --no-pager -l

root@server:~# systemctl restart nginx ; sleep 5 ; ls -l /run/nginx.pid  ; systemctl status nginx --no-pager -l
-rw-r--r-- 1 root root 8 Jun 15 02:29 /run/nginx.pid
● nginx.service - nginx - high performance web server
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled; preset: enabled)
     Active: active (running) since Sat 2024-06-15 02:29:15 PDT; 5s ago
       Docs: https://nginx.org/en/docs/
    Process: 1190886 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=0/SUCCESS)
   Main PID: 1190919 (nginx)
      Tasks: 4 (limit: 7103)
     Memory: 6.5M
        CPU: 105ms
     CGroup: /system.slice/nginx.service
             ├─1190919 "nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf"
             ├─1190920 "nginx: worker process"
             ├─1190921 "nginx: cache manager process"
             └─1190922 "nginx: cache loader process"

Jun 15 02:29:15 server.uniplex.xyz systemd[1]: Starting nginx.service - nginx - high performance web server...
Jun 15 02:29:15 server.uniplex.xyz systemd[1]: nginx.service: Can't open PID file /run/nginx.pid (yet?) after start: No such file or directory
Jun 15 02:29:15 server.uniplex.xyz systemd[1]: Started nginx.service - nginx - high performance web server.
root@server:~# 

Looks like there’s a problem here: Jun 15 02:29:15 server.uniplex.xyz systemd[1]: nginx.service: Can’t open PID file /run/nginx.pid (yet?) after start: No such file or directory

[sahsanu]

@lavishsphere

Can’t open PID file /run/nginx.pid (yet?)

But it creates it, that is the reason I told to show this command ls -l /run/nginx.pid

Again, I see no problem there, that’s pretty weird, try to reboot the VPS, try to access again your site and check the nginx logs /var/log/nginx/error.log and /var/log/nginx/domains/YourDomain.error.log

[lavishsphere]

@sahsanu

/var/log/nginx/error.log

Rebooted VPS to no luck, log files still showing the SSL stuff for the other domains. That’s about it. I have a hunch it has something to do with PHP but idk how it would relate to apache and nginx. I actually rebooted it twice, the first time I ran into an issue with none of the PHP on my sites working so like sites solely PHP were down but HTML was up. So I took another shot and did another reboot, and well it clearly didn’t like that and more stuff broke or something. Looking back, shouldn’t have rebooted the second time and tried to deal with the PHP issue instead…

[sahsanu]

Pretty weird. Just in case, did you add something to /etc/hosts ?

[lavishsphere]

@sahsanu

/etc/hosts

Nope not that I am aware of, but I’ve been able to fix the issues right now by deleting each domain and re-adding them. It’s a pain and something I certainly don’t want to do again as I scale up well I guess I shouldn’t reboot again.

[sahsanu]

Instead of delete and re-add, you could try to rebuild them:

v-rebuild-web-domain USER DOMAIN yes

[lavishsphere]

Nevermind, it didn’t fix it, I just thought the removal of the SSL and redirecting to https meant if I generated a SSL certificate, it would work. I’m gonna take backups and reinstall tomorrow. Thanks for your help. Sorry for the distuabance.

[lavishsphere]

Magically started working after I turned off the VPS for 12 hours to go sleep and turned it back on today to check and then reinstall. welp its magical.

[sahsanu]

I’m glad it works again, but it is strange, maybe some hardware is not working fine…

[molero.renan]

Once, something similar happened to me. Incredibly, it was my firewall automatically blocking the IP.

If this happens again, I recommend checking the status of the following services:

service apache2 status
service nginx status

If both are running correctly, try temporarily pausing iptables:

service iptables stop

Test again. If everything works, you’ve identified the problem. In that case, add your internal IPs to the whitelist or investigate why the block occurred.