Troubleshooting
Common issues and solutions for deploying and managing MCP servers on agnexus.
Deployment Issues
Deployment Fails Immediately
Symptoms: Deployment fails right after starting
Possible Causes:
- Invalid Dockerfile
- Missing dependencies in requirements.txt/package.json
- Syntax errors in code
- Port not configured correctly
Solutions:
- Check deployment logs for specific error messages
- Verify your Dockerfile is valid
- Test your code locally first
- Ensure port 8080 is exposed and your app listens on it
Build Timeout
Symptoms: Deployment times out during build phase
Possible Causes:
- Large dependencies taking too long to install
- Network issues downloading packages
- Complex build steps
Solutions:
- Optimize your Dockerfile (use multi-stage builds)
- Pre-build dependencies if possible
- Reduce image size
- Contact support if consistently timing out
Server Won't Start
Symptoms: Deployment succeeds but server doesn't respond
Possible Causes:
- Application crashing on startup
- Wrong entry point
- Missing environment variables
- Port configuration issue
Solutions:
- Check runtime logs
- Verify environment variables are set
- Test locally with same configuration
- Review health check endpoint
Runtime Issues
Server Returns 502 Errors
Symptoms: Requests return 502 Bad Gateway
Possible Causes:
- Server crashed
- Health check failing
- Resource limits exceeded
Solutions:
- Check server logs
- Verify health check endpoint works
- Review resource usage
- Restart the server
High Memory Usage
Symptoms: Server using too much memory
Possible Causes:
- Memory leaks in code
- Large data processing
- Inefficient algorithms
Solutions:
- Profile your application
- Optimize data structures
- Implement pagination for large datasets
- Consider upgrading plan
Slow Response Times
Symptoms: Requests take too long
Possible Causes:
- Blocking I/O operations
- External API delays
- Database query issues
- Resource constraints
Solutions:
- Use async/await patterns
- Implement caching
- Optimize database queries
- Review external API calls
GitHub Integration Issues
Auto-Deploy Not Working
Symptoms: Pushes to GitHub don't trigger deployments
Possible Causes:
- Webhook not configured
- Auto-deploy disabled
- Webhook delivery failures
Solutions:
- Check GitHub webhook settings
- Verify auto-deploy is enabled
- Review webhook delivery history
- Reconnect GitHub if needed
"Repository Not Found" Error
Symptoms: Can't find repository when browsing
Possible Causes:
- Private repo without GitHub connection
- Incorrect repository URL
- Token permissions issue
Solutions:
- Connect your GitHub account
- Verify repository URL
- Check token has repo access
- Try public repository URL format
Authentication Issues
"Authentication Required" Errors
Symptoms: Requests fail with auth errors
Possible Causes:
- Missing access key
- Invalid access key
- Key expired or revoked
Solutions:
- Verify access key is included in requests
- Check key is valid and not expired
- Regenerate key if needed
- Review authentication documentation
Platform-Specific Issues
Port 8080 Not Working
Symptoms: Can't connect to server on port 8080
Possible Causes:
- Server not listening on 8080
- Wrong port in Dockerfile
- Firewall blocking
Solutions:
- Verify
EXPOSE 8080in Dockerfile - Check app listens on
0.0.0.0:8080 - Test locally first
- Review platform requirements
HTTP/SSE Transport Errors
Symptoms: MCP client can't connect
Possible Causes:
- Server not using HTTP/SSE transport
- Wrong transport configuration
- Protocol errors
Solutions:
- Verify server uses Streamable HTTP with SSE
- Check transport configuration
- Review MCP protocol requirements
- Test with MCP Inspector
Getting Help
If you're still experiencing issues:
- Check Logs: Review deployment and runtime logs
- Documentation: Search our docs for specific topics
- Community: Ask in our community forums
- Support: Contact support through the dashboard