Problem with creating auth token

When I try to get auth token, site return me error: Unexpected auth token server, please try again later.

It seems the auth token server is down:

Error: rpc: tcp connector failed: rpc: dial tcp 35.188.114.190:8888: connect: connection refused

Any date when the service get back to normal?

Problem has been fixed. Works well now.

3 Likes

I still have issues →

"
2022/09/06 21:49:30 proto: duplicate proto type registered: node.SigningRequest
2022/09/06 21:49:30 proto: duplicate proto type registered: node.SigningResponse
2022-09-06T21:49:30.049+0100 INFO Anonymized tracing enabled
Error: rpc: tcp connector failed: rpc: dial tcp 35.188.114.190:8888: i/o timeout
"

Yes, me too. I’ve authorize one identity and one hour later I got same error like above.

2022/09/06 15:53:24 proto: duplicate proto type registered: node.SigningRequest
2022/09/06 15:53:24 proto: duplicate proto type registered: node.SigningResponse
2022-09-06T15:53:24.981-0500    INFO    Anonymized tracing enabled
Error: rpc: tcp connector failed: rpc: dial tcp 35.188.114.190:8888: i/o timeout

I have the exact same issue, tried on multiple PC, can’t connect to certs.alpha.storj.io:8888. all firewall disabled

Works now.

Identity successfully authorized using single use authorization token.
3 Likes

Hi, Problem is again there: Unexpected auth token server, please try again later.

Could you please be a more specific - what you did and where?

Hi,
one thing on the webside: Sign up and host a Node on Storj
Error when try to cerate a new token: Unexpected auth token server, please try again later.

Other, when I try to put my token from yesterday to a certificate on my machine
./identity.exe authorize storagenode email:token:
2022/12/04 11:10:24 proto: duplicate proto type registered: node.SigningRequest
2022/12/04 11:10:24 proto: duplicate proto type registered: node.SigningResponse
2022-12-04T11:10:24.542+0100 INFO Anonymized tracing enabled
Error: rpc: tcp connector failed: rpc: dial tcp 35.224.44.57:8888: connectex: No connection could be made because the target machine actively refused it.

Hello Alexey,
same here!

Trying to create a new Auth-Token here:
https://www.storj.io/host-a-node
Ends in the Message:
Unexpected auth token server, please try again later.

Trying to certificate a new Node with a Auto-Token from yesterday shows this:

2022/12/04 11:34:00 proto: duplicate proto type registered: node.SigningRequest
2022/12/04 11:34:00 proto: duplicate proto type registered: node.SigningResponse
Error: rpc: tcp connector failed: rpc: dial tcp 35.224.44.57:8888: connectex: No connection could be made because the target machine actively refused it.

Could you please try again?

coolio.
It works now and says its online

Thank you much.

Works again. Thank you

1 Like