Skip to content

fix: docker container not listening on all interfaces#11

Closed
nerdo wants to merge 1 commit intoCaddyGlow:mainfrom
nerdo:main
Closed

fix: docker container not listening on all interfaces#11
nerdo wants to merge 1 commit intoCaddyGlow:mainfrom
nerdo:main

Conversation

@nerdo
Copy link
Contributor

@nerdo nerdo commented Aug 20, 2025

The environment variable in the Dockerfile needed to set SERVER__HOST to 0.0.0.0 to listen on all interfaces.

PORT was being set, but it wasn't making its way into the server, causing it to listen on only the loopback address by default.

This was preventing access from the docker host even if the port was exposed.

The environment variable in the Dockerfile needed to set SERVER__HOST to 0.0.0.0 to listen on all interfaces.

PORT was being set, but it wasn't making its way into the server, causing it to listen on only the loopback address by default.

This was preventing access from the docker host even if the port was exposed.
CaddyGlow added a commit that referenced this pull request Aug 21, 2025
* fix: docker container not listening on all interfaces

The environment variable in the Dockerfile needed to set SERVER__HOST to 0.0.0.0 to listen on all interfaces.

PORT was being set, but it wasn't making its way into the server, causing it to listen on only the loopback address by default.

This was preventing access from the docker host even if the port was exposed.

* fix: update Docker configs to use consistent SERVER__ env vars

---------

Co-authored-by: Dannel Albert <cuebix@gmail.com>
@CaddyGlow
Copy link
Owner

Merged in #12 (due to permission issue) after updating other vairables.

@CaddyGlow CaddyGlow closed this Aug 21, 2025
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.

2 participants