grahamb@sfu.ca

[Graham Ballantyne]

Any attempt to view the Manage Add-ons page in our Bamboo installation results in two errors:

- The Atlassian Marketplace server is not reachable...

- An unexpected error occurred. Please refer to the logs for more information.

My server does not require a proxy to connect to the internet, and I can ping marketplace.atlassian.com and curl https://marketplace.atlassian.com. I have cranked up all logging to debug and haven't found much useful information, with the exception of:

2013-01-16 16:29:02,711 DEBUG qtp380254118-135 DefaultI18nBean Error getting text for key: (stringKey)

2013-01-16 16:29:02,767 DEBUG qtp380254118-135 DefaultI18nBean Error getting text for key: (upm.plugin.license.error)

2013-01-16 16:29:02,805 DEBUG qtp380254118-135 DefaultI18nBean Error getting text for key: (upm.plugin.license.sen.unknown)

2013-01-16 16:29:02,875 DEBUG bambooAgentMessageListenerConnector-1 FingerprintMatchingMessageListenerContainer Consumer ActiveMQMessageConsumer { value=ID:atlassian.f5esx.sfu.ca-52246-1358381937624-3:1:1:1, started=true } of session PooledSession { ActiveMQSession {id=ID:atlassian.f5esx.sfu.ca-52246-1358381937624-3:1:1,started=true} } did not receive a message

2013-01-16 16:29:03,159 DEBUG qtp380254118-135 DefaultI18nBean Error getting text for key: (upm.plugin.error.failed.to.remove.request)

2013-01-16 16:29:03,327 DEBUG qtp380254118-135 DefaultI18nBean Error getting text for key: (upm.messages.install.success.finished.button)

2013-01-16 16:29:03,340 DEBUG qtp380254118-135 DefaultI18nBean Error getting text for key: (upm.messages.install.licensing.required.button)

2013-01-16 16:29:03,370 DEBUG qtp380254118-135 DefaultI18nBean Error getting text for key: (upm.messages.update.success.finished.button)

I have attached log output collected while loading the add-ons page.

Additionally, nothing shows up under the System Plugins section of the page. The System Information page shows numerous enabled plugins.

[Graham Ballantyne · Accepted solution]

It turns out that the base URL was set incorrectly; fixing that resolves the issue.

[Sultan Maiyaki]

Hi Graham,

Are you using the crowd SSO? If yes pls see this bug https://jira.atlassian.com/browse/BAM-12484 and apply the workaround suggested in this comment https://jira.atlassian.com/browse/BAM-12484?focusedCommentId=420114&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-420114

[Graham Ballantyne]

It turns out that the base URL was set incorrectly; fixing that resolves the issue.