Error: write EPROTO 34557064:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER

Error: write EPROTO 34557064:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:../../third_party/boringssl/src/ssl/tls_record.cc:242: 

The issue was that I was trying to POST to https when that API actually only supports HTTP. Just leave this as a note for other folks who might run into the same issue.

Any Help can be appreciated

3

9 Answers

This type of issue comes when you use https instead of http. Change the URL to use http.

Example:

Change it to:

4

This error comes when the API that we are hitting is running on http and we are trying using https. Information was really useful.

Example: Using this when this must be used as API is running on http.

error-write-eproto-34557064error100000f7ssl-routinesopenssl-internalwrong 

replace HTTPS to HTTP

I had this issue in Postman when I tried to hit a before working API endpoint.

In my case, it was a Header that I had set manually before and forgotten to delete.

Header: Host

It has normally the value <calculated when request is sent> but I had it given a custom value.

I got this exact error message because I had configured certificates for SSL incompletely in Postman. When specifying URL and port for my certificates, the port input field had a placeholder value of 443, which was the correct one. So I skipped actually typing it.

Turns out I actually had to type it, for it to work.

For anyone who is still struggling I had another solution to remove the trailing "/" from my route for example:

@app.get("/api/book/{id}/info/") 

Changed to:

@app.get("/api/book/{id}/info") 
1

I encountered this error while trying to test the api request on postman. Ensure the the url link specified during the development process is the same url link been used during testing of postman.

example: during development, the url link specified is . Then, during testing on postman make sure that the link is the same http://.

API requests from Http:// and Https:// are treated and handled differently.

In my case, the request was a redirection 302, in that case, I disable Automatically follow redirects on Postman settings Settings

I also get the same error while I was accessing the rest API through postman.

Https//:localhost:8662/hello 

Instead of using HTTPS, We can use HTTP//:localhost:8662/hello

Now it'll work.

HTTPS-It is an advanced version of HTTP. This comes under SSL protocol which means Security .https encrypt the data so we can use HTTPS when we pass sensitive information like credit card transaction because it encrypts the data.

4

You Might Also Like