Skip to content

Troubleshooting

Common issues and solutions for Sproobo

This guide covers common issues you might encounter when using Sproobo and how to resolve them.

Deployment Issues

Deployment Fails to Start

Symptoms

  • Deployment status shows "Failed" or "Error"
  • Application doesn't respond to requests
  • Health checks fail
  1. 1

    Check Logs

    View deployment logs in Deployment → Logs to see error messages.
  2. 2

    Verify Environment Variables

    Ensure all required environment variables are set correctly.
  3. 3

    Check Health Check Endpoint

    Verify your health check endpoint is responding correctly.
  4. 4

    Review Dockerfile

    Ensure your Dockerfile is correctly configured and the application starts properly.

Build Failures

Common Causes

  • Syntax errors in Dockerfile
  • Missing dependencies in package.json or requirements.txt
  • Network issues during build
  • Build timeout (default: 15 minutes)
  1. 1

    View Build Logs

    Check build logs in Deployment → Logs → Build Logs to see specific errors.
  2. 2

    Test Build Locally

    Test your Dockerfile locally: docker build -t test .
  3. 3

    Optimize Dockerfile

    Ensure your Dockerfile follows best practices for caching and size.

Server Issues

Server Not Provisioning

Possible Causes

  • Insufficient Hetzner API permissions
  • Resource limits exceeded
  • Hetzner account issues
  • Invalid server configuration
  1. 1

    Check API Token

    Verify your Hetzner API token is valid and has read/write permissions.
  2. 2

    Check Resource Limits

    Ensure you haven't exceeded your Hetzner account limits.
  3. 3

    Verify Account Status

    Check your Hetzner account status and billing information.

Server Unreachable

Troubleshooting Steps

  • Check server status in Sproobo dashboard
  • View server logs for errors
  • Verify firewall rules are correct
  • Check Hetzner console for server status

DNS and Domain Issues

Domain Not Resolving

  1. 1

    Check DNS Propagation

    Use DNS propagation tools to verify DNS records are propagated.
  2. 2

    Verify DNS Records

    Ensure DNS records match what Sproobo provided.
  3. 3

    Wait for Propagation

    DNS changes can take up to 48 hours to fully propagate.

SSL Certificate Issues

Common SSL Issues

  • Certificate pending: Wait for DNS propagation
  • Certificate expired: Check automatic renewal status
  • Mixed content: Ensure all resources use HTTPS

Getting Help

Support Resources

  • Documentation: Browse other documentation pages
  • Community: Join our Discord or community forum
  • Email Support: Contact support@sproobo.com
  • GitHub Issues: Report bugs on GitHub

Next Steps

If you need additional help: