fix IPv6 #1

Closed
opened 2025-07-09 11:39:50 -04:00 by p4u · 9 comments

Hello!
Your services are currently unreachable via the IPv6 address listed in the DNS. It results in a timeout. Please fix that.

kind regards
Marco

Hello! Your services are currently unreachable via the IPv6 address listed in the DNS. It results in a timeout. Please fix that. kind regards Marco
Owner

I've used Mullvad Browser to test this and see something about the IPv6 has updated. I went ahead and updated the DNS for sudovanilla.org and connections via IPv6 should work now.
Close this issue if it is successfully working now on your end.

I've used Mullvad Browser to test this and see something about the IPv6 has updated. I went ahead and updated the DNS for sudovanilla.org and connections via IPv6 should work now. Close this issue if it is successfully working now on your end.
Author

IPv6 is still not working.
It resolves to 2600:6c5d:5800:5fb4::7a8. Is that correct?
Does the system listen on that and doesn't a firewall block the traffic?

IPv6 is still not working. It resolves to 2600:6c5d:5800:5fb4::7a8. Is that correct? Does the system listen on that and doesn't a firewall block the traffic?
Owner

There is no firewall blocking port 443. What service are you trying to connect to specifically?

There is no firewall blocking port 443. What service are you trying to connect to specifically?
Author

sudovanilla.org port 80 and 443.
Please test with curl etc. from a remote system to verify.
I can confirm that IPv4 works, but IPv6 doesn't.

You can use an online IPv6 port scanner to check too.

m@ryz:~$ sudo traceroute -p 443 sudovanilla.org -T
traceroute to sudovanilla.org (2600:6c5d:5800:5fb4::7a8), 30 hops max, 80 byte packets
 1  2a01:170:118f:2::1 (2a01:170:118f:2::1)  2.144 ms  2.142 ms  2.510 ms
 2  2a01:170:0:10::1 (2a01:170:0:10::1)  12.357 ms  12.382 ms *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  charter-20115-as20115.e0-15.core1.stl1.he.net (2001:470:0:4c0::2)  113.429 ms  113.463 ms  113.431 ms
13  lag-802.bbr01blvlil.netops.charter.com (2001:506:100:68::6)  118.614 ms  118.647 ms *
14  * * *
15  lag-5.rcr01sghlgaao.netops.charter.com (2001:506:100:5505::6)  133.827 ms  128.522 ms  128.596 ms
16  lag-11.rcr01mnchtnem.netops.charter.com (2001:506:100:5dfd::5)  139.598 ms lag-10.rcr01mnchtnem.netops.charter.com (2001:506:100:5dfc::7)  140.798 ms lag-11.rcr01mnchtnem.netops.charter.com (2001:506:100:5dfd::5)  149.027 ms
17  lag-100.crr01mnchtn.netops.charter.com (2001:506:100:5dfd::7)  139.383 ms  140.071 ms  139.952 ms
18  * * *
19  lag-1.mavltn3902w-dtr2.netops.charter.com (2001:506:100:5cff::5)  147.567 ms lag-10.mavltn3902w-dtr2.netops.charter.com (2001:506:100:5d2d::5)  142.113 ms lag-1.mavltn3902w-dtr2.netops.charter.com (2001:506:100:5cff::5)  147.603 ms
20  * * *
21  * * syn-2600-6c5d-7009-0100-58be-f380-f79d-e6cc.biz6.spectrum.com (2600:6c5d:7009:100:58be:f380:f79d:e6cc)  146.647 ms
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
m@ryz:~$ 
sudovanilla.org port 80 and 443. Please test with curl etc. from a remote system to verify. I can confirm that IPv4 works, but IPv6 doesn't. You can use an online IPv6 port scanner to check too. ``` m@ryz:~$ sudo traceroute -p 443 sudovanilla.org -T traceroute to sudovanilla.org (2600:6c5d:5800:5fb4::7a8), 30 hops max, 80 byte packets 1 2a01:170:118f:2::1 (2a01:170:118f:2::1) 2.144 ms 2.142 ms 2.510 ms 2 2a01:170:0:10::1 (2a01:170:0:10::1) 12.357 ms 12.382 ms * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 charter-20115-as20115.e0-15.core1.stl1.he.net (2001:470:0:4c0::2) 113.429 ms 113.463 ms 113.431 ms 13 lag-802.bbr01blvlil.netops.charter.com (2001:506:100:68::6) 118.614 ms 118.647 ms * 14 * * * 15 lag-5.rcr01sghlgaao.netops.charter.com (2001:506:100:5505::6) 133.827 ms 128.522 ms 128.596 ms 16 lag-11.rcr01mnchtnem.netops.charter.com (2001:506:100:5dfd::5) 139.598 ms lag-10.rcr01mnchtnem.netops.charter.com (2001:506:100:5dfc::7) 140.798 ms lag-11.rcr01mnchtnem.netops.charter.com (2001:506:100:5dfd::5) 149.027 ms 17 lag-100.crr01mnchtn.netops.charter.com (2001:506:100:5dfd::7) 139.383 ms 140.071 ms 139.952 ms 18 * * * 19 lag-1.mavltn3902w-dtr2.netops.charter.com (2001:506:100:5cff::5) 147.567 ms lag-10.mavltn3902w-dtr2.netops.charter.com (2001:506:100:5d2d::5) 142.113 ms lag-1.mavltn3902w-dtr2.netops.charter.com (2001:506:100:5cff::5) 147.603 ms 20 * * * 21 * * syn-2600-6c5d-7009-0100-58be-f380-f79d-e6cc.biz6.spectrum.com (2600:6c5d:7009:100:58be:f380:f79d:e6cc) 146.647 ms 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * m@ryz:~$ ```
Owner

I ran this on my end, testing from an outside connection, and a lot of connections do appear from Charter Spectrum. I would like note this is the ISP for SudoVanilla.

I also now see it's possible to connect to my own IP address via https://35.132.XXX.XXX with a HTTPS protocol, which was not possible in the past. So I don't think that's the issue either. This should allow me to add other services in the future like a Matrix server.

❯ sudo traceroute -p 80 sudovanilla.org -T
traceroute to sudovanilla.org (2600:6c5d:5800:5fb4::7a8), 30 hops max, 80 byte packets
 1  2607:fb90:8de3:1070::4 (2607:fb90:8de3:1070::4)  20.459 ms  20.417 ms  20.405 ms
 2  fc00:10:5:122::254 (fc00:10:5:122::254)  96.849 ms * *
 3  * * fc00:10:6:122::254 (fc00:10:6:122::254)  92.327 ms
 4  * * *
 5  ::ffff:10.188.62.39 (::ffff:10.188.62.39)  96.762 ms  96.752 ms  96.742 ms
 6  ae52.bar3.Detroit1.Level3.net (2001:1900:2100:32::e5)  97.723 ms  77.251 ms *
 7  2001:1900::3:1ee (2001:1900::3:1ee)  79.454 ms  79.416 ms  53.741 ms
 8  e0-36.core2.det1.he.net (2001:470:0:165::2)  73.906 ms  73.880 ms  83.254 ms
 9  * * *
