• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Resolved New Plex server, homepage works, but all other files/directories won't.

Reflux8731

New Pleskian
Server operating system version
AlmaLinux 8.9 (Midnight Oncilla)
Plesk version and microupdate number
Version 18.0.59 Update #2
Hello,

I just started using my own dedicated server within a datacenter to host a few of my customers websites. I've done this several times, but I experience an issue that I haven't seen before.
All my customers are running Wordpress websites. I am migrating them from their old host manually. I do this by exporting their website files and exporting the database file. After that I upload the website files to the root directory of their new public_html folder and import the .sql file. After that I change the wp-config file to match the new database (and server) and change the domain records accordingly.

Somehow only just the homepage works, when navigating to another page or an image Plesk returns a 404 server error. I know this error means it can't find the page or image it's navigating to, but I am pretty sure it should work this way. The same happens when navigating through its direct dedicated IP.

What can I try to solve this issue?

Thank you in advance!!
 
Tried solving this yesterday for a few hours, managed to find a fix. It's not Plesk related, but it seems I missed to upload the .htaccess file that contained the necessary data to make the correct 'forwards'.
 
Back
Top