Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IPv6 access broken #90

Closed
michicc opened this issue Jun 9, 2019 · 2 comments
Closed

IPv6 access broken #90

michicc opened this issue Jun 9, 2019 · 2 comments

Comments

@michicc
Copy link
Member

@michicc michicc commented Jun 9, 2019

Accessing the website via IPv6 (either production or staging) result in a connection reset. IPv4 works.

wget www.openttd.org
URL transformed to HTTPS due to an HSTS policy
--2019-06-09 11:21:28-- https://www.openttd.org/
Resolving www.openttd.org (www.openttd.org)... 2a03:b0c0:2:d0::dc6:7001, 178.128.140.43
Connecting to www.openttd.org (www.openttd.org)|2a03:b0c0:2:d0::dc6:7001|:443... connected.
GnuTLS: The TLS connection was non-properly terminated.
Unable to establish SSL connection.

@TrueBrain
Copy link
Member

@TrueBrain TrueBrain commented Jun 9, 2019

Should be solved now. Please close the ticket if it is the case, otherwise let me know :)

As IPv6 is not natively supported by DigitalOcean for their LoadBalancer, there is a proxy to handle IPv6. It needs internal IPs from the kubernetes cluster we run. These IPs change when ever an update is performed of the cluster. This happened ~20 hours ago. After that, it needs manual configuration change for IPv6 to kick in again. I will see if I can automate it :)

@michicc
Copy link
Member Author

@michicc michicc commented Jun 9, 2019

Working for me now.

Thank you.

@michicc michicc closed this as completed Jun 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants