github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-06 12:55:03 -05:00
Code Issues 477 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #711] Issues with TCP + UDP services #6382

New Issue
Closed
opened 2026-04-25 15:15:31 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-25 15:15:31 -05:00
Owner
Copy Link

Originally created by @kapsikkum on GitHub (May 12, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/711

Services that require both TCP and UDP on the same port only allow TCP. (Such as Mumble server)

Is there a workaround for this?

Originally created by @kapsikkum on GitHub (May 12, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/711 Services that require both TCP and UDP on the same port only allow TCP. (Such as Mumble server) Is there a workaround for this?
GiteaMirror added the stale label 2026-04-25 15:15:31 -05:00
GiteaMirror commented 2026-04-25 15:15:36 -05:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (May 12, 2025):

You should be able to create two Pangolin resources of different protocols. Let me know if there are any issues with this.

<!-- gh-comment-id:2873881497 --> @miloschwartz commented on GitHub (May 12, 2025): You should be able to create two Pangolin resources of different protocols. Let me know if there are any issues with this.
GiteaMirror commented 2026-04-25 15:15:38 -05:00
Author
Owner
Copy Link

@kapsikkum commented on GitHub (May 13, 2025):

Currently using the murmur mumble server with port 64738 open on both TCP and UDP with pangolin, and the server can only use TCP. UDP does not go through.

<!-- gh-comment-id:2876017608 --> @kapsikkum commented on GitHub (May 13, 2025): Currently using the murmur mumble server with port 64738 open on both TCP and UDP with pangolin, and the server can only use TCP. UDP does not go through.
GiteaMirror commented 2026-04-25 15:15:39 -05:00
Author
Owner
Copy Link

@Momi-V commented on GitHub (May 13, 2025):

I had a similar issue recently with a StorJ node not detecting quic support despite port 28967 TCP+UDP being forwarded, at least TCP working and everything set correctly in the compose and Traefik configuration.

What solved it for me was running Newt with network_mode: host.

<!-- gh-comment-id:2876697286 --> @Momi-V commented on GitHub (May 13, 2025): I had a similar issue recently with a StorJ node not detecting quic support despite port 28967 TCP+UDP being forwarded, at least TCP working and everything set correctly in the compose and Traefik configuration. What solved it for me was running Newt with `network_mode: host`.
GiteaMirror commented 2026-04-25 15:15:40 -05:00
Author
Owner
Copy Link

@TheRealTrip commented on GitHub (May 20, 2025):

I tried with two Pangolin resources set to the TCP and UDP ports and I can't seem to reach mumble through it, I just migrated from Nginx so I think that the issue lies with Pangolin. Are there any log files I should provide? I don't containerize newt.

<!-- gh-comment-id:2895523327 --> @TheRealTrip commented on GitHub (May 20, 2025): I tried with two Pangolin resources set to the TCP and UDP ports and I can't seem to reach mumble through it, I just migrated from Nginx so I think that the issue lies with Pangolin. Are there any log files I should provide? I don't containerize newt.
GiteaMirror commented 2026-04-25 15:15:41 -05:00
Author
Owner
Copy Link

@kapsikkum commented on GitHub (May 21, 2025):

Setting network_mode: host made no difference for me. UDP services are very spotty in general, for example, running a wireguard server has client handshake issues. Doesn't seem to be any errors either.

<!-- gh-comment-id:2897194750 --> @kapsikkum commented on GitHub (May 21, 2025): Setting `network_mode: host` made no difference for me. UDP services are very spotty in general, for example, running a wireguard server has client handshake issues. Doesn't seem to be any errors either.
GiteaMirror commented 2026-04-25 15:15:41 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 5, 2025):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

<!-- gh-comment-id:2942185052 --> @github-actions[bot] commented on GitHub (Jun 5, 2025): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
GiteaMirror commented 2026-04-25 15:15:43 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 19, 2025):

This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.

<!-- gh-comment-id:2986124507 --> @github-actions[bot] commented on GitHub (Jun 19, 2025): This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
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 stale
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#6382
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?