Skip to content

Updated

SSL Certificate Error Through a Proxy:
3 Causes and Fixes

  1. If the same site opens without a warning when you go direct, its own certificate is fine, so look at what sits between you and it.
  2. The three usual causes are: an HTTPS proxy whose certificate your device does not trust, software that inspects TLS (antivirus, a company firewall, a debugging tool) and re-signs certificates with its own CA, and a device clock that is outside the certificate dates.
  3. The name in the certificate Issuer field tells you which one you have.

Check it right after buyingExample output

curl -x http://USER:PASS@HOST:PORT https://ipinfo.io/json

ip
203.0.113.24
country
US
Matches the country you picked
Day 15
203.0.113.24
Same address for the whole term
Example addresses (203.0.113.0/24), not real exits
01 / 09The three causes in plain words

Find out whether the warning comes from an HTTPS proxy, TLS inspection on your side, or a wrong clock, and fix the right one.

The three causes in plain words

An HTTP or SOCKS5 proxy normally does not touch your TLS. With HTTP it uses the CONNECT method to open a tunnel to the site and then forwards bytes blindly, so your tool still checks the site's own certificate end to end. That is why a certificate error that appears only behind a proxy almost always points to something that is not the plain tunnel.

Cause 1: you use an HTTPS proxy (the connection to the proxy itself is TLS) and your device does not trust the proxy's certificate. Cause 2: something on your computer or network terminates TLS, reads the traffic and signs a new certificate for every site with its own CA. Cause 3: the clock is wrong, so a valid certificate looks expired or not yet valid.

Which cause: what you see and who fixes it

Which cause: what you see and who fixes it
ItemIssuer in the certificateWho fixes itFix
HTTPS proxy not trustedSelf-signed, internal CA, or a name that does not match the proxy hostWhoever runs the proxy, or you if it is yoursInstall the proxy CA in the system store, or give the tool the CA file (curl: --proxy-cacert)
TLS inspection (antivirus, firewall, debugging tool)Name of a security product, your company, or a tool such as mitmproxyYou or your IT teamFinish installing that product's root CA, or turn off HTTPS scanning for the tool you are testing
Wrong clockA normal public CA, but the error mentions expired or not yet validYouTurn on automatic date and time, then restart the app
Destination or old CA storeA normal public CA, and the same error appears without a proxySite owner, or you after updating the systemUpdate the OS or the app's CA bundle; do not blame the proxy

Compiled on 20 November 2026 from the curl manual, RFC 5280 and the mitmproxy documentation. These are the usual patterns, not a complete list.

Four checks, in this order

  1. Step 1: open the same URL without the proxy

    Turn the proxy off (or use a different browser profile) and open the same address. If it fails here too, the problem is the site, your CA store or your clock, not the proxy.

    Expected result Direct access works, only the proxied one warns.

  2. Step 2: read the certificate issuer

    In the browser, click the warning, open certificate details and read Issuer. A public CA name means the site's own certificate. A security product, a company or a tool name means something is re-signing traffic.

    Expected result You know whether the chain is public or re-signed.

  3. Step 3: check what kind of proxy you entered

    An address that starts with http:// or a SOCKS5 entry is a tunnel. Only an https:// proxy adds a second certificate to check. In curl, test the proxy leg alone with --proxy-cacert.

    Expected result You know whether a proxy certificate is even involved.

  4. Step 4: check the clock

    Compare your date and time with a trusted source, in UTC if you can. Error names like ERR_CERT_DATE_INVALID point at dates, not at the proxy.

    Expected result Fixing the time makes the warning disappear.

Compare direct and proxied certificates with curl

# 1) Same site, no proxy: if this is fine, the site's own certificate is fine
curl -sv https://example.com/ -o /dev/null 2>&1 | grep -iE "issuer|expire|SSL certificate"

# 2) Same request through your HTTP proxy: compare the issuer line
curl -sv -x http://LOGIN:PASSWORD@HOST:PORT https://example.com/ -o /dev/null 2>&1 | grep -iE "issuer|expire|SSL certificate"

# 3) Only if your proxy itself is an HTTPS proxy (https:// in the proxy URL):
curl --proxy-cacert proxy-ca.pem -x https://HOST:PORT https://example.com/ -o /dev/null

# 4) Rule out the clock (UTC)
date -u

Example only: replace LOGIN, PASSWORD, HOST and PORT with the values from your proxy page. The grep is a convenience; the lines you want are issuer and expire date.

Symptoms and what to do

The warning names a corporate or antivirus issuer

Check Open the certificate and read Issuer; check whether HTTPS scanning is on in your security software.

Fix Install that product's root CA properly, or ask IT for it. Do not click through the warning for sensitive sites.

