• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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