Skip to main content

The container started but is not listening on a port

StoreHosting

I am encountering an issue when trying to deploy via AI App Hosting on Meridiam; the following error appears at the end:

[...]

✓ Generating static pages (4/4)
Finalizing page optimization ...
Collecting build traces ...
Route (app) Size First Load JS
┌ ○ / 804 B 103 kB
└ ○ /_not-found 991 B 103 kB
+ First Load JS shared by all 102 kB
├ chunks/255-40634877ae3e8e9d.js 45.7 kB
├ chunks/4bd1b696-c023c6e3521b1417.js 54.2 kB
└ other shared chunks (total) 1.9 kB
○ (Static) prerendered as static content
Applying the current configuration and starting the application.
The container started but is not listening on a port — it likely exited immediately. Check the start command (“npm run start”) and the application logs.

This server is running CloudLinux 9 and LiteSpeed; I performed the same deployment on another server without CloudLinux but with LiteSpeed and it worked correctly. Is there a configuration setting that might be preventing the port from being set?

Regards,

Comments

7 comments

Date Votes
  • cPRex Jurassic Moderator

    Hey there!  This is a known issue in Meridian that we're tracking as part of case CPANEL-55035.  I've added a link to this thread to that case so if I hear updates on my end I'll post them.

    I see this has already been resolved, which means it will likely be included in the next cPanel release.

    0
  • StoreHosting

    Thank you!

    0
  • cPRex Jurassic Moderator

    Sure thing!

    0
  • Alex

    Thanks for the clarification. Since this is already tracked under CPANEL-55035, it would be useful to confirm whether the fix applies specifically to the CloudLinux 9 environment or to AI App Hosting on Meridian more generally.

    For anyone hitting the same message in the meantime, comparing the cPanel/Meridian version and the deployment behavior before and after the relevant update should help confirm whether the issue is resolved rather than changing the application's start command unnecessarily.

    0
  • cPRex Jurassic Moderator

    This case is specific to the issue in the Meridian environment.

    0
  • StoreHosting

    We are in contact with the CloudLinux team; so far, the test deployment has worked, but issues persist when performing new deployments. If the deployment is made to an account that already has a running application, it is created but triggers a port error; if the deployment is made to a new account, it results in a container creation error.

    0
  • cPRex Jurassic Moderator

    The CloudLinux team isn't going to be able to resolve this as the issue is specific to Meridian.  Until that case is resolved I wouldn't expect things to work properly in that environment.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post