Issue 404 Server Error on slugs

[Martin_2352]

Server operating system version

Ubuntu 22.04

Plesk version and microupdate number

18.0.62 Update Nr. 2

Hallo,

I updated a plesk installation with about 20 Websites (joomla 3.9 / wordpress) from Ubuntu 18.04 to 22.04.

Unfortunately I get an error 404 on slugs of every website. The websites are partly an old joomla 3.9 but also current wordpress versions.
Only a freshly added website works fine. I tried the

plesk repair

command, but it didn't help.

An example in the logs is:

2097909#0: *25107 open() "/var/www/vhosts/URL/websites/URL/slug" failed (2: No such file or directory)                nginx-Fehler

Do you know how I can fix this? I don't think there is any data missing as the error message indicates because a full backup restore was performed.

Thanks!

 

[Sebahat.hadzhi]

From what I understand, the issue occurs only on the internal pages. Please try adding an .htaccess file for WordPress-based websites following this guide. If that sorts the issue, you can find the default .htaccess rule for Joomla here.

 

[Martin_2352]

Yes it only occours on internal pages, the index page works fine.
I tried both guides but unfortunately it didn't help. The content of the .htaccess in the WP guide was already present in the .htaccess file of the website. I also replaced the entire content but it didn't help.

 

[mow]

Waaait ... that's an nginx error. htaccess won't help there because nginx doesn't touch htaccess.
Were those websites mistakenly set to nginx only instead of nginx proxy to apache?

 

[Martin_2352]

Waaait ... that's an nginx error. htaccess won't help there because nginx doesn't touch htaccess.
Were those websites mistakenly set to nginx only instead of nginx proxy to apache?

I had to disable the nginx "proxy mode" in "Apache and nginx" or I got a

Server Error 502 Bad Gateway

on the index page

 

[pleskpanel]

If you're using Nginx-only (no proxying to Apache) then you'll likely want to use either the the single domain or all domain versions of this:

https://support.plesk.com/hc/en-us/articles/12377889048855-After-switching-a-website-to-FPM-served-by-nginx-in-Plesk-it-fails-to-load-with-404-Not-Found-on-all-pages-except-start-page

Alternatively you could turn off custom error documents and that should do it too.

 

[Martin_2352]

If I turn off custom error documents and activate proxy mode, I get "502 Bad Gateway nginx" (?)
If I then activate proxy mode again and click on slugs, I get "404 Not Found nginx"

The link solved the issue both for joomla and wordpress!

Thank you very much!

 

[pleskpanel]

You're welcome!

It's not directly a Plesk issue per say but they could add better support/documentation for handling CMS platforms on Nginx-only scenarios which would shortcut the aggravation that you went through.

Sebahat's solution would work if requests were proxied to Apache while Mow astutely observed that this was a Nginux-only configuration which requires some additional steps to get WordPress/Joomla working.