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

  1. M

    Resolved NextJS works on Plesk?

    Here's an updated guide where you don't have to worry abount ginx directives: How to deploy Next.js 15 on Plesk | mytchall.dev
  2. M

    Question Incomplete response received from application NodeJS running on Plesk

    Plesk uses Phusion Passenger to serve the Node app and you can check the logs at `/var/log/passenger/passenger.log`. This article might help: How to resolve common issues when running a Next.js node app on Plesk
  3. M

    Issue Node+Phusion port conflicts

    3000
  4. M

    Issue Node+Phusion port conflicts

    When starting a Next.js Node app with the Plesk UI, it uses port 3000 by default. This is an issue if I want to start a new Next.js app on a different domain, as it conflicts with the same port, giving an error "This address is already in use". If I stop the first node app process, it frees up...
  5. M

    Resolved NextJS works on Plesk?

    This is the nginx config that fixed it for me: rewrite ^/_next/(.*\.(css|js))$ /$1 break; Also wrote a blog post featuring the topic: Removing the build folders when deploying Next.js on Plesk - mytchall.dev
See more
Back
Top