The container started but is not listening on a port
I am encountering an issue when trying to deploy via AI App Hosting on Meridiam; the following error appears at the end:
[...]
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,
-
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 -
Thank you!
0 -
Sure thing!
0 -
This case is specific to the issue in the Meridian environment.
0 -
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 -
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.
Comments
6 comments