this post was submitted on 13 Sep 2023
17 points (87.0% liked)

Selfhosted

39939 readers
552 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
17
Problem connecting to host from Docker container (sh.itjust.works)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/selfhosted
9 comments fedilink hide all child comments
 

I followed this Guide to setup headscale with caddy. And tried to add Keycloak with this guide from the same guy.

Sadly my docker containers do not seem to be able to connect to the keycloak server. What happens is that if i try to download the openid configuration from the host (via wget) or from my local PC it just works. But the headscale server gets a timeout when trying to connect to the endpoint. When i use the internal docker name to connect to the keycloak container the connection works fine but then i get an error because its not the external url.

I experimented a bit and managed to reproduce the issue with a different container (running an ubuntu container and also getting a timeout when trying to download the config from keycloak). If i run the container with the host network i works just fine.

Does anyone know how to fix this?

PS: i also tried the example from the guide with gitea an its also the same problem

Update: I tried most suggestions and for some reason it just didn't work. My solution that is working now is that I bind the container ports to localhost only (by using p.e.: ports: -"127.0.0.1:4567:8080") and using the caddy server in host network mode. Now all containers can connect like expected and are working flawlessly. Thanks for all your suggestions :)

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 1 year ago (2 children)

I think it would be easier to use only one docker compose file with all services, and use the same network across all of them

[–] [email protected] 3 points 1 year ago (3 children)

But the network is created externally, so shouldn't this be the same?

[–] [email protected] 2 points 1 year ago

I didn't read the docker files with attention in the first time, but since you have an external network it should work.

[–] [email protected] 1 points 1 year ago

yes is the same, or at least should.

[–] [email protected] 1 points 1 year ago (1 children)

And container to container works fine, im able to communicate p.e. with keycloak:9000

[–] [email protected] 1 points 1 year ago

Do you have coddy to point the DNS to your keyckloak instance like in this part of the tutorial? auth.gurucomputing.com { reverse_proxy http://keycloak:8080 }

Also do you have the domain registered?