SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-28 11:02:11 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

reason to not use port 443 also for the vpn connection? #1455

New Issue
Open
opened 2025-11-20 05:30:50 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:30:50 -05:00
Owner
Copy Link

Originally created by @ne0YT on GitHub (Nov 25, 2024).

Is your feature request related to a problem? Please describe.
form some places tcp 443 is open to the internet, but other ports are not. so it would make life easier to be able to connect to tcp 443 form the netbird clients instead.

Describe the solution you'd like
not only use tcp 443 for the webui but also for the vpn

Describe alternatives you've considered
reverse-proxy

Originally created by @ne0YT on GitHub (Nov 25, 2024). **Is your feature request related to a problem? Please describe.** form some places tcp 443 is open to the internet, but other ports are not. so it would make life easier to be able to connect to tcp 443 form the netbird clients instead. **Describe the solution you'd like** not only use tcp 443 for the webui but also for the vpn **Describe alternatives you've considered** reverse-proxy
saavagebueno added the feature-request label 2025-11-20 05:30:50 -05:00
saavagebueno commented 2025-11-20 05:30:51 -05:00
Author
Owner
Copy Link

@saule1508 commented on GitHub (Nov 27, 2024):

I am not sure I understand, but from my experience netbird management and netbird signal both can use 443 (grpc) and for coturn you can also use tcp 443 (address will be turns:...:443?transport=tcp. Also if you use the relay functionality it can use https.
But for wireguard itself, I don't know, I think it uses udp and cannot be changed. Maybe this is what your request would do ?
By having coturn listening on tcp 443 we are able to use netbird client on a restrictive corporate environment (behind zscaler)

@saule1508 commented on GitHub (Nov 27, 2024): I am not sure I understand, but from my experience netbird management and netbird signal both can use 443 (grpc) and for coturn you can also use tcp 443 (address will be turns:...:443?transport=tcp. Also if you use the relay functionality it can use https. But for wireguard itself, I don't know, I think it uses udp and cannot be changed. Maybe this is what your request would do ? By having coturn listening on tcp 443 we are able to use netbird client on a restrictive corporate environment (behind zscaler)
saavagebueno commented 2025-11-20 05:30:51 -05:00
Author
Owner
Copy Link

@mgarces commented on GitHub (Nov 29, 2024):

hi @ne0YT ; like @saule1508 perfectly described, we already run most of the control layer on TCP 443, but what you are asking is related to Wireguard itself. You can configure your client to run on any port (as long as it's available on your host), but this will be UDP, and on restrictive environments, even if 443 and 80 are allowed (TCP), Wireguard would still be blocked (UDP != TCP). Perhaps the best way you could go around this would be to use UDP 53 (DNS), but again, a restrictive network will probably block all requests to UDP 53 for exact IP addresses (like 1.1.1.1).

@mgarces commented on GitHub (Nov 29, 2024): hi @ne0YT ; like @saule1508 perfectly described, we already run most of the control layer on `TCP 443`, but what you are asking is related to Wireguard itself. You can configure your client to run on any port (as long as it's available on your host), but this will be **UDP**, and on restrictive environments, even if `443` and `80` are allowed (**TCP**), Wireguard would still be blocked (UDP != TCP). Perhaps the best way you could go around this would be to use UDP 53 (DNS), but again, a restrictive network will probably block all requests to UDP 53 for exact IP addresses (like `1.1.1.1`).
saavagebueno commented 2025-11-20 05:30:52 -05:00
Author
Owner
Copy Link

@ne0YT commented on GitHub (Nov 29, 2024):

hi @ne0YT ; like @saule1508 perfectly described, we already run most of the control layer on TCP 443, but what you are asking is related to Wireguard itself. You can configure your client to run on any port (as long as it's available on your host), but this will be UDP, and on restrictive environments, even if 443 and 80 are allowed (TCP), Wireguard would still be blocked (UDP != TCP). Perhaps the best way you could go around this would be to use UDP 53 (DNS), but again, a restrictive network will probably block all requests to UDP 53 for exact IP addresses (like 1.1.1.1).

hi @mgarces how do I configure my client ot use port 443 udp?

@ne0YT commented on GitHub (Nov 29, 2024): > hi @ne0YT ; like @saule1508 perfectly described, we already run most of the control layer on `TCP 443`, but what you are asking is related to Wireguard itself. You can configure your client to run on any port (as long as it's available on your host), but this will be **UDP**, and on restrictive environments, even if `443` and `80` are allowed (**TCP**), Wireguard would still be blocked (UDP != TCP). Perhaps the best way you could go around this would be to use UDP 53 (DNS), but again, a restrictive network will probably block all requests to UDP 53 for exact IP addresses (like `1.1.1.1`). hi @mgarces how do I configure my client ot use port 443 udp?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label feature-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1455
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?