Error Messages Reference
This page lists common error messages you might encounter, what they mean, and how to fix them.
Deployment Errors
DOCKER_BUILD_FAILED
Message: Docker build failed: [error details]
Cause: The Docker build process encountered an error
Solutions:
- Check the build logs for specific error messages
- Verify your Dockerfile syntax is correct
- Ensure all required files are present in the build context
- Check for network issues when downloading dependencies
GIT_CLONE_FAILED
Message: Failed to clone repository: [error details]
Cause: TurboV couldn't access or clone your repository
Solutions:
- Verify the GitHub App has access to the repository
- Check if the repository URL is correct
- Ensure the branch exists
- Try reconnecting your GitHub account
DOCKERFILE_NOT_FOUND
Message: No Dockerfile found and auto-detection failed
Cause: TurboV couldn't find a Dockerfile or determine how to build your app
Solutions:
- Add a Dockerfile to your repository root
- Enable auto-detection in environment settings
- Specify a custom Dockerfile path in settings
MISSING_GITHUB_TOKEN
Message: Deployment requires GitHub App installation
Cause: The repository requires authentication but no token was provided
Solutions:
- Install the TurboV GitHub App on your repository
- Ensure the app has read access to the repository
BUILD_TIMEOUT
Message: Build exceeded maximum duration
Cause: The build took longer than the allowed time limit
Solutions:
- Optimize your build process
- Use build caching effectively
- Split into smaller builds if possible
Runtime Errors
CONTAINER_START_FAILED
Message: Container failed to start: [error details]
Cause: The application container couldn't start properly
Solutions:
- Check application logs for startup errors
- Verify all required environment variables are set
- Ensure the application listens on the correct port
- Check for missing dependencies or files
CONTAINER_EXITED_UNEXPECTEDLY
Message: Container exited with code [X]
Cause: The application crashed after starting
Solutions:
- Review runtime logs for crash details
- Check for unhandled exceptions in your code
- Verify database connections are stable
- Look for out-of-memory errors
PORT_ALREADY_IN_USE
Message: Port [X] is already in use
Cause: Another process is using the required port
Solutions:
- Stop the conflicting process
- Change the port your application uses
- Check for zombie containers:
docker ps -a
OUT_OF_MEMORY
Message: Container killed due to memory limit
Cause: The application exceeded its memory allocation
Solutions:
- Optimize memory usage in your application
- Fix memory leaks if present
- Request a higher memory limit
- Scale to a larger server
Connection Errors
AGENT_CONNECTION_LOST
Message: Lost connection to agent
Cause: The server agent stopped responding
Solutions:
- Check if the server is still running
- Verify the agent service is active
- Check network connectivity
- Review agent logs for errors
AUTH_TOKEN_EXPIRED
Message: Authentication token has expired
Cause: Your session or API token is no longer valid
Solutions:
- Log out and log back in
- Refresh the page
- Generate a new API token if using the API
SERVER_UNREACHABLE
Message: Cannot reach server at [address]
Cause: The backend cannot connect to your server
Solutions:
- Verify the server is running
- Check firewall rules
- Ensure the agent is running
- Verify network connectivity
Domain & SSL Errors
DNS_VERIFICATION_FAILED
Message: DNS verification failed for [domain]
Cause: The domain's DNS records don't point to your server
Solutions:
- Verify DNS A/CNAME records are correct
- Wait for DNS propagation (up to 48 hours)
- Check for typos in the domain name
- Use a DNS checker to verify records
SSL_CERTIFICATE_FAILED
Message: SSL certificate provisioning failed for [domain]
Cause: Let's Encrypt couldn't issue a certificate
Solutions:
- Ensure DNS is properly configured
- Verify port 80 is accessible
- Check for CAA records blocking Let's Encrypt
- Try removing and re-adding the domain