# IPv6 not working with new zeus-1 runner?

**URL:** <https://forum.codefloe.com/t/ipv6-not-working-with-new-zeus-1-runner/172>\
**Category:** CI/CD\
**Created:** [September 12, 2026, 7:26pm UTC](https://forum.codefloe.com/t/ipv6-not-working-with-new-zeus-1-runner/172 "2026-09-12T19:26:18Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mbannert](https://forum.codefloe.com/user_avatar/forum.codefloe.com/mbannert/32/159_2.png) [@mbannert](https://forum.codefloe.com/u/mbannert)\
**Post date:** [September 12, 2026, 7:26pm UTC](https://forum.codefloe.com/t/ipv6-not-working-with-new-zeus-1-runner/172/1 "2026-09-12T19:26:18Z")

</div>

Is there a known issue with IPv6 addresses and the latest runners?  
I’ve always used IPv6 ever since you introduced it based on this thread: [Listing of runner's IPv6 addresses? - #2 by codefloe](https://forum.codefloe.com/t/listing-of-runners-ipv6-addresses/110/2)  
In particular, I whitelisted crow runners in my private network’s FW. Lately I am getting errors that crow can’t reach my server:

TASK [Gathering Facts] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

[ERROR]: Task failed: Failed to connect to the host via ssh: ssh: connect to host 2a01:4f8:1c19:d14d::1 port 22: Network unreachable

\*\*fatal: [toolserver]: UNREACHABLE! =\> {“changed”: false, “msg”: “Task failed: Failed to connect to the host via ssh: ssh: connect to host xxxx:yyyy:1c19:d14d::1 port 22: Network unreachable”, “unreachable”: true}  
\*\*  
It’s clearly a FW block on my side that happened because the IPv6 I had previously didn’t work.  
(In the meantime I’ve whitelisted the IPv4 and everything works again.)

Preparing step

Creating container

Connecting container networks

Starting container

apk add --no-cache curl \> /dev/null0s

echo "Agent IPv4:"0s

Agent IPv4:

curl -s -4 ifconfig.me0s

xx.yyy.zzz.203+ echo “Agent IPv6:”

Agent IPv6:

curl -s -6 ifconfig.me1s

---

<div class="post-metadata">

**Author:** ![codefloe](https://forum.codefloe.com/user_avatar/forum.codefloe.com/codefloe/32/42_2.png) [@codefloe](https://forum.codefloe.com/u/codefloe)\
**Post date:** [September 13, 2026, 11:09am UTC](https://forum.codefloe.com/t/ipv6-not-working-with-new-zeus-1-runner/172/2 "2026-09-13T11:09:28Z")

</div>

Thanks for reporting!

Yes, the new Proxmox-based runners didn’t properly receive the IPV6 from their actual host servers. This is now fixed in [https://codefloe.com/codefloe/infrastructure-as-code/pulls/248](https://codefloe.com/codefloe/infrastructure-as-code/pulls/248). Can you check if this works again now on your end?

---

<div class="post-metadata">

**Author:** ![mbannert](https://forum.codefloe.com/user_avatar/forum.codefloe.com/mbannert/32/159_2.png) [@mbannert](https://forum.codefloe.com/u/mbannert)\
**Post date:** [September 18, 2026, 1:59pm UTC](https://forum.codefloe.com/t/ipv6-not-working-with-new-zeus-1-runner/172/3 "2026-09-18T13:59:27Z")

</div>

jeez. you’re so freakin fast. Will take me some time, but will definitely check and report back. Thanks!

---

<div class="post-metadata">

**Author:** ![mbannert](https://forum.codefloe.com/user_avatar/forum.codefloe.com/mbannert/32/159_2.png) [@mbannert](https://forum.codefloe.com/u/mbannert)\
**Post date:** [September 19, 2026, 4:29pm UTC](https://forum.codefloe.com/t/ipv6-not-working-with-new-zeus-1-runner/172/4 "2026-09-19T16:29:14Z")

</div>

Thanks @codefloe, I can confirm it works for my servers. FWIW, the IPv6 changed and an IPv4 fallback did not work for me. However, using the IPv4 now.

---

<div class="post-metadata">

**Author:** ![codefloe](https://forum.codefloe.com/user_avatar/forum.codefloe.com/codefloe/32/42_2.png) [@codefloe](https://forum.codefloe.com/u/codefloe)\
**Post date:** [September 19, 2026, 4:32pm UTC](https://forum.codefloe.com/t/ipv6-not-working-with-new-zeus-1-runner/172/5 "2026-09-19T16:32:04Z")

</div>

> [@mbannert](#):
>
> FWIW, the IPv6 changed and an IPv4 fallback did not work for me. However, using the IPv4 now.

The IPs of Zeus did never change (assuming you were referring to Zeus here). We didn’t add any additional IPs to the Proxmox hosts since you’ve opened the thread.

---

<div class="post-metadata">

**Author:** ![mbannert](https://forum.codefloe.com/user_avatar/forum.codefloe.com/mbannert/32/159_2.png) [@mbannert](https://forum.codefloe.com/u/mbannert)\
**Post date:** [September 19, 2026, 4:37pm UTC](https://forum.codefloe.com/t/ipv6-not-working-with-new-zeus-1-runner/172/6 "2026-09-19T16:37:10Z")

</div>

Ok, just to clarify. What I was trying to say is: When I realized IPv6 did not work, I switch to IPv4, after you announced that you had fixed proxmox I realized my FW was blocking IPv4, so I added the new IPv6 of Zeus and it worked. All I am saying is: It did not fall back to the IPv4. Maybe also be a glitch on my side.

however, successfully using IPv6 of Zeus now. Up and running. Thx!
