| Previous | Next |
| HTTP_STATUS_CERTIFICATE_REQUIRED | HTTP_STATUS_INVALID_TOKEN |
HTTP_STATUS_HTTP_TO_HTTPS_PORT
The client connected to a TLS port but sent an unencrypted HTTP request. NGINX parses enough of the request to make the URI available for an error_page redirect or error response.
Use an https:// URL and verify port mappings in reverse proxies, health checks, and service discovery. Do not try to fix this by changing HTTP headers after the connection is opened.
This usually reveals a scheme or port mismatch in a client, health check, proxy, or redirect configuration. The HTTPS listener expects a TLS handshake before any HTTP request bytes. Correct the URL or upstream protocol so that TLS is established first; adding HTTP headers cannot make a clear-text request valid on that listener.
Looking for a different code? Search another status or error code.