• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Error starting web application. nextJs Installaton Error.

Gagandeep

New Pleskian
Server operating system version
Ubuntu 20.04.1 LTS
Plesk version and microupdate number
Plesk Obsidian Version 18.0.60
After setup NextJs on my plesk server. I'm facing this issue on webpage.

1714469900236.png
Here I'm sharing the Subprocess as well

1714470000158.png
1714470090585.png
 
You have NODE_ENV set to "dev". Per nextjs, that value can only be 1 of 3 things:
  • production: When your application is built with next build
  • development: When your application is run with next dev
  • test: When your application is being tested (e.g. jest)
 
I have set it to NODE_ENV: production. Still I'm facing 403 Error. I'm not quite sure what permission stopping it to run.
1714492793596.png
1714492827129.png
 
Maybe check fail2ban or Web Application Firewall "WAF" to see if they are blocking. Also, it seems odd that a document root location would start with a "." as shown in your screenshot....so check to make sure your public and app roots as seen by Plesk are correct. I could be wrong on that...but that looked odd to me.
 
Back
Top