Closed camjenk closed 8 years ago
This should be resolved with tomorrow's deployment and today's releases.
I also had this problem with 0.7.0.
I updated to 0.7.1, now i get the same error, but in a pop-up window.
My setup: Windows 2012R2 No upnp, with NAT behind cisco firewall. (no ports forwarded)
Please try again after bridge update. You get the error message because we had 2 problems. 1.) UPNP doesn't work. Most of the farmer are unable to open tunnel ports for you. Hopefully solved with the new version but you have to wait until other farmer did the update. Your own update doesn't help you. 2.) Bridge was full of tunnel connection and didn't point you to other farmer that would allow you a tunnel connection. Hopefully solved with the bridge update comming today.
Number 1 is not solved. See https://github.com/Storj/farmer/issues/23
Anyway the bridge update can still fix it. Blackduck and I got some open tunnel ports for you all.
Thanks for the help, I will keep the old client running until I see a working update. To get the new update do I simply open version 0.7.0 and accept a prompt? or should i travel to the new storj.io/share.html
Just want to be sure my upgrade to 0.7.1 is smooth (let me know if i need to delete shards or reformat drives ETC)
Storj Share 0.7.2, MacOS, behind a router with a working UPnP, problem exists.
{info} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] node created with nodeID 059e68178d3c4d2ebaea088f0ca6481dbf879155
{info} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] publishing message on topic "0e01"
{info} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] subscribing to topic "0e01"
{info} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] subscribing to topic "0e00"
{info} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] requesting probe from nearest neighbor
{info} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] sending PROBE message to {"protocol":"0.6.5","address":"api.storj.io","port":8443,"nodeID":"593844dc7f0076a1aeda9a6b9788af17e67c1052","lastSeen":1461924663323}
{warn} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] could not connect to NAT device via UPnP
{info} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] subscribing to topic "0f01020202"
{info} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] subscribing to topic "0f02020202"
{info} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] subscribing to topic "0f03020202"
{info} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] sending FIND_NODE message to {"protocol":"0.6.5","address":"api.storj.io","port":8443,"nodeID":"593844dc7f0076a1aeda9a6b9788af17e67c1052","lastSeen":1461924663468}
{info} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] received valid message from {"protocol":"0.6.5","address":"api.storj.io","port":8443,"nodeID":"593844dc7f0076a1aeda9a6b9788af17e67c1052","lastSeen":1461924663882}
{info} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] requesting tunnelers from nearest neighbor
{info} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] sending FIND_TUNNEL message to {"protocol":"0.6.5","address":"api.storj.io","port":8443,"nodeID":"593844dc7f0076a1aeda9a6b9788af17e67c1052","lastSeen":1461924663916}
{info} [Fri Apr 29 2016 13:11:03 GMT+0300 (EEST)] received valid message from {"protocol":"0.6.5","address":"api.storj.io","port":8443,"nodeID":"593844dc7f0076a1aeda9a6b9788af17e67c1052","lastSeen":1461924663966}
{info} [Fri Apr 29 2016 13:11:04 GMT+0300 (EEST)] sending FIND_NODE message to {"protocol":"0.6.5","address":"api.storj.io","port":8443,"nodeID":"593844dc7f0076a1aeda9a6b9788af17e67c1052","lastSeen":1461924664000}
{info} [Fri Apr 29 2016 13:11:04 GMT+0300 (EEST)] received valid message from {"protocol":"0.6.5","address":"api.storj.io","port":8443,"nodeID":"593844dc7f0076a1aeda9a6b9788af17e67c1052","lastSeen":1461924664363}
{info} [Fri Apr 29 2016 13:11:04 GMT+0300 (EEST)] sending OPEN_TUNNEL message to {"protocol":"0.6.5","address":"server012.storj.dk","port":5012,"nodeID":"ffa9832be51582d4a64bd3b60fb8c6347346ab79","lastSeen":1461924664391}
{info} [Fri Apr 29 2016 13:11:04 GMT+0300 (EEST)] received valid message from {"protocol":"0.6.5","address":"api.storj.io","port":8443,"nodeID":"593844dc7f0076a1aeda9a6b9788af17e67c1052","lastSeen":1461924664434}
{warn} [Fri Apr 29 2016 13:11:04 GMT+0300 (EEST)] missing or empty reply from contact
{warn} [Fri Apr 29 2016 13:11:23 GMT+0300 (EEST)] rpc call 82fb9ba02d89ac6a3fc3f5a6218403a7ca1ba82c timed out
{info} [Fri Apr 29 2016 13:11:23 GMT+0300 (EEST)] sending OPEN_TUNNEL message to {"protocol":"0.6.5","address":"server012.storj.dk","port":5012,"nodeID":"ffa9832be51582d4a64bd3b60fb8c6347346ab79","lastSeen":1461924683313}
{warn} [Fri Apr 29 2016 13:11:23 GMT+0300 (EEST)]
And I have unused tunnels. My log:
{"level":"info","message":"publishing message on topic \"0e01\"","timestamp":"2016-04-29T09:53:01.397Z"}
{"level":"info","message":"sending PUBLISH message to {\"protocol\":\"0.6.5\",\"address\":\"api.storj.io\",\"port\":8443,\"nodeID\":\"593844dc7f0076a1aeda9a6b9788af17e67c1052\",\"lastSeen\":1461923581398}","timestamp":"2016-04-29T09:53:01.398Z"}
{"level":"info","message":"received valid message from {\"protocol\":\"0.6.5\",\"address\":\"api.storj.io\",\"port\":8443,\"nodeID\":\"593844dc7f0076a1aeda9a6b9788af17e67c1052\",\"lastSeen\":1461923581730}","timestamp":"2016-04-29T09:53:01.730Z"}
{"level":"info","message":"publishing message on topic \"0e01\"","timestamp":"2016-04-29T10:08:01.480Z"}
{"level":"info","message":"sending PUBLISH message to {\"protocol\":\"0.6.5\",\"address\":\"api.storj.io\",\"port\":8443,\"nodeID\":\"593844dc7f0076a1aeda9a6b9788af17e67c1052\",\"lastSeen\":1461924481480}","timestamp":"2016-04-29T10:08:01.480Z"}
{"level":"info","message":"received valid message from {\"protocol\":\"0.6.5\",\"address\":\"api.storj.io\",\"port\":8443,\"nodeID\":\"593844dc7f0076a1aeda9a6b9788af17e67c1052\",\"lastSeen\":1461924482316}","timestamp":"2016-04-29T10:08:02.316Z"}
This should be resolved by https://github.com/Storj/core/releases/tag/v0.6.6 and related releases.
My node has 2 open tunnel connection now. Core 0.6.7 is working very good.
{"level":"info","message":"received valid message from {\"protocol\":\"0.6.7\",\"address\":\"server023.storj.dk\",\"port\":28260,\"nodeID\":\"8147c13a37bddd5aeb84a2e32b49ffa942c6ca1d\",\"lastSeen\":1461987216560}","timestamp":"2016-04-30T03:33:36.560Z"}
{"level":"info","message":"opening gateway for 8147c13a37bddd5aeb84a2e32b49ffa942c6ca1d","timestamp":"2016-04-30T03:33:36.716Z"}
{"level":"info","message":"publishing message on topic \"0e00\"","timestamp":"2016-04-30T03:33:36.829Z"}
{"level":"info","message":"sending PUBLISH message to {\"protocol\":\"0.6.7\",\"address\":\"api.storj.io\",\"port\":8443,\"nodeID\":\"593844dc7f0076a1aeda9a6b9788af17e67c1052\",\"lastSeen\":1461987216830}","timestamp":"2016-04-30T03:33:36.830Z"}
{"level":"info","message":"gateway opened for 8147c13a37bddd5aeb84a2e32b49ffa942c6ca1d at {\"address\":\"<myddns>\",\"port\":4004}","timestamp":"2016-04-30T03:33:37.015Z"}
I got also this issue: Upgraded from 0.6 to .0.7.4 Storj Share Version 0.7.4 Protocol Version 0.6.7 Linux Mint 17.3
{warn} [Tue May 03 2016 20:22:40 GMT+0200 (CEST)] could not connect to NAT device via UPnP ... {warn} [Tue May 03 2016 20:22:58 GMT+0200 (CEST)] rpc call d54b8240a1d10e881a5f8787869fb3ee7c87e728 timed out All other {info} messages seems ok.
Does Storj need a UPnP connection from outside to my computer?
Just updated from 0.6.0 to 0.7.0
Filled in the data for the drives (screen shotted the old gui with the GB amounts and paths to be sure everything is exact)
using Win10 When i try to farm I get this error. Please help? EDIT: Switched back to the older version for now and it works, hoping for news of a fix on the newer version.
Drive1
Drive 2
Drive 3
Drive 4
Drive 5