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

  1. J

    Issue New mail stuck in queue with age 23 hours

    No, no errors logged. But this is 15 sec after pressing send btn. The mail 'age' is already 23h.
  2. J

    Issue New mail stuck in queue with age 23 hours

    I have exactly the same issue; but on AlmaLinux 8.7. Mails in added to the queue have a Age of 23:00:00 h at the start. And are not send. Switching timezone will send them away. But switching back to correct timezone the issue is there again. Datetime settings in Plesk are correct according the...
  3. J

    Relation "502 Bad Gateway"/"can't apply process slot" and restart iptables?

    After 5 days of working without problems today I had the described issue 2 times till now. proxy_error_log: 2015/07/14 14:38:57 [error] 31724#0: *43582 connect() failed (111: Connection refused) while connecting to upstream, client: xxx.xx.xx.xxx, server: domeinname.nl, request: "GET...
  4. J

    Relation "502 Bad Gateway"/"can't apply process slot" and restart iptables?

    The first one I already did. The second not, added the "resolver 127.0.0.1;" to the nginx.conf file. Regenerate all domains and restarted apache and nginx. Lets see if this is the solution! Will keep you updated. Thanks so far!
  5. J

    Relation "502 Bad Gateway"/"can't apply process slot" and restart iptables?

    Thanks IgorG, for your quick reply! Resources are not an issue. Our monitoring tools give a highest CPU usage of 40,9% and for memory 39%. But ran the command you suggested and all failcounters are 0, as shown in attached file.
  6. J

    Relation "502 Bad Gateway"/"can't apply process slot" and restart iptables?

    Dear, I have a strange issue on a Plesk 12 VPS. Sometimes the sites result in a "502 Bad Gateway (nginx)". This happens 1 or 2 times a day on different times. In the httpd log I see a record "can't apply process slot" and in nginx log I see "connect() failed (111: Connection refused) while...
Back
Top