After deleting a user account, nginx stopped restarting

Community Support System
1

Hi,

Earlier today I had issues with the email system due to lack of storage in my VPS. So, to fix this I started removing old accounts, with all they included, to free some space. But after the second user removal, the panel stopped working and the loading animation got stuck, making the panel inaccesible. After that I restarted the VPS through the VPS panel on the provider website, but the nginx service is red now and the domains now don’t open in the browser.

Now I’ve tried deleting other user, and the loading animation got stuck again.
Tried removing only a domain, and the same, stuck in the animation.

Where can I check for the logs of what’s going on right now? Or is there any post I have missed while looking for solutions?

Thanks in advance for your time!

2

Hi @ArkeyWave,

Show the output of:

systemctl status nginx
nginx -t
df -h
3

Hi, here they are

Nginx status

image
image1095×452 41.2 KB

nginx -t (same domains as above)

image
image824×88 2.83 KB

df -h
image

Thank you

4

Please copy and paste the outputs, don’t paste screenshots, they are hard to read and don’t show all the lines.

5

Also, show the output of:

dig r3.o.lencr.org

6

Alright, here is in code

Nginx status

root@sv:~# systemctl status nginx
● nginx.service - nginx - high performance web server
   Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
   Active: failed (Result: timeout) since Thu 2023-12-14 12:31:05 -05; 1min 59s ago
     Docs: https://nginx.org/en/docs/
  Process: 4716 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=killed, signal=TERM)

Dec 14 12:29:35 sv.ventureops.agency systemd[1]: Starting nginx - high performance web server...
Dec 14 12:29:55 sv.ventureops.agency nginx[4716]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/630cafe/conf/web/630.cafe/ssl/630.cafe.pem"
Dec 14 12:30:15 sv.ventureops.agency nginx[4716]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/ArkeyWave/conf/web/arkeywave.com/ssl/arkeywave.com.pem"
Dec 14 12:30:35 sv.ventureops.agency nginx[4716]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/theepoxyguy/conf/web/buy.theepoxyguy.net/ssl/buy.theepoxyguy.net.pem"
Dec 14 12:30:55 sv.ventureops.agency nginx[4716]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/marcafab/conf/web/cafedelvalle.marcafab.com/ssl/cafedelvalle.marcafab.com.pem"
Dec 14 12:31:05 sv.ventureops.agency systemd[1]: nginx.service: Start operation timed out. Terminating.
Dec 14 12:31:05 sv.ventureops.agency systemd[1]: nginx.service: Control process exited, code=killed, status=15/TERM
Dec 14 12:31:05 sv.ventureops.agency systemd[1]: nginx.service: Failed with result 'timeout'.
Dec 14 12:31:05 sv.ventureops.agency systemd[1]: Failed to start nginx - high performance web server.

nginx -t

root@sv:~# nginx -t
nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/630cafe/conf/web/630.cafe/ssl/630.cafe.pem"
nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/ArkeyWave/conf/web/arkeywave.com/ssl/arkeywave.com.pem"
nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/theepoxyguy/conf/web/buy.theepoxyguy.net/ssl/buy.theepoxyguy.net.pem"
nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/marcafab/conf/web/cafedelvalle.marcafab.com/ssl/cafedelvalle.marcafab.com.pem"
nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/marcafab/conf/web/carlosoliva.marcafab.com/ssl/carlosoliva.marcafab.com.pem"

df -h

Filesystem      Size  Used Avail Use% Mounted on
udev             16G     0   16G   0% /dev
tmpfs           3.2G  8.6M  3.2G   1% /run
/dev/sda1       473G  422G   27G  95% /
tmpfs            16G  1.2M   16G   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs            16G     0   16G   0% /sys/fs/cgroup
tmpfs           3.2G     0  3.2G   0% /run/user/0

also now about dig r3.o.lencr.org

root@sv:~# dig r3.o.lencr.org
  
; <<>> DiG 9.11.5-P4-5.1+deb10u9-Debian <<>> r3.o.lencr.org
;; global options: +cmd
;; connection timed out; no servers could be reached
7

And that is your problem, you can’t resolve the address. What are the name servers you are using?

cat /etc/resolv.conf
grep resolver /etc/nginx/nginx.conf
8

well

root@sv:~# cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4

root@sv:~# grep resolver /etc/nginx/nginx.conf
        resolver                        1.0.0.1 8.8.4.4 1.1.1.1 8.8.8.8 valid=300s ipv6=off;
        resolver_timeout                5s;

these records are by default and haven’t been modified recently, it’s odd

9

For some reason you can’t resolve:

Try to resolve r3.o.lencr.org and for example google.com with all of them:


dig @8.8.8.8 r3.o.lencr.org +nodnssec +short -4
dig @8.8.4.4 r3.o.lencr.org +nodnssec +short -4
dig @1.1.1.1 r3.o.lencr.org +nodnssec +short -4
dig @1.0.0.1 r3.o.lencr.org +nodnssec +short -4

