-
Notifications
You must be signed in to change notification settings - Fork 486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Destination Host Unreachable, ping: sendmsg: Required key not available #254
Comments
Hello @FarisZR, can you share some details of your setup?
|
1- yes Wiretrustee logs
Compose file
|
Hello @FarisZR sorry for the late response, we've found a bug on our managed service that was affecting some network updates to be propagated. Can you check if the connections are more stable now? In case you still facing this issue, would you mind joining our slack? |
Hi, |
Hi, i have just updated Wiretrustee on both machines, and it now works for some reason.
And Yes, my docker node is also running wireguard on docker, however i don't this is really the cause, as it now works normally with the vpn.
I will keep you updated if any issue pops up.
…On Sat, Mar 12 2022 at 06:02:51 AM -0000, wiretrustee/wiretrustee - reply+aipxadsdtufjdqx4tnie2owahfvarevbnhheky5rui at reply.github.com ***@***.***> wrote:
> Hello, I have been using wiretrustee to expose a local server to a remote VPS.
>
> However, every once in a while it stops working, and this happens:
>
> Logs
>
> # ping 100.64.0.2
> PING 100.64.0.2 (100.64.0.2) 56(84) bytes of data.
> From 100.64.0.1 icmp_seq=1 Destination Host Unreachable
> ping: sendmsg: Required key not available
> From 100.64.0.1 icmp_seq=2 Destination Host Unreachable
> ping: sendmsg: Required key not available
> From 100.64.0.1 icmp_seq=3 Destination Host Unreachable
>
> Removing both peers and re-adding them sometimes fixes it, or peers still can't ping each other.
>
> setup details
>
> one peer is running wiretrustee inside docker, and the other is running a standard Debian installation inside an LXC, with [appropriate options](https://pve.proxmox.com/wiki/OpenVPN_in_LXC)
Hi,
I got same issue. And I realized that I install pivpn with wireguard before. Remove pivpn (and WG) by pivnp -u will solve problem. FYI
—
Reply to this email directly, [view it on GitHub](#254 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AIPXADV46LWAZF3OYFWLLZDU7QXQRANCNFSM5QKBJ7FQ).
Triage notifications on the go with GitHub Mobile for [iOS](https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675) or [Android](https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
The issue is back |
aaaand.. Its gone again. |
An update on this issue. I think this is an issue resides from the LXC side, as I have been using wiretrustee on full servers and it's mostly great. As for slack, unfortunately I don't use Slack, we can continue here, or you can open a matrx.org room which can be bridged to slack. |
Hi, |
Same here. I self-hosted on Linux. (Managed Service same error). And Connected 3 Linux Clients. Works perfectly fine. |
Hi @lyca-knight, What version are you running? Could you please run You might need to install Feel free to DM me on Slack |
Hey @braginini, I reinstalled the Mac to see if it's an error with my setting or something. Yeah, I will leave you a DM on Slack |
Hi @lyca-knight, Could you please run Also, could you share the NetBird IP of your Mac with the output of the above command? |
hi,
got this error while pinging: i'll take any advices thx |
Hello, @hicwic sorry for not replying sooner. This error usually indicates a problem with the P2P connection, it means that the peers didn't negotiate the best connection option. Recently we've improved our core connectivity layer and this kind of issue might be mitigated. |
I found that when "Interface type: Kernel", I can't access 100.124.255.254? write to '100.124.255.254': Required key not available; But how do I switch to "Interface type: Userspace"? OpenWrt 23.05.2 r23630-842932a63d / LuCI openwrt-23.05 branch git-23.306.39416-c86c256 |
I had the same ping errors* today on a new self-hosted install. The client for 2 of 3 peers (one being the server machine itself) for some reason was stopped. I ran The third peer was already running Wireguard. Maybe the quick install option could detect if wg0/51820 are in use and increment if necessary, but a manual tweak was easy enough:
*This issue was top of search so maybe this helps someone else... but more likely me when I forget in a month. |
Same problem here with new self-hosted install |
What version of the netbird client are you running? @grebois |
@braginini 0.26.2, 0.27.0 and 0.27.1 |
I'm expericing this issue right now - self-hosted install using the quick install script with Zitadel. Everything started correctly and the clients connected to the networks properly. However doing a ping gives me this error. Unsure if it's port related or not. |
had this on 0.27.2 ubuntu when pinging a specific peer, rebooting the machine fixed it |
Brand new self hosted install of 0.28.4 had the issue. I found this thread and then I went digging more. I tried restarting nodes and networking, no dice. My issue was solved when I opened wireguard port UDP 51820 to allow for tunneled traffic, specifically on the cloud side. If wireguard is trying to penetrate a hard NAT traversal and doesn't have free access to this port on at least one side, particularly with the public IP, then it can be challenging to bring up a proper p2p connection. This isn't netbird's fault, though they could bring attention to the issue in the docs. Maybe it is there, but I didn't run across it in my last install. I hope this helps. |
Hello, I have been using wiretrustee to expose a local server to a remote VPS.
However, every once in a while it stops working, and this happens:
Logs
Removing both peers and re-adding them sometimes fixes it, or peers still can't ping each other.
setup details
one peer is running wiretrustee inside docker, and the other is running a standard Debian installation inside an LXC, with appropriate options
The text was updated successfully, but these errors were encountered: