karang
I am getting the following error:
iex(16)> HTTPoison.post("https://myserver.com/api/v1.1.0/login",'{ "username": "myusername","password": "somepassword,"port": "80"}',[hackney: [ssl: [cacertfile: '/usr/local/share/ca-certificates/extra/RootCA.crt']]])
14:54:26.183 [info] TLS :client: In state :hello received SERVER ALERT: Fatal - Handshake Failure
{:error,
%HTTPoison.Error{
id: nil,
reason: {:tls_alert,
{:handshake_failure,
'TLS client: In state hello received SERVER ALERT: Fatal - Handshake Failure\n '}}
}}
We have a local RootCA.crt file which I have added to the OS and makes it so I can make a request with no problems. I am able to make this request in postman as well as from Python but not in Elixir. Perhaps my syntax is wrong or I don’t understand ssl properly (that’s definitely true!). This server is not accessible to the internet. I can provide more information if necessary. Thanks for any help!
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 4 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
karang
I solved this problem today like this:
I passed the insecure option to hackney and changed the https to http. I know this is not recommended but I need to login and I don’t have access to the SSL settings on the server.
karang
Thanks for the tips everybody. Unfortunately I think the problem lies with the IT department of the company I am working with. There appears to be some problems with their ssl setup. I can only access this api by setting a verify=false flag with the request. Which is ok for now but eventually they need to setup their certificates properly.
akash-akya
Along with what @lucaong suggested, once you specify
:sslyou have to specify all SSL options, hackney does not merge ssl options.from hackney readme:
lucaong
Not sure this is the actual issue, but the
HTTPoisonREADME does not use the atom:hackneyin the SSL options:Even when passing a
:cacertfile, it seems to be passed directly under:ssl: httpoison/test/httpoison_test.exs at 19f04da7949bf32141b8c3ff354e260542e4dd52 · edgurgel/httpoison · GitHub