Skip to content

Troubleshooting

Look for the message or behaviour you see below. Each entry links to a page with the cause and the steps to fix it.

Getting started

  • Deployrr install errors: root user, sudo and architecture
    [ERROR] Do not run Deployrr as the root user. Run as a regular user with sudo privileges instead. · This installer must be run as root. · This installer requires root privileges. · Unsupported architecture: <arch>. Deployrr supports x86_64 and ARM64. · Required command not found: curl · Required command not found: tar · Failed to download binary · Download failed. Check your internet connection. · NAME is not in the sudoers file · sudo: npx: command not found · deployrr: command not found · Could not create link in /usr/local/bin. You may need to run via absolute path. · App 'NAME' not found
  • System Checks failed in Prerequisites (clock drift, username not found, Docker not running, docker0)
    System clock drift detected (... seconds off) · Time Synchronization Error · CRITICAL WARNING: Your system clock is drifted by ... seconds. · Network API unreachable for time check. Skipping time synchronization check. · Username ... not found · Docker not installed. Installing now... · Docker installed but not running · Docker installation failed · Could not determine IP of docker0 interface · System and Docker Checks - NOT DONE · System Checks fails on a Proxmox LXC or a distro that is not Debian, Ubuntu or Arch
  • Domain Checks failed in Prerequisites (ports 80 and 443, DNS records, orange cloud)
    Port 80 is not reachable from the internet · Port 443 is not reachable from the internet · Port 80 is reachable but something is already listening on it · Could not complete port 80 check. API may be unavailable. · Domain resolution failed (empty IP returned) · IP mismatch: WAN IP is ... but domain resolves to ... · Subdomain resolution failed (empty IP returned) · IP mismatch: WAN IP is ... but subdomain resolves to ... · Cloudflare proxy is probably enabled/orange-clouded for the A record (IPv6 detected) · Cloudflare proxy is probably enabled/orange-clouded for the CNAME record (IPv6 detected) · IP and Domain Checks - NOT DONE · Domain Checks fails after Traefik is already running
  • Deployrr shows "Requirements Not Met"
    Requirements Not Met (1) · Requirements Not Met (3) · The following requirements must be met before continuing: · Prerequisites - All steps must be completed · Disclaimers - Must be read and acknowledged (Prerequisites menu) · Hybrid Mode - Setup Mode must be Hybrid. Current: Local (Prerequisites menu) · License - Plus or Pro required. Current: Free (Prerequisites->Verify) · Socket Proxy - Must be running (Docker menu) · Traefik Production - Must be completed (Proxy menu) · Advanced Authentication - Authelia, Authentik, OAuth, or TinyAuth must be running (Security menu) · Required app not running · System type not compatible

Apps

  • Home Assistant behind Traefik: fix 400 Bad Request
    400: Bad Request · A request from a reverse proxy was received from 192.168.1.100, but your HTTP integration is not set-up for reverse proxies · Home Assistant works on http://HOME_ASSISTANT_IP:8123 but shows a 400 error on https://homeassistant.YOUR_DOMAIN · How do I put Home Assistant behind Traefik with Deployrr
  • Jellyfin app on LG webOS TV or Xbox shows error -27
    Jellyfin app on my LG TV shows error -27 when I add my server · Jellyfin Xbox app can't connect to my server · Jellyfin works in a web browser but not in the LG webOS app · The TV app fails before it shows the login page
  • Media app shows an empty library or no folders
    My Plex library is empty · Jellyfin library shows no movies or shows after adding a folder · Emby library is empty · The folder browser in Plex, Jellyfin or Emby shows no media folders · Sonarr or Radarr root folder is empty or does not list /data/media1 · Media is on my NAS but the app cannot see it
  • Nextcloud says Access through untrusted domain
    Access through untrusted domain · Please contact your administrator. If you are an administrator, edit the "trusted_domains" setting in config/config.php · Nextcloud shows an untrusted domain page on https://nextcloud.YOUR_DOMAIN · Nextcloud shows an untrusted domain page on http://SERVER_IP:PORT · Behind Nginx Proxy Manager, Nextcloud shows the same address for every visitor
  • Pi-hole will not start because port 53 is already in use
    Error response from daemon: driver failed programming external connectivity on endpoint pihole: failed to bind host port for 0.0.0.0:53:172.18.0.18:53/tcp: address already in use · Pi-hole install fails and the pihole container does not start · Something else is already listening on port 53 · failed to bind host port for 0.0.0.0:67 ... address already in use
  • qBittorrent web UI says Unauthorized or won't open
    Unauthorized · qBittorrent login page says the username or password is wrong, even with admin and adminadmin · Your IP address has been banned after too many failed authentication attempts · This site can't be reached or connection refused on the qBittorrent port · qBittorrent VPN web page doesn't open, but the container is running · Sonarr or Radarr can't connect to qBittorrent
  • Sonarr, Radarr or Lidarr don't import finished downloads
    Import failed, path does not exist or is not accessible by Sonarr · Sonarr or Radarr download is finished but stuck in Activity > Queue · Download client places downloads in a folder that does not appear to exist inside the container · Remote Path Mappings warning in Sonarr or Radarr · Radarr or Lidarr will not import completed downloads from qBittorrent, SABnzbd, NZBGet or Transmission · Arr import fails with permission denied

