Charts: jenkins stable/chart - reverse proxy broken behind ssl

[tnimni]

Describe the bug
A clear and concise description of what the bug is.

Reverse proxy is broken according to jenkins, chart installed on eks behind ALB which route all traffic from 443 to ngnix inside the cluster

Version of Helm and Kubernetes:
kubernetes 1.13
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}

Which chart:
jenkins/stable

What happened:
jenkins alert that reverse proxy is broken

What you expected to happen:
reverse proxy works as expected

How to reproduce it (as minimally and precisely as possible):
install ALB on aws, alb listen on port 443 with valid certificate and redirect traffic to cluster

cluster has ngnix installed and actch all *.Domain taffic and redirect to cluster services

Anything else we need to know:

[torstenwalter]

You can specify master.jenkinsUrl

https://github.com/helm/charts/blob/master/stable/jenkins/templates/config.yaml#L195

[torstenwalter]

@tnimni Did this solve your problem?

[t451772]

I am having this issue.
Kubernetes 1.13.5
My command was:
helm install --name jenkins --namespace jenkins stable/jenkins --set master.ingress.enabled=true --set master.ingress.hostName=fake.node.com --set master.serviceType=ClusterIP --set master.jenkinsUrl=http://fake.node.com
My result is jenkins alert that reverse proxy is broken. Possibly related the Jenkins python API doesn't work for the chart, but does work for a standalone deployment with ingress loadbalancer.

Did I miss something?

[torstenwalter]

@ts4z

• Which URL are you using when accessing Jenkins?
• Which URL is shows under Jenkins -> Manage Jenkins -> Jenkins Location -> Jenkins URL?
• Are both identical?

[t451772]

I am accessing Jenkins on a URL which looks a lot like http://fake.node.com
Under Jenkins -> Manage Jenkins -> Configure System -> Jenkins Location the url is http://fake.node.com/
They are different by a /. I will see if changing that matters

Update: That mattered, the proxy problem is gone when I removed the / under Jenkins location. I will assume any other problems are not related to the issue.
Thank you!

[tnimni]

hi all, sorry for the late respone
@torstenwalter i did specify the url and it didn't help it just keep saying it's broken
when i run the test with curl from command line from this page https://wiki.jenkins.io/display/JENKINS/Jenkins+says+my+reverse+proxy+setup+is+broken
it works fine, meaning it's not broken
i specified the url from the ui not from the chart
so i don't understand why it say it's broken from ui

[torstenwalter]

@tnimni Did you try the solution @t451772 pointed out?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale[bot]]

This issue is being automatically closed due to inactivity.