-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
All
In our Jenkins instance I've set up HTTP tunnels on my host machine so I don't have to log onto a windows jump box in order to access the Jenkins GUI.
Everything is working fine, except for the build pipeline plug in.
On the pipeline when I click the 'run' or 'console' button I get a 404 error. The error is that is can't fine the server name
I suspect that the plugin is using absolute urls (which includes the server name) and not relative URLs
Some users can only access the Jenkins via the Jumpbox so I can't change the Jenkins URL setting under http://<ourserver>:8080/config
We seem to have the problem in a similar manner. Our Jenkins runs behind a reverse proxy on HTTPS and if you try to start a parameterised job, the plugin loads the data from an HTTP-URL. Which gets blocked by the web browsers security settings to block HTTP traffic on HTTPS-sites.
Ubuntu 15.10 (64-bit)
Firefox 43.0.4:
Blocked loading mixed active content "http://jenkins.example.com/view/Test-Pipeline/job/TEST-Test-Pipeline-Launcher-1//build?delay=0sec"[Learn More] (jquery.full.js:5756:4)
Chromium Version 47.0.2526.73:
Mixed Content: The page at 'https://jenkins.example.com/view/Test-Pipeline/' was loaded over HTTPS, but requested an insecure resource 'http://jenkins.example.com/view/Test-Pipeline/job/TEST-Test-Pipeline-Launcher-1//build?delay=0sec'. This request has been blocked; the content must be served over HTTPS (https://jenkins.example.com/adjuncts/1b902230/org/kohsuke/stapler/jquery/jquery.full.js:5756)