• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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