Reverse proxy issue with IIS after upgrading to 2.479.1

Using Jenkins Ask a question
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?

3 Likes
2

I am having the same issue on 2.479.1

3

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.

4

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?

2 Likes
5

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

1 Like
6

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

2 Likes
7

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

8

It looks like JENKINS-73667 is the same issue

1 Like
9

Is this issue fixed in version 2.479.2?
I do not see anything about it in the changelog.

1 Like
10

I have the same same issue after I update from Jenkins 2.462.3 to Jenkins 2.479.2 LTS.
I am getting Redirect URI issue.

Jenkins changelog includes upgrading Jetty from 10.x to 12.x.
I guess, something in there is causing the issue.

AADSTS50011: The redirect URI ‘https://{your_jenkins_host}:8080/securityRealm/finishLogin’ specified in the request does not match the redirect URIs configured for the application ‘’. Make sure the redirect URI sent in the request matches one added to your application in the Azure portal. Navigate to Error AADSTS50011 the redirect URI does not match the redirect URIs configured for the application | Microsoft Learn to learn more about how to fix this.

I use IIS in Windows server.

Jenkins setup:

Jenkins: 2.462.3
OS: Windows Server 2022 - 10.0
Java: 17.0.7 - Eclipse Adoptium (OpenJDK 64-Bit Server VM)

Office-365-Connector:5.0.0
active-directory:2.38

11

The issue still persists on Jenkins 2.479.3 LTS.
Does anyone has any idea how to fix the Jetty update issue?
Thank you,

1 Like
12

I am on 2.504.3, with a new jenkins installation. I have eliminated all of the reverse proxy issues except, the url:8080 vs url. I am assuming this issue has NOT been fixed, even in 2.504.3? and I can safely ignore?

13

I upgraded to 2.504.3 and the issue still existed, so I did further testing and discovered IIS reverse proxy was using HTTP_FORWARDED (RFC 7239). So I replaced it with HTTP_X_FORWARDED_PROTO, HTTP_X_FORWARDED_PORT and HTTP_X_FORWARDED_HOST. Now it is working correctly.

I had to remove HTTP_FORWARDED as it still had problems when both types were set.

1 Like