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

Search results

  1. A

    Resolved Statistic collection saturates disk

    Hi, Struggling with IO used by statistics_collector. Already enabled the suggestion with the ionice wrapper above, which helps to avoid the saturation. But statistics collector now takes days to run, have to kill the process as it never ends, then piles up with daily Cron and is running non...
  2. A

    Question Plesk Admin - Bad Bot protection

    Thanks @Kaspar, this is exactly what I was after. While Go-http-client may be default user agent of the GO HTTP client package, any PROD ready code using it shall rename the user agent accordingly - looking at the heavy amount of connections generated from multiple IPs with this user agent...
  3. A

    Question Plesk Admin - Bad Bot protection

    Hi, I see many attempts of connection from user agent Go-http-client, within short period of time to the Plesk Admin panel, seem to be a bad bot. Requests show up in the following log file: /var/log/plesk/httpsd_access_log This usually triggers same time the following alert - "The threshold of...
  4. A

    Question Watchdog v3 - New service configuration

    I just voted for the PHP-FPM in watchdog. What I'm after is monitoring the clamav milter, which obviously you do not formally support.
  5. A

    Question Watchdog v3 - New service configuration

    Hi, I've followed the following instructions for Watchdog to add new services configuration: Instruction - How to add a new service to the watchdog extension Nevertheless, since Watchdog v3 upgrade, these new custom services are not being monitored (while still being listed). I attempted to...
  6. A

    Issue FTP broken?

    Hi, same issue here - what was done to fix it? Thx
  7. A

    Issue FTP - Insecure server, it does not support FTP over TLS.

    got this to work - only FTP on 21 with TLS does not work.
  8. A

    Issue FTP - Insecure server, it does not support FTP over TLS.

    I even attempted to configure implicit encryption, no luck - timeout on port 990: https://docs.plesk.com/en-US/obsidian/advanced-administration-guide-linux/services-management/ftp.68761/#switching-on-implicit-ftps While service is actually listening: lsof -i TCP:990 COMMAND PID USER FD...
  9. A

    Issue FTP - Insecure server, it does not support FTP over TLS.

    Also adding tls content of the /etc/proftpd.conf file: <IfModule mod_tls.c> # common settings for all virtual hosts TLSEngine on TLSRequired off TLSLog /var/log/plesk/ftp_tls.log TLSRSACertificateFile /usr/local/psa/admin/conf/httpsd.pem...
  10. A

    Issue FTP - Insecure server, it does not support FTP over TLS.

    Hi, Somehow after a Plesk upgrade, I'm unable to connect via FTP over TLS - through both Filezilla and WinSCP. It works over non-secure FTP. Filezilla complaints with message "Insecure server, it does not support FTP over TLS". WinSCP advises that the parameter is not supported. FileZilla...
  11. A

    Question Cloudflare DNS extension & /usr/local/psa/admin/bin/dnsmng --update

    The export is done manually. But then if I update the DNS, I am willing to trigger the Sync function, to push latest changes to CloudFlare. Hence I am wondering if the command dnsmng would do so.
  12. A

    Question Cloudflare DNS extension & /usr/local/psa/admin/bin/dnsmng --update

    Hi, I have a domain exported to Cloudflare via the Cloudflare DNS extension. Would anyone know if the sync to Cloudflare for this domain is triggered by the command "/usr/local/psa/admin/bin/dnsmng --update"? Thanks.
  13. A

    Resolved Multi-Factor Authentication (MFA) - New Accounts tab - JS error showing blank page

    Just to add: Google Authenticator 1.5.6-3176 extension is still installed, which is disabled since MFA was delivered earlier this year.
  14. A

    Resolved Multi-Factor Authentication (MFA) - New Accounts tab - JS error showing blank page

    Just tried @Sebahat.hadzhi with Edge, same error. react-dom.production.min.js:188 TypeError: e.filter is not a function at main.js?&18.0.65:1:39030 at Object.useMemo (react-dom.production.min.js:177:189) at t.useMemo (react.production.min.js:26:48) at Ot...
  15. A

    Resolved Multi-Factor Authentication (MFA) - New Accounts tab - JS error showing blank page

    Username: TITLE Multi-Factor Authentication (MFA) - New Accounts tab - JS error showing blank page PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE AlmaLinux 8.10 (Cerulean Leopard), Plesk Obsidian 18.0.65 Web Host Edition, MFA Extension 1.1.0-1735 PROBLEM DESCRIPTION While...
  16. A

    Question Fail2Ban capture and ban IP, connection still being made

    I actually found something interesting: Using Fail2Ban with Cloudflare on a free account Shall be part of a Plesk extension, to sync up IP blocking list from fail2ban to cloudflare.
  17. A

    Issue Default plesk-apache-badbot fail2ban doesn't work

    Thanks for confirmation. Behavior I encountered has nothing to do with the failregex line. If I use the failregex line with the badbots list from @pleskpanel, works like a charm. The problem comes from a custom list of badbots I was trying - being a merge between a nginx regex and the one...
  18. A

    Question Fail2Ban capture and ban IP, connection still being made

    Thanks @AYamshanov, makes perfect sense. Logs from Apache/Nginx shows X-Forwarded-For IP as expected, hence fail2ban bans accordingly, while Iptables will see Cloudflare IP and hence let the traffic flow through. I will then rely on rules at nginx level for cloudflare exposed sites for now...
  19. A

    Issue Default plesk-apache-badbot fail2ban doesn't work

    Hi everyone, Thanks for this great post and all useful input. It really helped in leveraging the fail2ban bad bot jail. Nevertheless, while using the regex from Kaspar, it has actually started to block almost all IPs... rather than just the bad bots. Did you encounter the same? Just surprised...
Back
Top