github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-07-16 14:47:04 -05:00
Code Issues 1.6k Packages Projects Releases 79 Wiki Activity

[GH-ISSUE #2057] Loggin in with Pangolin CLI gives lots of Failed to forward handshake initiation... : write: destination address required errors #32126

New Issue
Closed
opened 2026-06-15 09:24:46 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-06-15 09:24:46 -05:00
Owner
Copy Link

Originally created by @hcwinsemius on GitHub (Dec 12, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2057

Describe the Bug

First, I love pangolin!

Second, I updated today from 1.9.4 to 1.13. I also updated all other dependencies as instructed. Looking at the server logs, once I log in with a machine client with olm, or pangolin CLI, I receive MANY of the messages as below. I have also done a complete install in a separate environment, made one site, made one pangolin CLI login and tested again. I do not see this issue in this case. I have checked and have not seen any BUG report so far that addresses this.

gerbil    | ERROR: YYYY/MM/DD HH:MM:SS Failed to forward handshake initiation: write udp 100.89.128.1:42209->100.89.128.48:51841: write: destination address required

The first IP address is always 100.89.128.1, the second moves around the subnet 100.89.128.0, the last number is changing 24, 36, 40, 48. Port number varies widely.

I can however login to devices, resources, private and public. So from the outside everything seems to work.

Environment

  • OS Type & Version: (e.g., Ubuntu 22.04): Ubuntu 24.04
  • Pangolin Version: 1.13.0
  • Gerbil Version: 1.3.0
  • Traefik Version: v3.6
  • Newt Version: 1.7.0
  • Olm Version: (if applicable) 1.2.0

To Reproduce

  • make sure there are a bunch of sites and resources, including private resources
  • Upgrade server from 1.9.4 to 1.13
  • Login with pangolin CLI
    As soon as I login, the ERROR messages start to appear. When I logout, they stop.

Expected Behavior

No ERROR messages in server.

Originally created by @hcwinsemius on GitHub (Dec 12, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2057 ### Describe the Bug First, I love pangolin! Second, I updated today from 1.9.4 to 1.13. I also updated all other dependencies as instructed. Looking at the server logs, once I log in with a machine client with olm, or pangolin CLI, I receive MANY of the messages as below. I have also done a complete install in a separate environment, made one site, made one pangolin CLI login and tested again. I do not see this issue in this case. I have checked and have not seen any BUG report so far that addresses this. ``` gerbil | ERROR: YYYY/MM/DD HH:MM:SS Failed to forward handshake initiation: write udp 100.89.128.1:42209->100.89.128.48:51841: write: destination address required ``` The first IP address is always 100.89.128.1, the second moves around the subnet 100.89.128.0, the last number is changing 24, 36, 40, 48. Port number varies widely. I can however login to devices, resources, private and public. So from the outside everything seems to work. ### Environment - OS Type & Version: (e.g., Ubuntu 22.04): Ubuntu 24.04 - Pangolin Version: 1.13.0 - Gerbil Version: 1.3.0 - Traefik Version: v3.6 - Newt Version: 1.7.0 - Olm Version: (if applicable) 1.2.0 ### To Reproduce - make sure there are a bunch of sites and resources, including private resources - Upgrade server from 1.9.4 to 1.13 - Login with pangolin CLI As soon as I login, the `ERROR` messages start to appear. When I logout, they stop. ### Expected Behavior No `ERROR` messages in server.
GiteaMirror commented 2026-06-15 09:24:48 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Dec 12, 2025):

Hi! Thanks for trying the new feature!

So just so I understand correctly: you are seeing the log message print
a lot but you are still able to connect to resources just fine using olm
or the desktop clients?

<!-- gh-comment-id:3647953981 --> @oschwartz10612 commented on GitHub (Dec 12, 2025): Hi! Thanks for trying the new feature! So just so I understand correctly: you are seeing the log message print a lot but you are still able to connect to resources just fine using olm or the desktop clients?
GiteaMirror commented 2026-06-15 09:24:48 -05:00
Author
Owner
Copy Link

@hcwinsemius commented on GitHub (Dec 12, 2025):

Yes! To clarify a bit more. I have a large number of field devices that communicate with a 4g modem and sim card. These log in with newt (1.7.0). On my desktop I then want to connect via ssh or vnc. I did this with olm before. I now use the new pangolin cli. Works fine as you say but I do see multiple of these ERROR messages come up each second.

Thanks for the hard work! Pangolin gives exactly what I need for these field devices.

<!-- gh-comment-id:3648151360 --> @hcwinsemius commented on GitHub (Dec 12, 2025): Yes! To clarify a bit more. I have a large number of field devices that communicate with a 4g modem and sim card. These log in with newt (1.7.0). On my desktop I then want to connect via ssh or vnc. I did this with olm before. I now use the new pangolin cli. Works fine as you say but I do see multiple of these ERROR messages come up each second. Thanks for the hard work! Pangolin gives exactly what I need for these field devices.
GiteaMirror commented 2026-06-15 09:24:49 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Dec 12, 2025):

Okay. I think this might be fine then. I think what is maybe happening
is some of the field devices are not responding to the Wireguard
messages and are generating that error.

I quieted up that error in the logs so it is not throwing a bunch of
errors for the next release. 5414d21dcd838df26e246204ca031626ad5ce7ce

<!-- gh-comment-id:3648522618 --> @oschwartz10612 commented on GitHub (Dec 12, 2025): Okay. I think this might be fine then. I think what is maybe happening is some of the field devices are not responding to the Wireguard messages and are generating that error. I quieted up that error in the logs so it is not throwing a bunch of errors for the next release. 5414d21dcd838df26e246204ca031626ad5ce7ce
GiteaMirror commented 2026-06-15 09:24:50 -05:00
Author
Owner
Copy Link

@hcwinsemius commented on GitHub (Dec 13, 2025):

Thanks for the response. I had that feeling also. These devices are indeed also offline for most of the time. They are configured in a power cycle circuit to switch on once every 15 or 30 minutes, do a task and then switch off after about 5 minutes. So they are quiet for more than 80% of the time. Thanks for checking out. If there is anything I could do for you to test this further let me know.

<!-- gh-comment-id:3649206431 --> @hcwinsemius commented on GitHub (Dec 13, 2025): Thanks for the response. I had that feeling also. These devices are indeed also offline for most of the time. They are configured in a power cycle circuit to switch on once every 15 or 30 minutes, do a task and then switch off after about 5 minutes. So they are quiet for more than 80% of the time. Thanks for checking out. If there is anything I could do for you to test this further let me know.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#32126
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?