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

Symptoms

  • Deployment status shows "Failed"
  • Site does not respond after deploy
  • Health check fails after deployment
  1. 1

    Check Deployment Logs

    Open the site in the dashboard, go to the Deployments tab, click the failed deployment, and review the full log output. The error is usually visible in the build or start phase.
  2. 2

    Verify Environment Variables

    Check that all required environment variables are set. Missing or incorrect values (e.g. a wrong database URL) are a common cause of startup failures.
  3. 3

    Test Your Build Locally

    Run your build commands locally against the same Node.js version to reproduce any build errors before pushing to the server.
  4. 4

    Check the Start Command

    For Node.js and worker sites, confirm the start command is correct and the app listens on the configured port.
  5. 5

    For Docker Sites — Check docker-compose.yml

    Verify your docker-compose.yml is valid and that all referenced images and build steps work correctly when run locally.

Server Issues

Server Not Provisioning

Possible Causes

  • Hetzner API token does not have read/write permissions
  • Hetzner account resource limits exceeded
  • Hetzner account billing issue
  1. 1

    Check Your Hetzner API Token

    Verify the token has "Read & Write" permissions in the Hetzner Cloud Console. Read-only tokens cannot create servers.
  2. 2

    Check Hetzner Resource Limits

    Log in to the Hetzner Cloud Console and check if you have reached your account's server or resource limits.
  3. 3

    View Provisioning Log

    On the server detail page in Sproobo, open the provisioning log to see which phase failed and what error occurred.

Server Unreachable

Troubleshooting Steps

  • Check server status in the Sproobo dashboard
  • Verify firewall rules are not blocking required ports
  • Check the Hetzner Cloud Console to confirm the server is running

DNS and Domain Issues

Domain Not Resolving

  1. 1

    Check DNS Propagation

    Use a tool like dig or an online DNS checker to verify your DNS records have propagated. DNS changes can take up to 48 hours to propagate globally, though typically much faster.
  2. 2

    Verify DNS Records

    Confirm your A record points to the correct server IP address shown in Sproobo.

SSL Certificate Issues

Common SSL Issues

  • Certificate pending: DNS must be fully propagated before Let's Encrypt can issue a certificate. Wait for propagation and redeploy.
  • Certificate failed: Ensure your domain's A record points to the correct server IP. Let's Encrypt verifies domain ownership via HTTP.
  • Certificate expired: Automatic renewal should prevent this. If renewal failed, check the site's SSL status and trigger a redeployment to re-run the cert process.

Getting Help

Support Resources

  • Documentation: Browse the other documentation pages for detailed guides
  • Support: Contact us via the in-app Support page or at support@sproobo.com