Skip to content

Update Deployrr

How-toDeployrr v6.0+CurrentUpdatesInstall

You can update Deployrr with one command, or say yes when Deployrr offers an update as it starts.

This page updates Deployrr itself. To update your apps, see Update your apps.

  • Deployrr v6 is installed. If not, follow the Quick start.
  • Your server is online.
  • sudo is installed and your user can use it. Deployrr needs it to start and to update. See Create a regular user with sudo rights.
  • wget is installed. Deployrr needs it to start and to check for updates. See Deployrr needs wget.
  • To see which version you run, open Help from the main menu and read Your Version. See Help menu.
  1. Open a terminal on your server as your normal user.

  2. Run this command, without sudo in front. Deployrr asks for your password when it needs it.

    Terminal window
    deployrr update
  3. Deployrr starts up first. If a newer version is out, you see the startup update prompt from Update when Deployrr offers it. Press Enter to go on to the updater. If you type y there, Deployrr exits instead and shows the npx command.

  4. The Deployrr CLI Updater screen shows your Local Version, the Latest Version and the Install Method (npx or curl).

  5. Wait while the update runs. It uses the same method you used to install Deployrr and prints the command it runs. If Deployrr can’t tell how it was installed, it uses the curl installer.

If you already have the latest version, Deployrr shows Deployrr is already up-to-date (v...) and asks:

Would you like to force reinstall Deployrr anyway? (y/N):
  • To reinstall anyway, type y and press Enter.
  • To cancel, press Enter. Deployrr shows Update cancelled.

When a newer version is out, Deployrr tells you as it starts:

You are running version X. There is a newer version: Y.
Update to vY using npx? Press Y/y to exit and update, or any other key to continue:
  1. Type y and press Enter. Deployrr exits and shows Exiting. Please run: sudo npx @simplehomelab/deployrr@latest.

  2. Run that command:

    Terminal window
    sudo npx @simplehomelab/deployrr@latest

To skip the update, press Enter instead. Deployrr shows Continuing with v... and opens as usual.

deployrr update runs your original install command for you. If it doesn’t work, you can run that command yourself.

If you installed with npx:

Terminal window
sudo npx @simplehomelab/deployrr@latest

If you installed with curl:

Terminal window
sudo bash -c "$(curl -fsSL https://files.deployrr.app/install.sh)"

Running the install command again also gets you the latest program files when Deployrr is already installed. It downloads the current version and installs it over the old one. With npx you see something like this:

Deployrr Installer
Installing app files...
Downloading Deployrr v6.0 (x86_64)...
...
Run: deployrr

npm may also print its own New major version of npm available notice. You can ignore it. When you see Run: deployrr, start Deployrr with deployrr.

You also need this after Settings > Reset, which deletes the Deployrr program. See Refresh, Reset or Remove Deployrr.

Both installers download the same Deployrr program into /opt/deployrr and link the deployrr command. They differ in what they need and in what deployrr update runs later:

Install method Needs deployrr update runs
npx Node.js, npm and curl sudo npx -y @simplehomelab/deployrr@latest
curl curl and tar the curl installer

If Node.js and npm are already on your server, either works. If not, the curl installer saves you from installing them. If you plan to remove Node.js, switch to curl first, or deployrr update fails with sudo: npx: command not found.

The installer you ran last sets your install method. The updater screen shows it as Install Method. To switch, run the other installer once:

  • To curl: run the curl command from Run the installer again. Nothing else is needed.
  • To npx: install Node.js and npm first. Check that sudo npx --version prints a version number. Then run the npx command from Run the installer again.

Then run deployrr update. The updater screen shows the new Install Method. If you are already on the latest version, press Enter to skip the reinstall.

Switching does not stop, change or remove your running apps or your Docker folder.

Find the message you see, then follow the fix.

deployrr update runs Deployrr’s normal startup before the updater. So a problem that stops Deployrr from starting also stops the update.

“Could not check for updates” or “Problem with some dependencies”

Section titled ““Could not check for updates” or “Problem with some dependencies””

As Deployrr starts, it looks up the latest version online. If that fails, you see:

Could not check for updates (network error). Continuing...

Deployrr then downloads the files it needs to run. If that fails too, it stops with Problem with some dependencies and never reaches the updater. If you see only the first message and Deployrr opens, only the version check failed.

When you run deployrr update, the updater looks up the version once more. If that fails, it shows Could not retrieve latest version information. Please check your internet connection. and stops.

Check these causes in order.

If wget is not installed, you see these messages even when your internet works. The Prerequisites > Packages step does not install it. Ubuntu and Debian usually have it already. Minimal installs may not.

  1. Check if wget is installed:

    Terminal window
    command -v wget

    If it prints a path, wget is installed. If it prints nothing, it is not.

  2. Install it with the command for your system:

    Terminal window
    sudo apt install wget
    Terminal window
    sudo dnf install wget
    Terminal window
    sudo pacman -S wget

    Use the first on Debian and Ubuntu, the second on Fedora and the RHEL family, and the third on Arch.

  3. Run deployrr update again.

Your server is offline or can’t resolve names

Section titled “Your server is offline or can’t resolve names”

Test the connection with either command:

Terminal window
ping -c 3 registry.npmjs.org
Terminal window
curl -I https://registry.npmjs.org

If both fail, fix your server’s network or DNS first. See No internet on the server or in containers after setup.

Something on your network blocks the lookup

Section titled “Something on your network blocks the lookup”

A firewall or a DNS blocker such as Pi-hole can block registry.npmjs.org or files.deployrr.app. Allow both, then run deployrr update again.

Deployrr’s server is down for a short time

Section titled “Deployrr’s server is down for a short time”

Problem with some dependencies can also mean Deployrr’s own server is down for maintenance. Wait a few minutes and try again.

deployrr update prints the install command after Running:. Update failed. means that command ended with an error. The reason is in the lines printed above Update failed.. Find your line in this list.

For any other message, see Install errors.

You installed with npx, and sudo can no longer find npx, for example because you removed Node.js and npm. To fix it, run the curl installer once:

Terminal window
sudo bash -c "$(curl -fsSL https://files.deployrr.app/install.sh)"

The curl installer saves curl as your install method. After that, deployrr update uses curl. The updater screen shows Install Method: curl.

Run the update again:

Terminal window
deployrr update

If you are already on the latest version, Deployrr asks if you want to force a reinstall. See Update with the command.

If it still fails, ask on Discord. Include the lines printed above Update failed.. Remove your domain and other personal details first.

  • After deployrr update, you see Deployrr has been updated successfully! and then Restarting Deployrr.... Deployrr opens again on its own.
  • If you see Update failed., Could not retrieve latest version information. Please check your internet connection. or Problem with some dependencies, see If the update fails.
  • If Deployrr shows Could not check for updates (network error). Continuing... as it starts and then opens, it could not check for a new version. See If the update fails to fix it.