curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number

stackoverflow.com/questions/50840101/curl-35-error1408f10bssl-routinesssl3-get-recordwrong-version-number
I saw TCP connection RESET (checked with tpctrack) on the server side and ssl3_get_record:wrong version number testing with CURL on the client side. The problem was traffic being either IPv4 ingress and IPv6 egress (or vice versa).

How to solve "error:1408F10B:SSL routines:ssl3_get_record:wrong version ...

stackoverflow.com/questions/70910540/how-to-solve-error1408f10bssl-routinesssl3-get-recordwrong-version-number
Now when we are sending request on those URLs, we are getting "Unsupported or unrecognized SSL message". And if I do curl -v on that URL, I get error:1408F10B:SSL routines:ssl3_get_record:wrong version number. Is it problem on our side or this need to be fixed by other systems who shared those URLs with us.

Unable to establish SSL connection: wrong version number

community.letsencrypt.org/t/unable-to-establish-ssl-connection-wrong-version-number/155529
A user reports an error when trying to access their website with SSL: wrong version number. Another user suggests a possible solution related to Apache configuration and port 443.

curl: (35) error:0A00010B:SSL routines::wrong version number

github.com/curl/curl/issues/9931
curl/libcurl version curl 7.87.0-DEV (x86_64-pc-linux-gnu) libcurl/7.87.0-DEV OpenSSL/3.0.0 zlib/1.2.11 ngtcp2/0.12.0-DEV nghttp3/0.8.0-DEV Release-Date: [unreleased] Protocols: dict file ftp ftps gopher gophers http https imap imaps mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftp Features: alt-svc AsynchDNS HSTS HTTP3 HTTPS-proxy IPv6 Largefile libz NTLM NTLM_WB SSL threadsafe TLS-SRP ...

raspbian - SSL error: Wrong version number - Super User

superuser.com/questions/1754642/ssl-error-wrong-version-number
The openssl version shown in Python might be unrelated to the one from curl. In fact, curl might not even use openssl but any of the various other TLS backends it supports. As suggested, use curl --version to get the exact details of what curl is using.

SSL routines:ssl3_get_record:wrong version number:../openssl-1 ... - GitHub

github.com/openssl/openssl/issues/10938
"wrong version number" can occur in a few different scenarios. This particular instance happens when we're processing the first record of data that we've received from the client. SSL/TLS records have a defined structure. From RF5246:

Why does SSLv3 reports error 'Wrong version number' ?

access.redhat.com/solutions/5696851
When higher protocols like TLSv1.x is enabled, for SSLv3 wrong version number system reports error as below in openssl commands $ openssl s_client -connect host:port SSL

SSL routines:ssl3_get_record:wrong version number

www.digitalocean.com/community/questions/ssl-routines-ssl3_get_record-wrong-version-number
Did you specify the listen 443 ssl; directive in the server block where you've defined the SSL certificate? If so, would you mind sharing the complete Nginx server block that you currently have so I could take a quick look?
Feedback