We’re hitting consistent timeouts when our Jenkins CI/CD connector tries to deploy builds to our staging environment. The connector worked fine until last week when we updated to pol-2406.
The deployment hangs for exactly 60 seconds before failing:
ERROR: Connection timeout after 60000ms
at JenkinsConnector.deploy(line 234)
Failed to reach endpoint: https://staging.alm.company.local:8443
Our proxy configuration hasn’t changed, and SSL certificates are valid through 2026. The same connector deploys successfully to our dev environment on the same network segment. This is blocking our daily release cycle - we can’t promote tested builds to staging for final validation.
Has anyone experienced similar timeout issues with environment endpoint registration after upgrading the CI/CD connector module?
We ran into the same proxy configuration headache. The new connector version changed how it handles proxy authentication. Make sure your proxy credentials are set correctly in the environment-specific connector configuration. Also verify that the staging endpoint URL is registered properly in the connector’s environment registry - we found ours had reverted to localhost after the upgrade.
Update: We’re making progress. The certificate chain was part of the issue - our staging cert is signed by an internal CA. But even after importing the CA cert, we still get intermittent timeouts. The proxy authentication credentials look correct. Starting to think this might be a combination of all four factors mentioned in this thread.
I worked through this exact scenario last month. You need to address all four configuration areas systematically:
1. Proxy Configuration
Update your connector properties with explicit proxy settings:
connector.proxy.host=proxy.company.local
connector.proxy.port=8080
connector.proxy.auth.enabled=true
2. SSL Certificate Validation
Import your internal CA certificate and configure validation:
keytool -import -alias company_ca -file ca.crt -keystore connector_trust.jks
connector.ssl.truststore=/path/to/connector_trust.jks
connector.ssl.validateCertChain=true
3. Connector Timeout Settings
Increase timeouts to account for proxy + SSL overhead:
connector.timeout.connection=180000
connector.timeout.socket=240000
connector.timeout.ssl.handshake=90000
4. Environment Endpoint Registration
Re-register your staging endpoint explicitly:
connector.environment.staging.url=https://staging.alm.company.local:8443
connector.environment.staging.enabled=true
connector.environment.staging.priority=2
The key issue in pol-2406 is that SSL handshake timeout is now separate from connection timeout. Your 60-second failures suggest the handshake is timing out before the connection timeout even kicks in. Set connector.timeout.ssl.handshake to at least 90 seconds when going through a proxy.
After applying all four configuration changes, restart the connector service and test with a small deployment first. The combination of stricter SSL validation plus proxy authentication overhead is what’s causing your staging-specific failures. Dev works because it likely bypasses the proxy or uses simpler certificates.
One more thing: verify your Jenkins plugin version matches pol-2406. There were compatibility issues with older Jenkins connector plugins that manifested as timeout errors with the new SSL validation.
Check if your connector timeout settings were reset during the upgrade. We had this exact issue after updating to pol-2406. The default timeout dropped from 120s to 60s in the new version, which wasn’t enough for our staging environment’s SSL handshake through the corporate proxy.
Good catch on the timeout change. I checked our connector config and you’re right - it defaulted back to 60000ms. However, even after bumping it to 180000ms, we’re still seeing failures. The logs show the connection attempt starts but never completes the SSL negotiation phase. Could this be related to certificate chain validation in the new version?