See this thread: Time before the first activity/usage on a new node?
Storj should just refuse to start if the identity hasn’t been signed.
See this thread: Time before the first activity/usage on a new node?
Storj should just refuse to start if the identity hasn’t been signed.
I comfirm the case, i helped about 1 or 2 people with this case to fix it.
This is likely Linux client issue. Docker gave me an error did not spin up when the identity was not authorized. I tested it with v1.19.6 and could not replicate this bug.
it is on windows gui isue.