• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Search results

  1. J

    Issue Bad RSA signature - DKIM fails

    Hi, I've searched a lot and need to clarify something. I have a problem when trying to validate via dkimvalidator.com. I get Validating Signature result = fail Details: bad RSA signature I checked, if the TXT record for default._domainkey.example.com is the same on all nameservers...
  2. J

    Resolved Messages log is flooding with many grafana alerts

    Here is my error message from "Advanced Monitoring", when I click at the exclamation mark: Ubuntu 16.04.7 LTS Plesk 18.0.34 Update #2 Grafana 8.0.2 Metric request error Object status:500 statusText:"Internal Server Error" data:Object message:"Metric request error" config:Object...
  3. J

    Forwarded to devs Grafana extension database rights too broad and cannot load unsigned backend plugin

    Same problem here: Ubuntu 16.04.7 LTS Plesk 18.0.34 Update #2 grafana 8.0.2
  4. J

    Resolved Messages log is flooding with many grafana alerts

    Same here in the syslog files. Started on June, 9th
  5. J

    wp-toolkit generates "Failed to reset cache for the instance #42" errors

    Same here since April, 20th: Failed to reset cache for the instance #24: Fehler bei der Dekodierung von JSON: Decoding failed: Syntax error It's really annoying
  6. J

    Resolved 5.7.0 The message could not be sent. You are not allowed to use sendmail utility. 4.2.1 Message can not be delivered at this time

    Hmmm, may be a bug. This domain seemed to be missing in the plesk outgoing mail limits database. After I added the domain with /usr/local/psa/admin/sbin/mailmng-outgoing --add-subscription --main-domain-name=domain.com the emails for that domain addresses went through. Here is someone with a...
  7. J

    Resolved 5.7.0 The message could not be sent. You are not allowed to use sendmail utility. 4.2.1 Message can not be delivered at this time

    Plesk Obsidian 18.0.25 Ubuntu 16.04.6 LTS Hi, I've got a problem with "forwarding only" emails with outgoing mail control on one domain: When I'm trying to send an email to one of this email addresses with mail forwarding I get this in the maillog: Mar 20 15:56:13 mail postfix/pipe[742]...
  8. J

    Resolved sw-cp-server.service doesn't start after update from 18.0.24 to 18.0.25

    Hello Monty, ah! I was on that page but didn't mention the part on the bottom of that page because the errors and error messages didn't match my problem (so I thought ;-)). The killing of the sw-cp-server processes from that instructions did the trick: Connect to the Plesk server via SSH...
  9. J

    Resolved sw-cp-server.service doesn't start after update from 18.0.24 to 18.0.25

    Ubuntu 16.04.6 LTS Plesk Obsidian 18.0.25 Hi, I updated Plesk Obsidian from 18.0.24 to 18.0.25 yesterday. This morning I got an error from Watchdog, that the Plesk Web Server been released from monitoring. I tried to reactivate the service monitoring for the Plesk Web Server but it fails...
  10. J

    Input Upgrade to Spamassassin 3.4.4

    That‘s correct but Plesk has implemented newer versions of different software in the past. We are running on Ubuntu 16.04LTS and you can install spamassassin 3.4.4 on that system. It is not in the repo (yeah they only support 3.4.2) but it is installable.
  11. J

    Question Plesk Email Security Pro and yet getting spam

    A negative SPAM score depends on the default values from the numerous tests spamassassin does. A list of the older spamassassin 3.3.x can be found here: spamassassin tests Search for „whitelist“ - there you can see, that messages with the responding header test get high negative SPAM scores...
  12. J

    Input Upgrade to Spamassassin 3.4.4

    The actual spamassassin supported from Plesk Obsidian 18.024 is version 3.4.2, which is already one and a half years old. A reasonable, preferably daily updated spam filtering should be a matter of course, therefore an early update to version 3.4.2 is highly desirable. Even better would be an...
  13. J

    An error occurred while executing WP-CLI command for instance

    Hi, since some days i get the following cron error message: [2019-06-15 12:53:31.787] ERR [extension/wp-toolkit] An error occurred while executing WP-CLI command for instance: WordPress instance #24 ('https://www.xyz.de') When I execute the command that causes that cron error manually...
  14. J

    Update Watchdog configuration for Spamassassin (Ubuntu 16.04)

    Hi, I can confirm that. But the change in "/opt/psa/etc/modules/watchdog/monitrc" only doesn't do the trick when the Watchdog service for spamassassin is reenabled, because the file "/opt/psa/etc/modules/watchdog/monitrc" is generated again with the old line "with pidfile "/var/run/spamd.pid""...
Back
Top