Connection refused: `127.0.0.1:80` appended to host

pmeyerin · June 23, 2024, 3:06am

Hi, all

I have a system where I'm trying to get two microservices to communicate with each other secured by a Keycloak auth server. I had everything working when running directly on localhost, but once I started dockerizing them I ran into problems. I'm trying to resolve those with Traefik and I almost have it working.

Looking in the Micronaut logs I see

2024-06-22 21:40:08 02:40:08.110 [main] DEBUG i.m.s.o.c.DefaultOpenIdProviderMetadataFetcher - Sending request for OpenID configuration for provider [keycloak] to URL [http://keycloak.psn.local/realms/spike-realm/.well-known/openid-configuration] running in thread main

Which is right. I can copy that into a browser and see my keycloak's OIDC configuration with the correct hosts set.

Then something goes wrong and a short ways later into the logs I see

2024-06-22 21:40:08 02:40:08.119 [default-nioEventLoopGroup-1-7] ERROR i.m.h.client.netty.DefaultHttpClient - Failed to connect to remote
2024-06-22 21:40:08 io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: keycloak.psn.local/127.0.0.1:80

I don't understand where the host has been transformed to add a localhost IP and http port.

I've tried moving these services out of docker and running them directly on the host machine they can reach keycloak successfully, which is what leads me to suspect this is something related to Traefik, but I don't know what.

I pushed the current state of what I'm working on

github.com

protocol-sn/spikes/blob/spike/1-oauth-in-docker/keycloak-oauth/compose.yaml

version: '1'

services:
  reverse-proxy:
    # The official v3 Traefik docker image
    image: traefik:v3.0
    # Enables the web UI and tells Traefik to listen to docker
    command: 
      - '--api.insecure=true' 
      - '--providers.docker'
#      - '--entrypoints.http.http.redirections.entrypoint.to=https'
#      - '--entrypoints.http.http.redirections.entrypoint.scheme=https'
#      - '--entrypoints.https=true'
#      - '--entrypoints.https.address=:443'
#      - '--certificatesResolvers.letsencrypt.acme.email=me@outlook.com'
#      - '--certificatesResolvers.letsencrypt.acme.storage=/etc/traefik/acme.json'
#      - '--certificatesResolvers.letsencrypt.acme.httpChallenge.entryPoint=http'
      - '--log=true'
      - '--log.format=json'
#      - '--log.filePath=/var/log/traefik/traefik.log'

This file has been truncated. show original

bluepuma77 · June 23, 2024, 11:59am

It seems the domain resolves to localhost. But localhost within a container is not localhost of the host, but only within the container.

pmeyerin · June 23, 2024, 5:23pm

I recreated this problem this morning using nginx proxy manager and got the same result. Looks like my problem lies elsewhere. Thanks to any who read and responded!

Topic		Replies	Views
Connection refused trying to connect to traefik from inside containers Traefik v2 docker	10	12654	October 14, 2021
Help setting up ForwardAuth using Keycloak and traefik-forward-auth Traefik v2 docker	1	7181	October 9, 2022
Traefik, keycloak, docker-compose flutter neither redirect or ssl works Traefik v2 docker	1	462	March 5, 2024
502 Bad Gateway connection refused error Traefik v2 docker	10	10641	December 4, 2020
Docker-ssl-passthrough problem Traefik v2 tcp	12	5479	November 13, 2019

Connection refused: `127.0.0.1:80` appended to host

Related Topics