if you have multiple ip’s on the storagenode host, it can be a good idea to
define those in the docker run command, sometimes the node can decide to run on different IP’s than one expects.
Does you node offline on the dashboard?
If so, please check the WAN IP on your router and compare it with IP on Open Port Check Tool - Test Port Forwarding on Your Router, if they don’t match, the port forwarding will not work.
If they matches, then please check your DDNS hostname:
nslookup collinsinfotech.com 8.8.8.8
it should resolve to the same IP, as your WAN IP and IP on yougetsignal.
If it’s not - you need to update it with their updater or use a different DDNS provider.
Does you node offline on the dashboard?
If so, please check the WAN IP on your router and compare it with IP on Open Port Check Tool - Test Port Forwarding on Your Router, if they don’t match, the port forwarding will not work.
If they matches, then please check your DDNS hostname:
nslookup collinsinfotech.com 8.8.8.8
it should resolve to the same IP, as your WAN IP and IP on yougetsignal.
If it’s not - you need to update it with their updater or use a different DDNS provider.
[storjnode]:</home/mike/> alias snlt
docker logs --tail 20 storagenode
[storjnode]:</home/mike/> snlt
2023-03-13T04:33:40.696Z ERROR Invalid configuration. {"Process": "storagenode", "error": "invalid contact.external-address: lookup \"collinsinfotech.com\" failed: lookup collinsinfotech.com on 8.8.4.4:53: read udp 172.17.0.3:34774->8.8.4.4:53: i/o timeout", "errorVerbose": "invalid contact.external-address: lookup \"collinsinfotech.com\" failed: lookup collinsinfotech.com on 8.8.4.4:53: read udp 172.17.0.3:34774->8.8.4.4:53: i/o timeout\n\tstorj.io/storj/storagenode.(*Config).Verify:161\n\tmain.cmdRun:188\n\tstorj.io/private/process.cleanup.func1.4:377\n\tstorj.io/private/process.cleanup.func1:395\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomConfigAndLogger:92\n\tmain.main:478\n\truntime.main:250"}
Error: invalid contact.external-address: lookup "collinsinfotech.com" failed: lookup collinsinfotech.com on 8.8.4.4:53: read udp 172.17.0.3:34774->8.8.4.4:53: i/o timeout
2023-03-13 04:33:40,699 INFO exited: storagenode (exit status 1; not expected)
2023-03-13 04:33:41,703 INFO spawned: 'storagenode' with pid 26
2023-03-13 04:33:41,704 WARN received SIGQUIT indicating exit request
2023-03-13 04:33:41,706 INFO waiting for storagenode, processes-exit-eventlistener, storagenode-updater to die
2023-03-13T04:33:41.705Z INFO Got a signal from the OS: "terminated" {"Process": "storagenode-updater"}
2023-03-13 04:33:41,707 INFO stopped: storagenode-updater (exit status 0)
2023-03-13T04:33:41.765Z INFO Configuration loaded {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2023-03-13T04:33:41.766Z INFO Anonymized tracing enabled {"Process": "storagenode"}
2023-03-13T04:33:41.768Z INFO Operator email {"Process": "storagenode", "Address": "mo...om"}
2023-03-13T04:33:41.768Z INFO Operator wallet {"Process": "storagenode", "Address": "0x38..5"}
2023-03-13 04:33:44,772 INFO waiting for storagenode, processes-exit-eventlistener to die
2023-03-13 04:33:47,777 INFO waiting for storagenode, processes-exit-eventlistener to die
2023-03-13 04:33:50,781 INFO waiting for storagenode, processes-exit-eventlistener to die
2023-03-13 04:33:51,783 WARN killing 'storagenode' (26) with SIGKILL
2023-03-13 04:33:51,785 INFO stopped: storagenode (terminated by SIGKILL)
2023-03-13 04:33:51,785 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)
2023-03-13 04:33:52,890 INFO RPC interface 'supervisor' initialized
2023-03-13 04:33:52,891 INFO supervisord started with pid 1
[storjnode]:</home/mike/>
Please login to your router and compare this IP with WAN IP, if they do not match the port forwarding will not work.
Also this one is concerning:
This is mean, that something is blocking connections, it even cannot resolve the hostname.
And it could also mean that your DNS server for this domain could be misconfigured.
Hmmm omg not this crap again, this cable modem, does this stupid thing forwarding out some weird 10.6.64.1 address, this is the reasson i put a real router in there, to stop that.
But i think its been doing it ll along, this is the same cablemodem i had originally setting up Storj.
Looks like it’s no more in a bridge mode and likely in the router mode (NAT is enabled). So you need to create a port forwarding rule on it.
If you have some router in between, then you need to have two such rules:
Need to check that your PC with storagenode has the same local IP, as specified in the port forwarding rule. And make sure that this port is allowed in your firewall.
The next would be to make sure that storagenode is running and check the port.
It also worth to check logs for errors.
Right now the port is closed.
I’m running storj in a vm, all by itself.
The ip address is static.
I do not currently have the firewall enabled, because this isn’t working.
I see errors, in the logs, but i guess they aren’t “real” errors, so it just leads me off the track to finding anything.
Plus i can barely stop and start the thing inside docker, so my troubleshooting skills are basically all the
simple things you’ve had me repeat, that’s why i’m on the forum now.
I would have no idea what to look for, or do , inside the docker.
I think the port is closed probably because the storagenode is not completly running cirrecctly, the rest of my network is fine, i have no issues with other vms or my pc. SMH
Yes, if the container is restarting, the port will be closed. Since it cannot resolve the own hostname using the external DNS, there are network issue in this VM.
By the way is docker installed using snap?
You may try to replace a hostname with your public IP instead.
| SGC
mocallins:
| 
