Reverse proxy issue with IIS after upgrading to 2.479.1

Hi,

I’m using IIS that allows accessing Jenkins through https. I’ve double-checked all the steps in the instructions Reverse proxy - IIS

Before update (2.462.1) everything was working fine. After update I’m getting “It appears that your reverse proxy set up is broken.” and URLs are wrong in several places. For example, if I call jenkins through jenkinsapi:
“ValueError: Not a Queue URL: https://myserver:8081/queue/item/2567053/

test for reverse proxy setup is trying to compare

https://myserver:8081/manage vs. https://myserver/manage/

For some reason left part has https URL but at the same time HTTP port. Do I need to update some configuration in jenkins to make it work again after update?

1 Like

I am having the same issue on 2.479.1

Could it be linked to the fact we migrated to Jetty 12 with Jenkins 2.479.1?
Edit: no because @Nekto89 was talking about 2.462.1 which was still using Jetty 10.

I am having the same issue with Version 2.479.1. Just updated Jenkins and plugins with the Jenkins GUI, and after that it shows that the reverse proxy is broken. There has been no changes in the proxy setup in IIS.
Builds seem to work, and I can reach Jenkins with my HTTPS url. The only thing is that when I click “Build”, it takes me to a url within the project which it can not reach. so apparently there is a bug introduced. Help?

1 Like

Same issue here. We have since reverted to 2.462.3 to get it working again.

Everything works properly on 2.462.1. Upgrade to 2.479.1 breaks Jenkins in my setup. So it may be related to Jetty.

1 Like

Please open a JIRA ticket if it does not already exist.