Skip to main content
Supported Regions:上海

Deployment Failure Related

Why Does It Run Locally but Fail to Deploy on CloudBase?​

For local debugging, we recommend using local Docker. If your local development and debugging are not Docker-based, the following issues may occur when deploying directly to CloudBase:

  • While all dependencies and extensions are complete locally during local execution, the Dockerfile lacks the correct dependency installation commands. Therefore, dependencies are not missing during local runs, but errors occur when deploying to CloudBase due to dependency deficiencies.
  • During local execution, it connects to a local database (address set to local IP or localhost). When deployed to CloudBase, the database address is not updated to the cloud-based database address, causing deployment failure due to inability to connect to the database.
  • The runtime environment used locally (such as JDK/python versions) is inconsistent with the runtime environment defined in the Dockerfile.

How to handle the error message "Readiness probe failed: dial tcp xx.xx.xx.xx:xxx: connect: connection refused"?​

Health check failure / port connection failure.

  • The service starts properly, but the port number is incorrectly entered. The actual port does not match the one specified during release, causing the system to incorrectly determine that the deployment has failed.
  • The service starts properly, but it is not listening on any local port at 0.0.0.0, causing the system to determine that the deployment has failed.
  • The service starts successfully but repeatedly restarts with unstable processes, resulting in unstable port connections and health check failures. Please investigate code issues by reviewing logs or consider whether the selected container specification is too small, causing memory OOM.
  • If your Dockerfile contains multiple independent CMD commands, note that this is incorrect! Only the last CMD command will be executed, and all previous ones will be ignored, causing application errors. Refer to Docker's official documentation on the CMD command.
  • Check whether the port exposed in the Dockerfile is inconsistent with the port configured in the service.

During local debugging, you can use commands such as netstat to check whether the locally listened port matches the port configured in the CloudBase service.

Deployment failed, but the business logs show it is already running normally?​

Check whether the port in the service settings matches the actual project port. If the service starts properly but the port number is incorrectly entered, causing the actual port to differ from the one specified during release, the system will incorrectly determine that the deployment has failed, and service calls will also result in errors.

How to handle the error message "check pod status is not ok"?​

Please first check the following information:

  • The service repeatedly restarts due to code issues, resulting in an unstable state. Please investigate the code issues yourself.
  • If the service does not repeatedly restart, please submit a ticket for us to investigate.

How to handle the error message "Back-off restarting failed container"?​

The service fails to start due to code issues. Please investigate the code problems yourself using service logs. If no service logs are collected, check whether the log collection path for the service is configured correctly.

Why does the deployed eggjs service repeatedly restart when running npm run start?​

Remove the process daemon parameter --daemon.

  • Before change: "start": "egg-scripts start --daemon --title=node-server",
  • After change: "start": "egg-scripts start --title=node-server"

Why are the environment variables referenced in the Dockerfile not taking effect?​

During the build or deployment phase, the service is not ready, so environment variables cannot be referenced.

Why are the private network addresses of other cloud products like MySQL/Redis referenced in the Dockerfile not taking effect?​

During the build/deployment phase, the service is not ready, so accessing other cloud products via private network addresses is not possible at this time.

How to handle the error message "err=[ResourceUnavailable.ClusterInAbnormalState][err=cloudrun cluster state is invalid(cluster state is deleted)]"?​

Underlying abnormality, please submit a ticket to contact us for assistance.

Does embedding a webview in a mini-program support calling CloudBase private network addresses?​

Not supported. The mini-program client's private network and the CloudBase server's private network are not in the same network space; they cannot call each other.

How to troubleshoot on your own when the pipeline executes normally but the service fails to start?​

  • Check the service startup logs for any obvious errors.
  • Customers can deploy the verification program locally using docker to check if there are any startup issues.

Error encountered when accessing the service: CERTIFICATE_VERIFY_FAILED​

Refer to Usage Notes, which requires the customer's service Dockerfile and customer code to trust the certificate.

Why does the service listening on 127.0.0.1:80 work locally but fails to start when deployed to CloudBase?​

After modifying the listening port to 0.0.0.0:80, redeploy the service.