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

IIS reverse proxy "It appears that your reverse proxy set up is broken." after Jenkins 2.473 upgrade

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core
    • None

      originally i followed Reverse proxy - IIS (jenkins.io) to set up reverse proxy and it was all working fine until I upgraded to Jenkins 2.473.

       

      from browser dev tools, I can see call is being made to 

      GET

      https://jenkins.mycompany.com/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testForReverseProxySetup/https%3A%2F%2Fjenkins.mycompany.com%2Fmanage%2F/ which returns 404

       

      If i open this url in browser tab, i see message Oops! message with 

       

      https://jenkins.mycompany.com:8080/manage vs. https://jenkins.mycompany.com/manage/

      This page may not exist, or you may not have permission to see it.

          [JENKINS-73667] IIS reverse proxy "It appears that your reverse proxy set up is broken." after Jenkins 2.473 upgrade

          Bharat Bhatia created issue -

          Mark Waite added a comment -

          Are you sure that your Jenkins URL is correctly configured as https://jenkins.mycompany.com/ ?

          My reverse proxy configuration is with nginx and uses a "/jenkins" suffix on the URL.

          Have you checked the instructions at https://www.jenkins.io/doc/book/system-administration/reverse-proxy-configuration-with-jenkins/reverse-proxy-configuration-iis/#experiencing-the-dreaded-it-appears-that-your-reverse-proxy-set-up-is-broken-error-for-yourself ?

          Mark Waite added a comment - Are you sure that your Jenkins URL is correctly configured as https://jenkins.mycompany.com/ ? My reverse proxy configuration is with nginx and uses a "/jenkins" suffix on the URL. Have you checked the instructions at https://www.jenkins.io/doc/book/system-administration/reverse-proxy-configuration-with-jenkins/reverse-proxy-configuration-iis/#experiencing-the-dreaded-it-appears-that-your-reverse-proxy-set-up-is-broken-error-for-yourself ?
          Bharat Bhatia made changes -
          Attachment New: image-2024-09-04-13-45-45-859.png [ 63231 ]

          Bharat Bhatia added a comment -

          markewaite yes, the url is configured correctly

           

          Also, i did followed the guide and it started recently since i upgraded

          Bharat Bhatia added a comment - markewaite yes, the url is configured correctly   Also, i did followed the guide and it started recently since i upgraded

          Bharat Bhatia added a comment -

          Also, just reverted back to 2.471 and warning goes away and reverse proxy is working as  expected with no changes on server or any rules.

          Bharat Bhatia added a comment - Also, just reverted back to 2.471 and warning goes away and reverse proxy is working as  expected with no changes on server or any rules.

          Bharat Bhatia added a comment -

          Any update on this as this is also causing Jenkins to redirect to port “8080” in url after clicking built button

          Bharat Bhatia added a comment - Any update on this as this is also causing Jenkins to redirect to port “8080” in url after clicking built button

          Mark Waite added a comment -

          I'm not aware of any case in the past where that message was anything other than a configuration error.  The fact that the configuration error is exposed on a Jenkins upgrade is interesting but not at all conclusive that the issue is a Jenkins bug.

          I don't run an IIS reverse proxy and I don't know many users that run an IIS reverse proxy.  Your alternatives include:

          • Switch to a more widely used reverse proxy (like nginx). Host the nginx reverse proxy on a Unix server and point it to the Jenkins controller on your Windows computer
          •  Stop using a reverse proxy

          I'm not willing to attempt to duplicate your configuration because I'm not interested in configuring an IIS reverse proxy. You're welcome to raise a question on https://community.jenkins.io in hopes that there are other users of IIS as a reverse proxy that are interested in helping.

          Mark Waite added a comment - I'm not aware of any case in the past where that message was anything other than a configuration error.  The fact that the configuration error is exposed on a Jenkins upgrade is interesting but not at all conclusive that the issue is a Jenkins bug. I don't run an IIS reverse proxy and I don't know many users that run an IIS reverse proxy.  Your alternatives include: Switch to a more widely used reverse proxy (like nginx). Host the nginx reverse proxy on a Unix server and point it to the Jenkins controller on your Windows computer  Stop using a reverse proxy I'm not willing to attempt to duplicate your configuration because I'm not interested in configuring an IIS reverse proxy. You're welcome to raise a question on https://community.jenkins.io in hopes that there are other users of IIS as a reverse proxy that are interested in helping.

          Bharat Bhatia added a comment -

          At least I found workaround for build with parameters redirect to port 8080 issue. Check "Reverse rewrite host in response headers" in iis for ARR settings if anyone else is having this issue

          Bharat Bhatia added a comment - At least I found workaround for build with parameters redirect to port 8080 issue. Check "Reverse rewrite host in response headers" in iis for ARR settings if anyone else is having this issue

          David added a comment -

          Just going to add my name to the list of 'rare IIS reverse proxy' users and we are also seeing this issue.

          Pre-upgrade to 2.479.2 we had no issues. Now we get this warning and the issues with redirects.

          Again we've had zero changes made to our functioning IIS reverse proxy.

          David added a comment - Just going to add my name to the list of 'rare IIS reverse proxy' users and we are also seeing this issue. Pre-upgrade to 2.479.2 we had no issues. Now we get this warning and the issues with redirects. Again we've had zero changes made to our functioning IIS reverse proxy.
          Mark Waite made changes -
          Summary Original: Message "It appears that your reverse proxy set up is broken." appears after Jenkins 2.473 upgrade New: IIS reverse proxy "It appears that your reverse proxy set up is broken." after Jenkins 2.473 upgrade

            Unassigned Unassigned
            xs2bharat Bharat Bhatia
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: