Skip to content

fix(deploy): bind the API port to localhost - #113

Merged
ASafaeirad merged 1 commit into
mainfrom
fix/bind-ports-localhost
Oct 28, 2026
Merged

ASafaeirad merged 1 commit into
mainfrom
fix/bind-ports-localhost

Conversation

@ASafaeirad

Copy link
Copy Markdown
Member

The deploy workflow publishes the API port as -p ${API_PORT}:${API_PORT}, which binds 0.0.0.0. Docker writes its own iptables rules, so ufw on the server doesn't apply, and port 6060 is reachable from the internet over plain HTTP, skipping nginx and TLS (verified from outside on 2026-10-28). nginx is the only thing that needs the port, and it proxies over loopback.

This binds the port to 127.0.0.1 in deploy.yml and in docker-compose.yaml so both stay the same.

Where to look: the docker run line in the deploy step. Webhooks still arrive through https://github-bot.fullstacksjs.com → nginx → 127.0.0.1:6060.

Not tested in CI: the workflow only runs on a published release. I'm recreating the running container by hand with the same flag now, and this PR keeps it that way on the next release.

Side effect for local dev: docker compose up now serves the port on localhost only, not on the LAN.

Note

This PR is generated by Claude Opus 5.5 using Claude Code.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ASafaeirad
ASafaeirad merged commit 100165a into main Oct 28, 2026
2 checks passed
@ASafaeirad
ASafaeirad deleted the fix/bind-ports-localhost branch October 28, 2026 10:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant