Common problems
Read the messages of a service. Replace server with the name of the service:
cd /opt/buuckdocker compose logs -f server| Problem | Cause and correction |
|---|---|
The command shows Run as root. |
Run the command with sudo, or sign in as root. |
Docker shows unauthorized or denied for a pull. |
The registry user name or the license key is not correct, or the credentials do not match your edition. Start credentials pull from project buuck. Pro credentials pull from project buuck-pro. Run buuck install again with the values from your purchase email. Put the registry user name in single quotes if you type it in a shell command. |
Docker shows manifest unknown for a pull. |
The value of BUUCK_VERSION is not correct, or the image path does not match your edition. Compare the value and the project with your email. |
Docker shows exec format error for a service. |
The processor of your VPS is not a 64-bit x86 processor. Use a different VPS. |
| The browser shows a certificate error. | The DNS records are not correct, or a proxy is active. Also make sure that port 80 is open. |
The db-migrate service shows exited (1). |
Read the messages of the service. Then start it again with docker compose up -d db-migrate. |
| The dashboard shows a connection error. | The value of API_DOMAIN or DASHBOARD_DOMAIN in /opt/buuck/.env is not correct. Correct the value. Then run docker compose up -d --force-recreate. |
| The emails do not arrive. | The SMTP values are not correct. Read the messages of the server service. |
| A Start install shows no “Powered by Buuck” line, or a Pro install still shows it. | You may have pulled the wrong edition. Check the image names in docker compose ps and in /opt/buuck/compose.yaml. Start uses project buuck. Pro uses project buuck-pro. |
| A service starts again and again. | The /opt/buuck/.env file has an empty value. Run buuck install again, or compare the file with a working install. |
| The install stops because a value is missing. | You used --yes without all required flags or environment variables. Add the missing values, or run without --yes. |
New Compose services are missing after buuck update. |
Run buuck upgrade, then buuck install (keep secrets), then buuck update if needed. |
| The log viewer page stays blank, or the messages do not update. | The reverse proxy buffers the live stream. The Caddyfile must have flush_interval -1 for the logs domain. Then run docker compose up -d --force-recreate caddy. |
| The log viewer shows a login error. | The password is DOZZLE_PASSWORD in /opt/buuck/.env. The user name is admin. |
| The log viewer does not list a Buuck service. | The viewer only shows containers from the Compose project named buuck. Check docker compose ps in /opt/buuck. |
If a problem continues, send an email with the details to [email protected].