Problem
It doesn't matter what settings are passed in to Jenkins on the command line (i.e.--httpPort=8001 --httpsPort=8002) the slave-agent.jnlp file refers to port 8010, as do the instructions on the Node page.
At the moment it's impossible to run a web-started node over https, or when Jenkins is running on a non-standard port.
Expected behaviour
If https is enabled then the instructions (and jnlp file) should all point to https, using the port set on the command line. If not then the instructions (and jnlp file) should all point to http, using the port set on the command line.
- is duplicated by
-
JENKINS-33524 Windows slave fails to connect to Jenkins via HTTPS
-
- Resolved
-
[JENKINS-43729] Slave-agent.jnlp does not obey httpPort or httpsPort settings
Andrew Ducker
created issue -
Andrew Ducker
made changes -
| Priority | Original: Critical [ 2 ] | New: Major [ 3 ] |
| Component/s | New: core [ 15593 ] |
| Component/s | Original: remoting [ 15489 ] |
| Labels | Original: https security | New: https remoting security |
| Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Andrew Ducker
added a comment - Aaah! Thank you! I had no idea that that was where it was getting that information from. Updating that setting meant that I can now connect over HTTPS.
Andrew Ducker
added a comment - Aaah! Thank you! I had no idea that that was where it was getting that information from. Updating that setting meant that I can now connect over HTTPS. | Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
As designed, I'd say. Jenkins relies on the URL specified in the Global system configuration. The Port from command line cannot be used, because in such case there may be issues with proxy setups (e.g. haproxy or Docker port mapping).