Unable to connect to the remote server

Speckle Help Help (Legacy V2)
1

Any updates on this issue? I’ve tried most of the solutions mentioned in other posts, nothing works. I’m using the latest connector (speckle.powerbi.installer-3.0.0-beta.74), latest Power BI (2.140.1577.0), my project is and was public, and the Power BI dashboard was working before, I tried updating it on Friday and I got the “Access to resource is forbidden” message. If it helps, while trying some of the fixes mentioned in other posts, I also got this message:

speckle1
speckle1764×191 7.8 KB

4

Hi @gergo ! When you said “I’ve pushed some more fixes”, do we need to download a new version of the connector?

1 Like
5

Nope, the fixes that Gergö mentioned on server side.

1 Like
6

Hello all,

I just removed all connectors and reinstalled them, removed custom connectors from the Power BI Desktop folder as I saw mentioned in another thread, also made sure to uninstall the previous Power BI v2 connector via the Speckle Manager, and I finally managed to connect to my projects. :sweat_smile:

Be aware that there are some small changes in the query, some of the columns are renamed (Object ID became Object IDs, speckle_type became Speckle Type) some do not exist anymore such as the Model URL and the URL Type.

7 Likes
7

Hi again! Halfway through the day I started getting this error again, although it was working earlier.

image
image558×142 5.5 KB

DataSource.Error: Unable to connect to the remote server
Details:
http://127.0.0.1:29364/download

Is something changing?

Should I wait and hopefully it will get solved?

Thanks!

2 Likes
8

@gergo any changes in the server side?

11

Hi @Anastasia,

Somehow the service we used is not responding on your end for a reason. It is hard to say without seeing it. I am happy to jump in a call to understand it better.

12

hi @oguzhan ,

Just downloaded the latest connector for power BI (3.0.0-beta.76) that came out about an hour ago and it seems the issue is solved.

I’ll let you know if the issue appears again!

1 Like
13

It is still suspicious that your service stopped working for a reason. Once you installed new version it triggered the service again and thats why it is solved I guess. If it happens again, let us know please.

Thanks