Status page broken for IPv6-only?

1

Hi!

I noticed that accessing https://desec-status.net/ on an IPv6-only network is not possible. On e.g. dual-stack setups, it seems fine.

Seems the service behind the status page simply does not listen on the IPv6 address, or some firewall inbetween is blocking it?

E.g. the curl output seems to at least indicate the above:

* Host desec-status.net:443 was resolved.
* IPv6: 2a01:4f8:c0c:834a::1
* IPv4: 94.130.151.107
*   Trying [2a01:4f8:c0c:834a::1]:443...
* connect to 2a01:4f8:c0c:834a::1 port 443 from 2a01:4f8:c17:6f57::1 port 47894 failed: Connection refused
*   Trying 94.130.151.107:443...
2

Also does not work for dual stack.
I get a A and AAAA record but both are unavailable.

3

Hi c8h4,

Thanks for your message, and welcome to deSEC! :slight_smile:

We have fixed this - thank you. I think this broke with some Docker update.

@KapernMagIchNicht I guess you were encountering a connectivity issue while we were fixing things. It should be working again now.

Stay secure,
Peter

3 Likes
4

Works now!




5

Yep, can confirm it now works on IPv6-only!

Thanks a lot!