Revit Connector authenticates but doesn't load any Projects

Help Developers
1

Hi There,

I deployed Speckle Community Edition successfully internally. So to take it out for a spin I created a project and downloaded the Revit Connector. The Connector authenticates with the server just fine but then when I click Publish it opens the Select Project box but no project can be selected… the blue progress bar shows up but nothing, same if I click Load Older Projects.

I get no logs under %APPDATA%\Roaming\Speckle. I also tried different versions of the plugin… same results.

Is there any other way to debug this? or anything else I should be trying?

2

Hi there! Do you have multiple accounts by any chance on your machine? I will cc @gokermu and @oguzhan - this is something i believe we fixed some two weeks ago in our internal testing (or it might be something new)

3

Yeah the machine is joined to Active Directory. usually users don’t have admin permissions to their machines so all software has to be provisioned or installed by an admin. This particular machine has two accounts: a local admin and the end user

4

Apologies, meant Speckle accounts! PS: Add screenshots!

5

Oh sorry… nope only one speckle account on that machine. I can only upload one screenshot because my account is new. So in that screenshot: There are no projects to select, loading older projects give you a quick progress bar but nothing loads, creating a problem also fails: it basically let me type a name for the project but the button is disabled

Screenshot 2025-04-28 at 12.28.47 PM
Screenshot 2025-04-28 at 12.28.47 PM2802×1626 313 KB

6

Just gave it a shot using our community edition server:

https://www.screenrecorder.me/player/FzSUHy90lbR7Elx

And all seems to work as advertised! Can you DM me your server URL’s so i can give it a shot there, to see if there’s anything specific wrong?

8

Hi Dimitrie I’m so sorry, I’m not sure if it’s because mine is a new account but I can’t find how to DM you… I see no option on your profile

9

DM sent, you should check your notifications! We’ll get to the bottom of this :slight_smile:

10

I’ll continue the conversation here! I don’t think it’s the server version. Something is appending an extra Access-Control-Allow-Origin value - probably your loadbalancer? @iainsproat was the one to ask that question (I’m not smart enough).

Basically, if i understand this correctly, CORS requests don’t go through.

How did you deploy your server?

12

Hey - let us know if you still have the problem. FWIW, there’s a new server release out (Release 2.24.0 · specklesystems/speckle-server · GitHub).

The wizard team suspects it’s more to do with config rather than the version, but who knows.

13

yeah we’re behind a reverse proxy. I’ll take a look at the configuration. Thanks for looking into that I didn’t think of checking the proxy

14

Hey Dimitrie do you mind taking a second look at this… I think I solved my CORS issues however projects are still not being loaded… inspecting the traffic the first call that fails is:

{"operationName":"CanCreatePersonalProject","variables":{},"query":"query CanCreatePersonalProject {\n  activeUser {\n    permissions {\n      canCreatePersonalProject {\n        authorized\n        code\n        message\n        payload\n        __typename\n      }\n      __typename\n    }\n    __typename\n  }\n}"}

with error:

{"errors":[{"message":"Cannot query field \"permissions\" on type \"User\". Did you mean \"versions\"?","locations":[{"line":3,"column":5}],"extensions":{"code":"GRAPHQL_VALIDATION_FAILED"}}]}

server is 2.23 - tried a bunch of Revit connectors from 3.x from the most recent to 3.1.2

15

Hi @JBlanco

Thanks for you patience.

We’ve been making lots of changes on both the server and connectors this week.

As such, it appears the latest version of connectors now require the latest server (2.24)

I suggest you update your server to the latest release. Please me know if you continue to see any errors

16

Thanks for the info, @Jedd. I’ve tried rolling back to older connector versions as well, but I still get the same errors. I’ll try the latest 2.24 server and report back but I’m not sure I understand why a new server release that I haven’t deployed yet will break compatibility with old connectors.

17

Good point, I’ll have to investigate a little more, I suspect the way we ship the web UI may explain why older connectors are still affected.

I’ll have a chat with the team next week, ideally we’d only make these sorts of breaking changes when they are absolutely critical.

Thank you for your patience.