• 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 Sebastian Thomas

  1. Sebastian Thomas

    Question How to configure a fixed process pool for NodeJS with Passenger

    Maybe you are using nginx in "Proxy mode" (Checkbox in Apache&Nginx settings of your app's domain)? If you don't need Apache turn Proxy mode off and restart nginx.
  2. Sebastian Thomas

    Question How to get rid of IP-addresses from Docker networks

    I'm also having this issue unfortunately this doesn't help much: https://support.plesk.com/hc/en-us/articles/213933865-Nginx-on-Plesk-server-fails-to-start-99-Cannot-assign-requested-address
  3. Sebastian Thomas

    Issue Laravel Deployment Composer Error

    I fixed it for `<username>` with these commands: ``` # su - <username> $ /opt/plesk/php/8.0/bin/php /usr/lib64/plesk-9.0/composer.phar global config --no-plugins allow-plugins.plesk/composer-command-info true ```
  4. Sebastian Thomas

    Issue Trying to access Nodejs configuration for domain results in "There is no web hosting configured on domain."

    Since the latest Plesk Obsidian update of the nodejs extension to 2.1.0 we encounter an error when trying to access the configuration. Anyone else noticed this?
  5. Sebastian Thomas

    Question How to configure a fixed process pool for NodeJS with Passenger

    You can configure the max-pool-size in `/etc/nginx/conf.d/phusion-passenger.conf` like this: ``` passenger_max_pool_size 250; ```
See more
Back
Top