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

Search results

  1. I

    Issue Atomic's rules are no longer updated

    My folder is not /etc/httpd/conf/modsecurity.d/rules/atomic, it is /etc/httpd/conf/modsecurity.d/rules/tortix Is this correct? The /etc/httpd/conf/modsecurity.d/rules/atomic folder does not exist.
  2. I

    Issue Atomic's rules are no longer updated

    By the way, I have the atomic payment rules but purchased through the plesk store.
  3. I

    Issue Atomic's rules are no longer updated

    The only way I can know if the rules have been updated that I know of is through the notifications, and they no longer appear since the last update. Is there any other way to find out? Another reference I can think of is when I used to run “plesk daily -UpdateModSecurityRuleSet” it took between...
  4. I

    Issue Atomic's rules are no longer updated

    Very strange, because updating the atomic rules from “aum” did not deactivate selinux, but doing it from plesk did. Now activating the rules from aum updates the rules correctly, but doing it from plesk does not update the rules at all. Are you sure nothing is broken in the last update?
  5. I

    Issue PHP Warning: gzinflate()

    they started to appear for me too after upgrading to Plesk Obsidian 18.0.67
  6. I

    Issue Atomic's rules are no longer updated

    Unfortunately it did not work. I never had to put in before: [modSecurity] ruleSet.tortix = true ruleSet.atomic = true in panel.ini, and it always worked, I tried it anyway but it didn't work. I have no error in plesk, and everything works perfectly until I run plesk daily...
  7. I

    Issue Atomic's rules are no longer updated

    Is there no news on this matter? We have had a month with Modsecurity broken in plesk. Something as important as security, I get the feeling that it is not given the attention it should be, and that can bring many problems.
  8. I

    Issue Atomic's rules are no longer updated

    I have manually modified the files /var/awp/etc/config and /var/awp/etc/config.aum by setting MODSEC_ENABLED=“yes” and it works correctly again if I run aum -uf. The rules are updated correctly, but if I run plesk daily UpdateModSecurityRuleSet the rules are not updated and the configuration...
  9. I

    Issue Atomic's rules are no longer updated

    I have the atomic advanced. I really don't see any errors. Just every night when the rules were updated I got a notification in plesk, notifying me of the rules update. That no longer appears. As I found it strange not to have the update, I tried to force it manually with plesk daily -f...
  10. I

    Issue Atomic's rules are no longer updated

    Since the last plesk update the modsecurity updates at least for atomic have stopped working. They don't work neither from plesk's daily cron job nor by forcing it with aum -uf. Running aum -uf gives as a result:
  11. I

    Issue Getting DANE working

    Chatgpt tells me that your version is newer than mine, and that the correct form for that version is this one: dnssec-validation auto; managed-keys-directory "/var/named/dynamic"; the path /var/named/dynamic I don't know if it corresponds to the one on your system.
  12. I

    Issue Getting DANE working

    Did you create that file? I had to create it. If you did it and the error persists I can't help you, see if there is someone on the forum who is more familiar with this.
  13. I

    Issue Getting DANE working

    what errors?
  14. I

    Issue Getting DANE working

    Right, I created that file with nothing in it. The file did not exist on my system.
  15. I

    Issue Getting DANE working

    Follow this path in the plesk interface. Plesk => Tools and Settings => DNS Settings => Server-wide Settings => Additional DNS Settings
  16. I

    Issue Getting DANE working

    follow in your footsteps. The only thing I think I did different from you was to add dns configuration at the server level, in the plesk interface: In the text field I already had: This made it start to work.
  17. I

    Issue Getting DANE working

    More logs confirming that it works as expected. postfix/smtp [1361245] Untrusted TLS connection established with wrong.havedane.net[xx.xx.xxx.xxx.xxx]:25: TLSv1.3 with encryption TLS_AES_256_GCM_SHA384 (256/256 bits) key exchange X25519 server signature RSA-PSS (2048 bits) server digest SHA256...
  18. I

    Issue Getting DANE working

    I think I have it, I have run the test on Have DANE? and the results are correct: postfix/smtp [1361244] 2ABC62000CBB38: to=<[email protected]>, relay=dont.havedane.net[xx.xx.xx.xxx.xxx.xxx]:25, delay=1.4, delays=0.85/0.05/0.35/0.11, dsn=2.0.0, status=sent (250 2.0.0 Ok...
  19. I

    Issue Getting DANE working

    I don't know, I am facing the same difficulties as you in getting the connections verified. My postfix configuration file also did not have the entries to the certificates. I am struggling for my server to use dnssec.
  20. I

    Issue Getting DANE working

    The error you are encountering typically occurs when trying to initiate an SSL/TLS connection on a port that expects a different protocol or handshake method. In your case, you are attempting to connect to mail.leagues-united.de on port 587 using OpenSSL's s_client without specifying the correct...
Back
Top