Installing Rundeck on Debian‑based systems is straightforward if you follow a few essential steps: update your system, install Java, add the official repository, and then install Rundeck itself. After installation, you may tweak permissions for non root job execution and enable the service to start at boot. Once running, access the UI via port 4440, set up credentials immediately, and optionally secure it behind a reverse proxy or dedicated database if scaling out. The guide provides clear commands and quick troubleshooting pointers to keep the process smooth.

How to install Rundeck on Ubuntu/Debian Servers

You’ll learn the quick‑and‑dirty way to get Rundeck up and running on any Debian‑based box, including those stubborn older releases that still run in your data‑center. No fluff, just the commands you need and a few tips to keep things from blowing up.

1 . Make sure your system is fresh

sudo apt update && sudo apt upgrade -y

Updating first saves you the headache of broken dependencies later. I’ve seen servers stall halfway through an install when they’re still on old package lists.

2 . Install Java – Rundeck’s favorite language

Rundeck runs on any JDK ≥ 8, but Ubuntu ships a lightweight OpenJDK 11 that works fine.

sudo apt install openjdk-11-jdk -y

Afterward confirm it’s the right version:

java -version

If you get “command not found,” the Java binary isn’t on your path and Rundeck will just complain about missing JVMs. Setting JAVA_HOME is a one‑liner, but most of the time the distro’s defaults are enough.

3 . Add the official Rundeck repository

sudo wget -qO- https://packages.rundeck.com/gpg/rundeck.key | sudo apt-key add -

Then tell APT where to find the packages:

echo "deb https://packages.rundeck.com/rundeck/rundeck stable main" | sudo tee /etc/apt/sources.list.d/rundeck.list

Update again so APT knows about Rundeck’s binaries.

sudo apt update

4 . Install the Rundeck server package

sudo apt install rundeck -y

That pulls in everything – the web UI, REST API, and the service script that will keep Rundeck alive after a reboot.

. Adjust file permissions (optional but handy)

If you want to run jobs as a non‑root user or avoid permission issues on your job files, tweak the rundeck group:

sudo adduser $USER rundeck

Log out and back in so the group change takes effect.

6 . Start Rundeck and enable it at boot

sudo systemctl start rundeckd
sudo systemctl enable rundeckd

A quick sanity check:

systemctl status rundeckd

You should see “active (running)”. If not, the logs (/var/log/rundeck/service.log) will tell you where it failed.

7 . Open the web UI

Rundeck listens on port 4440 by default. Point your browser to:

http://your-server:4440/

The first time you hit it, you’ll be prompted for a username and password. The defaults are admin/admin – change them right away.

8 . (Optional) Harden the installation

If your server sits behind a firewall or needs SSL, consider running Rundeck through Nginx or Apache in reverse‑proxy mode. Also, tweak /etc/rundeck/rundeck-config.properties to point at a dedicated database if you’re scaling out.

Give it a whirl and enjoy automating the stuff that used to require manual clicks. If anything goes sideways, drop a note on the Rundeck forums – the community usually has a quick fix up their sleeve.