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

[PR #396] Make Signal Service listen on a standard 443/80 port instead of 10000 #2739

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

Original Pull Request: https://github.com/netbirdio/netbird/pull/396

State: closed
Merged: Yes

This PR is a part of an effort to use standard ports (443 or 80) that are usually allowed by default in most of the environments.

Right now Signal Service runs the Let'sEncrypt manager on port 443
and a gRPC server on port 10000. There are two separate listeners.
This PR combines these listeners into one
With this change, the gRPC server runs on either 443 with TLS or 80 without TLS
by default (no --port specified).
Let's Encrypt manager always runs on port 443 if enabled.
The backward compatibility server runs on port 10000 (with TLS or without).

Agents that are running and on status Online will still be connected to 10000.
Triggering Agent restart of any version will force it to connect to port 443.

**Original Pull Request:** https://github.com/netbirdio/netbird/pull/396 **State:** closed **Merged:** Yes --- This PR is a part of an effort to use standard ports (443 or 80) that are usually allowed by default in most of the environments. Right now Signal Service runs the Let'sEncrypt manager on port 443 and a gRPC server on port 10000. There are two separate listeners. This PR combines these listeners into one With this change, the gRPC server runs on either 443 with TLS or 80 without TLS by default (no --port specified). Let's Encrypt manager always runs on port 443 if enabled. The backward compatibility server runs on port 10000 (with TLS or without). Agents that are running and on status Online will still be connected to 10000. Triggering Agent restart of any version will force it to connect to port 443.
saavagebueno added the pull-request label 2025-11-20 08:03:50 -05:00
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 pull-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#2739
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?