• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Error - Help Please - primary

Dodo

New Pleskian
Bonjour
Depuis quelques jours je trouve cette erreur de code très régulièrement.
Vous me aider Pourriez il vous plait? Avez-vous eu ce problème? Comment le réparer? Merci beaucoup pour votre aide!

24010 # 0: * 31233 FastCGI envoyé dans stderr: "Script principal inconnu" lors de la lecture de l'en-tête de réponse en amont
 
It is not clear from the log entry whether the script in question is actually one that ought to exist or one that is needed for proper website operations. It could also be the case that a bad bot is trying to check on common scripts or security flaws. Another very common reason for the error are faulty rewrite rules in your .htaccess file. I have also seen shop systems where search engine friendly urls don't resolve/rewrite to the correct shop pages. It's not really easy to fix, because the name of the script is not mentioned in the error messages. You need to look at the access_log file to at the given time to get an idea what is happening, then follow the bread crumbs to find out why something is missing that is expected to be there.
 
Back
Top