BB Runner I am facing The connection observed an error and runner status it's shown unregistered

[Rajkumar]

In Command Line run the BB Runner Token it shows the Updating runner state to "ONLINE".
After we getting this error, BB Runner I am facing The connection observed an error and runner status it's shown unregistered.https://bitbucket.org/rajkumar-dev/runner-demo-repo/admin/addon/admin/pipelines/runners 

[Patrik S]

Hello @Rajkumar ,

Welcome to Atlassian Community!

We had an incident on December 7th related with a downstream outage in our underlying platform provider AWS that affected the Bitbucket pipeline builds, as you can see in our public status page :

• https://bitbucket.status.atlassian.com/incidents/k6pbf7mbxhdd

The issue you reported seems to be related to that incident, so would you please try to run your runner container again and let us know if you face the same error ? If yes, then we can troubleshoot further.

Thank you, @Rajkumar :)

Best regards,

Patrik S

[Rajkumar]

Hi @Patrik S ,

             I am tried bitbucket runner container  but facing same issue, Please fix that error, PFA SS.

https://bitbucket.org/rajkumar-dev/workspace/settings/addon/admin/pipelines/account-runners

Regards,

Rajkumar T.

[Patrik S]

Hello @Rajkumar ,

Thank you for trying again and sharing the results.

In this case, looking at the error message being thrown on the console, it looks like the runner is not being able to connect to the Bitbucket API. Just to give you a background, when a runner is started, it creates a long living websocket connection to listen for Pipelines events. Also, once self-hosted Runners is done executing specific commands/actions, Runners will then update Pipelines through Bitbucket REST API.

That being said, to confirm your firewall is not blocking the requests to Bitbucket API, could you please make sure all the IPs below are in the allowlist of your firewall ?

• https://ip-ranges.atlassian.com/

Let me know how it goes, and if you have any other questions.

Thanks @Rajkumar

Kinds regards,

Patrik S

[Dinesh Gundeboina]

hi @Patrik S Even I am getting the same error when trying to register my VM (hosted in Cloud) and hence we have referred 

• https://ip-ranges.atlassian.com/

 and added 13.35.248.0/24 in the firewall, but still same issue with api.atlassian.com. 

Can you please check once and let us know how to proceed further because the below doc contains more number of Ip ranges and we cannot add all those in the firewall as there is a limit in adding the firewall.

• https://ip-ranges.atlassian.com/
  
  

[Patrik S]

Hey @Dinesh Gundeboina ,

and welcome to the Community!

That error message usually indicates your firewall is blocking the runner from connecting to the Atlassian Cloud infrastructure.

Could you please ensure that all the below IP ranges are currently allowed in your company's firewall ?

• 104.192.136.0/21

• 185.166.140.0/22

• 13.200.41.128/25

• 13.35.248.0/24

• 13.227.180.0/24

• 13.227.213.0/24

[Dinesh Gundeboina]

Thanks Patrick. I will ask the firewall team to allow all the mentioned IP ranges. The first 3 set of IP ranges corresponds to Bitbucket.org and is there any specific criteria on how you have selected the last 3 set of IP ranges from the below.

• https://ip-ranges.atlassian.com/

Also is there any chance of these IP ranges getting changed in future ?

-Dinesh