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

Question How to show logs for webmail.DOMAIN.com subdomain? Log section shows only logs for main domain

You can disable the rules globally or for a particular domain/subdomain. You can find detailed instructions here. I am not quite sure I was able to understand what you are implying to be a Plesk bug that needs to be fixed by the developers. Sorry. However, webmail being inaccessible while using the OWASP rule set is not a Plesk bug.
 
no, to turn off webapp firewall for one (1) specific domain domain.com does not disabled it for webmail.domain.com

1736970634862.png
 
when i disable webapp fw globally (so NOT domain-specific! Which means: on domain settings), the roundcube webmail on webmail.domain.com works.

1736970860310.png
 
so what to do now?

- disable on domain level does not include webmail subdomain
- disabled webabb fw globally is not what i want
- to apply curstom settings via command line (custom settings text box) does not work either due of using nginx (instead of apache) or inactive/locked (not: "disabled") domain
 
the only one way seems to set the rule to low security filtering on global settings, then the message is gone on webmail.domain.com / roundcube
1736971231154.png
 

Attachments

  • 1736971211000.png
    1736971211000.png
    31.1 KB · Views: 0
<implying to be a Plesk bug that needs to be fixed by the developers>

No, i just want to say that it should be possible to edit (maybe disable completly) the webapp firewall for webmai(.domain.com) subdomain - indepedent from main domain custom settings and global settings. I dont hope that is too complex to understand!
 
And its also not a solution to exclude ~30 rule IDs globally (for every domain and subdomain) just because or webmail/horde... because that f**ks the security there
 
The whole idea is to exclude ONLY the rule/s that are triggering the issue, not to disable ModSecurity on the entire server. You need to check the logs (Domains > example.com > Logs, and turn off all logs other than ModSecurity to see if there are any entries) and determine the Rule ID, which next needs to be excluded following the instructions I linked in one of my previous replies.

You can disable the rules globally or for a particular domain/subdomain. You can find detailed instructions here.

Lastly, I would like to kindly ask you to avoid using swear words on the Forum. We all want to keep the good tone here.
 
In theory, excluding the rule on a domain level should also affect webmail.domain.com. I can't say why exactly that's not working in this particular case. OWASP is a very restrictive set of rules and as the warning before enabling the ruleset indicates, it might cause issues with webmail, which is why it is not recommended. You can get in touch with our support team, so they can log into the server and review the logs, but please note that I cannot guarantee that they will be able to help as the configuration of the ruleset falls out of the scope of their expertise and it is usually something handled by clients.
 
Back
Top