Related

wordpress Twitter Feed is not displays on Digital ocean host Question Question
How can I fix this ERROR: Site wordpress does not exist! ? Question Question

Question

Apache keeps going offline

Posted November 25, 2021 82 views
UbuntuApacheWordPress

I’ve setup a new Wordpress droplet, and I believe I’ve got Certbot working fine too.

However, I find that after a while (15+ minutes), if I go to the site in my browser I get a “This site can’t be reached / DNSPROBEFINISHED_NXDOMAIN” error in Chrome, but then it comes online after a few seconds.

I’ve checked /var/log/apache2/error.log and found the following…

[Thu Nov 25 13:42:11.305444 2021] [mpm_prefork:notice] [pid 846] AH00169: caught SIGTERM, shutting down
[Thu Nov 25 13:43:48.303502 2021] [mpm_prefork:notice] [pid 865] AH00163: Apache/2.4.41 (Ubuntu) OpenSSL/1.1.1f configured -- resuming normal operations

I’ve also used the following command to see if anything is killing Apache, but I’m getting no results…

grep -i kill /var/log/syslog | grep apache

Any help much appreciated!

Add a comment
notpatrick
By:
notpatrick

Related

wordpress Twitter Feed is not displays on Digital ocean host Question Question
How can I fix this ERROR: Site wordpress does not exist! ? Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer
KFSys November 26, 2021

Hi @notpatrick,

I think the issue was with your DNS. If you just changed your DNS it can take up to 48 hours for it fully propagate.

Are you experiencing the issue now? Wait for your DNS to stop propagating and see if this is still being experienced.

Reply Report
  • notpatrick November 28, 2021

    Thanks so much - it does seem that it took 24-48 to sort itself out and is now working fine without anything else done at my end.

    Much appreciated!

    Reply Report
    • KFSys December 2, 2021

      Hi @notpatrick,

      I’m glad to be of help. Yes, usually the errors you’ve experienced is when your domain is not pinging or not pinging to where it is suppose to, in 99% of the cases it’s DNS related.

      Reply Report

Related

Looking for something else?

Ask a new question Search for more help