Browse docs

Troubleshooting

Common issues and their solutions.

Installation Issues

Docker Container Won't Start

Symptoms: Container exits immediately or fails health check

Solutions:

  1. Check logs:
docker-compose logs -f

Once the Manager is running, Settings → Logs shows the Manager's own log lines in-app, plus the OpenCode server's stdout/stderr, which the Manager captures in memory and does not forward to the container console — so those OpenCode-server lines are visible in-app only. If the container or the Manager itself fails before the Manager's HTTP server is up, use docker-compose logs; the in-app viewer has nothing to show at that point.

  1. Verify Docker resources (2GB RAM minimum)

  2. Check ports aren't in use:

lsof -i :5003
  1. Pull the image again:
docker compose pull
docker compose up -d

If you build from source, rebuild without cache instead: ./scripts/docker-upgrade.sh --full.

Installer Stops Before Starting

The installer checks Docker first and stops with the reason:

  • Docker is required: install Docker Desktop (macOS, Windows) or Docker Engine (Linux)
  • Docker is installed but not reachable: start Docker Desktop or the docker service; on Linux, make sure your user can run docker info without sudo
  • Docker Compose v2 is required: install the Compose plugin so docker compose works
  • Is a source checkout of OpenCode Manager: OCM_DIR points at a clone of the repository. Keep updating the clone with ./scripts/docker-upgrade.sh, or set OCM_DIR to another folder
  • Already installed from <folder>: a source checkout's container is running. Keep using it, or stop it there with docker compose down first. The installer starts with its own data and does not share the checkout's volumes
  • Already exists outside Docker Compose: a container named opencode-manager was started with docker run. Remove it with docker rm -f opencode-manager (its volumes are kept) and re-run the installer
  • Did not become healthy: check cd ~/opencode-manager && docker compose logs. On Linux, a PUID/PGID that collides with an account in the image stops startup; remove PUID/PGID from .env, or set free ids

Reset a Broken OpenCode Binary

Symptoms: Container won't start after an OpenCode upgrade, or the OpenCode settings show a malformed binary

OpenCode versions installed from Settings live in their own named volume (opencode-bin); the bundled version is part of the image. On start, the entrypoint already removes a persisted binary that is malformed or outside the supported range. If a persisted version still misbehaves, remove only that volume so the container falls back to the bundled binary, without touching the workspace or database volumes:

docker-compose down
# <project> is the Compose project name, usually the directory containing docker-compose.yml
docker volume rm <project>_opencode-bin
docker-compose up -d

Or via the package scripts:

pnpm docker:down
docker volume rm <project>_opencode-bin
pnpm docker:up

Do not use docker-compose down -v (or pnpm docker:reset) here: that also deletes the workspace and database volumes.

Port Already in Use

Symptoms: Error about port 5003, 5004, 5100, or 5101 being in use

Docker Compose publishes the Manager (5003), the preview gateway (5004), and two dev-server ports (5100, 5101); startup fails if any of them is taken.

Solutions:

  1. Find process using the ports:
lsof -i :5003 -i :5004 -i :5100 -i :5101
  1. Stop the process or change port in docker-compose.yml:
ports:
  - "8080:5003"  # Use different host port

Then add the new URL to the allowed origins in .env, or sign-in fails with an invalid-origin error:

AUTH_TRUSTED_ORIGINS=http://localhost:8080
PASSKEY_ORIGIN=http://localhost:8080

If you remap the preview port (5004), set PREVIEW_PUBLIC_URL to the new public origin of the preview gateway.

Permission Denied Errors

Symptoms: Container can't write to volumes

Startup tolerates workspace directories that already exist with wrong ownership; permission errors then appear on the first write into the directory rather than at startup.

Solutions:

  1. In Docker, the entrypoint re-owns /app/data and /workspace on every start, so a host-side chown is overwritten. When you bind-mount a host directory with OCM_WORKSPACE_HOST_PATH, set PUID and PGID in .env to the host user that owns it:
PUID=1000
PGID=1000
  1. For local development, fix ownership of the local directories:
sudo chown -R $(id -u):$(id -g) ./workspace ./data

Authentication Issues

Can't Log In

Solutions:

  1. Clear browser cookies
  2. Try incognito/private mode
  3. Outside Docker, check AUTH_SECRET is set in production
  4. Verify AUTH_TRUSTED_ORIGINS includes the exact URL in your address bar; localhost and 127.0.0.1 are different origins. Signing in from your phone at http://<lan-ip>:5003 needs that origin listed; the installer adds it when you allow network sign-in

