• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • 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.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

Search results

  1. I

    Issue Atomic Standard ruleset problem

    Thank for the update. I tried temporary disable IPv6 and run the command again and it works! I still confusing as why this one encountered a problem as I have 3 other servers with same environment and they're set to use atomic ruleset without any problem.
  2. I

    Issue Atomic Standard ruleset problem

    Hello, I'm seeing the same issue on one of my servers. Just changing the Web Application Firewall ruleset in the admin page. - Go to 'Tools & Settings' - Click 'Web Application Firewall' - Click tab Settings - Under 'Rule sets' select 'Atomic Standard' - Scroll to bottom of page, then click OK...
Back
Top