unsupported protocol scheme

[kadamwolfe]

I'm getting the following errors when trying to create and authorize my v3 identity:

$ ./identity_linux_arm create storagenode 2019-05-03T23:37:48.094-0500 ERROR Failed to do periodic version check: %!(EXTRA *url.Error=Get : unsupported protocol scheme "")

It's non-fatal and I'm able to get an identity, from what I can tell.

When I go to authorize I get the same error as well as a no such host though I can do a DNS lookup just fine.

$ ./identity_linux_arm authorize storagenode TOKEN REMOVED 2019-05-03T23:53:03.265-0500 ERROR Failed to do periodic version check: %!(EXTRA *url.Error=Get : unsupported protocol scheme "") Fatal error: error occurred while signing certificate: transport error: connection error: desc = "transport: error while dialing: dial tcp: lookup certs.alpha.storj.io: no such host" (identity files were still generated and saved, if you try again existing files will be loaded)

This is on an odroid XU4 running an up-to-date armbian stretch.

[FilipLaurentiu]

same fore me

[FilipLaurentiu]

filip@filip-pc:/mnt/sda/Download$ ./identity_linux_amd64 create storagenode
2019-05-07T22:08:22.636+0300 ERROR Failed to do periodic version check: %!(EXTRA *url.Error=Get : unsupported protocol scheme "")
Generating key with a minimum a difficulty of 30...
Generated 2186085 keys; best difficulty so far: 30
Found a key with difficulty 30!
Unsigned identity is located in "/home/filip/.local/share/storj/identity/storagenode"
Please move CA key to secure storage - it is only needed for identity management!
/home/filip/.local/share/storj/identity/storagenode/ca.key
filip@filip-pc:/mnt/sda/Download$ ./identity_linux_amd64 authorize storagenode
2019-05-07T22:10:21.428+0300 ERROR Failed to do periodic version check: %!(EXTRA *url.Error=Get : unsupported protocol scheme "")
Identity successfully authorized using single use authorization token.
Please back-up "/home/filip/.local/share/storj/identity/storagenode" to a safe location.

[stefanbenten]

@FilipLaurentiu Your identity was successfully signed, so you can ignore the error and go ahead.

@kadamwolfe Did you try the nslookup from the XU4?`

[vdcstore]

same here even if i use windows

[memopo]

same

[kadamwolfe]

@kadamwolfe Did you try the nslookup from the XU4?`

@stefanbenten , I did, and did again, ya. It's really weird.

user@host:~$ ./identity_linux_arm authorize storagenode me@dot.com:<token>

2019-05-15T19:12:19.329-0500	ERROR	Failed to do periodic version check: %!(EXTRA *url.Error=Get : unsupported protocol scheme "")

Fatal error: error occurred while signing certificate: transport error: connection error: desc = "transport: error while dialing: dial tcp: lookup certs.alpha.storj.io: no such host"
(identity files were still generated and saved, if you try again existing files will be loaded)

but if I look that up....

user@host:~$ host certs.alpha.storj.io
certs.alpha.storj.io has address 35.188.114.190

dig, nslookup etc are all able to resolve certs.alpha.storj.io.

[flo82]

same error for me:

./identity_linux_amd64 authorize storagenode email.com@xxx
ERROR Failed to do periodic version check: Get : unsupported protocol scheme ""

tried it with version: https://storj-v3-alpha-builds.storage.googleapis.com/8de6a97-v0.15.3-go1.12.7/identity_linux_amd64.zip

host system is ubuntu 18.04.2

[stefanbenten]

@flo82 It printed out the version fine for the identity create storagenode command?

[stefanbenten]

Seems like i missed a spot..

[flo82]

yes,

./identity_linux_amd64 create storagenode

worked like a charm.

[stefanbenten]

Cool, PR incoming!

[flo82]

thx. i will try it out, if there is a build ready.

[stefanbenten]

@flo82 Would you like to try this build? https://alpha.transfer.sh/13ec4r/identity

[flo82]

next error:

2019-07-24T18:42:40.105Z        INFO    running on version v0.15.4
2019-07-24T18:42:40.333Z        FATAL   error occurred while signing certificate: transport error: connection error: desc = "transport: authentication handshake failed: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert"
(identity files were still generated and saved, if you try again existing files will be loaded)

[stefanbenten]

Cool, seems like that fixes the issue.

[flo82]

so I do need to wait for an official build - or what do to against the new error?

[stefanbenten]

The second error is during the authorize step, would be good to get an entire dump of what you executed.

[flo82]

only:

./identity_linux_amd64 create storagenode
./identity_linux_amd64 authorize storagenode email.com@xxx

[stefanbenten]

Can you please post the entire output? @flo82

[flo82]

./identity_linux_amd64 create storagenode --log.level debug
2019-07-24T19:37:27.556Z        DEBUG   debug server listening on 127.0.0.1:41643
2019-07-24T19:37:28.036Z        DEBUG   allowed minimum version from control server is: v0.15.1
2019-07-24T19:37:28.036Z        INFO    running on version v0.15.4
Generating key with a minimum a difficulty of 30...
Generated 7501137 keys; best difficulty so far: 33
Found a key with difficulty 33!
Unsigned identity is located in "/home/flo/.local/share/storj/identity/storagenode"
Please *move* CA key to secure storage - it is only needed for identity management!
        /home/flo/.local/share/storj/identity/storagenode/ca.key

./identity_linux_amd64 authorize storagenode email@emal.com:XXXX --log.level debug
2019-07-24T19:39:58.140Z        DEBUG   debug server listening on 127.0.0.1:42697
2019-07-24T19:39:58.615Z        DEBUG   allowed minimum version from control server is: v0.15.1
2019-07-24T19:39:58.615Z        INFO    running on version v0.15.4
2019-07-24T19:39:58.866Z        FATAL   error occurred while signing certificate: transport error: connection error: desc = "transport: authentication handshake failed: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert"
(identity files were still generated and saved, if you try again existing files will be loaded)

[stefanbenten]

Let me test that.

[stefanbenten]

If you append --signer.tls.use-peer-ca-whitelist=false to the second command it works. We have introduced a check to outgoing requests, that bites us there.
I will open a new ticket and close this, as the version check issue is resolved.