Created At: 2026-11-19T18:01:01Z Completed At: 2026-11-19T18:01:05Z The search for ""Client sent an HTTP request to an HTTPS server"" returned the following summary: The error message **`"Client sent an HTTP request to an HTTPS server"`** (frequently generated by Go-based web servers, reverse proxies like Nginx/Caddy, or applications like HashiCorp Vault[1], Portainer[2], and Docker[3]) means exactly what it says: **a client tried to communicate using plain text HTTP on a port or endpoint that is strictly configured to expect encrypted HTTPS (TLS/SSL) traffic.** When the server receives plain text bytes instead of the expected cryptographic TLS handshake, it rejects the connection and throws this error. --- ### Common Causes & How to Fix Them #### 1. Using `http://` instead of `https://` in the URL * **The Problem:** You typed or configured a URL using `http://` (e.g., `http://myserver.com:9443`) instead of `https://`, or your client tool automatically defaulted to HTTP[2]. * **The Fix:** Check your browser address bar, API client (like Postman), or configuration file and ensure the protocol explicitly starts with **`https://`**. #### 2. Misconfigured Health/Readiness Probes (Kubernetes / Docker) * **The Problem:** In containerized environments (like Kubernetes), your liveness or readiness probes might be hitting a secure endpoint using `http://` instead of `https://`[1]. * **The Fix:** Update your probe configurations (e.g., in a Helm chart or Kubernetes deployment YAML) to use `scheme: HTTPS` or explicitly target an HTTP-only management port if one exists[1]. #### 3. Reverse Proxy or Load Balancer Mismatch * **The Problem:** You have a reverse proxy (like Nginx, Traefik, or Cloudflare) sitting in front of your application. The proxy might be terminating SSL and forwarding plain HTTP to your backend server—*or* conversely, the backend was changed to expect HTTPS, but the proxy is still sending raw HTTP[4]. * **The Fix:** Ensure that the communication protocol between your proxy and the backend application matches. If the backend demands TLS/SSL, configure the proxy to forward requests via HTTPS (or configure the backend to accept plain HTTP if it's meant to sit safely behind an internal network). #### 4. Client Scripts / Environment Variables * **The Problem:** Automated scripts, CLI tools (like Docker CLI), or application code might have an environment variable misconfigured (e.g., `DOCKER_HOST=tcp://...` instead of using proper TLS certificates, or an SDK client initialized with `ssl=False`)[3][5]. * **The Fix:** Inspect your application's connection settings, SDK initialization parameters, or environment variables to ensure secure transport is properly enabled. Sources: [1] [youtube.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQEM2fOzp46EYjgFlS42C25vrtAbU2_QTJLNBxj7iybiBSyNejSbcFctuC83a-rEyOSVpUMniuLIBHUYqv5V_NBYevq9iWp9geR9VMlsljTuYO_IUq6jmq4y569pWLKguM4=) [2] [portainer.io](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGJopyzu9GzZoxTdbYZ4HyKpVDp33QH_1TxmJ0iu-gjj6UiR5hizEQ9-GRSou_6-KMBKN6TfjzsNndclsL_O_B7BAygV0a-9nkjIKHKqcuNMF9dYmkL136lLrxqfXUc-3QEaF_MKK4re2Bq4ZnQLLxTS4CUEUqEuCO9zcMAxYc92J8q-LYs1oPCkvurTtjAzhr14of5-eFrrbgNNV9KP_-V1nVmYw6C52_6Xy0e) [3] [github.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQEEZqlKgje5KQgrZ3gtAx-fGqL-FMykg7IVa0ABonK0F5nwDEHm6lVuKJvOZZCTSYGLJknltuDr-hJW4lGBS9Wtqxnkpj-h0ooi-zESLVqZMjkD-_nUbHWRe3wK2rRLYkE-f1WqDSk13w==) [4] [stackoverflow.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGOM0TU5j7ig3Zl0XW9TRNMgrxCBYTkxFn__un8ytOT_5GiKnQaoGvj3oUIZvBSPaN7bOR3p0rHdiRml30tXogGpzQ2Wnn2a1_LSXo4DykWptbIBQyEQCh9y53J9UD6Oay1VOpf3pV8ZtL-KdLjDxVu9yl-etkTD514UI7xMCVv6sOrmtUeWfLqZ8puu5gdyqpwlOXCVPKJ-Xn5CDGQohBgkmP3YCm5VwG3RPSjQIQE) [5] [stackoverflow.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHWN_sCKBc3qm1oOto_-ydm9z6ieZDl6GS9QDIe_kevXdK8HoNdX7kFhSel_gshPjxWjW5j0mGP6nONL_ztUlHRVZFViBWjB5f7eZQc_R0EAq2awSxkJLnL1-3AIOw2qB7tHQc6uNklEpKjafIucMFFP3gpmxEWeOKnESg5ddkqaGPLW8u98PynLfQ_9jc2bRk=) Note: Source URLs are HTTP redirects; check where they resolve if you need the direct link.