• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Recent content by jmar83

  1. J

    Question Plesk webserver does block the access to website when computer is connected via VPN

    ok thx, will look on it ASAP :-)
  2. J

    Question Plesk webserver does block the access to website when computer is connected via VPN

    Hi there my Plesk web server does block the access to my websites when my computer is VPN connected via ch.hideservers.net (any maybe also other VPN servers). Where can i whitelist this? Can i whitelist it as a domain? Or do i need to whitelist it as an IP or CIDR? Thx for feedback(s).
  3. J

    Question Why i can't add nginx ModSecurity OWASP rules for a custom domain - "Nur genaue Übereinstimmungen werden unterstützt"

    now it works with SecRule REQUEST URI ARGS NAMES Chitoge id:1001001, phase:1, deny, status:403, msg:WAF Blocked Chitoge Backdoor Access Attempt, log, severity:CRITICAL SecRule ARGS NAMES Chitoge id:1001002, phase:1, deny, status:403, msg:WAF Suspicious parameter name: Chitoge, log...
  4. J

    Question Why i can't add nginx ModSecurity OWASP rules for a custom domain - "Nur genaue Übereinstimmungen werden unterstützt"

    same error message with SecRule REQUEST_URI ARGS_NAMES Chitoge id:1001001, phase:1, deny, status:403, msg:WAF Blocked Chitoge Backdoor Access Attempt, log, severity:CRITICAL SecRule ARGS_NAMES Chitoge id:1001002, phase:1, deny, status:403, msg:WAF Suspicious parameter name: Chitoge, log...
  5. J

    Question Why i can't add nginx ModSecurity OWASP rules for a custom domain - "Nur genaue Übereinstimmungen werden unterstützt"

    Oh... [ and ] ...
  6. J

    Question Why i can't add nginx ModSecurity OWASP rules for a custom domain - "Nur genaue Übereinstimmungen werden unterstützt"

    also same problem with: SecRule REQUEST_URI|ARGS_NAMES Chitoge id:1001001, phase:1, deny, status:403, msg:[WAF] Blocked Chitoge Backdoor Access Attempt, log, severity:CRITICAL SecRule ARGS_NAMES Chitoge id:1001002, phase:1, deny, status:403, msg:[WAF] Suspicious parameter name: Chitoge, log...
  7. J

    Question Why i can't add nginx ModSecurity OWASP rules for a custom domain - "Nur genaue Übereinstimmungen werden unterstützt"

    Will look what happens with that now :-)
  8. J

    Question Why i can't add nginx ModSecurity OWASP rules for a custom domain - "Nur genaue Übereinstimmungen werden unterstützt"

    Hmmm... now i've told ChatGPT the reason and asked for an alternative output: SecRule REQUEST_URI "Chitoge" "id:1001001, phase:1, deny, status:403, msg:WAF Block Chitoge Backdoor Access Attempt" SecRule ARGS_NAMES "Chitoge" "id:1001002, phase:1, deny, status:403, msg:WAF Suspicious parameter...
  9. J

    Question Why i can't add nginx ModSecurity OWASP rules for a custom domain - "Nur genaue Übereinstimmungen werden unterstützt"

    Hmmm... thank you very much, but how to solve / work around that issue?
  10. J

    Question Why i can't add nginx ModSecurity OWASP rules for a custom domain - "Nur genaue Übereinstimmungen werden unterstützt"

    Nobody knows why?
  11. J

    Question Why i can't add nginx ModSecurity OWASP rules for a custom domain - "Nur genaue Übereinstimmungen werden unterstützt"

    PS: Firstly, i tried it with comments, but removing them did not solved the problem (The rules was created via ChatGPT...) # Blockiert Requests mit dem GET/POST-Parameter "Chitoge" SecRule REQUEST_URI|ARGS_NAMES "@contains Chitoge" \ "id:1001001, phase:1, deny, status:403, msg:'[WAF]...
  12. J

    Question Why i can't add nginx ModSecurity OWASP rules for a custom domain - "Nur genaue Übereinstimmungen werden unterstützt"

    Hi there As the title says, i have a problem with custom webapp fw rules on a custom domain (so not in the general webapp fw settings section) Get that message... ***************************************************** Die folgenden Werte sind nicht gültig: SecRule REQUEST_URI|ARGS_NAMES...
  13. J

    Question Can i run Plesk 18.x “Obsidian” on Debian 10.x “Buster” with higher version “buster-backports” kernel?

    Thank you very much for your feedback. I think i shoud not be a problem - at least in theory. (Because Plesk and its components run on the application tier level). And yes, it does not replace a major version update - sure.
  14. J

    Question Can i run Plesk 18.x “Obsidian” on Debian 10.x “Buster” with higher version “buster-backports” kernel?

    Hi there As the title says: Is it possible to run Plesk 18.x “Obsidian” on Debian 10.x “Buster” with the higher version “buster-backports” kernel? Thank you very much for your feedback(s).
  15. J

    Issue "apt update" problem on Debian 10.x with Plesk 18.x "Obsidian"

    Yes, now 'apt update' seems to work again: Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://ftp.debian.org/debian buster InRelease Hit:3 http://autoinstall.plesk.com/WATCHDOG_3.1.0 buster InRelease Hit:4 http://ftp.debian.org/debian buster-updates InRelease Hit:5...
See more
Back
Top