• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  1. 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.
  2. 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.
  3. A

    Forwarded to devs 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.
  4. A

    Forwarded to devs 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...
  5. A

    Forwarded to devs 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...
  6. 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.
  7. 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...
  8. 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...
  9. 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...
  10. A

    Question Fail2Ban capture and ban IP, connection still being made

    Hi, Running Plesk Obsidian Version 18.0.61 on Centos 7.9.2009 (for the last week before moving to Alma) in a LXC in Proxmox. Proxmox firewall enabled for the LXC, while iptable rules within the LXC works. From inside the Plesk LXC, if I add an iptable rule to block an IP , it actually does...
  11. A

    Issue CGroup enabled in a privileged CT - Failed to set cpu.cfs_quota_us

    @kpushkarev here it is - thx for your help /sys/fs/cgroup/cpu,cpuacct/user.slice/user-30.slice/cpu.cfs_period_us 100000 /sys/fs/cgroup/cpu,cpuacct/user.slice/user-30.slice/cpu.cfs_quota_us -1 /sys/fs/cgroup/cpu,cpuacct/user.slice/user-10044.slice/cpu.cfs_period_us 100000...
  12. A

    Issue CGroup enabled in a privileged CT - Failed to set cpu.cfs_quota_us

    @kpushkarev here's the output: cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)...
  13. A

    Issue CGroup enabled in a privileged CT - Failed to set cpu.cfs_quota_us

    If I stop the Resource Controller (Cgroups) service via Plesk UI, I can see heaps of these messages appearing in the logs until the service actually stops. Then these messages do not appear anymore.
  14. A

    Issue CGroup enabled in a privileged CT - Failed to set cpu.cfs_quota_us

    Seems to be events handled by the monitoring of usage per subscription. I can see these appearing just after a "Started Session c**** of use ***". I also see a lot of "Cannot watch ****, PID is already watched twice". All of this in the /var/log/messages
  15. A

    Question named / bind - max-cache-size

    Ended having it working by doing so, since the checkconf was running against proper chrooted file, but execution of service still based on /etc: ln -s /var/named/chroot/etc/named-user-options.conf /etc/named-user-options.conf
  16. A

    Question named / bind - max-cache-size

    Realised that the DNS settings from Plesk UI are going into /var/named/chroot/etc/named-user-options.conf and are actually being taken into account. In brief, anything in /etc/ for named/Bind shall be ignored.
  17. A

    Resolved Loads of messages "named[...]: network unreachable resolving '...': 2001:7fe::53#53"

    Thanks for this, works very well. Any chance with Bind custom options? I raised another post where literally anywhere I attempt to add my custom options, they're never considered https://talk.plesk.com/threads/named-bind-max-cache-size.373672/#post-944458
  18. A

    Question named / bind - max-cache-size

    Also attempted the server wide settings for bind in Plesk UI, doesn't work > any parameter being put there isn't being brought into the /etc/named.conf file. https://docs.plesk.com/en-US/obsidian/administrator-guide/dns/dns-settings.72226/
  19. A

    Question named / bind - max-cache-size

    Hi again, I actually realized that the file /etc/named-user-options.conf is not taken into consideration. I did put wrong values in that file on purpose, and named chroot service still started without problem. Any other way to add options to Bind config? // -- THE FOLLOWING LINES WERE...
Back
Top