Issue it appears plesk is interjecting random 404 pages instead of my content

[DSCPM]

I'm running Obsidian 18.0.24 on AWS Lightsail (Ubuntu 18.04.4). I'm getting strange 404 errors and blank pages on about 20% of my page loads on one of my sites. It's almost as if Plesk intercepts a page request and returns this random stuff. Here are the logs and a screenshot of the page source when the 404 appears. Any help is appreciated. Thank you!

 

[DSCPM]

Here is the source of the 404 that appears. Upon refresh, the page loads just fine. I can refresh it 10 times before it 404's again,

 

[Martin.H]

Have you tried:

- activating Nginx to serve static content?
- checking if the User does have the rights to read the files?

 

[Bitpalast]

- Is DNS consistent, meaning that you don't use round robin so that sometimes a request might not be sent to your server but to somewhere else where the file does not exist?
- Is the website using rewrite rules? In that case you will need to exactly follow what it is doing with a request. Verify that the route leads to a valid file that is actually delivered.

 

[peterindexed]

I experience the same problem.

On fresh empty sites I get random 404 on same request both on static and script files. When I turn off Nginx as proxy to apache2 they dissapear.

in proxy_error_log:
2020/12/18 13:45:21 [error] 1600#0: *155262 openat() "/var/www/vhosts/*removed*/httpdocs/index.html" failed (2: No such file or directory), client: *removed*, server: *removed*, request: "GET / HTTP/2.0", upstream: "https://*removed*:7081/", host: "*removed*

This happens only on new sites and not existing.

 

[Bitpalast]

Please follow the guide in this article to mitigate the issue:

Site shows 404 not found on Plesk server: nginx error: index.html is not found (2: No such file or directory)

Applicable to: Plesk for Linux Symptoms Domain is inaccessible with 404 error.Rewrite rules specified in /var/www/vhosts/example.com/httpdocs/.htaccess file do not work. FPM application served...

support.plesk.com

 

[tasz]

I think this is issue of 2 ips provided AWS like internal ip might be inserted in <domain>/conf/httpd.conf and <domain>/conf/nginx.conf
<VirtualHost xxx.xxx.xxx.xxx:7081 >
change it your public ip and problem will be solved.