search

microsoft / vsts-extension-retrospectives

An Azure DevOps extension for efficient retrospectives
MIT License
180 stars 80 forks source link

When opening presented with - "We are unable to connect to the live syncing service" #112

Open Brandon-FS opened 3 years ago

Brandon-FS commented 3 years ago

When creating or opening a new board we are presented with: We are unable to connect to the live syncing service. You can continue to create and edit items as usual, but changes will not be updated in real-time to or from other users. Is this an issue per organization or a more wide spread issue. I checked through the issues however couldn't see anything active open for this at the moment but I have noticed some feedback saying that some people also have this issue.

b-lat commented 3 years ago

One of my colleagues is having this same issue. For the rest of the team however it is working fine. When they add items to the retro board they appear an hour or so later.

I had a look at ChromeTools and the console has a load of signalR errors and a 404 when performing a post to https://retrospectivesbackend.service.signalr.net and 2 more 404 errors when performing a GET on Azure endpoints.

deleister commented 3 years ago

I have the same issue. At least 2 other people in the same org do not. I get this with the most current versions of both Google Chrome and MS Edge. My VSTS settings/permissions are the same the 2 people who do not see the error.

The system also takes a long to to connect to the Retro Board. It connects after 5-10 sec of throbbing, but always with the error msg.

HenPle commented 3 years ago

Same behavior here. Some users receive the error message, others don't. image

RichardNieuwland commented 3 years ago

same issue here. Is there a workaround/fix available ?

adrianeyre commented 3 years ago

We have the same issue with a team member experiencing the same issue. Is there a fix please? 🙂

Praveen-reddy49 commented 3 years ago

Same issue here. Isn't there a solution/fix yet ?

smoooms commented 2 years ago

Bug still there here. (else this extension is excellent !)

marc-lauper commented 2 years ago

I also encounter this one from time to time, would love to see it improved. Doesn't seems to be browser-specific, as far as I can tell.

Vertex-btb commented 1 year ago

I see that this issue is still marked as open (since 2021) and does not contain any insight into why the error is generated. A few users in my Azure DevOps org have been reporting the error this week.

@polatengin , since I notice that you have made recent commits to the repo, is this something that you can look into? ...or connect us with someone that can look into the error? Thank you.

RichardLockwoodTR commented 1 month ago

Disabling UBlock Origin for the page resolved the issue for me. I haven't checked the logs, presumably it was blocking a required endpoint.