Node.js: write EPROTO ... SSL routines:ssl3_get_record:wrong version number (https:// to an HTTP port, or http agent for https)
The client attempted TLS against a server (or port) that doesn't speak TLS, or used the wrong HTTP agent.
write EPROTO error:1408F10B:SSL routines:ssl3_get_record:wrong version numberEPROTO SSL routines wrong version number NodeError: write EPROTO 139:error:1408F10BProtocol "https:" not supported. Expected "http:" Meaning
Check the URL scheme/port, use https.request/https.Agent for https URLs, and verify any proxy settings (an HTTP proxy URL with an https agent is a classic mistake). Test with curl -v.
Common causes
https://to a plain HTTP porthttp.Agentused for an https URL- Proxy URL scheme mismatch
- Server redirecting to plain HTTP
- Local dev server without TLS
⚡ Quick fix
- Match scheme and port
- Use the correct agent (
https-proxy-agentfor proxies) - Verify with
curl -vandopenssl s_client
Detailed fix by platform
Node.js
- javascript
const agent = new HttpsProxyAgent(process.env.HTTPS_PROXY); await fetch(url, { agent });
How to diagnose
- Scheme — Matches port?
- Agent — https?
- Proxy — Configured right?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- ACM region CloudFront can't use my ACM certificate: it must be requested in us-east-1 (N. Virginia)
- Django Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port)
- NODE_EXTRA_CA_CERTS Node.js: UNABLE_TO_VERIFY_LEAF_SIGNATURE / SELF_SIGNED_CERT_IN_CHAIN behind a corporate proxy (NODE_EXTRA_CA_CERTS)
Most viewed in SSL / TLS
- HTTPSConnectionPool: Max retries exceeded (SSLError) Python requests: HTTPSConnectionPool(host='api.example.com', port=443): Max retries exceeded with url: /v1 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] ...')))
- DST Root CA X3 expired (old clients fail) Old clients: certificate has expired — Let's Encrypt chain uses expired DST Root CA X3 (OpenSSL 1.0.x, Android < 7.1.1)
- Keystore was tampered with, or password was incorrect Java keytool: java.io.IOException: Keystore was tampered with, or password was incorrect
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026