I'm not sure it wasn't premature to go production on, but since this is also an experimental network, they could just be giving it a try.
I agree it is all about experimentation and learning. Learning that adding an IPv6 address may unexpectedly break some things is part of that, and it is better to experience it here that at work on some client visible site :-)
Rob
I think it's an apache2 redirect rule barking but not showing up as an error anywhere in my logs. It tests fine on my lan however that's internal not external. https://uronode.n1uro.com should work for IPv6 and also display your IP back to you. What's strange is that the config is identical to https://n1uro.ampr.org (minus server name, etc).
The reason for the redirect is as of October 1, 2017, google in it's infamous ways is going to be deploying out a new version of it's (ugh) Chrome browser which is designed to error and/or block outbound port 80 in hopes of forcing websites to go ssl/tls.
-
Brian -
Rob Janssen