MockFoxAdvertise

HTTP 495 SSL Certificate Error

Updated Free mock REST & WebSocket APIs

HTTP 495 SSL Certificate Error — nginx: the client presented an invalid TLS client certificate.

Class
4xx Client Error
Defined in
Unofficial (nginx)
Official
No — nginx-specific
Cacheable by default
No (unless Cache-Control/Expires say so)
Safe to retry
Not without changing the request

Try it: get a real 495 response

Our test endpoint answers every request with 495 SSL Certificate Error.

curl -i https://mockfox.dev/api/status/495

Use it in tests, health-check monitors or to see how your client handles a 495. Add ?delay=2000 to slow it down.

What does HTTP 495 mean?

Logged when mutual-TLS (ssl_verify_client on) is enabled and the client certificate fails verification — expired, untrusted CA or wrong chain. The client sees a 400 "The SSL certificate error" page. Check ssl_client_certificate and the client's certificate chain.

How to fix 495

  1. Visitors: Reload the page, check the address for typos, and clear the site's cookies. If it persists, the site owner needs to fix it.
  2. Developers: Read the response body and server logs for details, fix the request (method, headers, body, credentials) and return a clear error message to clients.

Example 495 response

HTTP/1.1 400 Bad Request
Server: nginx
Content-Type: text/html

# (logged internally as 495)

4xx Client Error: The request contains an error or can't be fulfilled — fix the request before retrying. See the full list of HTTP status codes.

Related status codes

Related tools

Frequently asked questions

What does HTTP 495 SSL Certificate Error mean?

nginx: the client presented an invalid TLS client certificate.

Is 495 a client or a server error?

495 is a 4xx code, so it signals a problem with the request (as seen by the server). Retrying the identical request usually gives the same result.

Is 495 an official HTTP status code?

No. It isn't in the IANA HTTP Status Code Registry; it's specific to nginx. Generic HTTP clients treat it as an unknown 4xx status.

How can I test how my app handles a 495?

Call https://mockfox.dev/api/status/495 — it responds with 495 to any method, with CORS enabled. Add ?delay=2000 to simulate a slow response.