Session Keeps Expiring

Solutions:

  1. Ensure AUTH_SECRET is persistent across restarts. In Docker, the generated secret lives in the opencode-data volume, so keep that volume
  2. Check browser isn't blocking cookies
  3. Verify AUTH_SECURE_COOKIES=false if using HTTP

OAuth Redirect Error

Solutions:

  1. Verify callback URL matches exactly in provider settings
  2. Check for trailing slashes
  3. Ensure protocol matches (http vs https)

Passkey Not Working

Solutions:

  1. Verify PASSKEY_RP_ID matches your domain
  2. Check PASSKEY_ORIGIN includes correct protocol and port
  3. Try a different browser
  4. Ensure WebAuthn is supported

Password Reset Not Working

Solutions:

  1. Set all required variables:
ADMIN_EMAIL=[email protected]
ADMIN_PASSWORD=new-password
ADMIN_PASSWORD_RESET=true
  1. Recreate the container so it picks up the new environment variables:
docker compose up -d --force-recreate app
  1. Remove ADMIN_PASSWORD_RESET=true and recreate the container again:
docker compose up -d --force-recreate app

Git Issues

Clone Fails for Private Repository

Solutions:

  1. Configure GitHub PAT in Settings > Git > Credentials
  2. Ensure PAT has repo scope
  3. Check PAT hasn't expired

Push/Pull Fails

Solutions:

  1. Verify GitHub PAT is valid
  2. Check PAT has write permissions
  3. Verify remote URL: git remote -v

Worktree Creation Fails

Solutions:

  1. Ensure branch doesn't already exist
  2. Check disk space
  3. Verify repo isn't in detached HEAD state

Chat Issues

Messages Not Sending

Solutions:

  1. Check OpenCode server is running:
docker exec opencode-manager ps aux | grep opencode
  1. Verify model is configured
  2. Check API key is valid

Streaming Stops Unexpectedly

Solutions:

  1. Check network connection
  2. Look for errors in browser console (F12)
  3. Check container logs for errors

File Mentions Not Working

Solutions:

  1. Ensure repository is selected
  2. Check file exists
  3. Refresh the file browser

Custom commands missing from /

Commands load per project the first time OpenCode opens it, and the list refreshes automatically, including after a reconnect. Wait a moment or reload the page; restarting OpenCode is not needed.

File Browser Issues

Files Not Loading

Solutions:

  1. Refresh the page
  2. Check repository is properly cloned
  3. Verify workspace volume is mounted

Upload Fails

Solutions:

  1. Check file size
  2. Verify write permissions
  3. Check browser console for errors

Performance Issues

Slow Response Times

Solutions:

  1. Check Docker resources:
docker stats
  1. Clear old sessions
  2. Use /compact to reduce session size

High Memory Usage

Solutions:

  1. Limit session count
  2. Delete unused sessions
  3. Restart container:
docker-compose restart

Database Errors

Solutions:

  1. Stop the container without removing it:
docker compose stop app
  1. Back up the data directory from the stopped container (DATABASE_PATH=/app/data/opencode.db in Compose), including any SQLite WAL/SHM sidecar files:
mkdir -p ./opencode-data-backup
docker cp opencode-manager:/app/data/. ./opencode-data-backup/
  1. Start the container again:
docker compose start app

Mobile Issues

Keyboard Doesn't Close

Solutions:

  1. Tap outside input field
  2. Update device OS
  3. Try Safari on iOS

PWA Won't Install

Solutions:

  1. iOS: Must use Safari
  2. Android: Must use Chrome
  3. Check HTTPS is enabled

Touch Gestures Not Working

Solutions:

  1. Start the swipe within 30px of the screen edge
  2. Swipe at least 80px
  3. Check no UI element is blocking

Stuck on an old version

Tap Reload in the update banner at the top of the app. If no banner appears, close and reopen the app.

Getting More Help

If your issue isn't covered:

  1. Check GitHub Issues
  2. Search GitHub Discussions
  3. Open a new issue with:
    • Steps to reproduce
    • Expected vs actual behavior
    • Container logs: docker-compose logs — required when the Manager fails to start; Settings → Logs in-app covers the same Manager lines plus captured OpenCode server output once the Manager is up
    • Browser console errors
    • Environment info (OS, browser, Docker version)