On Debian 13 amd64 server, I try to connect Olm client to my Pangolin (Gerbil) instance only via ipv6.
The goal is to establish a site to site connection to my Newt instances.
root@debian-amd64:/usr/local/bin# systemctl status olm --no-pager -l
● olm.service - Olm
Loaded: loaded (/etc/systemd/system/olm.service; disabled; preset: enabled)
Active: active (running) since Thu 2025-09-04 01:06:29 CEST; 12min ago
Invocation: ce950cb0c60b4ebdb010192d004f8228
Main PID: 1070661 (olm)
Tasks: 19 (limit: 76567)
Memory: 12.2M (peak: 13M)
CPU: 241ms
CGroup: /system.slice/olm.service
└─1070661 /usr/local/bin/olm --id <redacted> --secret <redacted> --endpoint <redacted> --holepunch
Sep 04 01:06:30 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:30 UDP hole punch goroutine ended for all exit nodes
Sep 04 01:06:30 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:30 UDP hole punch goroutine ended
Sep 04 01:06:31 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:31 UAPI listener started
Sep 04 01:06:31 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:31 Started monitoring for site 2 at 100.90.128.1:64639
Sep 04 01:06:31 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:31 Configured peer Q9hjJ19LYyA/wewcekHXdH7q7MpMb/pMt+YRfDh2wVc=
Sep 04 01:06:31 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:31 Started monitoring peer 2
Sep 04 01:06:31 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:31 WireGuard device created.
Sep 04 01:06:34 debian-amd64 olm[1070661]: WARN: 2025/09/04 01:06:34 Peer 2 is disconnected
Sep 04 01:06:34 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:34 Sent relay message
Sep 04 01:06:34 debian-amd64 olm[1070661]: ERROR: 2025/09/04 01:06:34 Failed to configure WireGuard device: IPC error -22: failed to set endpoint 2a01:cb05:810e:bb00:9876:5432:1098:7654:21820: invalid ip:port "xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:21820", IPv6 addresses must be surrounded by square brackets
I redacted my ipv6 but the DNS entry was correct.
I did encounter this issue before too with the previous Olm version, but with the current Olm version 1.1.1 the issue is no more related to colons but brackets now as you can see.
Originally created by @kevin-gillet on GitHub (Sep 3, 2025).
Original GitHub issue: https://github.com/fosrl/olm/issues/25
On Debian 13 amd64 server, I try to connect Olm client to my Pangolin (Gerbil) instance only via ipv6.
The goal is to establish a site to site connection to my Newt instances.
```
root@debian-amd64:/usr/local/bin# systemctl status olm --no-pager -l
● olm.service - Olm
Loaded: loaded (/etc/systemd/system/olm.service; disabled; preset: enabled)
Active: active (running) since Thu 2025-09-04 01:06:29 CEST; 12min ago
Invocation: ce950cb0c60b4ebdb010192d004f8228
Main PID: 1070661 (olm)
Tasks: 19 (limit: 76567)
Memory: 12.2M (peak: 13M)
CPU: 241ms
CGroup: /system.slice/olm.service
└─1070661 /usr/local/bin/olm --id <redacted> --secret <redacted> --endpoint <redacted> --holepunch
Sep 04 01:06:30 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:30 UDP hole punch goroutine ended for all exit nodes
Sep 04 01:06:30 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:30 UDP hole punch goroutine ended
Sep 04 01:06:31 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:31 UAPI listener started
Sep 04 01:06:31 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:31 Started monitoring for site 2 at 100.90.128.1:64639
Sep 04 01:06:31 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:31 Configured peer Q9hjJ19LYyA/wewcekHXdH7q7MpMb/pMt+YRfDh2wVc=
Sep 04 01:06:31 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:31 Started monitoring peer 2
Sep 04 01:06:31 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:31 WireGuard device created.
Sep 04 01:06:34 debian-amd64 olm[1070661]: WARN: 2025/09/04 01:06:34 Peer 2 is disconnected
Sep 04 01:06:34 debian-amd64 olm[1070661]: INFO: 2025/09/04 01:06:34 Sent relay message
Sep 04 01:06:34 debian-amd64 olm[1070661]: ERROR: 2025/09/04 01:06:34 Failed to configure WireGuard device: IPC error -22: failed to set endpoint 2a01:cb05:810e:bb00:9876:5432:1098:7654:21820: invalid ip:port "xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:21820", IPv6 addresses must be surrounded by square brackets
```
I redacted my ipv6 but the DNS entry was correct.
I did encounter [this issue](https://github.com/fosrl/olm/issues/8) before too with the previous Olm version, but with the current **Olm version 1.1.1** the issue is no more related to colons but brackets now as you can see.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @kevin-gillet on GitHub (Sep 3, 2025).
Original GitHub issue: https://github.com/fosrl/olm/issues/25
On Debian 13 amd64 server, I try to connect Olm client to my Pangolin (Gerbil) instance only via ipv6.
The goal is to establish a site to site connection to my Newt instances.
I redacted my ipv6 but the DNS entry was correct.
I did encounter this issue before too with the previous Olm version, but with the current Olm version 1.1.1 the issue is no more related to colons but brackets now as you can see.