• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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 run-parts: /etc/cron.daily/60sa-update exited with return code 4

    Anybody with idea/hint?
  3. 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?)
  4. F

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

    Hi, thank you for providing useful informations.
  5. 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.
  6. 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
  7. 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...
    • floh
    • Thread
    • cron error wordpress
    • Replies: 6
    • Forum: WP Toolkit
  8. 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...
  9. 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
  10. 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.
  11. 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...
  12. 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...
  13. 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...
  14. 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...
  15. 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"
  16. F

    Resolved eMail Security: Issue with hostname (not valid)

    Yes it is.
  17. 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?
  18. 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.
  19. F

    Resolved eMail Security: Issue with hostname (not valid)

    I should just remove the marked ‚hosting‘?
  20. 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...
View older results
Back
Top