• 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.

Primary script unknown --> File not found

rgruyters

Basic Pleskian
After upgrading to 12.5.30 I noticed that I have some issues with sites that don't have an index.html or index.php in the httpdocs folder. There is a ".htaccess" with a rewrite to a sub-folder.

The following message is displayed in the (Apache) error_log:

Code:
[Tue Nov 17 11:22:42.753581 2015] [proxy_fcgi:error] [pid 32559:tid 139724832347904] [client 80.79.108.129:34476] AH01071: Got error 'Primary script unknown\n'

In the browser I see a "File not found." message.

FPM is configured to served by Apache.

I know it is possible to serve it through NGINX, but I want to give users the freedom do this by themselves. (And it used to work)
 
Are you running fail2ban by any chance? Reason I ask is I've been chasing the same error and found multiple entries in my fail2ban log with times that tally.

2015-11-18 19:55:04,295 fail2ban.filter [688]: WARNING Error decoding line from '/var/log/plesk/panel.log' with 'ANSI_X3.4-1968'. Consider setting logencoding=utf-8 (or another appropriate encoding) for this jail. Continuing to process line ignoring invalid characters: 'rm: cannot remove \xe2\x80\x98/var/www/vhosts/********.**/httpdocs/img/apps/poa-box.gif\xe2\x80\x99: Permission denied\n'

Watching this thread for any answers.

edit

If it is fail2ban and you see the same errors with the panel log then via ssh:

# fail2ban-client set plesk-panel logencoding utf-8

Since setting this I've seen no more errors, but need to run a couple of days to be 100%
 
Last edited:
I started getting the error again after restarting the fail2ban service. Seemed to me the config was being rewritten so I went hunting for the config (on Ubuntu 14.04LTS). I found /etc/fail2ban/jail.d/plesk.conf and added a line there to make the [plesk-panel] section read:

[plesk-panel]

enabled = true
action = iptables-multiport[name="plesk-login", port="8880,8443"]
filter = plesk-panel
logpath = /var/log/plesk/panel.log
logencoding=utf-8
maxretry = 5

Your locations may be different (depends on the OS) but the edit should be the same. Zero errors now after several restarts.
 
Last edited:
Back
Top