This message was deleted.
# generala
adamant-kite-43734
01/26/2024, 1:25 AMThis message was deleted.
c
creamy-pencil-82913
01/26/2024, 1:40 AMare you sure it’s the ALB sending the redirect, and not just a redirect that your browser has cached?
creamy-pencil-82913
01/26/2024, 1:41 AMTry clearing cache, or opening it in a new private/incognito window
c
clean-painting-58815
01/26/2024, 3:24 AMIt's not a redirect from the ALB. The call is making it through to the application and the redirect is happening there. If I call https://<rancher_pod_ip> it will redirect to https://<rancher_pod_ip>/dashboard/home and the dashboard shows up. So it's definitely not a redirect on the ALB. However, when I call the app through the ALB the same way, it shows up as a 404.
h
hundreds-ambulance-1957
03/07/2024, 12:32 AMWas this ever resolved? I swear I’m hitting a similar issue upgrade from
v2.6.13v2.7.10c
clean-painting-58815
03/07/2024, 12:46 AMFunny you should ask - we did resolve this but I hadn't had a chance to post. The problem was with the ALB ingress controller path rules. Somehow, a / got added to the implementationSpecific path when it should have been blank. Take a look at your ingress settings and see if there's a / there. If so, remove it and everything should start working again. YMMV - good luck!
h
hundreds-ambulance-1957
03/07/2024, 12:46 AMOmgggg I saw that in the helm generated manifest.
hundreds-ambulance-1957
03/07/2024, 12:47 AMI thought that wouldn’t matter but will see if removing that fixes my issues.
hundreds-ambulance-1957
03/07/2024, 12:53 AMWow that was incredible
hundreds-ambulance-1957
03/07/2024, 12:54 AMThank you so much! That did the trick.
hundreds-ambulance-1957
03/07/2024, 12:54 AMUsers are happy again 🙂
c
clean-painting-58815
03/07/2024, 12:54 AMwoop woop! glad it worked for you
🙌 1