Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-68107

Unable to start Jenkins with HTTP2 unless httpsKeyStore is set

      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?

          [JENKINS-68107] Unable to start Jenkins with HTTP2 unless httpsKeyStore is set

          Dmitry Erastov created issue -
          Dmitry Erastov made changes -
          Description Original: This happened after upgrading from 2.338 (which worked fine) to 2.340. Jenkins fails to start with the following log:

           
          {noformat}
          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){noformat}
          The relevant portion of the Jenkins config:

           
          {noformat}
          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=""
          {noformat}
           

           

          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?

           
          New: This happened after upgrading from 2.338 (which worked fine) to 2.340. Jenkins fails to start with the following log: 
          {noformat}
          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){noformat}
          The relevant portion of the Jenkins config:
          {noformat}
          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=""
          {noformat}
          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?
          Dmitry Erastov made changes -
          Labels Original: http2 https keystore New: documentation http2 https keystore
          Basil Crow made changes -
          Assignee New: Dmitry Erastov [ dskrvk ]
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Basil Crow made changes -
          Remote Link New: This issue links to "jenkins-infra/jenkins.io#5021 (Web Link)" [ 27508 ]
          Basil Crow made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            dskrvk Dmitry Erastov
            dskrvk Dmitry Erastov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: