• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:
    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  1. D

    Resolved Mod_security integration

    If anyone should wonder, I solved it by placing a file badbots.conf in: /etc/httpd/conf/modsecurity.d/rules/tortix Containing for instance: SecRule REQUEST_HEADERS:User-Agent "AhrefsBot" \ "id:'300002',phase:2,t:none,log,deny,msg:'Ahrefs bot'" This works like a charm.
  2. D

    Resolved Mod_security integration

    We've been using Mod_security for years but the integration into Plesk is a puzzle to us. I tried to include a rule to block unwanted bots: In the directory /etc/httpd/conf/modsecurity.d/rules/tortix I've created a file z-custom.conf with: Include...
  3. D

    Adding custom rule to Mod_security

    Thanks, it works!
  4. D

    Adding custom rule to Mod_security

    Thank you Igor, I don't want to replace the whole ruleset but just add one rule: SecRule REQUEST_HEADERS "JDatabaseDriverMysqli" "phase:1,id:'999000',deny,t:urlDecode,t:removeNulls,status:403,log,noauditlog,msg:'Joomla RCE CVE-2015-8562'" Thanks, Erwin
  5. D

    Adding custom rule to Mod_security

    I have a hard time figuring out how Mod_security is exactly configured in Plesk 12. Its so different then on the server where we manually installed mod_security... I want to add a custom rule because of CVE-2015-8562. How can I add this rule without breaking anything and without it being...
  6. D

    SSL POODLE / SSLv3 bug

    @borisr, did you manage to patch port 8443? I also still haven't found out how to patch Qmail port 465.
  7. D

    SSL POODLE / SSLv3 bug

    I'm following the KB but am unable to fix 8443 and 465 on Plesk 9... Any suggestions?
  8. D

    Domeins not showing, Qmail does not react to panel.

    We installed a new VPS with Centos and Plesk 12. Domains are simply not showing in the controlpanel. We can see the subscritions but its empty under the button 'Domains'. Newly created sites as well as migrated sites do not show. Before we created or migrated a site to the server we...
  9. D

    Short mailname login doesn't work

    Hi, I migrated a older server to a new 8.6 install. All went well untill a custmer asked why he could send email anymore. I noticed I forgot to enable pop3 authentication so I enabled it. Immidate Plesk said short logins where not possible because a login was the same as a password...
Back
Top