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

  1. B

    Issue I don't get any system emails

    Ah thx. I found some strange entries between 1 and 2 o'clock. This looks like the email from the system. Unfortunately, I can't figure it out. I just find the gmail addresses strange. Where could they be stored in a config? I changed the names of the two gmail addresses before posting them...
  2. B

    Issue I don't get any system emails

    The mail queue is empty. So nothing got stuck there. If I take a look at the outgoing mail control, I can assume that the weekly mail was attempted to be sent on November 11th, 2023 at around 1 a.m. The maillog is so large from various login attempts. Probably the curse of a V-Server. If I...
  3. B

    Issue I don't get any system emails

    Hello, I have 3 servers with Plesk. One quite old and two newer ones. For example, on the old one I receive emails about updates, problems and other system emails. I don't get anything on the two new ones. In my opinion, I have compared everything and it is the same. I can't find a way to send...
  4. B

    Resolved fail2ban-vacuum

    Thats it! I installed bsdutils and now the comand run without error. Why Strato offers a VM image with Ubuntu 22.04 + Plesk pre-installed but with missing components... who knows. Thank you both very much!
  5. B

    Resolved fail2ban-vacuum

    #!/bin/sh ### Copyright 1999-2022. Plesk International GmbH. All rights reserved. [ -f "/var/lib/fail2ban/fail2ban.sqlite3" ] || exit 0 outfile=`mktemp /tmp/fail2ban-vacuum.XXXXXX` trap 'rm -f $outfile;' TERM INT EXIT sqlite3 /var/lib/fail2ban/fail2ban.sqlite3 "VACUUM;" >$outfile 2>&1 rc=$...
  6. B

    Resolved fail2ban-vacuum

    I checked it. logrotate 3.19.0 is installed.
  7. B

    Resolved fail2ban-vacuum

    /tmp has drwxrwxrwt
  8. B

    Resolved fail2ban-vacuum

    Hello. I set up a new vServer at Strato with Plesk. Now the first weekend came and the job "/etc/cron.weekly/fail2ban-vacuum" was executed for the first time. There was an error that I can reproduce if I try to run the script manually. /etc/cron.weekly/fail2ban-vacuum:13: logger: not found...
Back
Top