Why does Jenkins say “This Jenkins instance appears to be offline”












27














I have a fresh install of Jenkins 2.32.2 on Ubuntu.
Opened a browser on the instance and get to a page titled Offline, with the message "This Jenkins instance appears to be offline" and offers options to "Configure Proxy" or "Skip Plugin Installation"



The machine clearly isn't offline as I just used the internet connection to do the installation.
I also had a previous installation, done exactly the same way, that was working.
I removed the previous installation as Pipelines wouldn't work and Google told me it was because of JDK 9. So I removed all the JDK/JRE installations as well as jenkins, fresh installed JDK 8 only, installed Jenkins, and got to here.



Jenkins has worked on this box in the past so what makes it think it is offline?



Update: Found a log file /var/lib/jenkins/logs/tasks/Download metadata.log
and it starts with a message FATAL: Connection refused (Connection refused)
I would think that indicates that the internet connection is OK, but something else is stopping it getting data?



Update: Based on other research I checked the Update Site in the Plugin Manager. This is listed as http://updates.jenkins-ci.org/update-center.json and, from the command line a wget of this file succeeds. So most definitely not a connection issue. Worked with both http and https, jenkins works with neither.










share|improve this question
























  • I had the same promblem, and I had try proxy config, it works! On the same machine a pure http proxy. Still dont know why.
    – deemstone
    Mar 29 '17 at 9:48
















27














I have a fresh install of Jenkins 2.32.2 on Ubuntu.
Opened a browser on the instance and get to a page titled Offline, with the message "This Jenkins instance appears to be offline" and offers options to "Configure Proxy" or "Skip Plugin Installation"



The machine clearly isn't offline as I just used the internet connection to do the installation.
I also had a previous installation, done exactly the same way, that was working.
I removed the previous installation as Pipelines wouldn't work and Google told me it was because of JDK 9. So I removed all the JDK/JRE installations as well as jenkins, fresh installed JDK 8 only, installed Jenkins, and got to here.



Jenkins has worked on this box in the past so what makes it think it is offline?



Update: Found a log file /var/lib/jenkins/logs/tasks/Download metadata.log
and it starts with a message FATAL: Connection refused (Connection refused)
I would think that indicates that the internet connection is OK, but something else is stopping it getting data?



Update: Based on other research I checked the Update Site in the Plugin Manager. This is listed as http://updates.jenkins-ci.org/update-center.json and, from the command line a wget of this file succeeds. So most definitely not a connection issue. Worked with both http and https, jenkins works with neither.










share|improve this question
























  • I had the same promblem, and I had try proxy config, it works! On the same machine a pure http proxy. Still dont know why.
    – deemstone
    Mar 29 '17 at 9:48














27












27








27


9





I have a fresh install of Jenkins 2.32.2 on Ubuntu.
Opened a browser on the instance and get to a page titled Offline, with the message "This Jenkins instance appears to be offline" and offers options to "Configure Proxy" or "Skip Plugin Installation"



The machine clearly isn't offline as I just used the internet connection to do the installation.
I also had a previous installation, done exactly the same way, that was working.
I removed the previous installation as Pipelines wouldn't work and Google told me it was because of JDK 9. So I removed all the JDK/JRE installations as well as jenkins, fresh installed JDK 8 only, installed Jenkins, and got to here.



Jenkins has worked on this box in the past so what makes it think it is offline?



Update: Found a log file /var/lib/jenkins/logs/tasks/Download metadata.log
and it starts with a message FATAL: Connection refused (Connection refused)
I would think that indicates that the internet connection is OK, but something else is stopping it getting data?



Update: Based on other research I checked the Update Site in the Plugin Manager. This is listed as http://updates.jenkins-ci.org/update-center.json and, from the command line a wget of this file succeeds. So most definitely not a connection issue. Worked with both http and https, jenkins works with neither.










share|improve this question















I have a fresh install of Jenkins 2.32.2 on Ubuntu.
Opened a browser on the instance and get to a page titled Offline, with the message "This Jenkins instance appears to be offline" and offers options to "Configure Proxy" or "Skip Plugin Installation"



The machine clearly isn't offline as I just used the internet connection to do the installation.
I also had a previous installation, done exactly the same way, that was working.
I removed the previous installation as Pipelines wouldn't work and Google told me it was because of JDK 9. So I removed all the JDK/JRE installations as well as jenkins, fresh installed JDK 8 only, installed Jenkins, and got to here.



Jenkins has worked on this box in the past so what makes it think it is offline?



Update: Found a log file /var/lib/jenkins/logs/tasks/Download metadata.log
and it starts with a message FATAL: Connection refused (Connection refused)
I would think that indicates that the internet connection is OK, but something else is stopping it getting data?



Update: Based on other research I checked the Update Site in the Plugin Manager. This is listed as http://updates.jenkins-ci.org/update-center.json and, from the command line a wget of this file succeeds. So most definitely not a connection issue. Worked with both http and https, jenkins works with neither.







jenkins offline






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 23 '17 at 7:50

























asked Feb 23 '17 at 6:38









Simon

141125




141125












  • I had the same promblem, and I had try proxy config, it works! On the same machine a pure http proxy. Still dont know why.
    – deemstone
    Mar 29 '17 at 9:48


















  • I had the same promblem, and I had try proxy config, it works! On the same machine a pure http proxy. Still dont know why.
    – deemstone
    Mar 29 '17 at 9:48
















I had the same promblem, and I had try proxy config, it works! On the same machine a pure http proxy. Still dont know why.
– deemstone
Mar 29 '17 at 9:48




I had the same promblem, and I had try proxy config, it works! On the same machine a pure http proxy. Still dont know why.
– deemstone
Mar 29 '17 at 9:48












10 Answers
10






active

oldest

votes


















41














In my case, it has something to do with SSL. I manage to fix it by editing /var/lib/jenkins/hudson.model.UpdateCenter.xml and change url to use http instead of https.



Restart jenkins and reload the website, it no longer shows offline.






share|improve this answer

















  • 2




    worked for me. os x file at /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml
    – Joe Walsh
    Dec 13 '17 at 15:57










  • works with ubuntu 14.04 LTS 64bit
    – mils
    Mar 6 at 22:34






  • 1




    For me on macOS the file was /Users/you/.jenkins/hudson.model.UpdateCenter.xml.
    – weibeld
    Apr 5 at 16:58










  • If it doesn't work. Try to install CNTLM which give you local proxy for external proxy and Jenkins can use CNTLM as proxy server. Not my blog, but there is more explanation: alakbarv.azurewebsites.net/2017/09/12/…
    – jsosnowski
    May 8 at 8:12










  • @jsosnowski Your link is dead.
    – code_dredd
    Jul 6 at 17:07



















13














For macOS users:



Step -1: Edit /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml and change url to use http instead of https.



Step -2: Restart jenkins (for instance by going to http:localhost:8080) and reload the website



Step -3(Optional): If it asks for user and password and if you don't remember creating one; default user is admin and copy the password from



sudo cat /Users/Shared/Jenkins/Home/secrets/initialAdminPassword


credits - @Alex in this post and @Tuan Pham here and @Joe Walsh for the comment on macOS directory path






share|improve this answer































    3














    in my case (macOS), updating jdk to 8 and reinstall jenkins solved the problem.






    share|improve this answer























    • You don't need to reinstall Jenkins; you can upgrade the JDK and then kill the Jenkins process. It will restart automatically.
      – bonh
      Jul 17 at 3:10










    • For me "1.8.0_40" was no good, "1.8.0_181" was good. I've been fooled/forgotten apparently that "Java" on MacOSX was JDK, apparently it's JRE. Ref: stackoverflow.com/questions/15624667/…
      – joedragons
      Oct 12 at 20:59





















    1














    The issue is that for some reason Jenkins doesn't have access to the certificates chain of the Jenkins updates service.
    On Ubuntu 18.04 I had this issue and the next links and instructions helped me to start Jenkins properly without modifying the default url or using a proxy of some sort.



    Installing a new JDK 8(u101+) with JAVA_HOME should do the trick like at:




    • https://www.digitalocean.com/community/tutorials/how-to-install-java-with-apt-on-ubuntu-18-04


    is making sure that Lets Encrypt certificates are installed and available on the OS/SYSTEM.
    To test it you can use the instructions at:




    • Does Java support Let's Encrypt certificates?


    And to install manually if required the Let's encrypt root chain using the next script:




    • https://gist.github.com/Firefishy/109b0f1a90156f6c933a50fe40aa777e






    share|improve this answer





















    • I strongly recommend that you summarize the key points here in your response, as link-only answers are frowned upon for many reasons (including, but not limited to, the fact that external links often die out and become unavailable, making once useful answers into useless noise).
      – code_dredd
      Jul 9 at 17:22












    • @ray Indeed you are right but this post is not for "dummies". JAVA_HOME is required for JDK or JRE to work properly. On Ubuntu 18.04 which is still in it's "Testing" phase the issue is that the installation doesn't setup the JAVA_HOME variable globally. I am not writing a tutorial but merely pointing to the right direction which by the way alex solution wouldn't even touch... In this whole thread I have only seen guesses and nothing related to the real issue so I added a "redirection" towards a more fruitful one.
      – elico
      Jul 11 at 17:02



















    0














    On MacOS: 10.11.6



    Step-1: Go to /Users//.jenkins



    Step-2: Open the file: hudson.model.UpdateCenter.xml



    Step-3: CHange the value of "default" from "https://xxx" to "http://xxx"






    share|improve this answer





























      0














      I make no claims about this, especially Java related (I personally cannot stand the language), but on my Ubuntu 18.04 L/T, I needed to stand-up a standalone Jenkins instance; So I installed both the Java on which Jenkins appears to be dependent and Jenkins itself



      sudo apt install openjdk-8-jdk jenkins


      Then I updated the Jenkins defaults



      sudo gvim /etc/default/jenkins


      ... inserting the following at the top of the file - only because editing /etc/init.d/jenkins appeared to serve no purpose as it had no effect whatsoever ...



      JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/
      PATH=$JAVA_HOME:$PATH


      Finally, save & quit ... then attempt Jenkins restart



      sudo service jenkins restart


      HTH - it certainly worked for me :-)






      share|improve this answer





























        0














        There is something wrong with the internet connection of update center.I have met the same situation with Jenkins installed on macOS.



        You can try to modify the hudson.model.UpdateCenter.xml file.



        Jenkins installed with .pkg package on macOS,the file path is:
        /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml



        Jenkins installed by Homebrew on macOS,the file path is:
        /Users/{username}/.jenkins/hudson.model.UpdateCenter.xml



        Open the file:



        <?xml version='1.1' encoding='UTF-8'?>
        <sites>
        <site>
        <id>default</id>
        <url>https://updates.jenkins.io/update-center.json</url>
        </site>
        </sites>


        You can try to change https://updates.jenkins.io/update-center.json to:



        http://updates.jenkins.io/update-center.json


        or



        // If you are in China or near China area,https and http are both OK.
        https://mirrors.tuna.tsinghua.edu.cn/jenkins/updates/current/update-center.json


        And then you can restart Jenkins by:



        //loading the URL to restart Jenkins.
        http://localhost:8080/restart


        or



        // Use Homebrew command to restart Jenkins if you installed Jenkins LTS version by Homebrew.  
        brew services restart jenkins-lts





        share|improve this answer





























          0














          For Windows OS,
          Follow below steps

          1. Go to C:Users*your user name*.jenkins

          2. Open the file: hudson.model.UpdateCenter.xml

          3. Update the value of "url" from "https://xxx" to "http://xxx"






          share|improve this answer










          New contributor




          Mohammed Ashfaq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.


























            -1














            Enter this before running Jenkins.



            # iptalbes -F


            It may be because of the firewall.






            share|improve this answer





























              -1














              jenkins_enable="YES"
              jenkins_home="/usr/local/jenkins"
              jenkins_user="jenkins"
              jenkins_args="--webroot=${jenkins_home}/war --httpListenAddress=*.*.*.* --httpPort=8180"

              #jenkins_java_opts="-Djavax.net.ssl.trustStore=/usr/local/jenkins/cacerts -Djava.net.preferIPv6Addresses=true"

              #jenkins_java_opts="-Djavax.net.ssl.trustStore=/usr/local/jenkins/cacerts -Djava.net.preferIPv4Addresses=true"





              share|improve this answer























              • What about a bit of explanation!
                – TheStoryCoder
                Nov 30 at 10:54











              Your Answer






              StackExchange.ifUsing("editor", function () {
              StackExchange.using("externalEditor", function () {
              StackExchange.using("snippets", function () {
              StackExchange.snippets.init();
              });
              });
              }, "code-snippets");

              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "1"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f42408703%2fwhy-does-jenkins-say-this-jenkins-instance-appears-to-be-offline%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              10 Answers
              10






              active

              oldest

              votes








              10 Answers
              10






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              41














              In my case, it has something to do with SSL. I manage to fix it by editing /var/lib/jenkins/hudson.model.UpdateCenter.xml and change url to use http instead of https.



              Restart jenkins and reload the website, it no longer shows offline.






              share|improve this answer

















              • 2




                worked for me. os x file at /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml
                – Joe Walsh
                Dec 13 '17 at 15:57










              • works with ubuntu 14.04 LTS 64bit
                – mils
                Mar 6 at 22:34






              • 1




                For me on macOS the file was /Users/you/.jenkins/hudson.model.UpdateCenter.xml.
                – weibeld
                Apr 5 at 16:58










              • If it doesn't work. Try to install CNTLM which give you local proxy for external proxy and Jenkins can use CNTLM as proxy server. Not my blog, but there is more explanation: alakbarv.azurewebsites.net/2017/09/12/…
                – jsosnowski
                May 8 at 8:12










              • @jsosnowski Your link is dead.
                – code_dredd
                Jul 6 at 17:07
















              41














              In my case, it has something to do with SSL. I manage to fix it by editing /var/lib/jenkins/hudson.model.UpdateCenter.xml and change url to use http instead of https.



              Restart jenkins and reload the website, it no longer shows offline.






              share|improve this answer

















              • 2




                worked for me. os x file at /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml
                – Joe Walsh
                Dec 13 '17 at 15:57










              • works with ubuntu 14.04 LTS 64bit
                – mils
                Mar 6 at 22:34






              • 1




                For me on macOS the file was /Users/you/.jenkins/hudson.model.UpdateCenter.xml.
                – weibeld
                Apr 5 at 16:58










              • If it doesn't work. Try to install CNTLM which give you local proxy for external proxy and Jenkins can use CNTLM as proxy server. Not my blog, but there is more explanation: alakbarv.azurewebsites.net/2017/09/12/…
                – jsosnowski
                May 8 at 8:12










              • @jsosnowski Your link is dead.
                – code_dredd
                Jul 6 at 17:07














              41












              41








              41






              In my case, it has something to do with SSL. I manage to fix it by editing /var/lib/jenkins/hudson.model.UpdateCenter.xml and change url to use http instead of https.



              Restart jenkins and reload the website, it no longer shows offline.






              share|improve this answer












              In my case, it has something to do with SSL. I manage to fix it by editing /var/lib/jenkins/hudson.model.UpdateCenter.xml and change url to use http instead of https.



              Restart jenkins and reload the website, it no longer shows offline.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Sep 16 '17 at 2:26









              Alex

              50444




              50444








              • 2




                worked for me. os x file at /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml
                – Joe Walsh
                Dec 13 '17 at 15:57










              • works with ubuntu 14.04 LTS 64bit
                – mils
                Mar 6 at 22:34






              • 1




                For me on macOS the file was /Users/you/.jenkins/hudson.model.UpdateCenter.xml.
                – weibeld
                Apr 5 at 16:58










              • If it doesn't work. Try to install CNTLM which give you local proxy for external proxy and Jenkins can use CNTLM as proxy server. Not my blog, but there is more explanation: alakbarv.azurewebsites.net/2017/09/12/…
                – jsosnowski
                May 8 at 8:12










              • @jsosnowski Your link is dead.
                – code_dredd
                Jul 6 at 17:07














              • 2




                worked for me. os x file at /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml
                – Joe Walsh
                Dec 13 '17 at 15:57










              • works with ubuntu 14.04 LTS 64bit
                – mils
                Mar 6 at 22:34






              • 1




                For me on macOS the file was /Users/you/.jenkins/hudson.model.UpdateCenter.xml.
                – weibeld
                Apr 5 at 16:58










              • If it doesn't work. Try to install CNTLM which give you local proxy for external proxy and Jenkins can use CNTLM as proxy server. Not my blog, but there is more explanation: alakbarv.azurewebsites.net/2017/09/12/…
                – jsosnowski
                May 8 at 8:12










              • @jsosnowski Your link is dead.
                – code_dredd
                Jul 6 at 17:07








              2




              2




              worked for me. os x file at /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml
              – Joe Walsh
              Dec 13 '17 at 15:57




              worked for me. os x file at /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml
              – Joe Walsh
              Dec 13 '17 at 15:57












              works with ubuntu 14.04 LTS 64bit
              – mils
              Mar 6 at 22:34




              works with ubuntu 14.04 LTS 64bit
              – mils
              Mar 6 at 22:34




              1




              1




              For me on macOS the file was /Users/you/.jenkins/hudson.model.UpdateCenter.xml.
              – weibeld
              Apr 5 at 16:58




              For me on macOS the file was /Users/you/.jenkins/hudson.model.UpdateCenter.xml.
              – weibeld
              Apr 5 at 16:58












              If it doesn't work. Try to install CNTLM which give you local proxy for external proxy and Jenkins can use CNTLM as proxy server. Not my blog, but there is more explanation: alakbarv.azurewebsites.net/2017/09/12/…
              – jsosnowski
              May 8 at 8:12




              If it doesn't work. Try to install CNTLM which give you local proxy for external proxy and Jenkins can use CNTLM as proxy server. Not my blog, but there is more explanation: alakbarv.azurewebsites.net/2017/09/12/…
              – jsosnowski
              May 8 at 8:12












              @jsosnowski Your link is dead.
              – code_dredd
              Jul 6 at 17:07




              @jsosnowski Your link is dead.
              – code_dredd
              Jul 6 at 17:07













              13














              For macOS users:



              Step -1: Edit /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml and change url to use http instead of https.



              Step -2: Restart jenkins (for instance by going to http:localhost:8080) and reload the website



              Step -3(Optional): If it asks for user and password and if you don't remember creating one; default user is admin and copy the password from



              sudo cat /Users/Shared/Jenkins/Home/secrets/initialAdminPassword


              credits - @Alex in this post and @Tuan Pham here and @Joe Walsh for the comment on macOS directory path






              share|improve this answer




























                13














                For macOS users:



                Step -1: Edit /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml and change url to use http instead of https.



                Step -2: Restart jenkins (for instance by going to http:localhost:8080) and reload the website



                Step -3(Optional): If it asks for user and password and if you don't remember creating one; default user is admin and copy the password from



                sudo cat /Users/Shared/Jenkins/Home/secrets/initialAdminPassword


                credits - @Alex in this post and @Tuan Pham here and @Joe Walsh for the comment on macOS directory path






                share|improve this answer


























                  13












                  13








                  13






                  For macOS users:



                  Step -1: Edit /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml and change url to use http instead of https.



                  Step -2: Restart jenkins (for instance by going to http:localhost:8080) and reload the website



                  Step -3(Optional): If it asks for user and password and if you don't remember creating one; default user is admin and copy the password from



                  sudo cat /Users/Shared/Jenkins/Home/secrets/initialAdminPassword


                  credits - @Alex in this post and @Tuan Pham here and @Joe Walsh for the comment on macOS directory path






                  share|improve this answer














                  For macOS users:



                  Step -1: Edit /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml and change url to use http instead of https.



                  Step -2: Restart jenkins (for instance by going to http:localhost:8080) and reload the website



                  Step -3(Optional): If it asks for user and password and if you don't remember creating one; default user is admin and copy the password from



                  sudo cat /Users/Shared/Jenkins/Home/secrets/initialAdminPassword


                  credits - @Alex in this post and @Tuan Pham here and @Joe Walsh for the comment on macOS directory path







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Dec 14 '17 at 18:50

























                  answered Dec 14 '17 at 17:46









                  rak appdev

                  539517




                  539517























                      3














                      in my case (macOS), updating jdk to 8 and reinstall jenkins solved the problem.






                      share|improve this answer























                      • You don't need to reinstall Jenkins; you can upgrade the JDK and then kill the Jenkins process. It will restart automatically.
                        – bonh
                        Jul 17 at 3:10










                      • For me "1.8.0_40" was no good, "1.8.0_181" was good. I've been fooled/forgotten apparently that "Java" on MacOSX was JDK, apparently it's JRE. Ref: stackoverflow.com/questions/15624667/…
                        – joedragons
                        Oct 12 at 20:59


















                      3














                      in my case (macOS), updating jdk to 8 and reinstall jenkins solved the problem.






                      share|improve this answer























                      • You don't need to reinstall Jenkins; you can upgrade the JDK and then kill the Jenkins process. It will restart automatically.
                        – bonh
                        Jul 17 at 3:10










                      • For me "1.8.0_40" was no good, "1.8.0_181" was good. I've been fooled/forgotten apparently that "Java" on MacOSX was JDK, apparently it's JRE. Ref: stackoverflow.com/questions/15624667/…
                        – joedragons
                        Oct 12 at 20:59
















                      3












                      3








                      3






                      in my case (macOS), updating jdk to 8 and reinstall jenkins solved the problem.






                      share|improve this answer














                      in my case (macOS), updating jdk to 8 and reinstall jenkins solved the problem.







                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Jan 16 at 10:39

























                      answered Jan 16 at 9:53









                      mclovin

                      677




                      677












                      • You don't need to reinstall Jenkins; you can upgrade the JDK and then kill the Jenkins process. It will restart automatically.
                        – bonh
                        Jul 17 at 3:10










                      • For me "1.8.0_40" was no good, "1.8.0_181" was good. I've been fooled/forgotten apparently that "Java" on MacOSX was JDK, apparently it's JRE. Ref: stackoverflow.com/questions/15624667/…
                        – joedragons
                        Oct 12 at 20:59




















                      • You don't need to reinstall Jenkins; you can upgrade the JDK and then kill the Jenkins process. It will restart automatically.
                        – bonh
                        Jul 17 at 3:10










                      • For me "1.8.0_40" was no good, "1.8.0_181" was good. I've been fooled/forgotten apparently that "Java" on MacOSX was JDK, apparently it's JRE. Ref: stackoverflow.com/questions/15624667/…
                        – joedragons
                        Oct 12 at 20:59


















                      You don't need to reinstall Jenkins; you can upgrade the JDK and then kill the Jenkins process. It will restart automatically.
                      – bonh
                      Jul 17 at 3:10




                      You don't need to reinstall Jenkins; you can upgrade the JDK and then kill the Jenkins process. It will restart automatically.
                      – bonh
                      Jul 17 at 3:10












                      For me "1.8.0_40" was no good, "1.8.0_181" was good. I've been fooled/forgotten apparently that "Java" on MacOSX was JDK, apparently it's JRE. Ref: stackoverflow.com/questions/15624667/…
                      – joedragons
                      Oct 12 at 20:59






                      For me "1.8.0_40" was no good, "1.8.0_181" was good. I've been fooled/forgotten apparently that "Java" on MacOSX was JDK, apparently it's JRE. Ref: stackoverflow.com/questions/15624667/…
                      – joedragons
                      Oct 12 at 20:59













                      1














                      The issue is that for some reason Jenkins doesn't have access to the certificates chain of the Jenkins updates service.
                      On Ubuntu 18.04 I had this issue and the next links and instructions helped me to start Jenkins properly without modifying the default url or using a proxy of some sort.



                      Installing a new JDK 8(u101+) with JAVA_HOME should do the trick like at:




                      • https://www.digitalocean.com/community/tutorials/how-to-install-java-with-apt-on-ubuntu-18-04


                      is making sure that Lets Encrypt certificates are installed and available on the OS/SYSTEM.
                      To test it you can use the instructions at:




                      • Does Java support Let's Encrypt certificates?


                      And to install manually if required the Let's encrypt root chain using the next script:




                      • https://gist.github.com/Firefishy/109b0f1a90156f6c933a50fe40aa777e






                      share|improve this answer





















                      • I strongly recommend that you summarize the key points here in your response, as link-only answers are frowned upon for many reasons (including, but not limited to, the fact that external links often die out and become unavailable, making once useful answers into useless noise).
                        – code_dredd
                        Jul 9 at 17:22












                      • @ray Indeed you are right but this post is not for "dummies". JAVA_HOME is required for JDK or JRE to work properly. On Ubuntu 18.04 which is still in it's "Testing" phase the issue is that the installation doesn't setup the JAVA_HOME variable globally. I am not writing a tutorial but merely pointing to the right direction which by the way alex solution wouldn't even touch... In this whole thread I have only seen guesses and nothing related to the real issue so I added a "redirection" towards a more fruitful one.
                        – elico
                        Jul 11 at 17:02
















                      1














                      The issue is that for some reason Jenkins doesn't have access to the certificates chain of the Jenkins updates service.
                      On Ubuntu 18.04 I had this issue and the next links and instructions helped me to start Jenkins properly without modifying the default url or using a proxy of some sort.



                      Installing a new JDK 8(u101+) with JAVA_HOME should do the trick like at:




                      • https://www.digitalocean.com/community/tutorials/how-to-install-java-with-apt-on-ubuntu-18-04


                      is making sure that Lets Encrypt certificates are installed and available on the OS/SYSTEM.
                      To test it you can use the instructions at:




                      • Does Java support Let's Encrypt certificates?


                      And to install manually if required the Let's encrypt root chain using the next script:




                      • https://gist.github.com/Firefishy/109b0f1a90156f6c933a50fe40aa777e






                      share|improve this answer





















                      • I strongly recommend that you summarize the key points here in your response, as link-only answers are frowned upon for many reasons (including, but not limited to, the fact that external links often die out and become unavailable, making once useful answers into useless noise).
                        – code_dredd
                        Jul 9 at 17:22












                      • @ray Indeed you are right but this post is not for "dummies". JAVA_HOME is required for JDK or JRE to work properly. On Ubuntu 18.04 which is still in it's "Testing" phase the issue is that the installation doesn't setup the JAVA_HOME variable globally. I am not writing a tutorial but merely pointing to the right direction which by the way alex solution wouldn't even touch... In this whole thread I have only seen guesses and nothing related to the real issue so I added a "redirection" towards a more fruitful one.
                        – elico
                        Jul 11 at 17:02














                      1












                      1








                      1






                      The issue is that for some reason Jenkins doesn't have access to the certificates chain of the Jenkins updates service.
                      On Ubuntu 18.04 I had this issue and the next links and instructions helped me to start Jenkins properly without modifying the default url or using a proxy of some sort.



                      Installing a new JDK 8(u101+) with JAVA_HOME should do the trick like at:




                      • https://www.digitalocean.com/community/tutorials/how-to-install-java-with-apt-on-ubuntu-18-04


                      is making sure that Lets Encrypt certificates are installed and available on the OS/SYSTEM.
                      To test it you can use the instructions at:




                      • Does Java support Let's Encrypt certificates?


                      And to install manually if required the Let's encrypt root chain using the next script:




                      • https://gist.github.com/Firefishy/109b0f1a90156f6c933a50fe40aa777e






                      share|improve this answer












                      The issue is that for some reason Jenkins doesn't have access to the certificates chain of the Jenkins updates service.
                      On Ubuntu 18.04 I had this issue and the next links and instructions helped me to start Jenkins properly without modifying the default url or using a proxy of some sort.



                      Installing a new JDK 8(u101+) with JAVA_HOME should do the trick like at:




                      • https://www.digitalocean.com/community/tutorials/how-to-install-java-with-apt-on-ubuntu-18-04


                      is making sure that Lets Encrypt certificates are installed and available on the OS/SYSTEM.
                      To test it you can use the instructions at:




                      • Does Java support Let's Encrypt certificates?


                      And to install manually if required the Let's encrypt root chain using the next script:




                      • https://gist.github.com/Firefishy/109b0f1a90156f6c933a50fe40aa777e







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Jul 9 at 17:07









                      elico

                      293




                      293












                      • I strongly recommend that you summarize the key points here in your response, as link-only answers are frowned upon for many reasons (including, but not limited to, the fact that external links often die out and become unavailable, making once useful answers into useless noise).
                        – code_dredd
                        Jul 9 at 17:22












                      • @ray Indeed you are right but this post is not for "dummies". JAVA_HOME is required for JDK or JRE to work properly. On Ubuntu 18.04 which is still in it's "Testing" phase the issue is that the installation doesn't setup the JAVA_HOME variable globally. I am not writing a tutorial but merely pointing to the right direction which by the way alex solution wouldn't even touch... In this whole thread I have only seen guesses and nothing related to the real issue so I added a "redirection" towards a more fruitful one.
                        – elico
                        Jul 11 at 17:02


















                      • I strongly recommend that you summarize the key points here in your response, as link-only answers are frowned upon for many reasons (including, but not limited to, the fact that external links often die out and become unavailable, making once useful answers into useless noise).
                        – code_dredd
                        Jul 9 at 17:22












                      • @ray Indeed you are right but this post is not for "dummies". JAVA_HOME is required for JDK or JRE to work properly. On Ubuntu 18.04 which is still in it's "Testing" phase the issue is that the installation doesn't setup the JAVA_HOME variable globally. I am not writing a tutorial but merely pointing to the right direction which by the way alex solution wouldn't even touch... In this whole thread I have only seen guesses and nothing related to the real issue so I added a "redirection" towards a more fruitful one.
                        – elico
                        Jul 11 at 17:02
















                      I strongly recommend that you summarize the key points here in your response, as link-only answers are frowned upon for many reasons (including, but not limited to, the fact that external links often die out and become unavailable, making once useful answers into useless noise).
                      – code_dredd
                      Jul 9 at 17:22






                      I strongly recommend that you summarize the key points here in your response, as link-only answers are frowned upon for many reasons (including, but not limited to, the fact that external links often die out and become unavailable, making once useful answers into useless noise).
                      – code_dredd
                      Jul 9 at 17:22














                      @ray Indeed you are right but this post is not for "dummies". JAVA_HOME is required for JDK or JRE to work properly. On Ubuntu 18.04 which is still in it's "Testing" phase the issue is that the installation doesn't setup the JAVA_HOME variable globally. I am not writing a tutorial but merely pointing to the right direction which by the way alex solution wouldn't even touch... In this whole thread I have only seen guesses and nothing related to the real issue so I added a "redirection" towards a more fruitful one.
                      – elico
                      Jul 11 at 17:02




                      @ray Indeed you are right but this post is not for "dummies". JAVA_HOME is required for JDK or JRE to work properly. On Ubuntu 18.04 which is still in it's "Testing" phase the issue is that the installation doesn't setup the JAVA_HOME variable globally. I am not writing a tutorial but merely pointing to the right direction which by the way alex solution wouldn't even touch... In this whole thread I have only seen guesses and nothing related to the real issue so I added a "redirection" towards a more fruitful one.
                      – elico
                      Jul 11 at 17:02











                      0














                      On MacOS: 10.11.6



                      Step-1: Go to /Users//.jenkins



                      Step-2: Open the file: hudson.model.UpdateCenter.xml



                      Step-3: CHange the value of "default" from "https://xxx" to "http://xxx"






                      share|improve this answer


























                        0














                        On MacOS: 10.11.6



                        Step-1: Go to /Users//.jenkins



                        Step-2: Open the file: hudson.model.UpdateCenter.xml



                        Step-3: CHange the value of "default" from "https://xxx" to "http://xxx"






                        share|improve this answer
























                          0












                          0








                          0






                          On MacOS: 10.11.6



                          Step-1: Go to /Users//.jenkins



                          Step-2: Open the file: hudson.model.UpdateCenter.xml



                          Step-3: CHange the value of "default" from "https://xxx" to "http://xxx"






                          share|improve this answer












                          On MacOS: 10.11.6



                          Step-1: Go to /Users//.jenkins



                          Step-2: Open the file: hudson.model.UpdateCenter.xml



                          Step-3: CHange the value of "default" from "https://xxx" to "http://xxx"







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Jul 25 at 19:20









                          ArunDhwaj IIITH

                          3,21811311




                          3,21811311























                              0














                              I make no claims about this, especially Java related (I personally cannot stand the language), but on my Ubuntu 18.04 L/T, I needed to stand-up a standalone Jenkins instance; So I installed both the Java on which Jenkins appears to be dependent and Jenkins itself



                              sudo apt install openjdk-8-jdk jenkins


                              Then I updated the Jenkins defaults



                              sudo gvim /etc/default/jenkins


                              ... inserting the following at the top of the file - only because editing /etc/init.d/jenkins appeared to serve no purpose as it had no effect whatsoever ...



                              JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/
                              PATH=$JAVA_HOME:$PATH


                              Finally, save & quit ... then attempt Jenkins restart



                              sudo service jenkins restart


                              HTH - it certainly worked for me :-)






                              share|improve this answer


























                                0














                                I make no claims about this, especially Java related (I personally cannot stand the language), but on my Ubuntu 18.04 L/T, I needed to stand-up a standalone Jenkins instance; So I installed both the Java on which Jenkins appears to be dependent and Jenkins itself



                                sudo apt install openjdk-8-jdk jenkins


                                Then I updated the Jenkins defaults



                                sudo gvim /etc/default/jenkins


                                ... inserting the following at the top of the file - only because editing /etc/init.d/jenkins appeared to serve no purpose as it had no effect whatsoever ...



                                JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/
                                PATH=$JAVA_HOME:$PATH


                                Finally, save & quit ... then attempt Jenkins restart



                                sudo service jenkins restart


                                HTH - it certainly worked for me :-)






                                share|improve this answer
























                                  0












                                  0








                                  0






                                  I make no claims about this, especially Java related (I personally cannot stand the language), but on my Ubuntu 18.04 L/T, I needed to stand-up a standalone Jenkins instance; So I installed both the Java on which Jenkins appears to be dependent and Jenkins itself



                                  sudo apt install openjdk-8-jdk jenkins


                                  Then I updated the Jenkins defaults



                                  sudo gvim /etc/default/jenkins


                                  ... inserting the following at the top of the file - only because editing /etc/init.d/jenkins appeared to serve no purpose as it had no effect whatsoever ...



                                  JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/
                                  PATH=$JAVA_HOME:$PATH


                                  Finally, save & quit ... then attempt Jenkins restart



                                  sudo service jenkins restart


                                  HTH - it certainly worked for me :-)






                                  share|improve this answer












                                  I make no claims about this, especially Java related (I personally cannot stand the language), but on my Ubuntu 18.04 L/T, I needed to stand-up a standalone Jenkins instance; So I installed both the Java on which Jenkins appears to be dependent and Jenkins itself



                                  sudo apt install openjdk-8-jdk jenkins


                                  Then I updated the Jenkins defaults



                                  sudo gvim /etc/default/jenkins


                                  ... inserting the following at the top of the file - only because editing /etc/init.d/jenkins appeared to serve no purpose as it had no effect whatsoever ...



                                  JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/
                                  PATH=$JAVA_HOME:$PATH


                                  Finally, save & quit ... then attempt Jenkins restart



                                  sudo service jenkins restart


                                  HTH - it certainly worked for me :-)







                                  share|improve this answer












                                  share|improve this answer



                                  share|improve this answer










                                  answered Nov 11 at 17:17









                                  pointo1d

                                  1




                                  1























                                      0














                                      There is something wrong with the internet connection of update center.I have met the same situation with Jenkins installed on macOS.



                                      You can try to modify the hudson.model.UpdateCenter.xml file.



                                      Jenkins installed with .pkg package on macOS,the file path is:
                                      /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml



                                      Jenkins installed by Homebrew on macOS,the file path is:
                                      /Users/{username}/.jenkins/hudson.model.UpdateCenter.xml



                                      Open the file:



                                      <?xml version='1.1' encoding='UTF-8'?>
                                      <sites>
                                      <site>
                                      <id>default</id>
                                      <url>https://updates.jenkins.io/update-center.json</url>
                                      </site>
                                      </sites>


                                      You can try to change https://updates.jenkins.io/update-center.json to:



                                      http://updates.jenkins.io/update-center.json


                                      or



                                      // If you are in China or near China area,https and http are both OK.
                                      https://mirrors.tuna.tsinghua.edu.cn/jenkins/updates/current/update-center.json


                                      And then you can restart Jenkins by:



                                      //loading the URL to restart Jenkins.
                                      http://localhost:8080/restart


                                      or



                                      // Use Homebrew command to restart Jenkins if you installed Jenkins LTS version by Homebrew.  
                                      brew services restart jenkins-lts





                                      share|improve this answer


























                                        0














                                        There is something wrong with the internet connection of update center.I have met the same situation with Jenkins installed on macOS.



                                        You can try to modify the hudson.model.UpdateCenter.xml file.



                                        Jenkins installed with .pkg package on macOS,the file path is:
                                        /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml



                                        Jenkins installed by Homebrew on macOS,the file path is:
                                        /Users/{username}/.jenkins/hudson.model.UpdateCenter.xml



                                        Open the file:



                                        <?xml version='1.1' encoding='UTF-8'?>
                                        <sites>
                                        <site>
                                        <id>default</id>
                                        <url>https://updates.jenkins.io/update-center.json</url>
                                        </site>
                                        </sites>


                                        You can try to change https://updates.jenkins.io/update-center.json to:



                                        http://updates.jenkins.io/update-center.json


                                        or



                                        // If you are in China or near China area,https and http are both OK.
                                        https://mirrors.tuna.tsinghua.edu.cn/jenkins/updates/current/update-center.json


                                        And then you can restart Jenkins by:



                                        //loading the URL to restart Jenkins.
                                        http://localhost:8080/restart


                                        or



                                        // Use Homebrew command to restart Jenkins if you installed Jenkins LTS version by Homebrew.  
                                        brew services restart jenkins-lts





                                        share|improve this answer
























                                          0












                                          0








                                          0






                                          There is something wrong with the internet connection of update center.I have met the same situation with Jenkins installed on macOS.



                                          You can try to modify the hudson.model.UpdateCenter.xml file.



                                          Jenkins installed with .pkg package on macOS,the file path is:
                                          /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml



                                          Jenkins installed by Homebrew on macOS,the file path is:
                                          /Users/{username}/.jenkins/hudson.model.UpdateCenter.xml



                                          Open the file:



                                          <?xml version='1.1' encoding='UTF-8'?>
                                          <sites>
                                          <site>
                                          <id>default</id>
                                          <url>https://updates.jenkins.io/update-center.json</url>
                                          </site>
                                          </sites>


                                          You can try to change https://updates.jenkins.io/update-center.json to:



                                          http://updates.jenkins.io/update-center.json


                                          or



                                          // If you are in China or near China area,https and http are both OK.
                                          https://mirrors.tuna.tsinghua.edu.cn/jenkins/updates/current/update-center.json


                                          And then you can restart Jenkins by:



                                          //loading the URL to restart Jenkins.
                                          http://localhost:8080/restart


                                          or



                                          // Use Homebrew command to restart Jenkins if you installed Jenkins LTS version by Homebrew.  
                                          brew services restart jenkins-lts





                                          share|improve this answer












                                          There is something wrong with the internet connection of update center.I have met the same situation with Jenkins installed on macOS.



                                          You can try to modify the hudson.model.UpdateCenter.xml file.



                                          Jenkins installed with .pkg package on macOS,the file path is:
                                          /Users/Shared/Jenkins/Home/hudson.model.UpdateCenter.xml



                                          Jenkins installed by Homebrew on macOS,the file path is:
                                          /Users/{username}/.jenkins/hudson.model.UpdateCenter.xml



                                          Open the file:



                                          <?xml version='1.1' encoding='UTF-8'?>
                                          <sites>
                                          <site>
                                          <id>default</id>
                                          <url>https://updates.jenkins.io/update-center.json</url>
                                          </site>
                                          </sites>


                                          You can try to change https://updates.jenkins.io/update-center.json to:



                                          http://updates.jenkins.io/update-center.json


                                          or



                                          // If you are in China or near China area,https and http are both OK.
                                          https://mirrors.tuna.tsinghua.edu.cn/jenkins/updates/current/update-center.json


                                          And then you can restart Jenkins by:



                                          //loading the URL to restart Jenkins.
                                          http://localhost:8080/restart


                                          or



                                          // Use Homebrew command to restart Jenkins if you installed Jenkins LTS version by Homebrew.  
                                          brew services restart jenkins-lts






                                          share|improve this answer












                                          share|improve this answer



                                          share|improve this answer










                                          answered Nov 20 at 12:12









                                          ifeegoo

                                          3,91531427




                                          3,91531427























                                              0














                                              For Windows OS,
                                              Follow below steps

                                              1. Go to C:Users*your user name*.jenkins

                                              2. Open the file: hudson.model.UpdateCenter.xml

                                              3. Update the value of "url" from "https://xxx" to "http://xxx"






                                              share|improve this answer










                                              New contributor




                                              Mohammed Ashfaq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                              Check out our Code of Conduct.























                                                0














                                                For Windows OS,
                                                Follow below steps

                                                1. Go to C:Users*your user name*.jenkins

                                                2. Open the file: hudson.model.UpdateCenter.xml

                                                3. Update the value of "url" from "https://xxx" to "http://xxx"






                                                share|improve this answer










                                                New contributor




                                                Mohammed Ashfaq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                Check out our Code of Conduct.





















                                                  0












                                                  0








                                                  0






                                                  For Windows OS,
                                                  Follow below steps

                                                  1. Go to C:Users*your user name*.jenkins

                                                  2. Open the file: hudson.model.UpdateCenter.xml

                                                  3. Update the value of "url" from "https://xxx" to "http://xxx"






                                                  share|improve this answer










                                                  New contributor




                                                  Mohammed Ashfaq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                  Check out our Code of Conduct.









                                                  For Windows OS,
                                                  Follow below steps

                                                  1. Go to C:Users*your user name*.jenkins

                                                  2. Open the file: hudson.model.UpdateCenter.xml

                                                  3. Update the value of "url" from "https://xxx" to "http://xxx"







                                                  share|improve this answer










                                                  New contributor




                                                  Mohammed Ashfaq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                  Check out our Code of Conduct.









                                                  share|improve this answer



                                                  share|improve this answer








                                                  edited Dec 18 at 7:01









                                                  Yogesh Patel

                                                  5392722




                                                  5392722






                                                  New contributor




                                                  Mohammed Ashfaq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                  Check out our Code of Conduct.









                                                  answered Dec 18 at 5:46









                                                  Mohammed Ashfaq

                                                  1




                                                  1




                                                  New contributor




                                                  Mohammed Ashfaq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                  Check out our Code of Conduct.





                                                  New contributor





                                                  Mohammed Ashfaq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                  Check out our Code of Conduct.






                                                  Mohammed Ashfaq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                  Check out our Code of Conduct.























                                                      -1














                                                      Enter this before running Jenkins.



                                                      # iptalbes -F


                                                      It may be because of the firewall.






                                                      share|improve this answer


























                                                        -1














                                                        Enter this before running Jenkins.



                                                        # iptalbes -F


                                                        It may be because of the firewall.






                                                        share|improve this answer
























                                                          -1












                                                          -1








                                                          -1






                                                          Enter this before running Jenkins.



                                                          # iptalbes -F


                                                          It may be because of the firewall.






                                                          share|improve this answer












                                                          Enter this before running Jenkins.



                                                          # iptalbes -F


                                                          It may be because of the firewall.







                                                          share|improve this answer












                                                          share|improve this answer



                                                          share|improve this answer










                                                          answered Jul 2 at 6:25









                                                          dani_KR

                                                          72




                                                          72























                                                              -1














                                                              jenkins_enable="YES"
                                                              jenkins_home="/usr/local/jenkins"
                                                              jenkins_user="jenkins"
                                                              jenkins_args="--webroot=${jenkins_home}/war --httpListenAddress=*.*.*.* --httpPort=8180"

                                                              #jenkins_java_opts="-Djavax.net.ssl.trustStore=/usr/local/jenkins/cacerts -Djava.net.preferIPv6Addresses=true"

                                                              #jenkins_java_opts="-Djavax.net.ssl.trustStore=/usr/local/jenkins/cacerts -Djava.net.preferIPv4Addresses=true"





                                                              share|improve this answer























                                                              • What about a bit of explanation!
                                                                – TheStoryCoder
                                                                Nov 30 at 10:54
















                                                              -1














                                                              jenkins_enable="YES"
                                                              jenkins_home="/usr/local/jenkins"
                                                              jenkins_user="jenkins"
                                                              jenkins_args="--webroot=${jenkins_home}/war --httpListenAddress=*.*.*.* --httpPort=8180"

                                                              #jenkins_java_opts="-Djavax.net.ssl.trustStore=/usr/local/jenkins/cacerts -Djava.net.preferIPv6Addresses=true"

                                                              #jenkins_java_opts="-Djavax.net.ssl.trustStore=/usr/local/jenkins/cacerts -Djava.net.preferIPv4Addresses=true"





                                                              share|improve this answer























                                                              • What about a bit of explanation!
                                                                – TheStoryCoder
                                                                Nov 30 at 10:54














                                                              -1












                                                              -1








                                                              -1






                                                              jenkins_enable="YES"
                                                              jenkins_home="/usr/local/jenkins"
                                                              jenkins_user="jenkins"
                                                              jenkins_args="--webroot=${jenkins_home}/war --httpListenAddress=*.*.*.* --httpPort=8180"

                                                              #jenkins_java_opts="-Djavax.net.ssl.trustStore=/usr/local/jenkins/cacerts -Djava.net.preferIPv6Addresses=true"

                                                              #jenkins_java_opts="-Djavax.net.ssl.trustStore=/usr/local/jenkins/cacerts -Djava.net.preferIPv4Addresses=true"





                                                              share|improve this answer














                                                              jenkins_enable="YES"
                                                              jenkins_home="/usr/local/jenkins"
                                                              jenkins_user="jenkins"
                                                              jenkins_args="--webroot=${jenkins_home}/war --httpListenAddress=*.*.*.* --httpPort=8180"

                                                              #jenkins_java_opts="-Djavax.net.ssl.trustStore=/usr/local/jenkins/cacerts -Djava.net.preferIPv6Addresses=true"

                                                              #jenkins_java_opts="-Djavax.net.ssl.trustStore=/usr/local/jenkins/cacerts -Djava.net.preferIPv4Addresses=true"






                                                              share|improve this answer














                                                              share|improve this answer



                                                              share|improve this answer








                                                              edited Oct 23 at 7:14









                                                              Pang

                                                              6,8601563101




                                                              6,8601563101










                                                              answered Oct 23 at 7:05









                                                              user10540906

                                                              1




                                                              1












                                                              • What about a bit of explanation!
                                                                – TheStoryCoder
                                                                Nov 30 at 10:54


















                                                              • What about a bit of explanation!
                                                                – TheStoryCoder
                                                                Nov 30 at 10:54
















                                                              What about a bit of explanation!
                                                              – TheStoryCoder
                                                              Nov 30 at 10:54




                                                              What about a bit of explanation!
                                                              – TheStoryCoder
                                                              Nov 30 at 10:54


















                                                              draft saved

                                                              draft discarded




















































                                                              Thanks for contributing an answer to Stack Overflow!


                                                              • Please be sure to answer the question. Provide details and share your research!

                                                              But avoid



                                                              • Asking for help, clarification, or responding to other answers.

                                                              • Making statements based on opinion; back them up with references or personal experience.


                                                              To learn more, see our tips on writing great answers.





                                                              Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                                                              Please pay close attention to the following guidance:


                                                              • Please be sure to answer the question. Provide details and share your research!

                                                              But avoid



                                                              • Asking for help, clarification, or responding to other answers.

                                                              • Making statements based on opinion; back them up with references or personal experience.


                                                              To learn more, see our tips on writing great answers.




                                                              draft saved


                                                              draft discarded














                                                              StackExchange.ready(
                                                              function () {
                                                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f42408703%2fwhy-does-jenkins-say-this-jenkins-instance-appears-to-be-offline%23new-answer', 'question_page');
                                                              }
                                                              );

                                                              Post as a guest















                                                              Required, but never shown





















































                                                              Required, but never shown














                                                              Required, but never shown












                                                              Required, but never shown







                                                              Required, but never shown

































                                                              Required, but never shown














                                                              Required, but never shown












                                                              Required, but never shown







                                                              Required, but never shown







                                                              Popular posts from this blog

                                                              Ottavio Pratesi

                                                              Tricia Helfer

                                                              15 giugno