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

    Resolved run-parts: /etc/cron.daily/60sa-update exited with return code 4

    Fixed it with following commands: wget http://spamassassin.apache.org/updates/GPG.KEY sa-update --import GPG.KEY But do you know why this happened? And why doesn't plesk-update script check if the key is still valid and try to repair itself by updating the gpg key? Best regards Floh
  2. F

    Resolved Wordpress Cron: Unknown named parameter $interval

    Switch to PHP 8.2 fixed the issue. Thank you! :) (Where can I mark this thread as resolved?)
  3. F

    Resolved Plesk 18.0.52 System Updates / Extensions / Cron - Multiple Failures

    Hi, thank you for providing useful informations.
  4. F

    Resolved Wordpress Cron: Unknown named parameter $interval

    Hi everybody. That is a good hint, it was running with 8.0, now I installed 8.2 on Plesk and switched to that version. I hope the error is gone now if not I'll try different PHP-Version. In meanwhile I'll also try to find out where I can find logs from Wordpress.
  5. F

    Resolved Wordpress Cron: Unknown named parameter $interval

    Thank you for your quick reply. Will ask in Wordpress forum. I just want to be sure if it's not related to WP-Toolkit. Best regards Floh
  6. F

    Resolved Wordpress Cron: Unknown named parameter $interval

    Hi, I have a issue and I get daily an email with following subject: Cron <***.**_********@***> (/opt/plesk/php/8.0/bin/php -f 'httpdocs/wp-cron.php') > /dev/null And following content: PHP Fatal error: Uncaught Error: Unknown named parameter $interval in...
  7. F

    Resolved run-parts: /etc/cron.daily/60sa-update exited with return code 4

    Hi, I got that error message by email. How can I fix it and what is the cause of that? I believe it's related to that: Jul 23 06:36:08.506 [1636103] dbg: dns: query failed: 2.4.3.updates.spamassassin.org => REFUSED Jul 23 06:36:08.506 [1636103] dbg: dns: query failed...
  8. F

    Resolved Plesk 18.0.52 System Updates / Extensions / Cron - Multiple Failures

    Hi, I have several issues that curl cannot resolve hostnames but our dns is working well. Where can I find these CIDR bans in Plesk? Fail2Ban? If it's on your external firewall, do you know the reason for that? Best regards Floh
  9. F

    Resolved eMail Security: Issue with hostname (not valid)

    Everything is working well I bought license (to get ClamAV and statistics) yesterday. So the workaround for setup is working.
  10. F

    Resolved eMail Security: Issue with hostname (not valid)

    I'm using Debian Buster. In the meanwhile I successfully installed the eMail Security. See Post #18 Then I rebooted (so hostname is reverted) and I still can access the eMail Security pages. That is great. Will do some tests if everything is working as expected. So hostnamectl is a workaround...
  11. F

    Resolved eMail Security: Issue with hostname (not valid)

    Ok, I see. I just found out that Plesk eMail Security uses amavis and there I saw the requirement about the hostname. I tried to set the variable $myhostname same as you suggested, but I don't have /etc/amavis. Could it be be that it's installed after I run the eMail Security first time...
  12. F

    Resolved eMail Security: Issue with hostname (not valid)

    If I change the hostname with hostnamectl command, then eMail Security works which is good. But after reboot the hostname is reverted to non-fqdn hostname. root@hosting:/etc# hostnamectl set-hostname hosting.example.com root@hosting:/etc# hostnamectl Static hostname: hosting.example.com...
  13. F

    Resolved eMail Security: Issue with hostname (not valid)

    root@hosting:~# hostname --fqdn localhost.localdomain :oops: That of course is wrong... If I don't use the --fqdn parameter then its fine: root@hosting:~# cat /etc/hostname hosting root@hosting:~# hostname hosting Why? UPDATE: I just changed the order of hostnames in /etc/hosts in first line...
  14. F

    Resolved eMail Security: Issue with hostname (not valid)

    I've tried that, but after reboot the domain is removed by Proxmox. I asked them in their forum and this is reply with a quote: So they wrote: See more: Proxmox Forum - "FQDN as hostname for container"
  15. F

    Resolved eMail Security: Issue with hostname (not valid)

    Hi, removing 'hosting' from the hosts file, as suggested by Peter, did not help unfortunately. Do any of you have an idea how to fix this issue? Does anyone know where Plesk retrieves the hostname value from?
  16. F

    Resolved eMail Security: Issue with hostname (not valid)

    Just to be sure, do I need to restart anything after I changed the hosts file? The problem is, after I removed "hosting" Proxmox readd it to hosts when I reboot the container.
  17. F

    Resolved eMail Security: Issue with hostname (not valid)

    I should just remove the marked ‚hosting‘?
  18. F

    Resolved eMail Security: Issue with hostname (not valid)

    Hi everybody. I'm running Plesk Obsidian on my Proxmox-Machine as a Container. Everything works well except eMail Security which I'd like to setup. Unfortunately I only get an error message there: Hostname ist nicht valide. Der aktuelle Wert ist "hosting". Plesk Email Security funktioniert nur...
Back
Top