Jenkins inbound agent connectivity limited by Jenkins URL reachability
0 reputation · 24 Oct 2025, 10:47 UTC
Goal: confirm whether Jenkins inbound (JNLP) agents resolve the controller endpoint exclusively from the Jenkins URL configured under Manage Jenkins > Configure System > Jenkins Location, and whether Jenkins provides any automatic fallback to the request Host header or client IP.
Constraint: a controller reachable at http://localhost:8080 during local testing may work for agents on the same host but fails for remote production agents. Jenkins does not automatically rewrite the agent-facing address, and launch behavior differs between inbound agents, which connect to the controller, and SSH agents, which accept controller connections.
Assumption: classic inbound agent behavior, without WebSocket-specific overrides.
Questions:
- Does the configured Jenkins URL serve as the sole agent-facing endpoint for inbound channel establishment?
- Are there documented conditions under which Jenkins falls back to another address when the Jenkins URL is unreachable from an agent host?
- What verification distinguishes a misconfigured Jenkins URL from network-layer blocking by a reverse proxy or firewall?
