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

  1. A

    Nginx autostart does not work properly

    Well, I was able to solve ipv4 issue with: net.ipv4.ip_nonlocal_bind=1 The server indeed might start to fast for the network interfaces to become ready, because of the HW raid1+ssd, and it also uses NetworkManager, but in my opinion it is still a bug, that I cannot understand. My other server...
  2. A

    Nginx autostart does not work properly

    Hi, My Plesk server installation has following issue: 2015/11/11 11:16:27 [emerg] 1675#0: bind() to <IPv4>:80 failed (99: Cannot assign requested address) 2015/11/11 11:47:15 [emerg] 1722#0: bind() to [IPv6]:80 failed (99: Cannot assign requested address) Nginx works fine, if I start it...
  3. A

    Nginx + Plesk + Hotlinking

    Hi, I have a problem with Nginx+ Plesk. I need to stop hotlinkers from embedding pictures from my server, and I use Plesk functionality to add Nginx directive, like this: location ~* \.(jpg|jpeg|png|gif)$ { valid_referers none blocked server_names *.example.com...
  4. A

    security issue plesk panel

    Hi, your cert is fine. the error only shows, that it was not issued by a certificate authority, like Comodo, Thawte and etc., in other words, it is a self-signed certificate. To fix the problem, you basically have to buy a certificate for that particular domain from a certificate authority...
Back
Top