This page contains a list of common errors you may encounter using Humanitec and how to resolve them.
Cannot retrieve modules from CI pipeline
If your modules do not appear when you go to add modules to an environment, even though you have connected your CI pipeline, then please check the following:
- Have you added the snippet to your pipeline configuration to send the image to Humanitec? Is the YAML formatted properly?
- Have you added the Humanitec API token as a variable for your repository?
- Have you triggered a new build after following the previous steps?
If you’ve done all of this and it still doesn’t work, then please contact support.
Deployment failed (pre-configured Humanitec cluster)
Here are some common reasons why your environment could fail to deploy with Humanitec using the Humanitec-managed cluster. See below for troubleshooting around deploying to your own cluster.
Kubernetes connection error
The “Kubernetes connection error” may occur if Humanitec fails to connect to the Kubernetes API, or if the connection succeeds but Kubernetes fails to execute the deployment request.
- Try clicking the deployment button again.
- If the error persists, then please send a help request.
When Kubernetes begins to create pods for your modules, the pod could break due to an improper configuration in the module’s Dockerfile or its configurations.
Check to see if your module’s Dockerfile runs properly. You can see this in the Humanitec interface by going to your app, clicking on the module, and going to its Logs section.
Failure to connect to an external resource
If your app depends on a resource not deployed with Humanitec, such as an external database or API, and Humanitec cannot connect to it, then the deployment will fail.
- We recommend enabling logging in your app. You can view these logs in the Humanitec interface by going to your app, clicking on the module, and then going to its Logs section.
Cannot access module at its public URL
If you exposed your module with a public URL but get an error when you try to access it, then check the module’s configuration page (i.e., by clicking on it) to see if the ports you exposed match the ones exposed in its Dockerfile.