Troubleshooting

If your application URL returns an error or doesn’t load:

Possible Causes:

• Application is still deploying
• Application has crashed
• Resource limitations

Solutions:

1. Wait a few minutes if the application was recently deployed
2. Check application logs for errors
3. Ensure the application has sufficient resources
4. Restart the application from the dashboard
5. Verify that all required environment variables are set correctly

If your browser shows SSL/certificate warnings:

Possible Causes:

• New custom domain hasn’t completed verification
• SSL certificate is still being issued
• DNS configuration issues

Solutions:

1. Verify your DNS settings are correctly configured
2. Allow up to 24 hours for SSL certificate issuance and propagation
3. Ensure you’re using https:// in the URL
4. Check the domain verification status in the dashboard

If your application is loading slowly:

Possible Causes:

• Insufficient resources
• High database load
• Inefficient application code
• Network latency

Solutions:

1. Scale up your application resources
2. Enable caching if your application supports it
3. Optimize database queries and indexes
4. Consider deploying to a region closer to your users

If your application fails to deploy:

Possible Causes:

• Invalid configuration
• Resource constraints
• Temporary platform issues

Solutions:

1. Check the deployment logs for specific error messages
2. Verify that all required environment variables are correctly set
3. Ensure your resource tier is sufficient for the application
4. Try deploying again after a few minutes

If your deployment seems stuck for a long time:

Possible Causes:

• Large application data
• Network issues
• Platform resource constraints

Solutions:

1. For initial deployments, large applications may take up to 10 minutes
2. Check if there are any platform status notifications
3. Cancel the deployment and try again
4. Contact support if the issue persists

If your application deploys successfully but crashes shortly after:

Possible Causes:

• Missing or incorrect environment variables
• Application bugs
• Incompatible dependencies
• Resource limitations

Solutions:

1. Check application logs for error messages
2. Verify all required environment variables are set properly
3. Ensure your application has sufficient resources
4. For custom applications, verify compatibility with the container environment

If your application can’t connect to its database:

Possible Causes:

• Incorrect connection string
• Database service is not running
• Authentication issues

Solutions:

1. Verify database environment variables (host, user, password, database name)
2. Check if the database service is running
3. Restart both the application and database services
4. Ensure the database has not reached its connection limit

If database operations are slow:

Possible Causes:

• Insufficient resources
• Missing indexes
• Inefficient queries
• Database size issues

Solutions:

1. Scale up the database resources
2. Optimize database indexes
3. Review and optimize queries
4. Consider implementing caching
5. Purge unnecessary data or logs

If you experience data loss or corruption:

Possible Causes:

• Application bugs
• Disk space issues
• Unexpected shutdowns

Solutions:

1. Restore from a backup if available
2. Check for disk space issues
3. Verify application logs for errors during write operations
4. Contact support for assistance with data recovery

If an application update (rebuild) fails:

Possible Causes:

• Incompatible configuration
• Resource constraints
• Application data migration issues

Solutions:

1. Check logs for specific error messages
2. Verify that your configuration is compatible with the new version
3. Ensure sufficient resources for the update process
4. Try updating again after a few minutes
5. Contact support if the issue persists

If scaling your application causes issues:

Possible Causes:

• Application not designed for scaling
• Insufficient resources
• Configuration issues

Solutions:

1. Start with a small resource increase
2. Check application logs after scaling
3. Verify the application can utilize additional resources
4. Ensure database connections can handle increased load
5. Consider application-specific optimizations for scaling

If your custom domain doesn’t connect to your application:

Possible Causes:

• Incorrect DNS configuration
• Domain verification pending
• DNS propagation delay

Solutions:

1. Verify your DNS records match the ones provided in the dashboard
2. Check domain verification status in the dashboard
3. Allow up to 24-48 hours for DNS propagation
4. Test your DNS configuration using a tool like DNSChecker

If your site shows mixed content warnings:

Possible Causes:

• Resources loaded over HTTP instead of HTTPS
• Hardcoded URLs in application code

Solutions:

1. Update your application to use relative URLs or HTTPS URLs
2. Configure proper HTTP to HTTPS redirects
3. Check for hardcoded HTTP URLs in your application settings