jenkins behind nginx in kubernetes

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I have a jenkins server behind a Kubernetes (AWS ELB - NGINX proxy ). When I try to trigger a remote job using curl it fails:



# curl -X POST -H "$CRUMB" "https://jenkins:add91b3fefefefefef@jenkins.subdomain.domain.io/job/Excercise1/buildWithParameters?token=8buX7dddskddf&EMAIL=sfff@test.com&USER=muj"
curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.






share|improve this question

























    up vote
    0
    down vote

    favorite












    I have a jenkins server behind a Kubernetes (AWS ELB - NGINX proxy ). When I try to trigger a remote job using curl it fails:



    # curl -X POST -H "$CRUMB" "https://jenkins:add91b3fefefefefef@jenkins.subdomain.domain.io/job/Excercise1/buildWithParameters?token=8buX7dddskddf&EMAIL=sfff@test.com&USER=muj"
    curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
    More details here: http://curl.haxx.se/docs/sslcerts.html

    curl performs SSL certificate verification by default, using a "bundle"
    of Certificate Authority (CA) public keys (CA certs). If the default
    bundle file isn't adequate, you can specify an alternate file
    using the --cacert option.
    If this HTTPS server uses a certificate signed by a CA represented in
    the bundle, the certificate verification probably failed due to a
    problem with the certificate (it might be expired, or the name might
    not match the domain name in the URL).
    If you'd like to turn off curl's verification of the certificate, use
    the -k (or --insecure) option.






    share|improve this question























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have a jenkins server behind a Kubernetes (AWS ELB - NGINX proxy ). When I try to trigger a remote job using curl it fails:



      # curl -X POST -H "$CRUMB" "https://jenkins:add91b3fefefefefef@jenkins.subdomain.domain.io/job/Excercise1/buildWithParameters?token=8buX7dddskddf&EMAIL=sfff@test.com&USER=muj"
      curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
      More details here: http://curl.haxx.se/docs/sslcerts.html

      curl performs SSL certificate verification by default, using a "bundle"
      of Certificate Authority (CA) public keys (CA certs). If the default
      bundle file isn't adequate, you can specify an alternate file
      using the --cacert option.
      If this HTTPS server uses a certificate signed by a CA represented in
      the bundle, the certificate verification probably failed due to a
      problem with the certificate (it might be expired, or the name might
      not match the domain name in the URL).
      If you'd like to turn off curl's verification of the certificate, use
      the -k (or --insecure) option.






      share|improve this question













      I have a jenkins server behind a Kubernetes (AWS ELB - NGINX proxy ). When I try to trigger a remote job using curl it fails:



      # curl -X POST -H "$CRUMB" "https://jenkins:add91b3fefefefefef@jenkins.subdomain.domain.io/job/Excercise1/buildWithParameters?token=8buX7dddskddf&EMAIL=sfff@test.com&USER=muj"
      curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
      More details here: http://curl.haxx.se/docs/sslcerts.html

      curl performs SSL certificate verification by default, using a "bundle"
      of Certificate Authority (CA) public keys (CA certs). If the default
      bundle file isn't adequate, you can specify an alternate file
      using the --cacert option.
      If this HTTPS server uses a certificate signed by a CA represented in
      the bundle, the certificate verification probably failed due to a
      problem with the certificate (it might be expired, or the name might
      not match the domain name in the URL).
      If you'd like to turn off curl's verification of the certificate, use
      the -k (or --insecure) option.








      share|improve this question












      share|improve this question




      share|improve this question








      edited Jun 21 at 6:58









      Kusalananda

      101k13199312




      101k13199312









      asked Jun 21 at 6:56









      Mohd

      146114




      146114




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          This seems like SSL certificate issue, Try using -k option with curl to skip ssl verification



          # curl -X POST -k -H "$CRUMB" "https://jenkins:add91b3fefefefefef@jenkins.subdomain.domain.io/job/Excercise1/buildWithParameters?token=8buX7dddskddf&EMAIL=sfff@test.com&USER=muj"





          share|improve this answer





















          • im getting this now <html> <head><title>308 Permanent Redirect</title></head> <body bgcolor="white"> <center><h1>308 Permanent Redirect</h1></center> <hr><center>nginx/1.13.12</center> </body> </html>
            – Mohd
            Jun 21 at 7:09











          • The HyperText Transfer Protocol (HTTP) 308 Permanent Redirect redirect status response code indicates that the resource requested has been definitively moved to the URL given by the Location headers. Try using -ivvv to print Headers as well and found out where the resource have been now moved to
            – Arushix
            Jun 21 at 7:13











          • its not giving any thing specific,, see basically my jenknis is running in a kubernetes pod behind AWS ELB and Nginx Proxy,, although i can access jenknis thru its url globally,,only triggering job is not happening!
            – Mohd
            Jun 21 at 7:23










          • resolved it with -L option
            – Mohd
            Jun 21 at 10:30










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          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',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );








           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f451030%2fjenkins-behind-nginx-in-kubernetes%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          1
          down vote













          This seems like SSL certificate issue, Try using -k option with curl to skip ssl verification



          # curl -X POST -k -H "$CRUMB" "https://jenkins:add91b3fefefefefef@jenkins.subdomain.domain.io/job/Excercise1/buildWithParameters?token=8buX7dddskddf&EMAIL=sfff@test.com&USER=muj"





          share|improve this answer





















          • im getting this now <html> <head><title>308 Permanent Redirect</title></head> <body bgcolor="white"> <center><h1>308 Permanent Redirect</h1></center> <hr><center>nginx/1.13.12</center> </body> </html>
            – Mohd
            Jun 21 at 7:09











          • The HyperText Transfer Protocol (HTTP) 308 Permanent Redirect redirect status response code indicates that the resource requested has been definitively moved to the URL given by the Location headers. Try using -ivvv to print Headers as well and found out where the resource have been now moved to
            – Arushix
            Jun 21 at 7:13











          • its not giving any thing specific,, see basically my jenknis is running in a kubernetes pod behind AWS ELB and Nginx Proxy,, although i can access jenknis thru its url globally,,only triggering job is not happening!
            – Mohd
            Jun 21 at 7:23










          • resolved it with -L option
            – Mohd
            Jun 21 at 10:30














          up vote
          1
          down vote













          This seems like SSL certificate issue, Try using -k option with curl to skip ssl verification



          # curl -X POST -k -H "$CRUMB" "https://jenkins:add91b3fefefefefef@jenkins.subdomain.domain.io/job/Excercise1/buildWithParameters?token=8buX7dddskddf&EMAIL=sfff@test.com&USER=muj"





          share|improve this answer





















          • im getting this now <html> <head><title>308 Permanent Redirect</title></head> <body bgcolor="white"> <center><h1>308 Permanent Redirect</h1></center> <hr><center>nginx/1.13.12</center> </body> </html>
            – Mohd
            Jun 21 at 7:09











          • The HyperText Transfer Protocol (HTTP) 308 Permanent Redirect redirect status response code indicates that the resource requested has been definitively moved to the URL given by the Location headers. Try using -ivvv to print Headers as well and found out where the resource have been now moved to
            – Arushix
            Jun 21 at 7:13











          • its not giving any thing specific,, see basically my jenknis is running in a kubernetes pod behind AWS ELB and Nginx Proxy,, although i can access jenknis thru its url globally,,only triggering job is not happening!
            – Mohd
            Jun 21 at 7:23










          • resolved it with -L option
            – Mohd
            Jun 21 at 10:30












          up vote
          1
          down vote










          up vote
          1
          down vote









          This seems like SSL certificate issue, Try using -k option with curl to skip ssl verification



          # curl -X POST -k -H "$CRUMB" "https://jenkins:add91b3fefefefefef@jenkins.subdomain.domain.io/job/Excercise1/buildWithParameters?token=8buX7dddskddf&EMAIL=sfff@test.com&USER=muj"





          share|improve this answer













          This seems like SSL certificate issue, Try using -k option with curl to skip ssl verification



          # curl -X POST -k -H "$CRUMB" "https://jenkins:add91b3fefefefefef@jenkins.subdomain.domain.io/job/Excercise1/buildWithParameters?token=8buX7dddskddf&EMAIL=sfff@test.com&USER=muj"






          share|improve this answer













          share|improve this answer



          share|improve this answer











          answered Jun 21 at 7:04









          Arushix

          9968




          9968











          • im getting this now <html> <head><title>308 Permanent Redirect</title></head> <body bgcolor="white"> <center><h1>308 Permanent Redirect</h1></center> <hr><center>nginx/1.13.12</center> </body> </html>
            – Mohd
            Jun 21 at 7:09











          • The HyperText Transfer Protocol (HTTP) 308 Permanent Redirect redirect status response code indicates that the resource requested has been definitively moved to the URL given by the Location headers. Try using -ivvv to print Headers as well and found out where the resource have been now moved to
            – Arushix
            Jun 21 at 7:13











          • its not giving any thing specific,, see basically my jenknis is running in a kubernetes pod behind AWS ELB and Nginx Proxy,, although i can access jenknis thru its url globally,,only triggering job is not happening!
            – Mohd
            Jun 21 at 7:23










          • resolved it with -L option
            – Mohd
            Jun 21 at 10:30
















          • im getting this now <html> <head><title>308 Permanent Redirect</title></head> <body bgcolor="white"> <center><h1>308 Permanent Redirect</h1></center> <hr><center>nginx/1.13.12</center> </body> </html>
            – Mohd
            Jun 21 at 7:09











          • The HyperText Transfer Protocol (HTTP) 308 Permanent Redirect redirect status response code indicates that the resource requested has been definitively moved to the URL given by the Location headers. Try using -ivvv to print Headers as well and found out where the resource have been now moved to
            – Arushix
            Jun 21 at 7:13











          • its not giving any thing specific,, see basically my jenknis is running in a kubernetes pod behind AWS ELB and Nginx Proxy,, although i can access jenknis thru its url globally,,only triggering job is not happening!
            – Mohd
            Jun 21 at 7:23










          • resolved it with -L option
            – Mohd
            Jun 21 at 10:30















          im getting this now <html> <head><title>308 Permanent Redirect</title></head> <body bgcolor="white"> <center><h1>308 Permanent Redirect</h1></center> <hr><center>nginx/1.13.12</center> </body> </html>
          – Mohd
          Jun 21 at 7:09





          im getting this now <html> <head><title>308 Permanent Redirect</title></head> <body bgcolor="white"> <center><h1>308 Permanent Redirect</h1></center> <hr><center>nginx/1.13.12</center> </body> </html>
          – Mohd
          Jun 21 at 7:09













          The HyperText Transfer Protocol (HTTP) 308 Permanent Redirect redirect status response code indicates that the resource requested has been definitively moved to the URL given by the Location headers. Try using -ivvv to print Headers as well and found out where the resource have been now moved to
          – Arushix
          Jun 21 at 7:13





          The HyperText Transfer Protocol (HTTP) 308 Permanent Redirect redirect status response code indicates that the resource requested has been definitively moved to the URL given by the Location headers. Try using -ivvv to print Headers as well and found out where the resource have been now moved to
          – Arushix
          Jun 21 at 7:13













          its not giving any thing specific,, see basically my jenknis is running in a kubernetes pod behind AWS ELB and Nginx Proxy,, although i can access jenknis thru its url globally,,only triggering job is not happening!
          – Mohd
          Jun 21 at 7:23




          its not giving any thing specific,, see basically my jenknis is running in a kubernetes pod behind AWS ELB and Nginx Proxy,, although i can access jenknis thru its url globally,,only triggering job is not happening!
          – Mohd
          Jun 21 at 7:23












          resolved it with -L option
          – Mohd
          Jun 21 at 10:30




          resolved it with -L option
          – Mohd
          Jun 21 at 10:30












           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f451030%2fjenkins-behind-nginx-in-kubernetes%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay