Recent content by Patrick1

Same problem here. All of a sudden this error appears.

After the last update i also get the following error that the rules cant be updated; Fout: Het bijwerken van de ModSecurity-regelset is mislukt: modsecurity_ctl failed: gpg: key 4520AFA9: "Atomicorp (Atomicorp Official Signing Key) <[email protected]>" not changed gpg: Total number...

Hi Frono, I haven't found a solution to this problem yet. I am routing my email trough another server capable of handling DKIM and retired that plesk server. We still have plesk servers but not for serious mail. It seems that this issue has no priority for parallels and they are stuck in the...

Found it. Like i said, the real problem is that all calls to apache come from nginx. To make use of the .htaccess again do the following in .htaccess; Deny from All SetEnvIF X-Forwarded-For "1.2.3.4" AllowIP SetEnvIF X-Forwarded-For "2.3.4.5" AllowIP Allow from env=AllowIP Allow from 1.2.3.4...

I figured out where the real problem is, its is because nginx talks to apache, so apache thinks that all requests are coming from nginx. I found out that X-real-IP is forwared to apache, but i cant make use of that in .htaccess. So, how can i still make use of .htaccess files ? Patrick

Dear readers, I searched the web endlessly but cant seem to figure this out. I have several customers with wordpress domains. I want to protect these directory's with Nginx on a plesk 12 machine. I thought something simple will do, but i just spent all sunday afternoon getting it to work (what...

Dear Igor, Thanks for your reply. I am aware that protocol=2 is not correct, it crashes psa-pc-remote. However, with psa crashed DKIM works correct, but then i loose the functionality of plesk. (i just mentioned it for clarity that DKIM is setup right) I have for both a separate key of course...

Dear Reader, I am having trouble setting this up. If i set DKIM up together with plesk SPF and Domainkeys its not working. All checks come back as fail, even though the logfiles say its fine. Oct 19 20:04:27 p2 postfix/cleanup[6818]: 33B802BC00BA...