• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Need help understanding a common 404 error in logs

David Jimenez

Basic Pleskian
I see numerous 404 entries from IP address that are googlebots (e.g., 66.249.69.145). The errors come in pairs and the first one may change but the content is always very similar, the second is always the same:

GET /plugins/like.php?href=http://younggirls-sex.blogspot.com/...ion=like&show_faces=true&share=true&height=35 HTTP/1.1

471#0: *166940 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream

We don't host porn and the first GET always seems to be porn related. Any idea why we get these errors and any way to stop them? I can't block the IP addresses as they are all associated with Google web crawlers. Also, we don't have fast cgi or any cgi enabled in Plesk.
 
Thanks, that makes sense. That also explains the other common 404 for someone looking for wp-login.php...we don't run word press either.
 
I found a solution, but it involves more than a simple Plesk setting. I run our web site through Cloudflare. I can use their page rules to setup a rule such as:

*mydomain.com/plugins/like.php?href=*

and have that rule redirected to a non-existent URL. That way, the scum bag government censors won't be chewing up my bandwidth...on second thought, maybe I should find an IP address for a Chinese government web site and use that.:mad:
 
Back
Top