-
-
Notifications
You must be signed in to change notification settings - Fork 1k
Fix: Signal container backend port set to right value #5039
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
base: main
Are you sure you want to change the base?
Conversation
|
|
📝 WalkthroughWalkthroughThe Signal service port mapping in the docker-compose template is changed from a hardcoded Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related issues
Suggested reviewers
Poem
Pre-merge checks✅ Passed checks (3 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR fixes a port configuration issue in the Signal container's Docker Compose setup. The backend port was incorrectly hardcoded to port 80, when the Signal container actually listens on port 10000 by default.
- Corrects the Signal container's port mapping to use the
NETBIRD_SIGNAL_PORTenvironment variable for both host and container ports
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🤖 Fix all issues with AI Agents
In @infrastructure_files/docker-compose.yml.tmpl:
- Line 49: The docker compose port mapping uses $NETBIRD_SIGNAL_PORT as the
container port but the service process is configured to listen on port 80,
causing a mismatch; fix by making the host:container mapping match the process
port (e.g., change the port mapping entry from "-
$NETBIRD_SIGNAL_PORT:$NETBIRD_SIGNAL_PORT" to "- $NETBIRD_SIGNAL_PORT:80") or
alternatively change the signal service to listen on $NETBIRD_SIGNAL_PORT so
both sides use the same port; apply the same consistent change for the other
occurrences in the signal service block (the entries around 53-58).
| - $LETSENCRYPT_VOLUMENAME:/etc/letsencrypt:ro | ||
| ports: | ||
| - $NETBIRD_SIGNAL_PORT:80 | ||
| - $NETBIRD_SIGNAL_PORT:$NETBIRD_SIGNAL_PORT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Critical: Port mapping and listening port are mismatched.
Line 49 maps $NETBIRD_SIGNAL_PORT:$NETBIRD_SIGNAL_PORT (container port), but line 57 configures the signal service to listen on port 80. This mismatch will break the service—traffic sent to the container's $NETBIRD_SIGNAL_PORT won't reach the process listening on port 80.
🔎 Proposed fix
command: [
"--cert-file", "$NETBIRD_MGMT_API_CERT_FILE",
"--cert-key", "$NETBIRD_MGMT_API_CERT_KEY_FILE",
"--log-file", "console",
- "--port", "80"
+ "--port", "$NETBIRD_SIGNAL_PORT"
]Also applies to: 53-58
🤖 Prompt for AI Agents
In @infrastructure_files/docker-compose.yml.tmpl at line 49, The docker compose
port mapping uses $NETBIRD_SIGNAL_PORT as the container port but the service
process is configured to listen on port 80, causing a mismatch; fix by making
the host:container mapping match the process port (e.g., change the port mapping
entry from "- $NETBIRD_SIGNAL_PORT:$NETBIRD_SIGNAL_PORT" to "-
$NETBIRD_SIGNAL_PORT:80") or alternatively change the signal service to listen
on $NETBIRD_SIGNAL_PORT so both sides use the same port; apply the same
consistent change for the other occurrences in the signal service block (the
entries around 53-58).



Describe your changes
The backend port for the signal container was wrongly set to port 80 where the listenting port of the container is 10000 by default.
Stack
Checklist
Documentation
Select exactly one:
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.