• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Next.js 16 app crashing on Plesk with HTTP 499 despite Passenger configuration

Aapklub

New Pleskian
I have deployed a Next.js 16 application on a Plesk server. The application is finally running after following guidance from this stack overflow posy: Deploy Next JS 14 on Plesk server

I also created a Passenegerfile.json in the root directory with the following configuration:

{
"environment": "production",
"max_pool_size": 20,
"min_instances": 1,
"max_requests": 8000,
"max_request_queue_size": 400,
"pool_idle_time": 0
}

However, the application continues to crash constantly, returning HTTP error 499. I'm tired of manually restarting the server to keep it running.

Here is relevant server log.

4184995/T39 age/Cor/CoreMain.cpp:1094: Checking whether to disconnect long-running connections for process 253380, application /var/www/vhosts/[sitename.com]/httpdocs (production)

Any help or suggestions would be greatly appreciated.
 
Back
Top