Resolved Lots of 404 errors for new WordPress sites

[Peter Debik]

Instead of restarting the server it could also help to clear the Nginx cache with the according button in "Apache and nginx settings", because outdated server-side cache may lead to "not found" errors, too.

 

[ccoulibaly]

Hello,
I have the same problem for a week that I try to solve plesk server with 30 domains, when creating a new domain I have 404 errors once out of 5. By restarting the server there will be no impact on old domain and new? Thank you for your help.

 

[Peter Debik]

Hello,
I have the same problem for a week that I try to solve plesk server with 30 domains, when creating a new domain I have 404 errors once out of 5. By restarting the server there will be no impact on old domain and new? Thank you for your help.

If this is happening when creating a new domain, it is very likely that the web server restart interval has not yet expired or that the cpu power of the server is low or that the disk load is high so that configuration processes need much longer to complete than what they should. This can lead to temporary inconsistencies between the physical hosting configuration files and the symbolic links in the /etc/httpd and /etc/nginx vhost directories. The solution in that case can be to either wait at least one restart interval duration or to reload the web server configuration for httpd (apache2) and nginx manually (like # service nginx reload, # service httpd reload). The root cause however should be examined, especially the server load situation and disk i/o load situation.

 

[RenanD]

I'm having the same issue, new domain with WP migrated with Duplicator plugin. At first I thought it was WAF, but it is disabled.

It's weird, sometimes files load just fine (css, js, images, etc), sometimes they don't. It's not consistent, and it's not all of them. Some of the times it even loaded the "default plesk" page instead of the wordpress one.

Using just nginx stops the problem (nginx settings > disable "Proxy mode"), and restarting apache stops the problem.

It looks to me it's related to some apache caching or something like that. Server load was low.