• 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 Kevin Kleine

  1. K

    Plesk 12.5.30 email aliases and forwarding not working

    Output from the mchk utility: /usr/local/psa/admin/sbin/mchk --with-spam ==> Checking for: mailsrv_conf_init... ok ==> Checking for: mail_handlers_init... ok ==> Checking for: mailsrv_entities_dump... ok ==> Checking for: mail_admin_aliases... ok ==> Checking for: mail_auth_dump... ok ==>...
  2. K

    Plesk 12.5.30 email aliases and forwarding not working

    Does anyone know why emails sent to aliases set-up in Plesk 12.5.30 are not delivered or forwarded? Or how I should debug this?
  3. K

    Secure websockets (WSS)

    Dear all, Can anyone tell me how I should to set up a secure websocket server with Plesk? At this point I have set up the Plesk firewall so that traffic from/to port 8080 is allowed and I have a websocket server (Ratchet - a PHP implementation) running perfectly (but only for non-secure (ws)...
  4. K

    Plesk is preventing CORS headers from reaching external servers

    This PHP code worked for me: if ( isset( $_SERVER[ 'HTTP_REFERER' ] ) ) { header( 'Access-Control-Allow-Origin: ' . rtrim( $_SERVER['HTTP_REFERER'], '/' ) ); header( 'Access-Control-Allow-Credentials: true' ); header( 'Access-Control-Max-Age: 86400' ); } if...
Back
Top