Give your server a fixed IP address
Give your server an IP address that never changes. Do this before you set Server IP in Deployrr, and ideally before you install apps.
Deployrr saves your server IP in its settings and in the .env file in your Docker folder. App web addresses, Dashboard links and some apps’ compose settings use it. Your router port forwards point at it. If another server’s Traefik points at this server by IP, its rules file holds the IP too. If the IP changes, these break.
When you change the IP later, Tools > Change Server IP updates the Deployrr Dashboard and the Traefik app rules files on this server. It does not touch your router or other servers. See Multiple servers on one domain.
Before you start
Section titled “Before you start”- You can log in to the server over SSH, or at its keyboard and screen.
- You can log in to your router, if you use a DHCP reservation.
- You know whether the server is a home machine, a Proxmox container or a VPS.
Pick your option
Section titled “Pick your option”| Your server | What to do |
|---|---|
| Home or office network | Option 1: DHCP reservation. It is the easiest and safest. |
| You can’t change the router | Option 2: static IP in the operating system. |
| Proxmox LXC or VM | Set the address in Proxmox. See Proxmox LXC. |
| VPS | Usually nothing to do. |
Find your current network details
Section titled “Find your current network details”-
Run this command to list your interfaces and addresses:
Terminal window ip -br addrLook for the line with your LAN address, for example
192.168.1.50/24. The first word on that line is the interface name, for exampleeth0orenp3s0. Skiploand thedocker0orbr-lines. -
Find your gateway, which is your router:
Terminal window ip routeThe gateway is the address after
default via, for example192.168.1.1. -
Find your DNS servers. On systems that use systemd-resolved, such as Ubuntu:
Terminal window resolvectl statusLook for
DNS Servers. On many home networks this is the router address. You can also use1.1.1.1. -
Write down the interface name, current address, gateway and DNS servers. You need them below.
Option 1: Reserve the address in your router
Section titled “Option 1: Reserve the address in your router”A reservation tells your router to always hand the same address to your server. The server keeps using DHCP, so there is nothing to change on the server. Menus differ by router. Check your router’s manual for exact names.
-
Log in to your router’s admin page. Write down the server’s current entry and any existing reservation, so you can undo the change.
-
Find the list of connected devices. It is often called DHCP clients or Connected devices.
-
Find your server by its hostname or MAC address. To see the MAC address on the server, run
ip -br link. -
Choose the option to reserve or bind the address. It may be called Static lease, Address reservation or Static DHCP.
-
Pick the address. Using the one the server has now is the safest.
-
Save the reservation.
-
Make the server ask for its address again. The simplest way is to reboot it:
Terminal window sudo reboot
Option 2: Set a static IP in the operating system
Section titled “Option 2: Set a static IP in the operating system”Pick an address that is outside your router’s DHCP pool, so no other device gets it. Check the pool range in your router. If you pick an address inside the pool, two devices can end up with the same IP.
Use only the section that matches your system:
- Ubuntu, including Ubuntu Desktop: netplan.
- Debian with
/etc/network/interfaces: ifupdown. - Fedora, RHEL, Rocky and Debian desktops: NetworkManager.
Ubuntu (netplan)
Section titled “Ubuntu (netplan)”Replace eth0, the addresses and the DNS servers with your own values from above. The /24 is your subnet size. Most home networks use /24.
-
List the netplan files:
Terminal window ls /etc/netplan/ -
Copy the file you will edit. Replace
FILE.yamlwith its name, such as50-cloud-init.yamlor00-installer-config.yaml:Terminal window sudo cp /etc/netplan/FILE.yaml ~/FILE.yaml.bakKeep the copy in your home folder. Netplan reads every
.yamlfile in/etc/netplan/, so a copy left there can cause conflicts. -
If the file is
50-cloud-init.yaml, stop cloud-init from rewriting it. Create this file:Terminal window echo 'network: {config: disabled}' | sudo tee /etc/cloud/cloud.cfg.d/99-disable-network-config.cfgSkip this step if your file has another name.
-
Open the file:
Terminal window sudo nano /etc/netplan/FILE.yaml -
Edit the interface section. Keep the other lines in the file. Set
dhcp4tofalseand addaddresses,routesandnameservers. Keep the spaces exactly. YAML does not allow tabs. The interface section should look like this:network:version: 2ethernets:eth0:dhcp4: falseaddresses:- 192.168.1.50/24routes:- to: defaultvia: 192.168.1.1nameservers:addresses:- 192.168.1.1- 1.1.1.1 -
Save the file and close the editor.
-
Try the change:
Terminal window sudo netplan tryNetplan applies the change and starts a countdown of 120 seconds. If you can still use the server, press Enter to keep the change. You don’t need
netplan apply. If you lose the connection, do nothing. Netplan rolls back on its own.
If netplan warns that a file is too open, set its permissions and try again:
sudo chmod 600 /etc/netplan/FILE.yamlDebian (ifupdown)
Section titled “Debian (ifupdown)”Use this if your Debian system has /etc/network/interfaces and does not use NetworkManager.
-
Copy the file:
Terminal window sudo cp /etc/network/interfaces /etc/network/interfaces.bak -
Open it:
Terminal window sudo nano /etc/network/interfaces -
Find the existing lines for your interface. They look like
allow-hotplug eth0orauto eth0, followed byiface eth0 inet dhcp. -
Replace those lines with the block below. Don’t add a second block for the same interface. Use your own interface name and addresses:
auto eth0iface eth0 inet staticaddress 192.168.1.50/24gateway 192.168.1.1dns-nameservers 192.168.1.1 1.1.1.1 -
Save the file and close the editor. Check it again for typos.
-
Reboot from the console:
Terminal window sudo rebootRestarting the networking service can keep the old DHCP address, so reboot instead.
If you lose the connection, restore your copy at the console and reboot:
sudo cp /etc/network/interfaces.bak /etc/network/interfacessudo rebootNetworkManager (Fedora, RHEL, Rocky and Debian desktops)
Section titled “NetworkManager (Fedora, RHEL, Rocky and Debian desktops)”Don’t use this on Ubuntu, including Ubuntu Desktop. Ubuntu sets the network with netplan, so use the netplan steps above.
-
List your connections:
Terminal window nmcli con showNote the name of the connection that uses your interface. Replace
CONNECTION_NAMEbelow with it. Use quotes if it has spaces. -
Save the current settings, so you can compare or restore them later:
Terminal window nmcli con show "CONNECTION_NAME" > ~/nm-before.txt -
Set the static address, gateway and DNS. Replace the addresses with your own:
Terminal window sudo nmcli con mod "CONNECTION_NAME" ipv4.method manual ipv4.addresses 192.168.1.50/24 ipv4.gateway 192.168.1.1 ipv4.dns "192.168.1.1 1.1.1.1" -
Bring the connection up again:
Terminal window sudo nmcli con up "CONNECTION_NAME"This can drop an SSH session. Run it at the console if you can.
To go back to DHCP, run this and bring the connection up again:
sudo nmcli con mod "CONNECTION_NAME" ipv4.method auto ipv4.addresses "" ipv4.gateway "" ipv4.dns ""Proxmox LXC and VM
Section titled “Proxmox LXC and VM”For a Proxmox LXC container, set the address in Proxmox, on the container’s Network tab. Don’t set it inside the container as well. If Deployrr already runs in the container and the address changes, see Change the server IP. For a VM, use a reservation in your router or the steps above inside the VM. See Run Deployrr in a Proxmox LXC for other Proxmox settings. To watch the static IP set while you create a container, see Docker on Proxmox LXC: static IP at 7:47.
The provider gives a VPS a fixed public IP. You have nothing to do. Don’t edit its network files. See UFW firewall on a VPS to protect it. On a VPS, enter the public IP in Prerequisites > Server IP.
Check it worked
Section titled “Check it worked”-
Show the addresses again:
Terminal window ip -br addrYour interface shows the address you picked.
-
Ping your gateway. Use your own gateway address:
Terminal window ping -c 3 192.168.1.1 -
Ping the internet by IP:
Terminal window ping -c 3 1.1.1.1 -
Check that DNS works:
Terminal window getent hosts deployrr.appYou see an IP address. If the pings work but this prints nothing, fix your DNS servers.
-
Reboot and run
ip -br addragain. The address must stay the same.
Tell Deployrr and your router
Section titled “Tell Deployrr and your router”If the address is the same as before, you are done.
If the address changed, pick the case that fits you.
New install, or apps not installed yet. Open Prerequisites > Server IP. You need Disclaimers and Environment done first. At “Enter the Docker Host IP (LAN IP or WAN IP for VPS):”, the box shows the address saved earlier, or the one Deployrr detects if none is saved. Check it, change it to your fixed address if it differs, and select OK. Don’t leave it empty. On a VPS, enter the public IP. See Server IP in Prerequisites.
Apps already installed, with a Pro license. Use Tools > Change Server IP. You need a Pro license and all Prerequisites done.
- Write down your old IP before you start. The tool asks for it.
- Enter the new IP when asked.
- Enter the previous IP when asked.
- In the Update Service IP box, select Yes to proceed.
The tool then updates the Deployrr Dashboard and the Traefik app rules files on this server. It does not recreate your apps. Recreate them afterwards. See Restart, recreate and reinstall apps.
Apps already installed, without Pro. Open Prerequisites > Server IP and enter the new address. Then do the manual fixes in Change the server IP.
Also update your router’s port forwards so they point to the new address. See Simple vs Advanced mode for the ports you forward. If another server’s Traefik points at this server by IP, change the IP in that rules file too. See Multiple servers on one domain.

