NexaaNexaa
All ideas

IPv6 blocked on ingress by default

The default 0.0.0.0/0 gives 403's on ingress on IPv6. Adding ::0/0 resolves this, it should probably be added to the default. drbob@stingray purposepilot % wget https://next.purposepilot.co --2025-10-23 17:27:45-- https://next.purposepilot.co/ Resolving next.purposepilot.co (next.purposepilot.co)... 84.22.96.186 Connecting to next.purposepilot.co (next.purposepilot.co)|84.22.96.186|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 25907 (25K) [text/html] Saving to: ‘index.html.1’ index.html.1 100%[===========================================================================================>] 25.30K --.-KB/s in 0.04s 2025-10-23 17:27:46 (669 KB/s) - ‘index.html.1’ saved [25907/25907] drbob@stingray purposepilot % wget https://next.purposepilot.co --2025-10-23 17:30:13-- https://next.purposepilot.co/ Resolving next.purposepilot.co (next.purposepilot.co)... 2a02:2770:12::1:0:3, 84.22.96.186 Connecting to next.purposepilot.co (next.purposepilot.co)|2a02:2770:12::1:0:3|:443... connected. HTTP request sent, awaiting response... 403 Forbidden 2025-10-23 17:30:13 ERROR 403: Forbidden.

Activity · 2
mathijs
mathijs1y
deletedmarked this as In Progress· 1y
Mark van den Boogaard
Mark van den Boogaard1y
It looks like 0.0.0.0/0 is filled in manually in the allow-list. This will indeed set an allow-list for everything IPv4 related and will block all IPv6 traffic. When the allow-list is completely empty we allow all traffic for IPv4 and IPv6 (so 0.0.0.0/0 and ::/0). Otherwise you have to add ::/0 as well to allow IPv6 traffic. We did see the information pop-up was not mentioning the IPv6 part. We will update the information pop-up so it mentions both.
Mark van den Boogaardmarked this as Closed· 1y

More in Improvement