Proxy and logins

  • Traefik can't get a Let's Encrypt certificate
    Unable to obtain ACME certificate · Failed to find zone · Possibly wrong Cloudflare API token. Ensure that your Scoped API Token has Zone/Zone/Read and Zone/DNS/Edit privileges. · Could not find DNS validation TXT record · Cannot get ACME client get directory. Possible DNS server issue. · Getting certificate failed with error 429 · You probably hit Let's Encrypt rate limit. Wait at least 24 hours and retry. · Staging certificate could not be verified. Try re-running Deployrr. · Real LetsEncrypt certificate could not be verified. · Real LetsEncrypt certificate could not be verified after restart. · Invalid Cloudflare token. Please check token permissions. · Port 443 is occupied. This is needed for Traefik. · Traefik Staging or Production stops with a red error · The browser still shows Not Secure after Traefik Production
  • One app behind Traefik shows 404, 502 or Gateway Timeout
    404 page not found · Bad Gateway · 502 Bad Gateway · Gateway Timeout · 504 Gateway Timeout · middleware "chain-NAME@file" does not exist · One app does not open at its https address, but your other apps behind Traefik do · There is no app-NAME.yml file for the app in the Traefik rules folder · Authelia, Authentik, TinyAuth, OAuth or the Traefik dashboard shows 404 page not found

Remote access and networking

  • Behind CG-NAT: your apps can't be reached from the internet
    Port 80 is not reachable from the internet · Port 443 is not reachable from the internet · You are not behind ISP CG-NAT - Carrier-grade NATs use a shared IP. · Router port forwards for 80 and 443 are set but nothing reaches your server · Router WAN IP starts with 100.64 to 100.127 · Router WAN IP is different from the IP a "what is my IP" site shows · Apps open at home but not from mobile data
  • Fix the UFW firewall on a VPS: apps can't reach the internet or show certificate errors
    SSL certificate problem: self-signed certificate · curl: (60) SSL certificate problem: self-signed certificate · Serving default certificate for request · local error: tls: bad record MAC · Apps on a VPS or dedicated server cannot connect to the internet, and features that call outside services fail · Your browser shows a certificate warning for your own domain
  • Traefik staging fails with unable to obtain ACME certificate on OPNsense
    Unable to obtain ACME certificate · Traefik staging step fails even though the Cloudflare records and port forwards are correct · You use OPNsense, a UDM or another advanced firewall and no certificate is issued · Cannot get ACME client get directory. Possible DNS server issue. · OPNsense redirects all DNS on your LAN to its own resolver

Storage

  • Rclone mount fails with "is not empty, use --allow-non-empty to mount anyway"
    Fatal error: failed to mount FUSE fs: "/media/rclone/NAME" is not empty, use --allow-non-empty to mount anyway · failed to mount FUSE fs is not empty · use --allow-non-empty to mount anyway · Mount verification failed · Failed to start service. Check · My NAS share does not show up in the Rclone mount folder
  • Server won't boot after an /etc/fstab change
    You are in emergency mode · Give root password for maintenance · Cannot open access to console, the root account is locked · A start job is running for · Server does not come back after a reboot and SSH does not work · Server hangs at boot after I edited /etc/fstab

