You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Greetings,
I am working on setting up SSL reverse proxy for bamboo according to this article: https://confluence.atlassian.com/bamkb/securing-bamboo-behind-nginx-using-ssl-829075298.html. For some reason, bamboo continues to attempt to redirect to port 8085 and does not respect the context path /bamboo.
After restart, when attempting to access the site behind nginx, protected w/ SSL, Bamboo is redirecting me back to port 8085 without the context path, which results in error.
Any guidance from the community is appreciated :)
Thanks,
Austin
Hi!
1. Please, verify the base url.
2. Double check configs.
3. Check using private mode of your browser
Thanks for the response!
I certainly have done all of the above. All of the other atlassian apps are working GREAT behind the same proxy. Bamboo is the last and final one to get going ;)
The location directive in nginx near-matches the rest of the toolset's directives. I modified the server.xml in the connector directive and added the path in the context directive. Followed the instructions to the exact letter.
I am very lost here, unless there is a need to change something within the bamboo UI itself, there is no reason for the port to be redirecting to 8085 anymore according to the configurations...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is certainly something inside bamboo. The nginx logs are showing bamboo issuing the redirect...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeap - that was it.. the good ole baseURL needed to be updated under general configuration. Will submit the request on the article I followed.
thanks for the response. hope this helps someone else w/ the same issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's great as you fixed you issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.