-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Backend IPv6 in Consul Catalog #714
Labels
area/provider/consulcatalog
kind/bug/confirmed
a confirmed bug (reproducible).
status/5-frozen-due-to-age
Milestone
Comments
ldez
added
the
kind/bug/possible
a possible bug that needs analysis before it is confirmed or fixed.
label
Jun 2, 2017
So , my crude attempt at passing BackendAddress with, or without square brackets depending if it's IPv4 or IPv6 address is here: |
I'll close the issue due to inactivity but feel free to re-open if needed. |
Hi there, Just got hit by this one, it is very similar to #3428 and most likely the fix is identical. Generated backend config: "radosgw-0-24j0duzKFiHUlSC0ABuYpAd8jic": {
"url": "http://2001:xxx:xxx:e3::100:13d:8080",
"weight": 1
} Output of a test curl:
Desired backend config: "radosgw-0-24j0duzKFiHUlSC0ABuYpAd8jic": {
"url": "http://[2001:xxx:xxx:e3::100:13d]:8080",
"weight": 1
} PR incoming... |
ldez
added
kind/bug/confirmed
a confirmed bug (reproducible).
and removed
kind/bug/possible
a possible bug that needs analysis before it is confirmed or fixed.
labels
Jun 12, 2018
Closed by #3477. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area/provider/consulcatalog
kind/bug/confirmed
a confirmed bug (reproducible).
status/5-frozen-due-to-age
We are using consul_catalog with IPv6 only services.
Traefik correctly discovers their addresses, however it uses malformed http config for backend.
Backends get constructed as
http://200X:XXX:XX:d3:0:242:ac11:4:8300
instead of
http://[200X:XXX:XX:d3:0:242:ac11:4]:8300
and causing errors:
Error forwarding to http://200X:XXX:XX:d3:0:242:ac11:5:8080, err: dial tcp: too many colons in address 200X:XXX:XX:d3:0:242:ac11:5:8080"
The text was updated successfully, but these errors were encountered: