As stated in the title.
Users are experiencing this intermittent 502 error, that comes and goes away.
I'm not sure on how to troubleshoot this, I was hoping the community may be able to recommend some things.
We have only started to hear about this since we went offline - I think something is trying to access the internet and timing out - however it is holding on to the client request while it waits for this timeout.
To expand more, we recently migrated our network to an offline network, meaning it cannot be reached via the internet. Could this be the source of these errors?
Anyway to pinpoint the culprit.
if it is not happening all the time it might be related to overload situations - probably due to high peak hours with users accessing the systems.
Are all of the three products behind a reverse proxy - probably the same? In other words, is the reverse proxy generating the 502 error?
If so, I would start looking into this first.
In case you have no proxy in front of the services I'd suggest to look into the logfiles first - one after the another and to compare if anything suspicious is recognizable by viewing them.
The network change should not be related to it when the error only happens sometimes - in case it would have caused the issue I suspect the error would be of permanent nature.
In any case here comes the link with the general troubleshooting documentation for Jira (but the high-level steps apply for Bamboo and Bitbucket as well):
Announced in this blog, this holiday season we’re celebrating all things CI/CD and between now and the end of 2019 we’ll be showcasing content, use cases, feature announcements and more. One featur...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events