Speckle server is not allowing new registrations, nor is it indicating that there is some error from preventing it in doing so. This applies to both the web ui and Rhino/Grasshopper clients.
ERROR:
Failed to register user. System.Threading.Tasks.TaskCanceledException: A task was canceled.
Plugin version: 1.0.0.0
Server Build: latest
Transmit over http and not https, all ports and traffic is pingable and accessible – no contact issues.
Okay, and if you try via the online admin interface? A screenshot from the console would help; the .net error above is rather cryptic…
Might be that it actually created the account, but something else failed - did you try with a different email too?
From console (Chrome):
:3000/api/accounts?omit=logins:1 Failed to load resource: the server responded with a status of 401 (Unauthorized)
:3000/#/register:1 Unchecked runtime.lastError: The message port closed before a response was received.
:3000/api/accounts/register:1 Failed to load resource: net::ERR_EMPTY_RESPONSE
chunk-db6349ea.41ccfd07.js:1 Uncaught (in promise) TypeError: Cannot read property ‘data’ of undefined
at chunk-db6349ea.41ccfd07.js:1
:3000/#/register:1 Unchecked runtime.lastError: The message port closed before a response was received.
No visual indication in web ui that anything has failed … only the log.
Soooo it’s a bug in your server deployment. Can’t help there… Ideally, someone in your IT department could help?
Hang on now, are we absolutely sure that this is not client related? Could the client be somehow creating the server disconnection? The auth client that is?
from what i see in the logs:
2019-04-24 12:41:43 e[34mdebuge[39m: Mongoose default was disconnected
2019-04-24 12:41:43 e[34mdebuge[39m: connected to mongoose at mongodb://localhost:27017/speckle
2019-04-24 12:41:43 e[34mdebuge[39m: Mongoose default was disconnected
2019-04-24 12:41:43 e[34mdebuge[39m: Failed to connect to DB mongodb://localhost:27017/speckle on startup
2019-04-24 12:41:43 e[34mdebuge[39m: connected to mongoose at mongodb://localhost:27017/speckle
2019-04-24 12:41:43 e[34mdebuge[39m: Failed to connect to DB mongodb://localhost:27017/speckle on startup
2019-04-24 12:41:43 e[34mdebuge[39m: 1647 connected to redis.
2019-04-24 12:41:43 e[34mdebuge[39m: Mongoose default was disconnected
2019-04-24 12:41:43 e[34mdebuge[39m: connected to mongoose at mongodb://localhost:27017/speckle
2019-04-24 12:41:43 e[34mdebuge[39m: Failed to connect to DB mongodb://localhost:27017/speckle on startup
2019-04-24 12:41:43 e[34mdebuge[39m: Mongoose default was disconnected
2019-04-24 12:41:43 e[34mdebuge[39m: connected to mongoose at mongodb://localhost:27017/speckle
2019-04-24 12:41:43 e[34mdebuge[39m: Failed to connect to DB mongodb://localhost:27017/speckle on startup
but essentially the workers never get to actually connect to mongo. try accessing the db from the cli and see if that reveals more.
I highly doubt it’s anything to do with the server/clients code as the exact same things are running in production in a few places and i should’ve heard about such a problem.
(logs are duplicated in the original file because you’re spawning four workers; there’s no auth clients, just plain old post requests to the login endpoint)
I can confirm that it was the ver. of Mongo DB that I was using – also, using the repo and ref’s provided on Digital Ocean at How To Install MongoDB from the Default APT Repositories on Ubuntu 18.04 | DigitalOcean work best. DO NOT expose 27017 via UFW though.