Stop when If IT forbids changing it, stop and test from a network without inspection.

You entered an https:// proxy and every site warns

Check Test with curl --proxy-cacert and the CA file of that proxy.

Fix Add the proxy CA to the system store or to the tool; make sure the proxy hostname matches its certificate.

Stop when If the proxy gives no CA file, ask its operator; do not turn verification off.

Error mentions expired or not yet valid, on all sites

Check Check date, time zone and time source.

Fix Turn on automatic date and time and restart the browser or tool.

Stop when If the clock keeps drifting (a virtual machine, a dead CMOS battery), fix that first.

Error looks like a proxy error, not a certificate error

Check Check host, port and protocol first.

Fix Use the proxy connection failed guide to separate a bad address from a certificate problem.

Stop when If the connection never opens, no certificate is involved yet.

Why not just turn verification off

curl --insecure and similar switches skip the check, so any certificate is accepted, including a forged one. The curl documentation advises against using it in production. If you must test something quickly, do it on a throwaway request that carries no passwords or personal data, and put the real fix (the right CA file) in place afterwards.

With Proxy302: set it up so the tunnel stays plain

  1. Step 1

    Open My assets and copy HOST, PORT, USERNAME and PASSWORD of the IP you bought.

  2. Step 2

    Enter an HTTP or SOCKS5 proxy in your tool, matching the protocol shown on the asset: HTTP uses port 2222 and SOCKS5 uses port 3333 on proxy.proxy302.com. Do not type https:// in front of the proxy address.

  3. Step 3

    Run the curl test above through the proxy and compare the issuer line with the direct run. If it differs, look at your own computer and network first.

  4. Step 4

    Still stuck? Open a Support ticket with the exact error text and the test output.

SSL proxy error: common questions

Why does the SSL error appear only when I use a proxy?

Because the proxy changes who your device talks TLS to: either an HTTPS proxy with its own certificate, or inspection software that re-signs certificates. Open the certificate and read the Issuer to see which.

Does an HTTP or SOCKS5 proxy decrypt my HTTPS traffic?

A normal HTTP proxy opens a CONNECT tunnel and forwards the bytes without reading them, so TLS runs between your tool and the site. A proxy that is built to inspect traffic, such as mitmproxy, does the opposite and needs its CA installed.

Is it safe to use curl -k or verify=False?

It removes the protection the certificate check gives you. The curl documentation advises against it in production. Use the right CA file instead.

Can the wrong date really cause a certificate error?

Yes. A certificate is valid only between its notBefore and notAfter dates, so a clock outside that interval makes it invalid on your device even though the site is fine.

Which proxy type avoids certificate warnings?

A plain HTTP or SOCKS5 proxy used as a tunnel does not add a certificate to check. If a warning still appears, the cause is on your side: inspection software, the clock or an outdated CA store.

Further reading

Setup guides Proxy302 publishes on GitHub on the same topic:

Reference links

6
  1. curl: SSL certificate verification

    Official documentation · Confirmed on:

    Read on 20 November 2026: curl checks the certificate signature and the server name by default; --cacert points one transfer at a CA file; --insecure skips verification and the page advises against it in production; the HTTPS connection to a proxy is verified separately with --proxy-cacert / --proxy-insecure.

  2. curl manual: --proxy-cacert

    Official documentation · Confirmed on:

    Read on 20 November 2026: --proxy-cacert uses a PEM file to verify the HTTPS proxy and allows a different trust for the proxy than for the remote server; it is the --cacert equivalent for an HTTPS proxy.

  3. RFC 9110, section 9.3.6 CONNECT

    Official documentation · Confirmed on:

    Read on 20 November 2026: CONNECT asks the proxy to establish a tunnel to the destination server and then forward data blindly in both directions; such tunnels are commonly secured end to end with TLS.

  4. RFC 5280, section 4.1.2.5 Validity

    Official documentation · Confirmed on:

    Read on 20 November 2026: a certificate has a validity period defined by notBefore and notAfter dates, so a device clock outside that interval makes the certificate invalid for that device.

  5. mitmproxy docs: certificates

    Official documentation · Confirmed on:

    Read on 20 November 2026: mitmproxy runs its own certificate authority and issues a certificate for each site the client visits, signed by the mitmproxy CA; the client must trust that CA or it rejects the certificates.

  6. Proxy302 product facts and price list

    Product observation · Confirmed on:

    Product facts file of the site (values checked against the console, the backend and the price table on 18-19 October 2026): products, prices in US$ (1 PTC = US$1), lease terms, protocols and ports, countries, quantity limits, no free trial.

Ready to try it?

Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.