- When using the Jenkins CLI, it reports an exception like the following:
java.io.IOException: HTTP full-duplex channel timeout: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx at jenkins.util.FullDuplexHttpService.download(FullDuplexHttpService.java:104) at jenkins.util.FullDuplexHttpService$Response.generateResponse(FullDuplexHttpService.java:171) [...]
- CloudBees CI (CloudBees Core)
- CloudBees CI (CloudBees Core) on modern cloud platforms - Managed Master
- CloudBees CI (CloudBees Core) on modern cloud platforms - Operations Center
- CloudBees CI (CloudBees Core) on traditional platforms - Client Master
- CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
- CloudBees Jenkins Platform - Client Master
- CloudBees Jenkins Platform - Operations Center
- Jenkins CLI
This error is in most cases caused by a Reverse Proxy that is buffering HTTP requests and it impacts only the CLI Protocols that relies on HTTP Full Duplex: either the deprecated
-remoting mode or the
-http mode of the Jenkins CLI.
As mentioned in this comment from JENKINS-43666: Since the HTTP Duplex transport requires connections to be long-lasting and unbuffered, any reverse proxy must be configured to act transparently in these regards.
The solution is to configure the Reverse Proxy that is front of Jenkins to not buffer the request. Here are some examples:
Note: When running Jenkins in Kubernetes and using the Nginx Ingress Controller, add the annotations
nginx.ingress.kubernetes.io/proxy-request-buffering: "off" to the Ingress resource of you master. In CloudBees Core on Modern Platform, this annotation is set by default to CJOC and Master ingresses.