• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Recent content by Xantiva

  1. X

    Resolved can't enable Fail2Ban after upgrade Onyx Version 17.5.3

    Hi UFHH01, what do you want to tell me? The first google hit is Man page of IPTABLES
  2. X

    Resolved can't enable Fail2Ban after upgrade Onyx Version 17.5.3

    Thank for your reply. I only found this thread: iptables -L pretty slow. Is this normal? with this as best answer:
  3. X

    Resolved can't enable Fail2Ban after upgrade Onyx Version 17.5.3

    The server and my internet connection aren't very slow. The problem seems to be all the DNS requests if the option "-n" (numeric output of addresses and ports) is not used. iptables -L -n is much faster now (no visible delay)! And I still use the recidive jail ...
  4. X

    Resolved can't enable Fail2Ban after upgrade Onyx Version 17.5.3

    I can tell you only what I observed. My Putty Connection doesn't response, a reconnect didn't work. How long could these flush command run? Maybe several minutes? Even if I run iptables -L it takes 18 minutes (!!!) for an output of < 900 lines. Most of them like: Is that normal? Or is there...
  5. X

    Resolved can't enable Fail2Ban after upgrade Onyx Version 17.5.3

    Hi, after an update from Onyx 17.0 to 17.5.3 I got also this "Broken pipe" error from the daily logrotate script: I tried the "RE-install the FAIL2Ban" instruction, but after the /sbin/iptables -F the VPS is completly locked. I have to restart it with the Virtuozzo. With the restart, the...
  6. X

    Resolved Suddenly getting ASL errors today

    After the update to version 4.0.19-40 it works here, even with REPUTATION_REPORT="yes" ... !?!
  7. X

    Resolved Suddenly getting ASL errors today

    Hi, I restored the /etc/asl/config yesterday and got "only" the exit code 127. This night the new version 4.0.19-39 was installed, but I still got the error mails every hour.
  8. X

    Resolved Suddenly getting ASL errors today

    Same problem here! The english message is: "Subscription creating: Specify ArticleID parameter" but there is no field for the ArticleID ?
  9. X

    Resolved Suddenly getting ASL errors today

    And now, since 12 o'clock, the antivirus DrWeb fails on every mail: Dear Postmaster, A message with the following attributes was not delivered because it contains an object which cannot be checked by antivirus. Sender = [email protected] Recipients = [email protected] Subject = New Doc...
  10. X

    Resolved Suddenly getting ASL errors today

    Hi, I've got the same error message here on two vServer with 12.0.18 Update #89 and 12.5.30 Update #42 @IgorG:
Back
Top