Comment on Caddy touble in Docker
doeknius_gloek@discuss.tchncs.de 1 week ago
Is your Caddy actually reachable on port 443 when you use the Container Station App?
My first thought was that your NAS might use port 443 for its own web ui?
Yes it works fine if I build the container from The imagine directly inside the container station app, but I’m having trouble pointing that to the Caddyfile.
If I try to create the container from a docker compose file, it says it can’t bind to port 443 because it’s already in use.
Have you tried running it but not exposing any ports using docker compose?
EDIT: Saw that it worked with 4443:443.
damnthefilibuster@lemmy.world 1 week ago
Yeah, most likely the Compose version is aware of the ports in use and 443 is pretty standard for the NAS to keep to itself. The direct docker process would not be aware of the default config, or env Vars.
Also, welcome to Selfhosing! 😂