Docker

  • A container keeps restarting, is unhealthy or has exited
    Restarting (1) 12 seconds ago · Up 2 minutes (unhealthy) · Exited (1) 3 minutes ago · Exited (137) · My container keeps restarting · The app's web page does not open or keeps going away
  • Deployrr times out waiting for a container to start
    Waiting for Traefik to start... · Waiting for APP to initialize... · Timed out. Could not verify if Traefik is running. · Timed out waiting for APP container to start · Required dependency APP did not become healthy · Required dependency not running: APP · Failed to start required dependency: APP · Failed to pull image for required dependency: APP · unknown flag: --profile · Apps never start after you installed Docker from snap or apt before Deployrr
  • Apps are stopped or show empty folders after a reboot
    Exited (N) 5 minutes ago · Jellyfin, Plex, Sonarr or Radarr is not running after I rebooted my server · My apps do not start after a reboot · Media apps stay stopped after Docker restarts · My media app shows an empty library after a reboot · My NAS share or disk is not mounted after a reboot · I want my media apps to start after my SMB or NFS share is mounted · My apps stopped after I restarted Docker
  • Port already in use: find what uses it and pick another port
    Port In Use · WARNING! Port N is already in use. Using suggested port: N · Invalid Port · Port must be a number between 1 and 65535. Using suggested port · Error response from daemon: driver failed programming external connectivity on endpoint: Bind for 0.0.0.0:PORT failed: port is already allocated · failed to bind host port: address already in use · Port Conflict - Cannot Install · Port 80 is occupied. This is needed for Traefik. · An app container will not start after install and another app uses the same port
  • No internet on the server or in containers after setup
    [ERROR] Problem with some dependencies. This can be due to two reasons: No internet connection · Deployrr server is down for maintenance · Internet connectivity could not be verified · Internet Connectivity Check Failed · sudo apt update fails after Prerequisites > Packages on Debian · Temporary failure in name resolution · Server has internet but containers cannot reach the internet
  • Docker environment setup fails with: docker-compose file is malformed
    /home/USERNAME/docker/docker-compose-HOSTNAME.yml is malformed (missing placeholders) · docker-compose-HOSTNAME.yml is malformed · Setup Docker Environment stops after "Creating starter compose files..." · Installing Socket Proxy or Deployrr Dashboard ends with a malformed compose file error · Compose Validation Error · One or more compose files has errors
  • Docker image pulls fail with: toomanyrequests or TLS handshake timeout
    toomanyrequests: You have reached your pull rate limit · Get "https://registry-1.docker.io/v2/": net/http: TLS handshake timeout · Docker Compose failed to pull image for · Failed to pull image for required dependency · docker compose pull fails on some images and works on others when you run it again · Docker prints Error next to several apps during Update Stack or the dcpull alias
  • Lazydocker shows "client version 1.25 is too old"
    Error response from daemon: client version 1.25 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version · Error response from daemon: client version 1.25 is too old. Minimum supported API version is 1.40 · Lazydocker & Docker v29 Incompatibility · Lazydocker is currently incompatible with Docker v29 and newer due to deprecated Docker API versions · Lazydocker does not start or shows no containers

Host and OS

  • Docker fails with "failed to create shim task" in a Proxmox LXC container
    Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open sysctl net.ipv4.ip_unprivileged_port_start file: reopen fd 8: permission denied: unknown · failed to create shim task · open sysctl net.ipv4.ip_unprivileged_port_start file permission denied · Containers stopped starting after I updated Docker on a Debian or Ubuntu LXC container in Proxmox

Support

  • Deployrr shows "Unhealthy - Issues detected"
    System Health: Unhealthy (Run Tools->Diagnostics) · Overall System Health: Unhealthy - Issues detected · Run System Health Checks (Unhealthy) · Permissions should be 600: Unhealthy (644) · Permissions should be 600: Unhealthy () · Permissions should be 600: File not found · Status - ACTIVE - Security Warning! · One or more compose files has errors · Compose Validation Error · System Health: Error - Hostname Mismatch (Run Tools->Change Hostname) · System Health: Not Applicable (until Prerequisites are completed) · Requirements Not Met
  • I forgot my Deployrr PIN
    I forgot my Deployrr PIN · Previously set pin found. Enter your 6-digit pin for verification. · Forgot your pin? Check · Incorrect pin. · Invalid Pin · License not verified after entering my PIN