changelog.com does not load over IPv6 #244
Comments
|
This is a great idea, I'll look into it! |
|
TL;DR I didn't forget about this, still planning on seeing it through. Since we will have a Linode node balancer in front of the app host, it makes sense to do this part of that story, rather than solving IPv6 on the app host, then doing it again when we set up the node balancer. |
|
I'm actually able to fetch changelog.com over IPv6 with some trickery, e.g. For the CDN, it's still a matter of asking Fastly support to enable IPv6 on |
|
Might also be a good idea to ask Fastly to enable HTTP/2 along with IPv6. |
|
Spot on: there are a few small steps to see the IPv6 support through properly. As a show of appreciation for your comments: 💚 |
|
I put in a request to Fastly to enable both ipv6 and http/2 ✊ |
|
Awesome! I did quite a bit of poking around and here are all other IPv6-related issues I could find:
I've also made a PR to enable HTTPS and HSTS preloading. |
|
I checked netdata, and it seems after enabling IPv6, an IPv4 socket leak has manifested: The leaks seems to be because of containers: This doesn't seem to have impacted the website itself at all though. |
|
That was a good catch! This seems to be related to TCP6 sockets remaining stuck in
What happens after 30' of Docker running: More info on the TCP6 sockets in I am going to disable IPv6 for a few hours and see if this resolves the |
|
Yup, it seems that disabling IPv6 prevents the tcp6 socket leak in Docker (see attached screenshot). For the time being, I've deleted all changelog.com AAAA records until this is addressed in Docker. I'm open to alternatives, but for now not having IPv6 support seems preferable to leaking TCP sockets.
|
|
Since a node balancer is now used, could this change be attempted again? Node balancers proxy traffic to servers over IPv4 so the IPv6 socket leak shouldn't occur. As for |
|
Yes, definitely. Feel free to have a go at it. I'll pick it up as soon as I'm done with the few things that I have in flight. |
|
Didn't realize stuff's now in Terraform – neat! Had a go at it with #283.
|
|
Yup, cdn.* is Fastly. The new infrastructure is covered in detail in The new changelog.com setup for 2019 😉 Will make the necessary changes in Fastly before I close this. |
|
Awesome, thanks! A few more things:
|
|
Nice catches, will look into them next time I'm around 👍 I was also going to add some end-to-end tests for this. Do you want to help out with a preliminary PR? You can use proxy.bats as a starting point. This is invoked via proxy-test make target. |
|
@gerhard My bash knowledge is non-existant and I don't have a Linux machine on hand, so I'm afraid I'm unable to help with the tests. |
|
I was not even aware that |
|
@gerhard https://changelog.com/nightly has a link pointing to http://nightly.changelog.com/2016/10/06/. Not sure how I stumbled upon |
|
@jerodsanto if Nightly is still a thing, maybe we should move the content example to changelog.com. nightly.changelog.com is completely off my radar. @tambry I've asked Fastly to make the IPv6 change to cdn.changelog.com, still waiting. |
|
Nightly is still a thing. Here is yesterday's issue: http://nightly.changelog.com/2019/04/10/ We send this url over to Campaign Monitor to deliver the email. |
|
Are we running nightly.changelog.com on DigitalOcean? If yes, is it worth adding IPv6 to it? We might also want to update the SSL certificate: |
|
|
Had to import the existing record first:
terraform import dnsimple_record.cdn_changelog_com changelog.com_5801801
re #244
|
One step closer: dig cdn.changelog.com A +short
dualstack.changelog.map.fastly.net.
151.101.17.162
^A^AAAA
dig cdn.changelog.com AAAA +short
dualstack.changelog.map.fastly.net.
2a04:4e42:4::418
|
|
In the interest of wrapping this issue up - it has been open long enough! - I have reduced the scope and shipped it:
I don't expect a response @tambry, but just in case this is still important to you, feel free to open the next IPv6 issue that you are still facing. Rather than creating a single issue which is likely to take a really long time to address, smaller ones that we can tackle between Kaizens are more likely to get us to full IPv6 support sooner. Thanks for sticking with us! |
The changelog.com website seems to be inaccessible over IPv6. Since the site seems to be hosted on Linode, which has great IPv6 support, it should hopefully be a fairly simple fix.
For cdn.changelog.com it should be a matter of asking Fastly support to enable IPv6 on the map, per their IPv6 documentation.
The text was updated successfully, but these errors were encountered: