• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Sporadic Site not Found message for newly installed WordPress pages

darktime

New Pleskian
Hi, when we install a new WordPress site using WP Toolkit, we get sporadic site not found messages every 3 times it loads.

We suspect that this has been happening since the new WP Toolkit update (6.2.15-8047).

What have we tried?

- Installing multiple times
- Change from Apache FPM to Nginx
- Manual installation of WordPress

Log message:
Error 428 GET / HTTP/1.0

It only affects the new pages, all those installed 1-2 weeks ago do not have the problem.

Thank you!
 
This could be caused by the Plesk temporary domain as that requires a security dialog confirmation before the page is shown.
 
Everyone who has not yet visited the website or doesn't accept cookies will see the dialog. If you use a subdomain to a real domain name it should not happen, but if you use a subdomain to a *.plesk.page domain, this will happen, too. It was a necessary tweak for the temporary domains, because too many people were abusing them for phishing.
 
Everyone who has not yet visited the website or doesn't accept cookies will see the dialog. If you use a subdomain to a real domain name it should not happen, but if you use a subdomain to a *.plesk.page domain, this will happen, too. It was a necessary tweak for the temporary domains, because too many people were abusing them for phishing.
Even with a normal domain, the problem occurs.
 
If it's not an issue with the *.plesk.page domain, the website itself might cause it or a DNS configuration that has additional A or AAAA records that do not point to the same website. This could lead to round-robin DNS where every n-th request is answered with a wrong IP address.
 
Back
Top