Change the server IP
Use the Change Server IP tool when your server gets a new IP address. This happens after a DHCP change, after a router swap, or after you move to a new server. The tool saves the new IP and swaps it into your Dashboard and Traefik file provider files. It does nothing else, so this page also lists what you still do by hand.
Before you start
Section titled “Before you start”- Deployrr is installed and Prerequisites are done.
- You have a Pro license. Without it, or without Prerequisites, Deployrr shows a requirements box. See Requirements not met and Licenses.
- You know the new IP and the old IP.
- Give the server a fixed IP so it does not change again. Set a DHCP reservation in your router, or a static IP in the operating system. This is not a Deployrr step.
If Deployrr runs in a Proxmox LXC container
Section titled “If Deployrr runs in a Proxmox LXC container”Change the address in Proxmox first, then run the Deployrr steps below. This is general Proxmox knowledge, not a Deployrr feature.
-
In the Proxmox web interface, select the container.
-
Open Network, select the network device (usually
net0) and select Edit. -
With IPv4 set to Static, type the new address with its prefix in IPv4/CIDR, for example
192.168.1.60/24. Check the Gateway. Select OK.If IPv4 is set to DHCP, change the reservation in your router instead. See Give your server a fixed IP.
-
Restart the container so it uses the new address. An SSH session to the old IP stops working, so use the container’s Console in Proxmox or connect again to the new IP.
-
Check the address inside the container:
Terminal window ip -4 addr show
Set the address only in Proxmox, not inside the container as well. For other Proxmox settings, see Run Deployrr in a Proxmox LXC.
Back up the files the tool changes
Section titled “Back up the files the tool changes”All paths are inside your Docker folder. The recommended folder is /home/USERNAME/docker. Replace USERNAME with your Linux username. Replace HOSTNAME with your server’s hostname.
-
Exit Deployrr, or open a second terminal.
-
Copy the Dashboard services file:
Terminal window sudo cp /home/USERNAME/docker/appdata/deployrr-dashboard/config/services.yaml /home/USERNAME/docker/appdata/deployrr-dashboard/config/services.yaml.bakSkip this step if you don’t run the Dashboard.
-
Copy the Traefik rules folder:
Terminal window sudo cp -r /home/USERNAME/docker/appdata/traefik3/rules/HOSTNAME /home/USERNAME/docker/appdata/traefik3/rules/HOSTNAME-backupSkip this step if you don’t run Traefik.
Run the tool
Section titled “Run the tool”-
Start Deployrr.
-
Select Tools.
-
Select Change Server IP. Its description reads “Adapt Deployrr to a new server IP” and shows the IP Deployrr has saved now.
-
In the Docker Environment Variables box, read “Enter the new Docker Host IP (LAN IP or WAN IP for VPS):”. The box shows the current IP.
-
Type the new IP and select OK. Use the LAN IP of the server, or the public IP if the server is a VPS.
Deployrr saves the new IP right away, as
SERVER_LAN_IPin the.envfile in your Docker folder. If you stop at a later step, the new IP stays saved.If you select Cancel, nothing changes and the tool stops. If you leave the box empty and select OK, the tool also stops, but the saved IP is cleared. Run the tool again and enter the IP.
-
At “Enter the previous Docker Host IP”, type the old IP.
If it is empty or the same as the new IP, you see “Invalid input. Previous IP cannot be empty or the same as the new IP.” and go back to Tools.
-
Read the Update Service IP box. It says Deployrr will update the IP for services in the Deployrr Dashboard and in all Traefik file providers.
-
Select Yes. If you select No, you go back to Tools. The Dashboard and rules files stay as they are, but the new IP from step 5 stays saved in
.env. -
Read the lines Deployrr prints. See the next section.
-
Press Enter, or wait a few seconds, to go back to Tools. There is no final success message.
-
Go to Prerequisites > Server IP. Enter the new IP and select OK. You see “Server IP set to NEW_IP.”
The box is already filled in with the new IP, so you can just select OK. Deployrr keeps a second copy of the server IP in its own settings, and Change Server IP does not update it. Without this step, the Server IP entry in Prerequisites keeps showing the old IP. Your apps and a rerun of Environment still use the new IP from
.env. To see the Server IP entry in Prerequisites, watch Deployrr 5 walkthrough: Server IP at 10:37 (shows Deployrr v5; menus and steps differ in v6).
Read the output
Section titled “Read the output”First you see “Updating Deployrr Dashboard services file…”, with one of these lines for the services.yaml file:
| Line | Meaning |
|---|---|
[INFO] Updated OLD to NEW in FILE. |
The old IP was in the file and is replaced. |
[INFO] No occurrence of OLD found in FILE. |
The file did not contain the old IP. Nothing changed. |
[WARNING] FILE does not exist. No update performed. |
You have no Dashboard installed. |
Then you see “Updating Traefik file providers…”. Deployrr checks the app-*.yml files in the appdata/traefik3/rules/HOSTNAME folder:
| Line | Meaning |
|---|---|
[INFO] Updated OLD to NEW in FILE. |
One line for each file that held the old IP. |
[INFO] No occurrence of OLD found in any app-*.yml file in FOLDER. |
No file held the old IP. |
[WARNING] FOLDER does not exist or contains no app-*.yml files. No update performed. |
You have no such files. |
Only files named app-*.yml are changed. Other files in the rules folder, for example ones you named differently, are not.
“No occurrence” is normal for apps you installed from the Deployrr menu. Their rules files point at the Docker bridge address (usually 172.17.0.1) and the app’s host port, not at your LAN IP. Traefik is not on the app’s Compose network, so it reaches the app that way. See The networks in your Compose files. Files that do hold the old IP are usually ones you made with Traefikify and pointed at this server’s IP.
Check the changed files
Section titled “Check the changed files”-
Open the Dashboard services file and look for IPs that should not have changed:
Terminal window sudo nano /home/USERNAME/docker/appdata/deployrr-dashboard/config/services.yaml -
Compare the rules folder with your backup:
Terminal window sudo diff -r /home/USERNAME/docker/appdata/traefik3/rules/HOSTNAME-backup /home/USERNAME/docker/appdata/traefik3/rules/HOSTNAMEEvery changed line should show the old IP replaced by the new one. Fix any other IP that changed by mistake.
Fix what the tool does not change
Section titled “Fix what the tool does not change”The tool does not touch anything outside the files above. Do these yourself:
- Update the port forwards in your router to point at the new IP.
- Update DNS records that hold the server IP. If you use Hybrid or VPS, this includes the A record.
- Update firewall rules that name the old IP. See UFW firewall on a VPS.
- Update bookmarks that use the old IP.
- Update other servers that point at this one. For example, the main server’s Traefik may send traffic for a remote app to this server. See Traefikify and Multiple servers on one domain.
- Update remote apps you added to the Dashboard.
- Watch out for Tools > ReDash. It rebuilds the Dashboard and brings back the entries you added with Dashify from Deployrr’s own list. That list is not updated, so a ReDash run can bring back the old IP for those entries. After a ReDash run, check
services.yamlagain and fix any old IP.
Recreate apps that use the server IP
Section titled “Recreate apps that use the server IP”Four apps read the server IP from the .env file in their compose files:
- Plex
- Open WebUI
- Paperless-ngx
- BookStack
A running container keeps the old value until you recreate it. For each of these apps you run, go to Tools > Stack Manager > Recreate and pick the app at “Select an app to recreate:”. Pick all to recreate every app at once. Stack Manager needs a Basic, Plus or Pro license. See Stack Manager.
Where Deployrr keeps the server IP
Section titled “Where Deployrr keeps the server IP”Deployrr keeps the server IP in two places: as SERVER_LAN_IP in the .env file in your Docker folder, and in its own settings. Each menu changes a different part:
| Menu | What it changes |
|---|---|
| Prerequisites > Server IP | Both copies. No other file. |
| Tools > Change Server IP | The .env copy, plus the old IP in the Dashboard services.yaml and the app-*.yml rules files. Not Deployrr’s own copy. |
| Tools > .env Editor | The .env copy only. See Edit .env and secrets. |
So after a change, run Change Server IP and then Prerequisites > Server IP, as in the steps above. Editing SERVER_LAN_IP in the .env Editor alone leaves the Dashboard, the rules files and Deployrr’s own copy on the old IP.
Check it worked
Section titled “Check it worked”- In Tools, the Change Server IP description shows the new IP.
- Your apps open in the browser at their usual addresses.
- The links on your Dashboard work. If a link does not change, refresh the page.
- If an app does not load, check the Traefik logs.

