Common Errors Reference

A comprehensive list of error codes and messages you may encounter in OEC.sh, with quick solutions.

Deployment Errors

DEP001: Build Failed

Message: Build process failed

Cause: Error during Docker image build.

Solution:

1. Check deployment logs for specific error
2. Verify requirements.txt has valid packages
3. Ensure Dockerfile (if custom) is valid
4. See Deployment Failures

DEP002: Git Clone Failed

Message: Failed to clone repository

Cause: Cannot access Git repository.

Solution:

1. Verify Git connection is active: Settings → Git Connections
2. Check repository URL is correct
3. Ensure branch exists
4. Regenerate access token if expired

DEP003: Container Start Failed

Message: Container failed to start

Cause: Odoo container crashed on startup.

Solution:

1. Check Odoo logs for specific error
2. Verify environment variables
3. Ensure database is accessible
4. Check for port conflicts

DEP004: Health Check Failed

Message: Health check timed out

Cause: Odoo didn't respond within timeout period.

Solution:

1. Check if Odoo started successfully in logs
2. Verify server has sufficient resources
3. Increase health check timeout if needed
4. Check for long-running startup operations

Database Errors

DB001: Connection Refused

Message: Could not connect to database server

Cause: PostgreSQL is not accessible.

Solution:

1. Verify database container is running
2. Check database credentials
3. Restart the environment
4. See Database Errors

DB002: Authentication Failed

Message: Password authentication failed for user

Cause: Invalid database credentials.

Solution:

1. Check DB_USER and DB_PASSWORD in environment variables
2. Verify user exists in database
3. Reset database password if needed

DB003: Database Does Not Exist

Message: Database "dbname" does not exist

Cause: Target database hasn't been created.

Solution:

1. OEC.sh creates databases automatically
2. Check environment configuration
3. Try redeploying the environment
4. Contact support if persists

DB004: Out of Memory

Message: FATAL: out of memory

Cause: PostgreSQL ran out of allocated memory.

Solution:

1. Increase RAM allocation: Environment → Settings → Resources
2. Enable PgBouncer for connection pooling
3. Optimize memory-heavy queries
4. Check for memory leaks in custom code

DB005: Lock Wait Timeout

Message: Lock wait timeout exceeded

Cause: Transaction blocked by another transaction.

Solution:

1. Check for long-running transactions
2. Identify blocking queries
3. Kill stuck transactions if safe
4. Review application transaction handling

Backup Errors

BKP001: Backup Creation Failed

Message: Failed to create backup

Cause: Error during database dump or filestore backup.

Solution:

1. Check disk space on server
2. Verify database is accessible
3. Check backup logs for specific error
4. See Backup Issues

BKP002: Upload Failed

Message: Failed to upload backup to storage

Cause: Cannot upload to configured storage provider.

Solution:

1. Verify storage provider credentials
2. Test connection: Settings → Storage Providers → Test
3. Check network connectivity
4. Verify bucket/container exists

BKP003: Restore Failed

Message: Failed to restore backup

Cause: Error during backup restoration.

Solution:

1. Verify backup file is not corrupted
2. Check target has sufficient disk space
3. Ensure Odoo versions are compatible
4. See Restore Issues

BKP004: Invalid Backup Format

Message: Invalid or corrupted backup file

Cause: Backup file is damaged or incompatible.

Solution:

1. Download and verify backup locally
2. Try a different backup
3. Check storage provider for issues
4. Contact support with backup details

Domain/SSL Errors

SSL001: Certificate Issuance Failed

Message: Failed to issue SSL certificate

Cause: Let's Encrypt couldn't verify domain ownership.

Solution:

1. Verify DNS points to correct server
2. Wait for DNS propagation
3. Check domain isn't rate-limited
4. See SSL Errors

SSL002: Certificate Expired

Message: SSL certificate has expired

Cause: Auto-renewal failed.

Solution:

1. Check domain configuration
2. Verify DNS is still correct
3. Force renewal: Environment → Domains → Refresh SSL
4. Contact support if issue persists

DNS001: Domain Verification Failed

Message: Could not verify domain ownership

Cause: DNS records don't match expected configuration.

Solution:

1. Compare DNS records with required configuration
2. Remove conflicting records
3. Wait for DNS propagation
4. See DNS Issues

Resource Errors

RES001: Insufficient CPU

Message: CPU limit exceeded

Cause: Environment needs more CPU resources.

Solution:

1. Scale up CPU: Environment → Settings → Resources
2. Optimize CPU-intensive operations
3. Consider running during off-peak hours

RES002: Insufficient Memory

Message: Memory limit exceeded

Cause: Environment needs more RAM.

Solution:

1. Scale up RAM: Environment → Settings → Resources
2. Enable PgBouncer to reduce memory usage
3. Check for memory leaks
4. Reduce worker count if needed

RES003: Disk Space Full

Message: No space left on device

Cause: Server disk is full.

Solution:

1. Check disk usage: Server → Metrics
2. Remove unused environments
3. Clean up old backups
4. Scale up disk allocation

RES004: Quota Exceeded

Message: Organization quota exceeded

Cause: Reached plan limits.

Solution:

1. Check current usage: Settings → Usage
2. Delete unused resources
3. Upgrade plan: Settings → Billing

Permission Errors

AUTH001: Unauthorized

Message: Authentication required

Cause: User not logged in or session expired.

Solution:

1. Log in again
2. Check if session timed out
3. Clear browser cookies and retry

AUTH002: Permission Denied

Message: You don't have permission to perform this action

Cause: User lacks required permission.

Solution:

1. Check your role in the organization
2. Contact organization admin for access
3. See Teams & Permissions

AUTH003: Organization Access Denied

Message: You are not a member of this organization

Cause: Trying to access organization you're not part of.

Solution:

1. Request invitation from organization admin
2. Check you're logged into correct account
3. Switch to correct organization if member of multiple

API Errors

API001: Rate Limited

Message: Too many requests

Cause: Exceeded API rate limit.

Solution:

1. Wait before retrying
2. Reduce request frequency
3. Contact support for higher limits

API002: Invalid Request

Message: Invalid request parameters

Cause: API request has invalid data.

Solution:

1. Check request body format
2. Verify required fields are present
3. Check data types match schema

API003: Resource Not Found

Message: Resource not found

Cause: Requested resource doesn't exist.

Solution:

1. Verify resource ID is correct
2. Check resource wasn't deleted
3. Ensure you have access to the resource

Server Errors

SRV001: Connection Failed

Message: Could not connect to server

Cause: SSH connection to server failed.

Solution:

1. Verify server is online
2. Check SSH credentials
3. Test connection: Server → Test Connection
4. Check firewall allows port 22

SRV002: Server Unreachable

Message: Server is unreachable

Cause: Network connectivity issue.

Solution:

1. Verify server IP is correct
2. Check server is powered on
3. Verify network/firewall configuration
4. Contact hosting provider if needed

SRV003: Docker Error

Message: Docker operation failed

Cause: Error executing Docker command.

Solution:

1. Check server has Docker installed
2. Verify Docker daemon is running
3. Check disk space for Docker
4. Review Docker logs on server

Quick Reference Table

Still Having Issues?

If you encounter an error not listed here or need additional help:

1. Note the Error Code - Include it in your support request
2. Collect Logs - Download relevant logs from the dashboard
3. Contact Support - Email [email protected]