Created At: 2026-11-19T18:02:18Z Completed At: 2026-11-19T18:02:22Z The search for ""HTTP 400: Client sent an HTTP request to an HTTPS server"" returned the following summary: The error message **"HTTP 400: Client sent an HTTP request to an HTTPS server"** (often phrased as *"The plain HTTP request was sent to HTTPS port"*)[1] occurs when a client attempts to communicate with a server using plain, unencrypted **HTTP**, but the server is explicitly configured to listen for encrypted **HTTPS (TLS/SSL)** traffic on that port[1]. Because the server expects a secure handshake (TLS negotiation) right away, it cannot understand the plain text HTTP request and rejects it with a `400 Bad Request`[2][1]. --- ### Common Causes & How to Fix Them #### 1. You typed `http://` instead of `https://` in the URL * **The Cause:** You are manually testing an API, opening a web dashboard, or entering a URL in your browser, but you accidentally used `http://` on a secure port (like `443`, `8443`, `9443`, etc.)[1][3]. * **The Fix:** Change the URL scheme in your address bar or client (like Postman or cURL) from `http://` to `https://`[3]. #### 2. Misconfigured Client/Health Probes (Kubernetes, Docker, etc.) * **The Cause:** If you are using container orchestration tools like Kubernetes (e.g., for HashiCorp Vault[4], ArgoCD, or custom apps) or Docker tools[5], your liveness/readiness probes or internal connection settings might be making an `http://` request to a backend pod/port that only accepts `https://`[4]. * **The Fix:** Update your configuration YAML files or client connection settings to use `https://` and configure the appropriate TLS/certificate skipping options if using self-signed certs[4]. #### 3. Reverse Proxy / Ingress Misconfiguration (Nginx, Traefik, Apigee) * **The Cause:** Your reverse proxy or API gateway is expecting HTTPS from the client, but an upstream service or routing rule is forwarding requests using plain HTTP, or vice-versa[1][6]. * **The Fix:** * Ensure your Nginx/Ingress rules match the protocol expected by the backend service. * If the backend only speaks HTTP, make sure the proxy terminates SSL at the edge and forwards plain HTTP internally *only* to a non-secure port. Do not forward plain HTTP to a port on the backend that expects TLS. #### 4. Hardcoded Links or Redirects in Code * **The Cause:** Your application code (e.g., an API client library, mobile app, or frontend framework) has hardcoded base URLs pointing to `http://` instead of `https://`. * **The Fix:** Search your codebase for the API endpoint and ensure the base URL utilizes `https://`. Sources: [1] [apigee.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHbQcRd4DvK-L4ojzZq5Ih7oRzT3Inhbr6lbgLBCSCxxZ959KJsixsOn6NPQiHt-WAd1cVDQ4frUQY9bZwxUng2E2j9SClJxpWhlChu0FNIf-EnmiUc81YpHdGBx9N72EyjN91t3G7o52oqS3Cfr3Ca-3NqOQ8slru5shq24CcE2XTYef-TvdLjum9ujUi4XJlW59dz0LEagixKZS-z_s8MFmvzqg==) [2] [mozilla.org](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGelwtTXbibl22Ib7hKYwfhF2qQn0QWxfbL7Q4bZtzBF7s6ffiayb-ZcppozkwrXuhzhCo4l74-_H0SFJPWJCQO5wIEHThKueXUrmQ-XEALRZ1z42kZXOBO1gmCPNeWeNuaHAI7q_Esx-awKtKnwpwhjFvYZ_8yfrcewCU=) [3] [portainer.io](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHb5NPsH-R-sbRF01rfy5JJbBCdthKjRvVxh8BIasdlYoJuyw9Dnwj5cX8qkIRhrolznpMUKuwG1DKUZMMaWXsUGOKuiCX3Gr63het7-MqF8VJ_oEl6VSxv9olLsKR2AGXZlBl0YiuSNKIE0aDEDfljvv9BR6ncVQsyLoPmDHKS91_0hK0BNfBu7sPiU6TUynHpJDyDz5u8my18sM0ogc4LLmxIifSvEDUd954f) [4] [youtube.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQFHf_miGTiNhilubDZ3xzSuoCm7KSjC0fB_e4RtUJEMGGyNwgG0LWMoiFrJ8zqAY2lZ3MzHH9htCZAyw6KRAYTLXqdyptolzTShlBE7qF0qByOwl_3SDITPI77FqXHpYmQ=) [5] [stackoverflow.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQEpfBoiQJVhp-C8rjht2MXUbxNrkbWcTHmWNFQowQ23gxnTLAhgE64rGfqaLqcoJxl3PIoGlAxPZLbUMAMZsaga6wVLQB-IJ4z0oywQdXqWS5v9M6GjH3Veb_Y-yvzLHoPEnhVe77n6U5l7ibwMwwtzMAniLxTht-DEYQDMWpzCDjgumX1e-5ZMBZKbVUviRFHenGdxCEhDNXaKbhshu7COIqmve_1jRDR2b2T8qQ==) [6] [stackoverflow.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQF3TvtyP_mrJcr6Uqtli_TGdCT_gMafda2wrgGqvqhRcnwtHQhKm-y5NvhkzjLVZemYKZ7CpjqqCgD4Y1IE64oerzNgCWcS0gE0BtaAuTsR5Fa6Tp36KRS1yuLQxOJ_zg4R2GvDQcb4enVQQs-ZXES8apuAXsXIEt7W7CqbT2tZ_GyNszDl_8iN_sCzKz-JugyU2gczHompidm9r4A1KAubYCFAtr7_U37JH4EKgkzc) Note: Source URLs are HTTP redirects; check where they resolve if you need the direct link.