-
Notifications
You must be signed in to change notification settings - Fork 341
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
{:error, %HTTPoison.Error{id: nil, reason: "closed"}} #326
Comments
I had a similar error, looks like is this hackney issue: #475 Updating hackney with |
I'm having the same issue and deps.update hackney didn't help. It isn't https url. |
@lypborges have you found a solution? |
I have the same issue elixir 1.7.1 OTP 21 erts 10.0. None of the workarounds are working for me. |
@kaminooni no. Not yet. I had to change the lib. ;( |
Having the same issues with non-tls URLs (locally over to couchdb), elixir 1.6.5 with OTP 20 and elixir 1.7.3 with OTP 21. HTTPoison |
Does anyone have any new information on this? |
Tried the README suggestion to update HTTPoison calls with:
No luck. Throwing a parsing error in production. |
^FYI I added that line and updated :httpoison |
Similar issue for me, that's easy to recreate on:
The first request to Setting tlsv to 1.2 does not change anything. |
Any update on this issue? I am facing the same? |
still facing the same issue. |
even with the update of hackney, the issue is the same. |
I had the same issue, what happened is that there was an |
I’m getting a strange error in HTTPoison. When I do two request to a server “A” in the second I get connection close.
When I do this with other server it works.
So I think it was a error on the server “A” , so a did a manual call with curl 20 times and all work perfect in the server “A” and “B”.
I tried with another lib and the server respond with no error.
I also tried with the default options and with the options above
[ ssl: [{:versions, [:'tlsv1.2']}] , hackney: [pool: :mypool], max_connections: 1000]
. But I get the same error.Any tip what could be the error?
The text was updated successfully, but these errors were encountered: