Skip to content

Deployrr shows "Unhealthy - Issues detected"

TroubleshootingDeployrr v6.0+CurrentDockerHost systemDocker ComposeTraefikSupport

Deployrr checks a few things on your server every time it draws the main menu. If one of them is wrong, the main menu says Unhealthy. This page shows how to find out which one and how to fix it.

The main menu has a System Health line. It shows one of these:

System Health: Healthy
System Health: Unhealthy (Run Tools->Diagnostics)
System Health: Error - Hostname Mismatch (Run Tools->Change Hostname)
System Health: Not Applicable (until Prerequisites are completed)

In Tools, the Diagnostics entry (“Run System Health Checks”) shows (Healthy) or (Unhealthy) after it.

When you open Diagnostics, the box says:

Overall System Health: Unhealthy - Issues detected

Healthy is shown in green. Unhealthy is shown in red.

Deployrr flags your system as Unhealthy when any of these is true:

  • The .env file in your Docker folder does not have permissions 600.
  • The secrets folder in your Docker folder does not have permissions 600.
  • Traefik is running, the file acme.json exists, and it does not have permissions 600.
  • Remote Assist is on.
  • One or more compose files have a YAML syntax error.

Permissions 600 mean only the owner can read and write the file. These files hold passwords and keys, so Deployrr wants them locked down. Remote Assist counts as a problem because it gives the support team access to your server.

To see why acme.json needs 600, watch Traefik 3 guide: creating acme.json and setting permission 600 at 26:13 (manual Docker Compose setup). With Deployrr, don’t create acme.json by hand. If it is missing, see The line says File not found below.

The other main menu messages mean something different:

  • Error - Hostname Mismatch means your server’s name changed. See Change the hostname. The main menu shows this instead of the other results, but Tools > Diagnostics still runs all the checks.
  • Not Applicable means you have not finished the Prerequisites yet. See Quick start.

You need all Prerequisites done and a Basic, Plus or Pro license. Without them, Deployrr shows a box titled Requirements Not Met with the number of missing items, such as “Requirements Not Met (1)”, and lists them. For unfinished Prerequisites it says “Prerequisites - All steps must be completed”. For a missing license it says “License - Basic, Plus, or Pro required”, followed by your current license and a hint to Prerequisites > Verify. See Deployrr shows “Requirements Not Met” for what each line means.

  1. In Deployrr, open Tools.
  2. Select Diagnostics.
  3. Read the five lines. Each line is one check. Deployrr runs the checks when you open the screen. To share results, generate a log from Settings > Logs.

The lines are:

Line Healthy looks like Problem looks like
.env Permissions should be 600: Healthy (600) Permissions should be 600: Unhealthy (644)
secrets Permissions should be 600: Healthy (600) Permissions should be 600: Unhealthy (755)
acme.json Permissions should be 600: Healthy (600) Permissions should be 600: Unhealthy (644) or File not found
Remote Assist Status - NOT ACTIVE Status - ACTIVE - Security Warning!
YAML Yoda All good - No syntax errors in compose files One or more compose files has errors

The number in brackets is the permission the file has now. Your number may differ from the examples.

For acme.json, you may also see Not Applicable (Traefik not running). That is not a problem. Deployrr only checks this file while Traefik runs.

  1. Pick the line that is not healthy and follow its section below. Selecting a line runs its fix or check.

2. Fix .env, secrets or acme.json permissions

Section titled “2. Fix .env, secrets or acme.json permissions”

Deployrr fixes these for you.

  1. In Diagnostics, select the line (.env, secrets or acme.json).

  2. Wait for the screen to finish. You should see these lines:

    Fixing permissions for: /home/USERNAME/docker/.env
    Permissions set to 600

    If the permissions were already right, you see Permissions already correct (600).

  3. Read “Going back to the menu in 60 seconds. Or, press OK to go back now…”. Wait, or press Enter.

  4. Select Back, then open Diagnostics again. The line now shows Healthy (600).

The menu does not update its lines right after a fix. Leaving and opening Diagnostics again shows the new state.

To see Deployrr catch a wrong .env permission and fix it with one click, watch Deployrr 5 walkthrough: Tools menu detects a wrong .env permission and fixes it at 1:21:31 (shows Deployrr v5; menus and steps differ in v6).

