-
-
Notifications
You must be signed in to change notification settings - Fork 622
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
connect() tries to use IPv6 address on IPv4 connections (sometimes), when it doesn’t it gives a ssl error #105
Comments
Additional info: I’m running docker for mac and my nginx.conf is as follows:
As you can see, the |
We don't yet currently support ipv6 literals (but we should). This PR is under review: #104 I suspect the SSL issue is unrelated. Are you calling |
I didn’t use a literal, the problem was probably due my connection being IPv4 only and resty sometimes getting an IPv6 from the DNS resolver. |
That's still very much an issue. The SSL error can be silenced using the ssl verify param, but if the resolver gives an IPv6 address, the request fails. In my example, I'm using Cloudflares |
I still get the same issue using version 0.16.1. Thought it was fixed on PR #104
Also using docker. |
I solved this problem by turning off ipv6 in the resolver:
|
thank dude. you save my day |
I simply copied the sample code, replaced with a dual stack domain (in this case, the telegram bot api) and I have noticed it sometimes throws this error:
When it does use the correct IP address, I get a ssl error:
I’m using openresty/openresty:alpine-fat docker image, if it matters.
The text was updated successfully, but these errors were encountered: