fix IPv6 #1
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Korbs/sudovanilla-website#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
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.
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?
There is no firewall blocking port 443. What service are you trying to connect to specifically?
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.
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.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.
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.
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.
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
.