Hello
I have two StartOS servers running. The both are reachable through lokal IP or servername.local.
It have worked fine through StartTunell set up on a VPS. But now I can not reach the servers via the WireGuard tunnel.
I can connect to the VPS and StartTunnel opens, do not see anything wierd, but not sure what to look for.
The windows WireGurad klients on several computers connect, give green check, and handshake works. Also on Android it shake hands.
This all worked earlier, I have not changed any settings on my two servers or the StartTunnel, that I know about. But somehow it does not connect
I can ping the StartTunell VPS and also gateway. I can ping from one Windows client to the other, and back. I can ping my phone. All through the StartTunell. And get Reply.
On local network I get ping replyes from the StartOS servers on IP and name.local
But I get “Destination host unreachable.” when I try to ping any of my StartOS servers via the wireguard StartTunell.
SO, why does it not work? Not sure where to go from here.
Seams like the StartTunell works (devices ping eachother), and the StartOS servers works (works on local network, and services connect to the internet). I have not changed any settings.
But I can not connect like before via the StartTunell to the StartOS servers. Both.
If anyone can help, I would love that.
Greetings
Additional info: My two servers is one clean install of 0.4.0 and one updated from 0.3.5.1
Both on the latest update. Have been working for a long time.
Hey, thanks for the detailed writeup — that’s helpful.
Since your Windows and Android clients handshake fine and can ping each other and the VPS through the tunnel, the tunnel itself is up. This looks specific to how traffic is routed to your two StartOS boxes rather than a general WireGuard problem.
A few things to check:
In the StartTunnel dashboard, check that you’re running the latest version and update from there if not — there have been a couple of reliability fixes recently around automatic routes not renewing properly until the tunnel is restarted.
If still issue persists, use the restart option in the StartTunnel dashboard (under Settings) to restart the tunnel. That’s cleared up similar “stuck routing” reports before.
On each StartOS server, go to System > Gateways and remove/re-add the StartTunnel gateway. This forces a fresh WireGuard connection between that server and the tunnel, which can clear up a stuck state that a simple restart on the VPS side won’t touch. Test again after each server.
One more thing — you mentioned your servers are on “0.4.0.” The current stable is 0.4.0.1. Can you confirm both boxes show 0.4.0.1 specifically under System? If either is sitting on an earlier 0.4.0.x point release, that’s worth ruling out too. Let us know if you had any progress.
This worked!! Delete the Wireguard config frem the servers and set up a new config. I was thinking it had to be on the server side, but found it odd that both of them did have the same problem.
Anyway, THANKS h0mer!!
What about showing an “online/offline” status on the Devices in StartTunell?? That would have showed where the problem was.