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

  1. S

    Issue IPv6 ranges not working as they should

    For example, if you give a Docker daemon v6-fixed-cidr of 2a01:4f9:2b:f810::/64, it will in fact allocate ::1 to itself and all others in order to containers so it's understood as a network prefix, so why's this any different? You are supposed to be able to configure a IPv6 prefix of /64 for...
  2. S

    Issue IPv6 ranges not working as they should

    Then how are you supposed to do that for IPv6? In almost all other instances, outside Plesk that's understood as a prefix as I cannot simply do 2a01:4f9:2b:f810::/64 as it will not accept it, but most other applications does accept it.
  3. S

    Issue IPv6 ranges not working as they should

    Hi, When I add an IPv6 range like 2a01:4f9:2b:f810:0:0:0:1 -> 2a01:4f9:2b:f810:ffff:ffff:ffff:ffff (Mask /64), it will only use the 2a01:4f9:2b:f810::1 address for all of the sites, and not allocate one IP per site from it, why's that? I don't think that's how it's supposed to work?
See more
Back
Top