[{"data":1,"prerenderedAt":239},["ShallowReactive",2],{"seo-verification":3,"blog-tls-handshake-timeout-post-quantum-clienthello-diagnose-ma-en":6,"promo-bar-likely":238},{"google":4,"bing":5},"EycwPY2XMyTkVzas3n1ygeNJFGAH513qrMjfDljzsMQ","",{"key":7,"data":8},"blog-tls-handshake-timeout-post-quantum-clienthello-diagnose-ma-en",{"id":9,"slug":10,"slugs":11,"title":15,"excerpt":16,"readTime":17,"views":18,"isPinned":19,"noindex":19,"publishedAt":20,"updatedAt":21,"category":22,"categories":28,"featuredImage":30,"bgImage":31,"posterImage":32,"relatedSolution":33,"intro":36,"keyPoints":37,"sections":38,"ctaTitle":172,"ctaBody":173,"ctaButton":174,"ctaUrl":175,"relatedPosts":176},576,"tls-handshake-timeout-post-quantum-clienthello-diagnose",{"fr":12,"en":10,"ar":13,"es":14},"tls-handshake-timeout-clienthello-post-quantique-diagnostiquer","انتهاء-مهلة-مصافحة-tls-تشخيص-clienthello-ما-بعد-الكم","tls-handshake-timeout-clienthello-poscuantico-diagnostico","TLS handshake timeout: diagnosing the post-quantum ClientHello","curl answers but your client times out in TLS? Diagnose a filtered post-quantum ClientHello with openssl and curl, then fix it or work around it with GODEBUG.",10,0,false,"2026-11-11T00:00:00+00:00","2026-11-11T11:38:05+00:00",{"id":23,"name":24,"slug":25,"color":26,"icon":27},8,"Security & Monitoring","securite-monitoring","bg-rose-500\u002F10 text-rose-400","security",[29],{"id":23,"name":24,"slug":25,"color":26,"icon":27},null,"\u002Fblog\u002Fcovers\u002Fbg.svg","\u002Fblog\u002Fcovers\u002Ftls-handshake-timeout-clienthello-post-quantique-diagnostiquer-poster.svg",{"categorySlug":34,"appSlug":35},"artificial-intelligence","ollama","Since late October 2026, tools such as `ollama pull` fail with `net\u002Fhttp: TLS handshake timeout` on hosts that still answer curl. The server is not down: recent clients announce a post-quantum key exchange by default, its first message is much larger, and a device on the path drops it. This guide explains the mechanism, gives two openssl commands that prove it in a few minutes, then sorts the fixes: repair the path first, and disable post-quantum for a single process only as a last resort.",[],[39,43,46,82,107,110,131,134,143,147,150,157,160],{"type":40,"title":41,"body":42},"h2","The symptom: curl answers, the tool times out","The typical scenario fits in three lines. A download started by a tool written in Go stops on `Error: pull model manifest: Get \"https:\u002F\u002Fregistry.ollama.ai\u002F...\": net\u002Fhttp: TLS handshake timeout`. The same host, queried with an older-generation `curl`, answers in a fraction of a second. And retrying changes nothing: three attempts out of three fail the same way.\n\nThis is the pattern of the ollama\u002Follama#19430 thread, opened on 31 October 2026. The point to keep is the asymmetry: the TCP connection is established, then the TLS handshake never completes. It is not a broken DNS record, a closed port or an expired certificate, which would produce different messages. When TCP works and only the first TLS message stays unanswered, look at the size and shape of that message, the ClientHello.",{"type":40,"title":44,"body":45},"Why a bigger ClientHello can block everything","The ClientHello is the first message of a TLS connection: the client lists its algorithms there and sends its key exchange shares. Since Go 1.24, the standard library enables the hybrid post-quantum exchange X25519MLKEM768 by default when `Config.CurvePreferences` is nil. OpenSSL 3.5.0, released on 8 April 2025, does the same: its default group list puts X25519MLKEM768 first and sends two key shares, X25519MLKEM768 and X25519.\n\nThe ML-KEM share is large. In thread #19430 the post-quantum ClientHello weighs 1573 bytes, against 512 for the classical one: it no longer fits in a single packet. Yet some servers and devices assume the ClientHello arrives in one TCP read. The tldr.fail site describes this bug: the server reads the first fragment, judges the handshake invalid and hangs up, whereas a correct server would ignore the unknown option. The bug predates post-quantum, and size merely reveals it. The Go documentation presents it as the reason to use `GODEBUG=tlsmlkem=0`.",{"type":47,"title":48,"headers":49,"rows":53},"comparison","Symptom, likely cause and deciding test",[50,51,52],"Symptom","Likely cause","Deciding test",[54,58,62,66,70,74,78],[55,56,57],"Only the hybrid group times out with `openssl s_client`","Post-quantum ClientHello filtered or misread","`-groups X25519MLKEM768` then `-groups X25519`",[59,60,61],"curl passes with `--curves X25519:P-256`, the Go client times out","The Go client announces the hybrid group by default","`GODEBUG=tlsmlkem=0` on that process only",[63,64,65],"Everything times out, even with X25519 alone","Firewall or routing: size is not the issue","`curl -v` to another host and another port",[67,68,69],"Small requests pass, large exchanges freeze","MTU or MSS, ICMP black hole","`ping -M do -s 1472` then `tcp_mtu_probing`",[71,72,73],"One host fails, from all your networks","Server that misreads a fragmented ClientHello","Same test from a second network",[75,76,77],"Failure on one network, success on another","Access filtering: ISP, company, middlebox","Second path: a VPS or a phone hotspot",[79,80,81],"Immediate cut (reset) after the ClientHello","Device that hangs up on an unexpected message","`tcpdump`: an RST right after the ClientHello",{"type":83,"title":84,"steps":85},"steps","Diagnose in ten minutes",[86,89,92,95,98,101,104],{"title":87,"body":88},"Reproduce with curl","Measure time and response code: `curl -sS -o \u002Fdev\u002Fnull -w '%{http_code} %{time_total}\\n' https:\u002F\u002Fexample.com\u002F`. If curl answers fast and your tool times out, the server is reachable and the fault lies elsewhere.",{"title":90,"body":91},"Force a classical ClientHello","Run again with `curl --curves X25519:P-256 -sS -o \u002Fdev\u002Fnull -w '%{http_code} %{time_total}\\n' https:\u002F\u002Fexample.com\u002F`. In thread #19430 this 512-byte ClientHello gets an answer in 0.32 s. Depending on the TLS library behind your curl, the option may be refused: read the message before concluding.",{"title":93,"body":94},"Compare the two groups with openssl","You need OpenSSL 3.5 or later for the first test. Run `timeout 10 openssl s_client -connect example.com:443 -servername example.com -tls1_3 -groups X25519MLKEM768 \u003C\u002Fdev\u002Fnull`, then the same command with `-groups X25519`.",{"title":96,"body":97},"Read the verdict","If X25519 alone completes and the hybrid group stays silent until the timeout, the post-quantum ClientHello is too large or filtered. In the thread, the hybrid one times out after 8 seconds. If both fail, this is not that bug.",{"title":99,"body":100},"Rule out the MTU","Test `ping -M do -s 1472 example.com`: the 1500-byte packet without fragmentation must pass. Also read `sysctl net.ipv4.tcp_mtu_probing`: 0 disables detection, 1 enables it when an ICMP black hole is detected, 2 keeps it always on.",{"title":102,"body":103},"Capture the exchange, optional","With `sudo tcpdump -ni any host HOST_IP and tcp port 443`, look at what follows the ClientHello: retransmissions with no answer point to a dropped packet, an RST points to an active cut.",{"title":105,"body":106},"Change network path","Run the two openssl commands again from another connection: a mobile hotspot, or a VPS. Same result everywhere, the fault is on the remote host. Different result, it is on your access.",{"type":40,"title":108,"body":109},"Who blocks: remote server, middlebox or access path","The test from a second network points at the culprit. If the host fails from everywhere, it is a server or a device in front of it: an old reverse proxy, an application firewall, a load balancer that misreads a fragmented ClientHello. You cannot fix that, but you can warn the operator by attaching the two openssl commands and their output, which saves the usual round trip.\n\nIf the host answers from one network and not from the other, the fault is on your access path: a corporate TLS inspection box, a firewall that does not recognise the hybrid group code, or filtering by an access provider. That is the case described in thread #19430, where the reporter is on an ISP that silently drops these ClientHellos. In that thread the block follows the destination IP address, not the SNI name, and the MTU test passes: the MTU lead was ruled out.",{"type":83,"title":111,"steps":112},"Fix it, or work around it",[113,116,119,122,125,128],{"title":114,"body":115},"Fix the path when it is yours","Update the reverse proxy, firewall or inspection box that rejects the ClientHello. It is the only fix that keeps post-quantum.",{"title":117,"body":118},"Handle the MTU if the test showed it","If `ping -M do -s 1472` fails, enable detection with `sudo sysctl -w net.ipv4.tcp_mtu_probing=1`, then persist the value in a file under `\u002Fetc\u002Fsysctl.d\u002F`. It is a separate lead, to test after the hybrid group.",{"title":120,"body":121},"Disable post-quantum for a Go client","Run the command with `GODEBUG=tlsmlkem=0`, for example `GODEBUG=tlsmlkem=0 .\u002Fmy-tool`. The client now announces only classical groups, and the ClientHello falls back to an ordinary size.",{"title":123,"body":124},"Set it in a systemd service","Create a drop-in with `sudo systemctl edit my-service`, add the line `Environment=\"GODEBUG=tlsmlkem=0\"` under `[Service]`, then `sudo systemctl restart my-service`.",{"title":126,"body":127},"Set it in a container","With Docker, add `-e GODEBUG=tlsmlkem=0` to `docker run`. With Compose, add `- GODEBUG=tlsmlkem=0` under `environment:` of the service concerned, then `docker compose up -d`.",{"title":129,"body":130},"Remove the workaround once the path is repaired","Note in your configuration repository why the variable is there. When the middlebox or server is fixed, delete it and repeat the openssl test to check that the hybrid group passes.",{"type":40,"title":132,"body":133},"Ollama on a VPS: the case in thread #19430","The thread reports this behaviour with Ollama 0.40.13, in the official `ollama\u002Follama:latest` image under Docker, on an access provider connection with no VPN or proxy. The error is the one quoted above, on `registry.ollama.ai`. The reporter measured 1573 bytes for the post-quantum ClientHello, which times out, and 512 for the classical one, which gets a 404 answer in 0.32 s. With `GODEBUG=tlsmlkem=0` on the process doing the download, three attempts out of three succeed, against three failures out of three without.\n\nAt the time of writing, this thread is open and mentions no official fix: the workaround is the reporter's, presented as temporary. For Ollama on a VPS the consequence is practical. If `ollama pull` times out while curl reaches the registry, apply the diagnosis above from the VPS, then set the variable on the ollama container, with `docker run -e GODEBUG=tlsmlkem=0 ...` or under `environment:` in Compose, and rerun `docker exec ollama ollama pull the-model`. A VPS also gives a network path different from yours: if it pulls the model without the variable, the filtering is on your access.",{"type":135,"title":136,"items":137},"ul","What the GODEBUG=tlsmlkem=0 workaround costs",[138,139,140,141,142],"**No more post-quantum** — the process no longer announces X25519MLKEM768: its connections lose the protection against traffic captured today and decrypted later.","**A wide scope** — the variable applies to the whole process, so to all its outgoing calls, not only to the host that causes trouble.","**A temporary setting** — it is a workaround, not a fix: it hides a network path defect that stays in place.","**A debt to document** — without a comment in the configuration, the variable survives for years and nobody knows why.","**No universal guarantee** — if the filtering does not come from the ClientHello, the variable changes nothing: repeat the openssl test to find out.",{"type":144,"title":145,"body":146},"tip","Prove before working around","Keep the output of the two `openssl s_client` commands (with and without the hybrid group), dated, in your ticket or in the message to the operator. It is enough to show that the host answers in classical and not in hybrid, and it avoids installing a workaround on a wrong diagnosis.",{"type":40,"title":148,"body":149},"Troubleshooting: the messages you will meet","The same fault is displayed differently depending on the tool. Here are the most common forms, and what each says about the failure.",{"type":135,"items":151},[152,153,154,155,156],"**`net\u002Fhttp: TLS handshake timeout`** — the Go client established TCP, then received no answer to its ClientHello. Run the openssl test with and without the hybrid group.","**`curl: (28) SSL connection timeout`** — the same symptom on the curl side: the handshake does not complete within the delay. Compare with `--curves X25519:P-256`.","**`timeout 10 openssl s_client ...` with no output, return code 124** — the handshake did not complete in ten seconds. It is the expected result for a filtered hybrid group.","**`read: connection reset by peer`** — the other end or a device is actively cutting. Look for an RST right after the ClientHello with `tcpdump`.","**`connect:errno=110` in the openssl output** — TCP itself times out, before any ClientHello: firewall or routing, not this bug.",{"type":40,"title":158,"body":159},"Keep the proof, not only the workaround","A TLS handshake timeout that hits a single tool feels like a bug in the software. Comparing two groups with openssl puts the question back in the right order: does the host answer a classical ClientHello, and a hybrid one? Depending on the answer, the fix lies on the server, on the middlebox, on your access or, as a last resort, in an environment variable set on a process.\n\nWhat is certain today: Go and OpenSSL announce the hybrid group by default, and some devices handle it badly. What is not: an official fix on the Ollama side, absent from the thread so far. Treat `GODEBUG=tlsmlkem=0` as a dated patch, and repeat the test after every change to the path.",{"type":83,"title":161,"steps":162},"Going further",[163,166,169],{"title":164,"body":165},"Set up an Ollama server on a VPS","Installation, models and API exposure: \u003Ca href=\"\u002Fen\u002Fblog\u002Fhow-to-host-ollama-on-a-vps\">How to host Ollama on a VPS\u003C\u002Fa>.",{"title":167,"body":168},"Close repeated access attempts on this server","To block attempts hitting the same service, see \u003Ca href=\"\u002Fen\u002Fblog\u002Ffail2ban-enhanced-on-vps-blocking-repeated-attacks\">Fail2Ban Enhanced on a VPS\u003C\u002Fa>.",{"title":170,"body":171},"Choose the reverse proxy that terminates TLS","Caddy, Traefik or Nginx Proxy Manager each handle TLS in their own way: \u003Ca href=\"\u002Fen\u002Fblog\u002Fcaddy-traefik-or-nginx-proxy-manager-which-to-choose\">the comparison\u003C\u002Fa>.","A second network path to settle it","A ServOrbit VPS works as a test point: if the same call passes from the VPS and fails from your place, the fault is on your access. You keep root access there to run the openssl and curl commands of this guide.","Test from a VPS","\u002Fvps-cloud",[177,200,218],{"id":178,"slug":179,"slugs":180,"title":184,"excerpt":185,"readTime":186,"views":187,"isPinned":19,"noindex":19,"publishedAt":188,"updatedAt":189,"category":190,"categories":196,"featuredImage":30,"bgImage":31,"posterImage":198,"relatedSolution":199},11,"how-to-host-ollama-on-a-vps",{"fr":181,"en":179,"ar":182,"es":183},"heberger-ollama-vps","كيفية-استضافة-ollama-على-خادم-vps","como-alojar-ollama-en-un-vps","Hosting Ollama on a VPS: advanced operational guide","Advanced Ollama VPS setup: model management, nginx reverse proxy, API security, Q4_K_M\u002FQ8 quantization, CVE-2026-45672 Open WebUI and secure coupling.",9,3,"2026-06-09T00:00:00+00:00","2026-11-04T16:30:24+00:00",{"id":191,"name":192,"slug":193,"color":194,"icon":195},1,"Artificial Intelligence","intelligence-artificielle","bg-purple-500\u002F10 text-purple-400","ia",[197],{"id":191,"name":192,"slug":193,"color":194,"icon":195},"\u002Fblog\u002Fcovers\u002Fheberger-ollama-vps-poster.svg",{"categorySlug":34,"appSlug":35},{"id":201,"slug":202,"slugs":203,"title":207,"excerpt":208,"readTime":178,"views":191,"isPinned":19,"noindex":19,"publishedAt":209,"updatedAt":210,"category":211,"categories":212,"featuredImage":30,"bgImage":31,"posterImage":214,"relatedSolution":215},109,"fail2ban-enhanced-on-vps-blocking-repeated-attacks",{"fr":204,"en":202,"ar":205,"es":206},"proteger-vps-fail2ban","fail2ban-enhanced-على-خادم-vps-حجب-الهجمات-المتكررة","fail2ban-en-vps-bloquear-ataques-repetidos","Fail2Ban Enhanced on VPS: blocking repeated attacks","Link Fail2Ban Enhanced to the ServOrbit catalog: SSH\u002FNginx banning, readable logs and official documentation.","2026-03-03T00:00:00+00:00","2026-11-01T14:14:36+00:00",{"id":23,"name":24,"slug":25,"color":26,"icon":27},[213],{"id":23,"name":24,"slug":25,"color":26,"icon":27},"\u002Fblog\u002Fcovers\u002Fproteger-vps-fail2ban-poster.svg",{"categorySlug":216,"appSlug":217},"securite","fail2ban-enhanced",{"id":219,"slug":220,"slugs":221,"title":225,"excerpt":226,"readTime":17,"views":227,"isPinned":19,"noindex":19,"publishedAt":228,"updatedAt":229,"category":230,"categories":235,"featuredImage":30,"bgImage":31,"posterImage":237,"relatedSolution":30},227,"caddy-traefik-or-nginx-proxy-manager-which-to-choose",{"fr":222,"en":220,"ar":223,"es":224},"choisir-reverse-proxy-vps-caddy-traefik-nginx","caddy-أم-traefik-أم-nginx-proxy-manager-أيهما-تختار","elegir-reverse-proxy-vps-caddy-traefik-nginx","Caddy, Traefik or Nginx Proxy Manager: which to choose?","Caddy, Traefik or Nginx Proxy Manager for your VPS? A practical comparison to choose the right reverse proxy for your Docker stack.",7,"2026-08-06T00:00:00+00:00","2026-11-10T14:39:01+00:00",{"id":231,"name":232,"slug":233,"color":234,"icon":233},5,"Comparison","comparatif","bg-info\u002F10 text-info",[236],{"id":231,"name":232,"slug":233,"color":234,"icon":233},"\u002Fblog\u002Fcovers\u002Fchoisir-reverse-proxy-vps-caddy-traefik-nginx-poster.svg",true,1794785367985]