If you prefer to do it yourself, run the command for the file that is flagged. Replace YOUR_DOCKER_FOLDER with the path of your Docker folder. This is a value you fill in. The path is the one Deployrr shows on the fix screen. A common path is /home/USERNAME/docker.

Terminal window
sudo chmod 600 YOUR_DOCKER_FOLDER/.env
sudo chmod 600 YOUR_DOCKER_FOLDER/secrets
sudo chmod 600 YOUR_DOCKER_FOLDER/appdata/traefik3/acme/acme.json

Run only the line for the file Deployrr flagged.

The line says File not found or Unhealthy ()

Section titled “The line says File not found or Unhealthy ()”

For acme.json, File not found means Traefik is running but the file is missing. Deployrr shows this at the end of the fix screen:

acme.json file not found at expected path

Deployrr adds the path it looked in. It can’t recreate the file. Don’t create it by hand. Read the Traefik logs to see why it is missing.

For .env or secrets, Unhealthy () with nothing in the brackets means Deployrr could not find the file or folder. The fix screen says File/folder not found: and the path, and offers no repair. Check the path in your Docker folder. If it is really gone, ask for help on Discord.

A missing acme.json, .env or secrets does not make the overall result Unhealthy, so the header can say Healthy while a row shows a problem. A wrong permission on a file that exists does make it Unhealthy, as do an active Remote Assist session and YAML errors.

Selecting acme.json says Traefik is not running

Section titled “Selecting acme.json says Traefik is not running”

If Traefik is not running, selecting acme.json shows a box titled acme.json - Not Applicable. It says “Traefik is not currently running.” Start Traefik first, then try again. If Traefik does not start, see Deployrr times out waiting for a container to start.

If the Remote Assist line says ACTIVE, a remote support session is running on your server, even one Deployrr did not start. If a support member is still helping you, wait until they finish. If you did not start a session, we suggest you treat it as a security problem.

Stopping needs a Pro license. For a short look at what the feature is, watch Deployrr 6 overview: Remote Assistance with Tmate at 8:52.

  1. In Diagnostics, select Remote Assist.
  2. In the Remote Assist - Confirm Stop box, select Yes. Stopping also ends any other remote terminal-sharing session on the server.
  3. Wait for Deployrr to finish stopping the session.
  4. In the Change Password box, select Yes to set a new password. Follow the Set New Password and Confirm Password prompts. If you select No, you see a Password Reminder box instead.
  5. You return to Diagnostics. The line now shows NOT ACTIVE.

With a Basic or Plus license, the line still shows, but selecting it opens Remote Assist - Pro License Required: “Remote Assist is only available for Pro license holders.” Deployrr can’t stop the session for you then. Ask for help on Discord.

Diagnostics can only stop Remote Assist. If the line says NOT ACTIVE and you select it, Deployrr shows Remote Assist Not Active and tells you to use Help > Remote Assist to turn it on. See Get remote help with Remote Assist for the full steps and what the password prompts mean.

YAML Yoda checks the compose files in compose/HOSTNAME/ and your main compose file docker-compose-HOSTNAME.yml for syntax errors and missing included files. It shows one error at a time.

  1. In Diagnostics, select YAML Yoda.
  2. Read the box.
    • A Compose Validation Success box starts with “All good!”. There is nothing to fix.
    • For a file in compose/HOSTNAME/, a Compose Validation Error box names the file after Error found in: and shows Docker’s message, such as yaml: line 12: found character that cannot start any token.
    • For the main compose file, the Compose Validation Error box shows only Docker’s message, with no file name.
  3. Open the named file and go to that line. Common causes are a tab instead of spaces, wrong indentation and a missing colon.
  4. Save the file.
  5. Select YAML Yoda again until you see “All good!”. After each fix, run it again, because it may show another error.

For the full walk through, see Compose file is malformed.

  1. Select Back until you reach the main menu.
  2. Read the System Health line. It should say Healthy.

If it still says Unhealthy, open Diagnostics again and look for the line that is not healthy.

  • Tools > Diagnostics shows Overall System Health: Healthy.
  • The Tools menu shows Run System Health Checks (Healthy).
  • The System Health line on the main menu shows Healthy.

Generate a log and share it with the exact line that stays red.

  1. Open Settings.
  2. Choose Logs (“Generate Sanitized Deployrr Log”) and press Y to continue.
  3. Note the log path Deployrr shows at the end.
  4. Share the log on Discord. See Get help on Discord for what else to include.