All Next-Gen Connectors are black

Speckle Help
, , ,
1

I’m trying to get my Next-Gen connectors to work but they are all black (Rhino, Revit, Blender).

I think it’s due to our company strict firewall. (Tried to run on PC with legacy connectors and manual account setup without succes and also tried fresh company PC with only next-gen without succes)

For testing purposes we tried to allow through:

  • Desktop.Services
  • Rhino itself
  • Revit itself (also tried to disable other addons as this was issue at some time → some dependency conflicts)
  • Blender itself

but with no success, all connectors are just black.

Also we have our own company self-hosted speckle-server so it would be great if there could be option in which the connectors could run offline - resp. in our local network .. is this possible?

Thank you for any info

2

Currently, there is no solution for self-hosting the UI for new connectors.

Could you please try whitelisting the following URL: https://boisterous-douhua-e3cefb.netlify.app/ in your IT setup?

3

So for self-hosting we need to stay at older version of server and connectors? (By any chance do you know number of last server version working with V2 connectors? )

Whitelisting didn’t resolve the issue for us.

4

Which version of v2 connectors are you using?
v2 is not so picky about the server version, I would expect any reasonably recent version of the server to work, including the very latest versions.

5

With:
Revit connector 2.23.2
Server 2.25.4

I’m getting

image
image922×375 9.22 KB

For the V3 connector I’m getting

[ERR] An unhandled Exception occured
System.Exception: IBrowser instance is null. Browser has likely not finished initializing or is in the process of disposing.
6

Update:
Sorry, my fault I haven’t checked the server after the error - the V2 connectors do work … even though it throws the error it pushes the model to the server.

any ideas about the V3 error mentioned in previous post?

7

The “Version string portion was too short or too long” error is occurring because your server is reporting a version that is is not a valid semver.

You can see what the server does return by going to /graphql and testing this query

query ServerInfo {
  serverInfo {
    version
  }
}

You should see it return a semver like 2.25.4 or 2.25.5-alpha.409268
dev would also be considered a valid value.

an empty string would be considered invalid, as would anything else that isn’t a valid semver.

If you’re using our docker images, this should already be configured for you.