10  * * *
11  * * *
12  charter-20115-as20115.e0-15.core1.stl1.he.net (2001:470:0:4c0::2)  76.175 ms  65.613 ms  79.771 ms
13  * lag-802.bbr01blvlil.netops.charter.com (2001:506:100:68::6)  83.167 ms *
14  * * *
15  lag-5.rcr01sghlgaao.netops.charter.com (2001:506:100:5505::6)  218.223 ms  218.196 ms  138.338 ms
16  lag-11.rcr01mnchtnem.netops.charter.com (2001:506:100:5dfd::5)  132.463 ms  132.388 ms lag-10.rcr01mnchtnem.netops.charter.com (2001:506:100:5dfc::7)  132.280 ms
17  lag-100.crr01mnchtn.netops.charter.com (2001:506:100:5dfd::7)  126.327 ms *  132.119 ms
18  lag-1.mavltn3901w-dtr1.netops.charter.com (2001:506:100:5cfa::4)  115.869 ms  133.661 ms  133.571 ms
19  lag-1.mavltn3902w-dtr2.netops.charter.com (2001:506:100:5cff::5)  109.702 ms lag-10.mavltn3902w-dtr2.netops.charter.com (2001:506:100:5d2d::5)  113.861 ms  113.834 ms
20  * * *
21  syn-2600-6c5d-7009-0100-58be-f380-f79d-e6cc.biz6.spectrum.com (2600:6c5d:7009:100:58be:f380:f79d:e6cc)  131.001 ms  126.758 ms  112.991 ms
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
❯ sudo traceroute -p 443 sudovanilla.org -T
traceroute to sudovanilla.org (2600:6c5d:5800:5fb4::7a8), 30 hops max, 80 byte packets
 1  2607:fb90:8de3:1070::4 (2607:fb90:8de3:1070::4)  7.049 ms  7.027 ms  7.021 ms
 2  * fc00:10:6:122::254 (fc00:10:6:122::254)  51.961 ms  51.955 ms
 3  * fc00:10:6:122::254 (fc00:10:6:122::254)  48.861 ms *
 4  fd00:976a:c000:1::48 (fd00:976a:c000:1::48)  48.867 ms * *
 5  ::ffff:10.188.62.40 (::ffff:10.188.62.40)  51.925 ms ::ffff:10.188.62.39 (::ffff:10.188.62.39)  51.815 ms  53.618 ms
 6  ae52.bar3.Detroit1.Level3.net (2001:1900:2100:32::e5)  55.526 ms  48.447 ms  48.411 ms
 7  2001:1900::3:1ee (2001:1900::3:1ee)  62.615 ms  62.571 ms  62.550 ms
 8  e0-36.core2.det1.he.net (2001:470:0:165::2)  92.764 ms * *
 9  * * *
10  * * *
11  * * *
12  charter-20115-as20115.e0-15.core1.stl1.he.net (2001:470:0:4c0::2)  88.603 ms  88.579 ms  88.575 ms
13  lag-802.bbr01blvlil.netops.charter.com (2001:506:100:68::6)  88.590 ms *  88.155 ms
14  * * *
15  lag-5.rcr01sghlgaao.netops.charter.com (2001:506:100:5505::6)  102.007 ms  97.630 ms  107.533 ms
16  lag-10.rcr01mnchtnem.netops.charter.com (2001:506:100:5dfc::7)  117.784 ms lag-11.rcr01mnchtnem.netops.charter.com (2001:506:100:5dfd::5)  117.905 ms  117.900 ms
17  * lag-100.crr01mnchtn.netops.charter.com (2001:506:100:5dfd::7)  117.762 ms  117.755 ms
18  * lag-1.mavltn3901w-dtr1.netops.charter.com (2001:506:100:5cfa::4)  105.650 ms  115.392 ms
19  lag-1.mavltn3902w-dtr2.netops.charter.com (2001:506:100:5cff::5)  112.930 ms  107.496 ms *
20  syn-2600-6c5d-7009-0100-58be-f380-f79d-e6cc.biz6.spectrum.com (2600:6c5d:7009:100:58be:f380:f79d:e6cc)  129.968 ms * *
21  * * syn-2600-6c5d-7009-0100-58be-f380-f79d-e6cc.biz6.spectrum.com (2600:6c5d:7009:100:58be:f380:f79d:e6cc)  114.746 ms
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
I ran this on my end, testing from an outside connection, and a lot of connections do appear from Charter Spectrum. I would like note this is the ISP for SudoVanilla. I also now see it's possible to connect to my own IP address via `https://35.132.XXX.XXX` with a HTTPS protocol, which was not possible in the past. So I don't think that's the issue either. This should allow me to add other services in the future like a Matrix server. ``` ❯ sudo traceroute -p 80 sudovanilla.org -T traceroute to sudovanilla.org (2600:6c5d:5800:5fb4::7a8), 30 hops max, 80 byte packets 1 2607:fb90:8de3:1070::4 (2607:fb90:8de3:1070::4) 20.459 ms 20.417 ms 20.405 ms 2 fc00:10:5:122::254 (fc00:10:5:122::254) 96.849 ms * * 3 * * fc00:10:6:122::254 (fc00:10:6:122::254) 92.327 ms 4 * * * 5 ::ffff:10.188.62.39 (::ffff:10.188.62.39) 96.762 ms 96.752 ms 96.742 ms 6 ae52.bar3.Detroit1.Level3.net (2001:1900:2100:32::e5) 97.723 ms 77.251 ms * 7 2001:1900::3:1ee (2001:1900::3:1ee) 79.454 ms 79.416 ms 53.741 ms 8 e0-36.core2.det1.he.net (2001:470:0:165::2) 73.906 ms 73.880 ms 83.254 ms 9 * * * 10 * * * 11 * * * 12 charter-20115-as20115.e0-15.core1.stl1.he.net (2001:470:0:4c0::2) 76.175 ms 65.613 ms 79.771 ms 13 * lag-802.bbr01blvlil.netops.charter.com (2001:506:100:68::6) 83.167 ms * 14 * * * 15 lag-5.rcr01sghlgaao.netops.charter.com (2001:506:100:5505::6) 218.223 ms 218.196 ms 138.338 ms 16 lag-11.rcr01mnchtnem.netops.charter.com (2001:506:100:5dfd::5) 132.463 ms 132.388 ms lag-10.rcr01mnchtnem.netops.charter.com (2001:506:100:5dfc::7) 132.280 ms 17 lag-100.crr01mnchtn.netops.charter.com (2001:506:100:5dfd::7) 126.327 ms * 132.119 ms 18 lag-1.mavltn3901w-dtr1.netops.charter.com (2001:506:100:5cfa::4) 115.869 ms 133.661 ms 133.571 ms 19 lag-1.mavltn3902w-dtr2.netops.charter.com (2001:506:100:5cff::5) 109.702 ms lag-10.mavltn3902w-dtr2.netops.charter.com (2001:506:100:5d2d::5) 113.861 ms 113.834 ms 20 * * * 21 syn-2600-6c5d-7009-0100-58be-f380-f79d-e6cc.biz6.spectrum.com (2600:6c5d:7009:100:58be:f380:f79d:e6cc) 131.001 ms 126.758 ms 112.991 ms 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ``` ``` ❯ sudo traceroute -p 443 sudovanilla.org -T traceroute to sudovanilla.org (2600:6c5d:5800:5fb4::7a8), 30 hops max, 80 byte packets 1 2607:fb90:8de3:1070::4 (2607:fb90:8de3:1070::4) 7.049 ms 7.027 ms 7.021 ms 2 * fc00:10:6:122::254 (fc00:10:6:122::254) 51.961 ms 51.955 ms 3 * fc00:10:6:122::254 (fc00:10:6:122::254) 48.861 ms * 4 fd00:976a:c000:1::48 (fd00:976a:c000:1::48) 48.867 ms * * 5 ::ffff:10.188.62.40 (::ffff:10.188.62.40) 51.925 ms ::ffff:10.188.62.39 (::ffff:10.188.62.39) 51.815 ms 53.618 ms 6 ae52.bar3.Detroit1.Level3.net (2001:1900:2100:32::e5) 55.526 ms 48.447 ms 48.411 ms 7 2001:1900::3:1ee (2001:1900::3:1ee) 62.615 ms 62.571 ms 62.550 ms 8 e0-36.core2.det1.he.net (2001:470:0:165::2) 92.764 ms * * 9 * * * 10 * * * 11 * * * 12 charter-20115-as20115.e0-15.core1.stl1.he.net (2001:470:0:4c0::2) 88.603 ms 88.579 ms 88.575 ms 13 lag-802.bbr01blvlil.netops.charter.com (2001:506:100:68::6) 88.590 ms * 88.155 ms 14 * * * 15 lag-5.rcr01sghlgaao.netops.charter.com (2001:506:100:5505::6) 102.007 ms 97.630 ms 107.533 ms 16 lag-10.rcr01mnchtnem.netops.charter.com (2001:506:100:5dfc::7) 117.784 ms lag-11.rcr01mnchtnem.netops.charter.com (2001:506:100:5dfd::5) 117.905 ms 117.900 ms 17 * lag-100.crr01mnchtn.netops.charter.com (2001:506:100:5dfd::7) 117.762 ms 117.755 ms 18 * lag-1.mavltn3901w-dtr1.netops.charter.com (2001:506:100:5cfa::4) 105.650 ms 115.392 ms 19 lag-1.mavltn3902w-dtr2.netops.charter.com (2001:506:100:5cff::5) 112.930 ms 107.496 ms * 20 syn-2600-6c5d-7009-0100-58be-f380-f79d-e6cc.biz6.spectrum.com (2600:6c5d:7009:100:58be:f380:f79d:e6cc) 129.968 ms * * 21 * * syn-2600-6c5d-7009-0100-58be-f380-f79d-e6cc.biz6.spectrum.com (2600:6c5d:7009:100:58be:f380:f79d:e6cc) 114.746 ms 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ```
Author

