🐛 Bug Report: IPv6 only HOST #206

New Issue

OVERLORD · 2026-02-04T17:59:56+03:00

OVERLORD commented

2026-02-04 17:59:56 +03:00

Originally created by @q-b on GitHub (Mar 14, 2025).

Reproduction steps

When setting the HOST env var to [::] nodejs fails:

node:events:496
      throw er; // Unhandled 'error' event
      ^

Error: getaddrinfo ENOTFOUND [::]
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)
Emitted 'error' event on Server instance at:
    at GetAddrInfoReqWrap.callback (node:net:2198:12)
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:17) {
  errno: -3008,
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: '[::]'
}

Node.js v22.14.0

When setting it to :: (no brackets) it seems to be happy (I did not test the service) but Caddy complains:

2025/03/14 12:36:27 listen tcp: address :::8020: too many colons in address

Expected behavior

Actual Behavior

Version and Environment

latest v0.40.0 sha256:17079de410ddfccfe2d33b423cad76cb14b2757b77209ffe715aa33f0de68d97

Log Output

No response

Originally created by @q-b on GitHub (Mar 14, 2025). ### Reproduction steps When setting the `HOST` env var to `[::]` nodejs fails: ``` node:events:496 throw er; // Unhandled 'error' event ^ Error: getaddrinfo ENOTFOUND [::] at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26) Emitted 'error' event on Server instance at: at GetAddrInfoReqWrap.callback (node:net:2198:12) at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:17) { errno: -3008, code: 'ENOTFOUND', syscall: 'getaddrinfo', hostname: '[::]' } Node.js v22.14.0 ``` When setting it to `::` (no brackets) it seems to be happy (I did not test the service) but Caddy complains: ``` 2025/03/14 12:36:27 listen tcp: address :::8020: too many colons in address ``` ### Expected behavior - ### Actual Behavior - ### Version and Environment latest v0.40.0 sha256:17079de410ddfccfe2d33b423cad76cb14b2757b77209ffe715aa33f0de68d97 ### Log Output _No response_

OVERLORD added the bug label 2026-02-04 17:59:56 +03:00

OVERLORD closed this issue

2026-02-04 17:59:58 +03:00

OVERLORD commented

2026-02-04 18:00:11 +03:00

@kmendell commented on GitHub (Mar 14, 2025):

If you try setting it with quotes around like this does it work? HOST="::"

@kmendell commented on GitHub (Mar 14, 2025): If you try setting it with quotes around like this does it work? `HOST="::"`

OVERLORD commented

2026-02-04 18:00:12 +03:00

@q-b commented on GitHub (Mar 14, 2025):

It does not.

@q-b commented on GitHub (Mar 14, 2025): It does not.

OVERLORD commented

2026-02-04 18:00:16 +03:00

@stonith404 commented on GitHub (Mar 14, 2025):

What's the reason you're trying to change the HOST inside the Docker container?

@stonith404 commented on GitHub (Mar 14, 2025): What's the reason you're trying to change the HOST inside the Docker container?

OVERLORD commented

2026-02-04 18:00:20 +03:00

@q-b commented on GitHub (Mar 15, 2025):

I'm trying to rely only on IPv6. Not a strong requirement but it helps me to get some habits and uncover some bugs.

@q-b commented on GitHub (Mar 15, 2025): I'm trying to rely only on IPv6. Not a strong requirement but it helps me to get some habits and uncover some bugs.

OVERLORD commented

2026-02-04 18:00:22 +03:00

@stonith404 commented on GitHub (Mar 16, 2025):

It's not really recommended to change these environment variables inside the Docker container. If you really want to change such things I would recommend you to use the standalone installation or build your own Docker image.

@stonith404 commented on GitHub (Mar 16, 2025): It's not really recommended to change these environment variables inside the Docker container. If you really want to change such things I would recommend you to use the standalone installation or build your own Docker image.

OVERLORD commented

2026-02-04 18:00:27 +03:00

@craigcabrey commented on GitHub (Apr 9, 2025):

@q-b I initially had the same problem. But Caddy listens on IPv6 & IPv4 by default, so make sure you're accessing Caddy on port 80, not the application on port 3000.

@craigcabrey commented on GitHub (Apr 9, 2025): @q-b I initially had the same problem. But Caddy listens on IPv6 & IPv4 by default, so make sure you're accessing Caddy on port 80, not the application on port 3000.

OVERLORD referenced this issue

2026-02-04 20:17:51 +03:00

🐛 Bug Report: Something went wrong - Internal Error #505

Sign in to join this conversation.