• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Weird 404 not found errors

Edi Duluman

Basic Pleskian
Hello guys ! I have a client who's running Smarty just fine on one of his old servers.
He decided to do a move to test the perfomance on the new server and I'm having this annoying problem which I can't really figure out how to solve.

Here you have two requests, first one ends up in 404 Not Found and second one works fine.

  1. http://nakenpraten.com/external_c/dp/%%10/103/10379A4F%%form_QuickSearch.js
  2. http://nakenpraten.com/external_c/dp/%%CA/CAD/CADB2AD9%%menu-line-bottom.style.css

I don't understand what's the difference between these two ?

The files exist at the following paths:

  1. /external_c/dp/%25%2510/103/10379A4F%25%25form_QuickSearch.js
  2. /external_c/dp/%%CA/CAD/CADB2AD9%%menu-line-bottom.style.css

They work just fine on the old server... and I'm really struggling to understand what's different here.
Do you have any idea ?

Sometimes I get some errors from nginx access like this:

1253#0: *1781 open() "/var/www/vhosts/nakenpraten.com/httpdocs/external_c/dp/%DE/DE6/DE65EBD5%form_SignUp.js" failed (2: No such file or directory)

I don't understand why nginx sees %25%25 ( originally %% ) as only one %.

Print of the logs:

S6MySku.png



I havel literally no idea..
 
Last edited:
I have found out that if I disable Smart static files processing for the domains that have trouble with this in Apache & Nginx Settings after few minutes, if you refresh couple of times, the errors dissapear. It's very strange. Before finding the workaround, there were files that sometimes were loading, sometimes they were returning a 404. Don't understand why.
 
Back
Top