Details
-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
None
-
None
-
Severity 3 - Minor
-
Description
Summary
When connecting Bitbucket Server to Bamboo via a reverse proxy that serves multiple SSL certificates, Bitbucket Server fails to send Bamboo an event.
Steps to Reproduce
- Setup Bamboo behind a reverse proxy that serves multiple SSL certificates
- Connect BBS to this Bamboo instance via AppLinks
- After pushing a commit to BBS, the build never gets triggered
Expected Results
Build should be triggered normally.
Actual Results
The below exception is thrown in the atlassian-bitbucket.log file:
016-10-23 18:23:31,079 DEBUG [RemoteEvents CapabilitiesCacheLoader:thread-1] c.a.failurecache.CacheUpdateCallback Exception raised while refreshing cache entry with key 'xxxxxxxxx-b07f-3e00-a38b-xxxxxxx'; treating this as a null result: javax.net.ssl.SSLException: hostname in certificate didn't match: <bamboo.xxxxxxxx.com> != <some.other.server.xxxx.com>
Diagnosis
A specific DEBUG log has to be switched on Bitbucket Server Reference: Bitbucket Server debug logging |
To do that you can either:
- Perform a curl call on your instance
curl -u <username> -v -X PUT -d "" -H "Content-Type: application/json" http://<BB_ADDRESS>/rest/api/latest/logs/logger/com.atlassian.failurecache/debug
- Or edit <Bitbucket home directory>/shared/bitbucket.properties add the line logging.logger.com.atlassian.failurecache=DEBUG and restart your Bitbucket Server
Workaround
You will need to bypass the proxy when possible. Refer to How to create an unproxied application link
Attachments
Issue Links
- relates to
-
JRASERVER-64059 Workflow triggers not working when behind a reverse proxy that serves multiple SSL certificates
- Gathering Impact