• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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

    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...
  4. 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
Back
Top