-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Minor
-
Component/s: core
-
Environment:Jenkins 2.340
This happened after upgrading from 2.338 (which worked fine) to 2.340. Jenkins fails to start with the following log:Â
SEVERE winstone.Logger#logInternal: Container startup failed
winstone.WinstoneException: Please set --httpsKeyStore
at winstone.AbstractSecuredConnectorFactory.configureSsl(AbstractSecuredConnectorFactory.java:88)
at winstone.Http2ConnectorFactory.start(Http2ConnectorFactory.java:59)
at winstone.Launcher.spawnListener(Launcher.java:255)
Caused: java.io.IOException: Failed to start a listener: winstone.Http2ConnectorFactory
at winstone.Launcher.spawnListener(Launcher.java:261)
at winstone.Launcher.<init>(Launcher.java:191)
at winstone.Launcher.main(Launcher.java:405)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at Main._main(Main.java:304)
at Main.main(Main.java:108)
The relevant portion of the Jenkins config:
JENKINS_PORT="8080" JENKINS_LISTEN_ADDRESS="127.0.0.1" JENKINS_HTTPS_PORT="" JENKINS_HTTPS_KEYSTORE="" JENKINS_HTTPS_KEYSTORE_PASSWORD="" JENKINS_HTTPS_LISTEN_ADDRESS="" JENKINS_HTTP2_PORT="8029" JENKINS_HTTP2_LISTEN_ADDRESS="127.0.0.1" JENKINS_EXTRA_LIB_FOLDER="" JENKINS_ARGS=""
In our case we specifically don't want Jenkins to handle HTTPS, and instead let the webserver do that. Is this still a supported configuration?
- links to
