How to change the server address
If your hosting provider has replaced the server’s public IPv4 address, you can move the BeAdmin panel to the new address with a single command, beadmin newip, in the server’s web console. The command reconfigures the operating system’s network and checks the connection, and the panel then moves its VPN, the sites served by IP address and its own SSL certificate to the new address. What the panel can’t fix — the configs of your VPN users and your DNS records — it lists in a notification the next time you sign in.
When you need this
Your hosting provider has replaced the server’s public IPv4 address and the panel no longer opens: the operating system’s network settings still hold the old address. SSH to the old address won’t connect either, so you run the command in the server’s web console, which your hosting provider offers in its account area.
What you need
- The new public IPv4 address of the server and the gateway address. Your hosting provider shows them in your account. The command rejects a private address.
- Access to the server’s web console in your hosting provider’s account, and
rootrights. - Debian 13, Ubuntu 24.04 or Ubuntu 26.04, with the server address set statically in netplan (the
/etc/netplan/*.yamlfiles) or in ifupdown (/etc/network/interfacesand the/etc/network/interfaces.d/directory). If the server gets its address automatically or the settings are kept elsewhere, the command won’t find them — change the address manually.
Step 1. Open the web console
Open the server’s web console in your hosting provider’s account and sign in as root. If you sign in as a regular user with sudo privileges, put sudo in front of the command.
Step 2. Run the command
Run the command with the new IPv4 address of the server:
beadmin newip 130.17.10.145The command finds the server’s static address in the network settings, prints what it is about to change, and asks for the gateway:
Current address: 213.239.156.37/24, gateway 213.239.156.1
New address: 130.17.10.145/24
Gateway [130.17.10.1]:The first line shows the current address and gateway from the network settings, the second shows the new address. The network mask stays the same (/24 in the example): the command doesn’t change it.
Step 3. Confirm the gateway
In square brackets the command proposes a default gateway — the first address of the new address’s subnet. Compare it with the gateway in your hosting provider’s account:
- it matches — press Enter;
- it differs — type the gateway from your hosting provider and press Enter.
If what you type doesn’t look like an IPv4 address, the command asks for the gateway again. Until you confirm the gateway, the command changes nothing.
What happens after you enter the gateway
From here on the command works without your input. It saves copies of the files it changes, writes the new address and gateway into the network settings, applies them and checks that the server is on the network. Then it restarts the panel and waits until the panel has moved to the new address everything it kept under the old one. The result looks like this:
✓ Network reconfigured, connection is up
✓ VPN, sites and the panel certificate now use the new address
! Some modules need your attention: https://130.17.10.145:8080The operating system’s network
The Network reconfigured, connection is up line means the server is running on the new address. In the network settings only the address and gateway of the interface that carries the default route change; IPv6 and DNS servers stay as they were.
If the network settings are in a 50-cloud-init.yaml file created by cloud-init, the command also creates the file /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg containing network: {config: disabled}. Without it, cloud-init would write the old address back after a reboot. If that file already exists, the command leaves it alone.
VPN, sites and the panel certificate
The VPN, sites and the panel certificate now use the new address line means the panel has been restarted and has moved the following to the new address:
- the "Server address" setting of the VPN modules — if it holds the old IP address. A domain or another address you entered yourself stays as it was;
- the "Panel address" field in the password recovery settings — if it holds the old IP address. A domain stays as it was;
- sites served by the server’s IP address: the site address, the virtual host and, for WordPress, the addresses in its settings if they hold the old IP address;
- the panel’s SSL certificate: the panel requests a certificate for the new address and deletes the one for the old address.
The address for signing in to the panel
The last line holds the address the panel now opens at. The port in it is the panel port, 8080 by default. The ! sign means that a list of what to do manually is waiting for you after you sign in.
Step 4. Sign in to the panel
Open the address from the last line of the command output and sign in as usual. An administrator sees the notification “Server address changed. Some modules need your attention.” Click "More" to open a window listing what is left to do manually.
An example of the window:
Server address changed: 213.239.156.37 → 130.17.10.145
VPN, sites and the panel certificate already use the new address.
Remaining manual steps:
1. Share new configs with your VPN users — the old ones still
point to the old address and won't connect.
Mimicry — 7 users, WireGuard — 3 users.
2. Generate new links for the entry hops of your multi-hop chains
and apply them on those servers.
Amnezia — 2 users in exit hop mode.
3. Update the A records to 130.17.10.145 for
example.com, shop.example.com.
4. Replace the old address with the new one in the SPF record
for example.com and ask your hosting provider to set a PTR
record for 130.17.10.145.The window lists only the items that apply to your server, and the numbering is continuous. The list is rebuilt each time you sign in, so the A record item disappears once the domains point to the new address.
⚠️ Close the notification only when the list is done
The notification stays on screen until you close it with the cross. Once it is closed, the panel no longer shows it — neither to you nor to other administrators — and the list can’t be brought back in the panel. Users with other roles don’t see the notification.
What is left to do manually
The panel can’t fix what is stored outside it: with your VPN users, on other servers and in DNS. The "More" window lists only what applies to your server.
Share new configs with your VPN users
The configs, links and QR codes you handed out earlier hold the old server address and no longer connect. New configs, links and QR codes from the module already hold the new address if the "Server address" setting is "Automatic" or held the old IP address. Hand them to your users again. The window shows which modules and how many users are affected.
💡 A domain instead of an IP address
If a module’s "Server address" setting is "Custom address" with a domain, you don’t need to hand out its users’ configs again: point the domain’s A record to the new address. The "More" window still lists the users of such a module, and it won’t show the A record of a domain that isn’t in "Websites & Domains" — check it yourself. With a domain instead of an IP address, configs survive the next address change too.
Generate new links for the entry hops of your multi-hop chains
Multi-hop mode is a VPN module mode in which traffic passes through a chain of servers. If this server works in it as an exit hop, the entry hops on other servers reach it by the old address. The window lists the modules and the number of users in exit hop mode. Generate new links for the entry hops and pass them to the servers of those entry hops.
Point the A records of your domains to the new address
The domains in "Websites & Domains" whose A records point to the old address will stop leading to this server. Enter the new address in the A records of those domains at your registrar or in the service that hosts the domain’s DNS zone. How to create an A record is covered in How to configure DNS records for a mail server.
Update SPF and ask for a PTR record
If the mail module is installed on the server, the window asks you to fix the DNS records of your mail domains:
- In the SPF record of each domain, replace the old address with the new one:
ip4:130.17.10.145should stand in place ofip4:213.239.156.37. - Ask your hosting provider to create a PTR record for the new address: it belongs to the IP address, so only your hosting provider can create it.
You can check the result in the "Mail DNS" dialog of the domain, in "Websites & Domains".
If the command fails
No connection on the new address
✗ No connection on the new address — previous network settings restored.
Check the address and gateway with your hosting provider and run the command again.The server didn’t get onto the network with the new address, and the command restored the previous network settings. The panel and its settings were not changed.
A newip: … line with the reason may appear above the message: the gateway … does not answer — the gateway doesn’t answer; nothing outside answers — the gateway answers, but outside addresses are unreachable. Compare the address and gateway with your hosting provider’s data and run the command again. The command keeps the network mask as it was: if the new address comes with a different mask, change the address manually.
The previous settings couldn’t be restored
✗ No connection on the new address, and the previous network settings couldn't be restored.
Restore the files manually from /var/lib/beadmin/newip-backup/1762958412/The server is left without a connection. The directory named in the message holds copies of the files the command changed; inside, the system’s directory structure is repeated, for example etc/netplan/50-cloud-init.yaml. Copy the files back to their places, using the path from your message:
cp -a /var/lib/beadmin/newip-backup/1762958412/etc/. /etc/Then apply the settings: netplan apply for netplan or systemctl restart networking for ifupdown. Once the connection is back, compare the address and gateway with your hosting provider’s data and run the command again.
The panel didn’t finish moving
✗ The network is up, but the panel didn't finish moving to the new address.
See the panel log: journalctl -u beadminThe network already runs on the new address, but the panel hasn’t moved everything it kept under the old one. Run the same command with the same address again:
beadmin newip 130.17.10.145The command doesn’t ask for the gateway and doesn’t change the network: it repeats only the panel’s move. On success it prints the lines about VPN with sites and about the panel address:
✓ VPN, sites and the panel certificate now use the new address
! Some modules need your attention: https://130.17.10.145:8080If the panel opens, the "More" window reports the unfinished move too: “The switch to the new address wasn't completed. Run beadmin newip 130.17.10.145 in the server console again.” If the second run ends with the same error, look for the cause in the panel log: journalctl -u beadmin. A newip: … line with the reason may appear above the message.
The network configuration wasn’t found
✗ Couldn't find the network configuration. Supported: netplan and /etc/network/interfaces.
Change the address manually — see the documentation.The command changed nothing. It looks for the server’s static IPv4 address in netplan and in /etc/network/interfaces; if the address is obtained automatically or the settings are kept elsewhere, it won’t find them. Change the address manually: the end of that section describes how to move the panel afterwards.
The panel holds several old addresses
✗ The panel uses several old addresses: 213.239.156.37, 198.51.100.7.
Fix the panel address and the sites opened by IP manually.The old addresses in the "Panel address" field and in the sites opened by IP address differ. The command can’t choose which of them to replace and changes nothing. Enter the new address manually in the "Panel address" field in the password recovery settings, and fix the address of the sites opened by IP address.
The command refuses to run
In these cases the command changes nothing:
| Message | What to do |
|---|---|
✗ Run the command as root: sudo beadmin newip 130.17.10.145 | The command wasn’t run as root. Repeat it with sudo, as the message says. |
Usage: beadmin newip <new IPv4 address> | The address is missing, or more than one value was given. Give exactly one new IPv4 address. |
✗ 130.17.10 isn't an IPv4 address. | The address is written incorrectly: an IPv4 address is four numbers separated by dots. |
✗ 10.0.0.5 is a private address. Enter the public address from your hosting provider. | A private address was entered. Enter the public address your hosting provider assigned. |
The server already uses 130.17.10.145 — nothing to change. | The network already runs on this address, and the panel holds no other address: there is nothing to move. Compare the address with your hosting provider’s data. |
✗ No gateway entered — nothing changed. | No gateway was entered. Run the command again and give the gateway. |
Change the address manually
If the command didn’t find the network settings, change the address manually. This happens when the server gets its address automatically, or when the network is set up by systemd-networkd or NetworkManager rather than netplan and ifupdown.
Find out which interface carries the default route:
baship -4 route show defaultThe interface name follows
dev, for exampleeth0.Find the file where the system stores this interface’s address, keep a copy of it, and replace the address and gateway in it with the new ones. If the network is set up by cloud-init (a
50-cloud-init.yamlfile), also create the file/etc/cloud/cloud.cfg.d/99-disable-network-config.cfgcontainingnetwork: {config: disabled}: otherwise cloud-init will write the old address back after a reboot.Apply the settings the way your system does it and check the connection:
bashping -c 3 8.8.8.8
Once the network works on the new address, run the command again with that address. It doesn’t touch the network settings this time:
beadmin newip 130.17.10.145The command finds the old address in the panel — in the "Panel address" field, among the sites opened by IP address and in the panel’s SSL certificate — and moves the panel to the new one. On success it prints:
The network already uses 130.17.10.145. Moving the panel from 213.239.156.37…
✓ VPN, sites and the panel certificate now use the new address
! Some modules need your attention: https://130.17.10.145:8080From here on, proceed as after a regular run: sign in to the panel at the address from the last line and go through the list in What is left to do manually.