As you can see in your traceroute, you did not reach your machine.

Maybe your ISP blocks it. At least people cannot reach it via IPv6.

As you can see in your traceroute, you did not reach your machine. Maybe your ISP blocks it. At least people cannot reach it via IPv6.
Owner

Since I selfhost on a residential IP address, I'm not sure if I have any control over getting the IPv6 unblocked if it is. I'm also not the owner of the Spectrum account that at the address, so I'm not able to contact Spectrum easily about the issue.
SudoVanilla has moved locations since March 2024 and this issue may of been occurring since. Previously I was on AT&T with full control, as I did own the account for it.

Since I selfhost on a residential IP address, I'm not sure if I have any control over getting the IPv6 unblocked if it is. I'm also not the owner of the Spectrum account that at the address, so I'm not able to contact Spectrum easily about the issue. SudoVanilla has moved locations since March 2024 and this issue may of been occurring since. Previously I was on AT&T with full control, as I did own the account for it.
Author

Do you have access to the router? If so, check if there is a packet filter enabled.
As long as it doesn't work, you should remove the AAAA records from the DNS as this causes timeouts until the fallback to IPv4 happens.

Do you have access to the router? If so, check if there is a packet filter enabled. As long as it doesn't work, you should remove the AAAA records from the DNS as this causes timeouts until the fallback to IPv4 happens.
Owner

After more testing and troubleshooting any router configurations, https://[2600:6c5d:5800:5fb4::7a8]/ is not possible.

AAAA records will be remove to force use of the IPv4 address for sudovanilla.org and *.sudovanilla.org.

After more testing and troubleshooting any router configurations, [https://[2600:6c5d:5800:5fb4::7a8]/](https://[2600:6c5d:5800:5fb4::7a8]/) is not possible. AAAA records will be remove to force use of the IPv4 address for `sudovanilla.org` and `*.sudovanilla.org`.
Korbs 2025-07-09 16:42:21 -04:00
  • closed this issue
  • added the
    wontfix
    label
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Korbs/sudovanilla-website#1
No description provided.