Speckle Server: v2.26.8-alpha.1226 (Docker/Podman self-hosted on http://localhost:3000)
Client: Revit 2025 with Speckle Connector (User-Agent: Chrome/119.0.6045.159 Autodesk.Revit/2025) - latest version 3.13.1
Issue:
After fresh database initialization, the Revit 2025 connector fails to complete authentication against a custom server. The frontend shows “Could not resolve app”.
Server logs show the connector requests AuthorizableAppMetadata for app ID sdui, but this app is not in the server_apps table.
Pre-seeded apps include sca, sdas, sdm, but NOT sdui.
Question:
Should sdui be added to the default seed data in packages/server/modules/core/helpers/defaultApps.ts? Or is there a configuration we’re missing?
Part 2:
After manually adding the sdui entry similar to sdas, the authentication proceeds to allow the app registration, however on the redirect back to the Desktop client (port 29364) the process fails and the client redirects to the public connection failure page at Connector Auth - Failed to log in | Speckle. The Desktop client log shows an error: Speckle.Sdk.SpeckleException: “We don’t have a challenge at Speckle.Desktop.Services.Accounts.AccountUtility.CreateAccountFromAccessCode”
Could the team advise how to configure the Speckle server and Revit/Desktop client to authenticate on the latest versions in a fully self-hosted environment with no reliance on speckle.systems?
Seems still not working. Our server side auth flow gets all the way through approving the app registration and redirecting back to the desktop client, but when the desktop service tries to validate against localhost:3000 again it fails and redirects to the speckle.systems connector fail message. Should it be hitting http://localhost:3000 without a path? or the path isnt visible and it should be hitting 3001?
I still need to understand though how we can host in a fully isolated environment without reliance on dui.speckle.systems. It seems the connectors by default are going there first.
I copied the docker files and created my own ingress container files and it seems to be working. You can close this issue or keep open if you want to track the main issue with the ingress container.
I will open a separate issue re connectors relying on speckle.systems.
Is it (non-legacy) login supposed to work for self-hosted installations? We using the latest connectors, with Revit 2025, getting the ‘Could not resolve app’ message. Server is 2.27.1, sdui entry is not in server_apps in the database. I tried inserting it, but that seemed to break log in completely.
Self-hosted servers should use the legacy sign-in option right now. We will be aligning it, and you will need to update your server version to be able to log in with the default way.
Through this, we discovered that the login part of the connector is running as a Speckle hosted web site which was updated for all versions of the connector. For our use case it’s a bit worrying that such a critical part of the equation can suddenly shift underneath our feet. Will the login page be moved to the connector itself in the future, or should we look into hosting it and building our own connector with this path reconfigured if it’s a pain point?
