Yes, I do see files.
Please, check the CLI dashboard:
sudo docker exec -it storjlabsSnContainer ./dashboard.sh
Yes, I do see files.
Please, check the CLI dashboard:
sudo docker exec -it storjlabsSnContainer ./dashboard.sh
Had trouble copy and pasting the CLI.
It shows . . .
ID (my long id)
Status (Offline)
Uptime. 22h53m55s
Available Used Egress Ingress
Bandwidth N/A 0 B 0 B 0 B (since Nov 1)
Disk 1.00 TB 0 B
Internal 127.0.0.1:7778
External (my domain):28967
Thats it.
Qnap however shows storage node running.
This log appears. Could it be that the network is constrained for some reason, with data moving very slowly. The system may be running but effectively no files are moving back and forth ?
2020-11-17T06:35:56.720Z INFO bandwidth Performing bandwidth usage rollups
General Network Info from where I sit - does these figures seem reasonable? I suspect that this is not my real problem though. I do not seem to have any files populating Storj Folders.
ping saltlake.tardigrade.io
PING saltlake.tardigrade.io (34.94.235.192): 56 data bytes
64 bytes from 34.94.235.192: seq=0 ttl=106 time=181.737 ms
64 bytes from 34.94.235.192: seq=1 ttl=106 time=181.573 ms
64 bytes from 34.94.235.192: seq=2 ttl=106 time=181.462 ms
64 bytes from 34.94.235.192: seq=3 ttl=106 time=181.400 ms
64 bytes from 34.94.235.192: seq=4 ttl=106 time=181.322 ms
64 bytes from 34.94.235.192: seq=5 ttl=106 time=181.147 ms
ping asia-east-1.tardigrade.io
PING asia-east-1.tardigrade.io (35.221.206.245): 56 data bytes
64 bytes from 35.221.206.245: seq=0 ttl=100 time=198.377 ms
64 bytes from 35.221.206.245: seq=1 ttl=100 time=188.136 ms
64 bytes from 35.221.206.245: seq=2 ttl=100 time=187.973 ms
64 bytes from 35.221.206.245: seq=3 ttl=100 time=187.977 ms
64 bytes from 35.221.206.245: seq=4 ttl=100 time=188.051 ms
If the CLI dashboard shows the storagenode as offline too, then it’s really offline.
Please, check your identity:
docker exec -it storjlabsSnContainer grep -c BEGIN /app/identity/ca.cert
docker exec -it storjlabsSnContainer grep -c BEGIN /app/identity/identity.cert
Should return 2 and 3 respectively.
Please, check your external address in the storagenode setup:
docker inspect storjlabsSnContainer -f "{{ .Config.Env }}" | grep -Po "ADDRESS=.*? "
Put this external address into Remote Address and port into Port Number fields on https://www.yougetsignal.com/tools/open-ports/ and click Check.
If port is closed, check your DDNS updater for the external address.
Please also check the WAN IP on the status page of the router and compare it with IP on yougetsignal, if they do not match the port forwarding will not work.
Apologies for my absence. I have been on leave.
My results for the first part of your post.
1
2
Re second part I get an error - grep does not like the -P
Your identity is not signed, you need to authorize it with a new authorization token. If it’s placed in a non-default location, you should specify the path with a --identity-dir
option of identity authorize
command.
For example, if your identity placed in the /Volume/indentity/storagenode
, then the command for authorization would looks like
identity authorize --identity-dir /Volume/identity storagenode your@email:setojwogjeprjwgktrbnprojeiojferojneiorj...
Seems your grep command is little bit outdated. Then use the different one:
docker inspect storjlabsSnContainer -f "{{ .Config.Env }}" | awk '"ADDRESS=(.*)" {print $1}'
Take two . .
docker inspect storjlabsSnContainer -f “{{ .Config.Env }}” | awk ‘“ADDRESS=(.*)” {print $1}’
[WALLET=(mywalletaddress)
Re authorization token. These are single use so I guess I need to reapply.
NB. I am wondering if too much time had elapsed from when I recieved my original token - to when I actually used it.
Ok, the awk doesn’t work too. Nice OS.
Then please, give me the output of the whole command (you can do it in PM):
docker inspect storjlabsSnContainer -f "{{ .Config.Env }}"
The Qnap OS says . . .
[WALLET=0x___________7c EMAIL=c______t@d___e.org ADDRESS=d___e.org:28967 STORAGE=1000GB PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin GOARCH=]
I needed this one and you hided it
But nevermind - please, go to the Open Port Check Tool - Test Port Forwarding on Your Router and place the hostname (which is ended on e.org
) and place it to the Remote Address, the 28967 place to the Port Number and click Check.
Did you manage to sign the identity?