• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Search results

  1. M

    Issue Node+Phusion port conflicts

    3000
  2. 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...
  3. 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