Basic Wireguard connections not working after Pangolin restart #1280

Closed
opened 2026-04-05 18:43:14 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @sstickel on 7/3/2025

Hello everybody.

As I was having trouble getting decent speeds using Newt I tested the Basic Wireguard Tunnel to connect my Nextcloud and Jellyfin to Pangolin. This worked almost flawlessly and the down speed is way higher now (Jellyfin Movie Download in the sub 5MB/s range using Newt and now almost hitting my upload limit at around 22MB/s)

The problem that I am facing is that all the Wireguard tunnels are dead after I restart the Pangolin stack. Pangolin no longer answers the handshake requests of all my Wireguard clients.

I found a workaround: Switch the resources that use Wireguard Sites to a different site and back to the original and the tunnels work again.

A second problem occurred today testing around a little bit. I installed Wireguard on my openWRT router at home and set up a raw tcp forward for testing with iperf3. I got a handshake but was unable to even ping 100.89.128.1. Pinging from the client side just did nothing, pinging the client IP (100.89.128.32) from inside the gerbil container resulted in this.

/ # ping 100.89.128.32
PING 100.89.128.32 (100.89.128.32): 56 data bytes
ping: sendto: Required key not available

Don't ask me what brought up the idea to test the following, but it worked: As soon as I created another (bogus) resource which was NOT raw tcp but a proxy to that openWRT wireguard site the raw forward started to work properly. Ping was possible from both sides, also the iperf forward worked.

If I can help out with logs, testing a dev version or whatever, please tell. If you think these are two independent bugs I will happily create another one and edit the other one out here.

Best,
Sebastian

*Originally created by @sstickel on 7/3/2025* Hello everybody. As I was having trouble getting decent speeds using Newt I tested the Basic Wireguard Tunnel to connect my Nextcloud and Jellyfin to Pangolin. This worked almost flawlessly and the down speed is way higher now (Jellyfin Movie Download in the sub 5MB/s range using Newt and now almost hitting my upload limit at around 22MB/s) The problem that I am facing is that all the Wireguard tunnels are dead after I restart the Pangolin stack. Pangolin no longer answers the handshake requests of all my Wireguard clients. I found a workaround: Switch the resources that use Wireguard Sites to a different site and back to the original and the tunnels work again. A second problem occurred today testing around a little bit. I installed Wireguard on my openWRT router at home and set up a raw tcp forward for testing with iperf3. I got a handshake but was unable to even ping 100.89.128.1. Pinging from the client side just did nothing, pinging the client IP (100.89.128.32) from inside the gerbil container resulted in this. `/ # ping 100.89.128.32` `PING 100.89.128.32 (100.89.128.32): 56 data bytes` `ping: sendto: Required key not available` Don't ask me what brought up the idea to test the following, but it worked: As soon as I created another (bogus) resource which was NOT raw tcp but a proxy to that openWRT wireguard site the raw forward started to work properly. Ping was possible from both sides, also the iperf forward worked. If I can help out with logs, testing a dev version or whatever, please tell. If you think these are two independent bugs I will happily create another one and edit the other one out here. Best, Sebastian
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#1280