dig @8.8.8.8 google.com +nodnssec +short -4
dig @8.8.4.4 google.com +nodnssec +short -4
dig @1.1.1.1 google.com +nodnssec +short -4
dig @1.0.0.1 google.com +nodnssec +short -4

If you are using bind with Hestia, try this too:

dig @127.0.0.1 r3.o.lencr.org +nodnssec +short -4
dig @127.0.0.1 google.com +nodnssec +short -4

As your server filled the disk… did you try to reboot it?

10

Here is the output for the commands

root@sv:~# dig @8.8.8.8 r3.o.lencr.org +nodnssec +short -4


; <<>> DiG 9.11.5-P4-5.1+deb10u9-Debian <<>> @8.8.8.8 r3.o.lencr.org +nodnssec +short -4
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
root@sv:~#
root@sv:~# dig @8.8.4.4 r3.o.lencr.org +nodnssec +short -4

; <<>> DiG 9.11.5-P4-5.1+deb10u9-Debian <<>> @8.8.4.4 r3.o.lencr.org +nodnssec +short -4
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
root@sv:~# dig @1.1.1.1 r3.o.lencr.org +nodnssec +short -4
o.lencr.edgesuite.net.
a1887.dscq.akamai.net.
23.35.98.57
23.35.98.41
root@sv:~# dig @1.0.0.1 r3.o.lencr.org +nodnssec +short -4
o.lencr.edgesuite.net.
a1887.dscq.akamai.net.
104.98.118.155
root@sv:~# dig @8.8.8.8 google.com +nodnssec +short -4
142.250.217.78
root@sv:~# dig @8.8.4.4 google.com +nodnssec +short -4
142.250.217.78
root@sv:~# dig @1.1.1.1 google.com +nodnssec +short -4
142.251.215.238
root@sv:~# dig @1.0.0.1 google.com +nodnssec +short -4
142.251.215.238
root@sv:~# dig @127.0.0.1 r3.o.lencr.org +nodnssec +short -4
root@sv:~# dig @127.0.0.1 google.com +nodnssec +short -4
142.250.217.110

I’ve been rebooting the server repeteadly, but doesn’t seem to fix anything :confused:

11

For some weird reason, google name servers dont work to resolve r3.o.lencr.org.

What I would do:

Edit /etc/resolv.conf and change it to:

nameserver 127.0.0.1
nameserver 8.8.8.8
nameserver 8.8.4.4

Note: don’t use 1.1.1.1 or 1.0.0.1 in resolv.conf or you will have problems with Exim and Spamhaus dnsbl.

Edit /etc/nginx/nginx.conf and change this line:

resolver                        1.0.0.1 8.8.4.4 1.1.1.1 8.8.8.8 valid=300s ipv6=off;

to this:

resolver                        127.0.0.1 1.0.0.1 1.1.1.1 valid=300s ipv6=off;

Once done, restart nginx:

systemctl restart nginx

1 Like
12

This worked!
Thank you very much @sahsanu, is there any recommended documentation about this topic I should be reading? That might help me in a later scenario.

btw, success status code

root@sv:~# systemctl restart nginx
root@sv:~# systemctl status nginx
● nginx.service - nginx - high performance web server
   Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2023-12-14 13:14:56 -05; 6s ago
     Docs: https://nginx.org/en/docs/
  Process: 11231 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=0/SUCCESS)
 Main PID: 11232 (nginx)
    Tasks: 11 (limit: 4915)
   Memory: 25.1M
   CGroup: /system.slice/nginx.service
           ├─11232 nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf
           ├─11233 nginx: worker process
           ├─11234 nginx: worker process
           ├─11235 nginx: worker process
           ├─11236 nginx: worker process
           ├─11237 nginx: worker process
           ├─11238 nginx: worker process
           ├─11239 nginx: worker process
           ├─11240 nginx: worker process
           ├─11241 nginx: cache manager process
           └─11242 nginx: cache loader process

Dec 14 13:14:55 sv.ventureops.agency systemd[1]: Starting nginx - high performance web server...        
Dec 14 13:14:56 sv.ventureops.agency systemd[1]: Started nginx - high performance web server.
13

EDIT sorry I didn’t see that your own nameserver 127.0.0.1 doesn’t resolve r3.o.lencr.org too.

resolv.conf should remain with google nameservers as seems they are resolving other domains.

nameserver 8.8.8.8
nameserver 8.8.4.4

and nginx.conf should have only cloudflare name servers:

resolver                        1.0.0.1 1.1.1.1 valid=300s ipv6=off;
1 Like
14

Alright, made this update and the service is still up and running. Thanks for the fix!

1 Like
15

I’m glad it works, but it is something really really weird that you can’t resolve the domain neither with google nor with your own name server…

16

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.