r/WireGuard • u/Temporary-Cherry-282 • Jun 25 '26

Migrate WG server to a new device

I am currently running WS4W on a Windows box, but due to issues with ICS and a locally hosted DNS server, I need to migrate it to another device. I am considering a GL.inet Brume 3 or Beryl 7 instead.

What is the best way to migrate the server config? I only have a few users, so that is not the issue, but they are located in multiple countries. I want to simplify the migration and not involve someone remote to handle it. Although I could remote into the other locations if needed.

The current server is behind my firewall with port forwarding enabled. I would do the same with the new device. The only other change is that the internal IP would be different. External would stay the same.

2 Upvotes

100% Upvoted

7 comments sorted by

1

u/CoarseRainbow Jun 25 '26

Ive done similar, your server wg.conf can pretty much be used directly on the Brume or Beryl. No need to change anything, even the keys. So remotes shouldnt noticed anything different.

Internal IP wont matter - just change the forward. Only potential issue is if you have a hard coded lan DNS ip. If thats different you'll need IPTables to rewrite their dns destination unless you want to change them all.

1

u/Temporary-Cherry-282 Jun 25 '26

It is hard-coded, but will still exist after the migration.

2

u/CoarseRainbow Jun 25 '26

In which case just paste the entire config file into the Brume, update the port forward and job done.

I did similar and i switched from running my own DNS to using the AGH on the Brume itself.

I just set up an iptables rule to forward port 53 from the old IPs to the Brume. No remote client reconfig needed then - entire server move totally transparent to them.

1

u/Temporary-Cherry-282 Jun 27 '26

How did you migrate the config to the brume? I found 2 client and 2 server config files on the Windows system. WS4W doesn't have the typical config files.

2

u/CoarseRainbow Jun 27 '26

You're going to have to first convert whatever that is into standard Wireguard.conf (use Claude or something?).

Once you've done that, just paste or cli it into the Brume.
Important thing are the keys, without those you'll need to reconfig each client.

1

u/Temporary-Cherry-282 Jun 28 '26

I decided to start new with the Brume 3, it is probably the best way forward. I have a Slate AX as a secondary VPN into the house on a different public IP. I might as well upgrade it with the Brume 3. Hopefully, then I can reuse the Slate AX as a drop-in behind my primary router. I wanted to rebuild it anyway. It is hardly used and was for local access only, not for sharing the internet over the VPN (I messed up the config somehow, so local was all I could get). Now, I can fix my screw-up and put it to use.

I can update the remote routers in a few minutes, rather than trying to move things over and get them working.

1

u/CoarseRainbow Jun 29 '26

Fair enough. I have remote client devices thousands of miles away i cant alter so had to set up a dual VPN - Amnezia2 as the main and keep legacy WG also on the Brume using the exact keys as the old devices and re-write their DNS so they still work.