Heracles31
Heracles31
HHomarr
Created by Heracles31 on 4/28/2025 in #💬・get-help
Homarr struggles with IPv6...
Running a Talos Linux Kubernetes cluster here, configured dual stack IPv4 / IPv6. In that cluster, I have both Keycloak and Homarr (and more...). Keycloak is using 2 URLs (auth.domain.tld and keycloak.domain.tld) to separate users and admin access. Both of these are exposed with an ingress that listens on both IPv4 and IPv6. I also have both A and AAAA records for these names. When I try to configure Homarr for my Keycloak service, it fails. 2025-04-28T03:28:09.512Z error: fetch failed ... at async doRender (/app/node_modules/next/dist/server/base-server.js:1513:42) caused by Error: getaddrinfo ENOTFOUND auth.domain.tld errno="-3007" code="ENOTFOUND" syscall="getaddrinfo" hostname="auth.domain.tld" at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:122:26) at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17) When I open a shell in a pod, Homarr or another, nslookup successfully retrieve both DNS records : (from Homarr's pod here...) /app # nslookup auth.domain.tld Server: 10.96.0.10 Address: 10.96.0.10:53 auth.domain.tld canonical name = nginx-ing64.domain.tld Name: nginx-ing64.domain.tld Address: 172.24.138.10 auth.domain.tld canonical name = nginx-ing64.domain.tld Name: nginx-ing64.domain.tld Address: 2001:0DB8:6000:c4::100 Should I try to connect the SSL socket with OpenSSL from inside Homarr's pod, it fails : /app # openssl s_client -connect auth.domain.tld:443 28AB5B27057F0000:error:10080002:BIO routines:BIO_lookup_ex:system lib:crypto/bio/bio_addr.c:763:Name has no usable address connect:errno=22 The pod itself has both IPv4 and IPv6. In all cases, DNS records and IPs exist for both. Should Homarr be limited to v4, it should still be able to connect to Keycloak. Any idea how to fix that ?
6 replies