Troubleshooting

Common problems when installing and running OpsVibes, and how to fix them.

Check the status

See whether the panel and Traefik are running, and read the latest logs:

docker ps --filter name=opsvibes

docker logs --tail 100 opsvibes

Port 80 or 443 is already in use

A server that once ran Nginx, Apache or another control panel keeps ports 80/443 busy, so Traefik cannot start. Find the process using them:

sudo ss -tlnp | grep -E ':(80|443|3000)\s'

Stop and disable that service (for example sudo systemctl disable --now nginx), then restart the panel with docker restart opsvibes.

The panel does not open on port 3000

• Check the server firewall (ufw or firewalld) and your cloud provider's firewall. See Network ports.
• Check that Docker is running:

sudo systemctl status docker

SELinux on Rocky, AlmaLinux, RHEL

With SELinux enforcing, the panel container may be denied access to the Docker socket, and the log shows permission denied for /var/run/docker.sock.

getenforce

The install script already handles this. If you installed with Docker, use the command with --security-opt label=disable from the Rocky / AlmaLinux tab on the Installation page.

HTTPS certificate is not issued

• The A record does not point to the right IP yet, or DNS has not propagated. Check with dig +short as shown in Domain and HTTPS.
• Port 80 is blocked from outside. Let's Encrypt needs port 80 to verify the domain.
• The domain is proxied by Cloudflare. Switch it to DNS only and try again.
• Let's Encrypt limits how many certificates a domain can get per week. If you retried many times, wait a few hours.

Lost the setup token

The setup token stays in a file on the server until the first admin account is created:

sudo cat /etc/opsvibes/setup.token

It is also printed in the opsvibes container log every time the panel starts.