• 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.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

Recent content by frg62

  1. F

    Issue No data displayed in Monitoring extension anymore after modifying the Panel access port

    Cool, thanks for this info! :cool:
  2. F

    Issue No data displayed in Monitoring extension anymore after modifying the Panel access port

    I had indeed modified plesk.conf, as instructed in: https://support.plesk.com/hc/en-us/articles/12377561753111-How-to-change-the-ports-for-the-Plesk-interface-on-Linux And reverting there to port 8880 solved the display problem. Thanks a lot! (I also deleted the lines I previously added to...
  3. F

    Issue No data displayed in Monitoring extension anymore after modifying the Panel access port

    I applied the two first suggestions, they did not change anything. After a while, I still end up with the following error message: The page is not redirected correctly. An error occurred while connecting to <domain>:<modified_secured_port>. The cause of this problem may be the deactivation or...
  4. F

    Issue No data displayed in Monitoring extension anymore after modifying the Panel access port

    Hello, Following continuous attacks on the Plesk panel of one of my servers (several hundreds per hour 24/7 for over a week now), I modified the access ports from 8880 and 8443 to other values. Fail2ban was doing a good job, but this modification radically reduced the attacks to... zero...
  5. F

    Issue Fail2ban: Ip addresses are not blocked by Recidive

    OK, thanks for the explanation. But it still does not explain why, when an IP address is jailed in recidive, other jails still detect it.
  6. F

    Issue Fail2ban: Ip addresses are not blocked by Recidive

    In jail.conf, I find: Default findtime = 10m recidive findtime = 1d (bantime = 1w) In jail.local: Default findtime = 600 no specific findtime in recidive: [recidive] enabled = true action = iptables-allports[name=recidive] sendmail-whois[mailcmd='/usr/sbin/sendmail -f "<sender>"...
  7. F

    Issue Fail2ban: Ip addresses are not blocked by Recidive

    Here is what I find in iptables: root@server:~# iptables -L -n | grep 194.0.234.230 # Warning: iptables-legacy tables present, use iptables-legacy to see them REJECT all -- 194.0.234.230 0.0.0.0/0 reject-with icmp-port-unreachable root@server:~# iptables-legacy -L -n |...
  8. F

    Issue Fail2ban: Ip addresses are not blocked by Recidive

    I am going to have a look at it, because presently, the address appears as jailed by 2 processes:
  9. F

    Issue Fail2ban: Ip addresses are not blocked by Recidive

    OK, after looking at F2B logs over a long period, I think I have finally understood how it works. It looks like each jail works in total independence. An IP address can first be jailed several times by f.i. "postfix", and "recidive" increment its counter, until it jails the attacking address...
  10. F

    Issue Fail2ban: Ip addresses are not blocked by Recidive

    It looks like the warning should no longer be displayed, see the results for each command line: root@server:~# iptables-legacy -L -n Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source...
  11. F

    Issue Fail2ban: Ip addresses are not blocked by Recidive

    No it is not: root@server:~# iptables -L -n | grep 185.226.117.240 # Warning: iptables-legacy tables present, use iptables-legacy to see them root@server:~# Yet it should be, because it was supposedly sent to Recidive 2 days ago (2025-02-24 04:31:21,413).
  12. F

    Issue Fail2ban: Ip addresses are not blocked by Recidive

    Hello, I have noticed that the IP addresses that are supposed to be banned in Recidive, actually still can access the server. Here is an extract from the F2B logs for a specific attacking IP address: 2025-02-23 02:36:01,726 fail2ban.filter [939832]: INFO [plesk-postfix] Found...
  13. F

    Forwarded to devs faulty DKIM record created after customer migration

    Because I host several domains for which the mail system is not hosted on my servers. Acting globally would create incorrect DKIM records for these domains.
  14. F

    Resolved Plesk Migrator creating DKIM error

    Hello, Last day of January 2024, and the bug is still there...
  15. F

    Forwarded to devs faulty DKIM record created after customer migration

    Hello, Last day of January 2024, and the bug is still there...
See more
Back
Top