I get this in the log file when I try to connect to our test bamboo server: http://bamboo002.hq.viviport.com/:8085
2016-06-28 16:07:15,478 INFO [http-nio-8085-exec-12] [AccessLogFilter] 126.96.36.199 GET http://bamboo002.hq.viviport.com:8085/ 940816kb 2016-06-28 16:07:15,484 WARN [http-nio-8085-exec-12] [AuthorizationLoggerListener] Authorization failed: org.acegisecurity.AccessDeniedException: Access is denied; authenticated principal: org.acegisecurity.providers.anonymous.AnonymousAuthenticationToken@9055c2bc: Username: anonymousUser; Password: [PROTECTED]; Authenticated: true; Details: org.acegisecurity.ui.WebAuthenticationDetails@b364: RemoteIpAddress: 188.8.131.52; SessionId: B6BC99F149266F3F5C635F1274EEA79E; Granted Authorities: ROLE_ANONYMOUS; secure object: com.atlassian.bamboo.webwork.StarterAction@55e1aabb; configuration attributes: [WW_READ, GLOBAL_READ] 2016-06-28 16:07:15,495 INFO [http-nio-8085-exec-13] [AccessLogFilter] 184.108.40.206 GET http://bamboo002.hq.viviport.com:8085/userlogin!default.action?os_destination=%2Fstart.action 940226kb
I don't even get a login screen, but instead get:
bamboo002.hq.viviport.com refused to connect.
Since I get errors in the log file, I clearly have connected, albeit briefly, to the bamboo server.
I had started bamboo up yesterday and logged in with a local user account and installed a stash-destined plugin into bamboo, by mistake. The "upload" failed, as it should. Then I shut down the bamboo server.
Today, I started bamboo up again, but I cannot connect, and I believe nothing has changed in the world since yesterday.
I then proceeded to upgrade bamboo software from 5.9.1 to 220.127.116.11, hoping that would fix something. It didn't.
I have our test Bitbucket server on the same machine, and have no problem browsing from my laptop to http://bamboo002.hq.viviport.com:7990/
I have no idea what could be wrong. Is there something in the postgresql database that I need to change?
Is there a setting in the setenv.sh that needs to change.
I'll take any advice as I am at wit's end.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs