RuSolv VPN — быстрый и стабильный VPN-сервис

Restarting the VPN on a router

What to do on Keenetic, OpenWrt, MikroTik and GL.iNet when the VPN on your router stops working after server maintenance.

Why a router does not reconnect on its own

During server maintenance the server's address can change. Your configuration file stays valid (unless you downloaded it with “Download with IP address”): it holds the server's name, not its address, and the name points to the new address right away.

But WireGuard and AmneziaWG look the name up only when the connection starts. A phone restarts its connection often; a router keeps it on for weeks and keeps talking to the old address: the connection looks on, but no traffic passes.

To make the router pick up the new address, turn the VPN connection on it off and on. When a server's address changes, we send you a notification.

If the VPN on your router stopped working

  1. 1If you downloaded the file with “Download with IP address”, a restart will not help: the file holds the previous address. Download it again with the same button and import it in place of the old one.
  2. 2Otherwise, turn the VPN connection on the router off and on — the steps for your router are below.
  3. 3Not connected yet — wait 5 minutes and restart the connection once more.
  4. 4If that did not help, download the configuration again in your dashboard, the mini app or the Telegram bot and import it on the router in place of the old one.

Of these routers, only OpenWrt 25.12 and newer has an automatic restart described in the vendor's documentation — see the OpenWrt section.

Keenetic / Netcraze

AmneziaWG on Keenetic is the same WireGuard connection, so the steps are the same for both protocols.

How to restart the connection

  1. 1Open the router's web interface and go to Internet → Other connections.
  2. 2In the WireGuard section, find the RuSolv connection.
  3. 3Turn its switch off, then set it back to On.

Or run these in the router's command line (Telnet, SSH or the web CLI — the router's address with /a at the end, for example http://192.168.1.1/a), replacing WireguardN with the interface name that the show interface command lists:

interface WireguardN down
interface WireguardN up
  • ⚠KeeneticOS 4.1.3 or newer is required: from this version on, restarting the connection makes the router look the server address up again. On older firmware a restart does not update the address — update the firmware to the current version.

OpenWrt

The steps are the same for WireGuard and AmneziaWG (the amneziawg-openwrt packages).

How to restart the connection

  1. 1Open the LuCI web interface and go to Network → Interfaces.
  2. 2In the VPN interface's row, click Restart.

Over SSH (replace wg0 with the name of your VPN interface):

ifup wg0
  • ⚠A restart brings the interface up again, and the router looks the server address up by its name.

Automatic restart

On OpenWrt 25.12 and newer, the watchcat package restarts the interface by itself when pings through it stop getting through:

  1. 1Install the luci-app-watchcat package: System → Software.
  2. 2Open Services → Watchcat and click Add.
  3. 3In the Mode field, choose Restart Interface.
  4. 4In the Interface field, choose the VPN interface (for example, wg0).
  5. 5In the Period field, replace 6h with 5m (5 minutes): otherwise watchcat waits six hours.
  6. 6Leave Hosts To Check and Check Interval at their defaults.
  7. 7Click Save & Apply.
  • ⚠If pings through the VPN interface fail for 5 minutes, watchcat restarts it and the router picks up the new server address.
  • ⚠On OpenWrt 24.10 and older this mode does not restart a WireGuard interface — restart the connection by hand there.

MikroTik

RouterOS supports WireGuard. RouterOS has no AmneziaWG — use a WireGuard configuration. Since RouterOS 7.11, MikroTik states that a peer with a server name follows an address change; if the tunnel still does not come back, restart the peer as below.

How to restart the connection

  1. 1Open WinBox or WebFig and go to WireGuard → the Peers tab.
  2. 2Select the RuSolv peer, disable it (Disable), then enable it again (Enable).
  • ⚠On RouterOS 7.24, disabling and enabling a peer could leave the tunnel not working — fixed in 7.24.1. Update RouterOS to the current stable version.

GL.iNet

The steps are the same for WireGuard and AmneziaWG (AmneziaWG from firmware 4.9).

How to restart the connection

  1. 1Open the router's admin panel and go to VPN → VPN Client Profile (on firmware before 4.9: VPN → WireGuard Client).
  2. 2Turn the RuSolv profile's connection off, then start it again: the three-dot icon → Start. Once it is connected, a green dot lights up next to the profile.
  • ⚠On firmware 4.9 and newer, Kill Switch is on by default for VPN tunnels: if the VPN stops working, devices whose traffic goes through it have no internet at all until you restart the connection.