• 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.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • 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.

Question Fail2Ban settings missing in Obsidian 18.0.48 for Windows

Johan Donne

New Pleskian
Server operating system version
Windows Server 2016
Plesk version and microupdate number
Obsidian Web Pro 18.0.48
In 'Tools & Settings', the link for Fail2Ban settings seems to have disappeared.
Does anyone know why (or how to reach those settings)?
 

Attachments

  • Tools & Settings.png
    Tools & Settings.png
    132 KB · Views: 5
Fail2Ban is no longer in the list of components...
Tough it seems to be active: all connections coming from our reverse proxy are refused (In a previous version I whitelisted that IP-address).
Connections from other machines are working.
 
I would say remove it and reinstall it but i am only experienced with Linux and not windows server (i only just noticed that you are on windows)

Edit: it seems that fail2ban is not available on windows. Thanks Kaspar!
 
Ok, then I must be mistaken (I remember whitelisting our reverse proxy in Fail2Ban, but that must have been on a Linux-machine).
Still very strange: that plesk server resets all requests coming from the reverse proxy and accepts them from all other machines.
None of the existing firewall rules could explain that behavior...
 
Back
Top