I stated earlier i have a static ip address on my local subnet.
| SGC
March 8 |
mocallins:
2023-03-08T18:57:59.164Z INFO Configuration loaded {“Process”: “storagenode-updater”, “Location”: “/app/config/config.yaml”}
2023-03-08T18:57:59.165Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “contact.external-address”}
2023-03-08T18:57:59.165Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet”}
2023-03-08T18:57:59.165Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-bandwidth”}
2023-03-08T18:57:59.166Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “healthcheck.details”}
2023-03-08T18:57:59.166Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.email”}
2023-03-08T18:57:59.166Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.private-address”}
2023-03-08T18:57:59.167Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet-features”}
2023-03-08T18:57:59.167Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “healthcheck.enabled”}
2023-03-08T18:57:59.167Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-disk-space”}
2023-03-08T18:57:59.168Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.address”}
2023-03-08T18:57:59.168Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “console.address”}
2023-03-08T18:57:59.168Z INFO Invalid configuration file value for ke{“Process”: “storagenode-updater”, “Key”: “log.level”}
actually i think this is normal…
as you can see later in the log it does catch the configuration.
and apply wallet and email and such
mocallins:
2023-03-08T18:57:59.220Z INFO Operator wallet {“Process”: “storagenode”, “Address”: “0x38…edited…b5”}
been a long time since i tinker with the storagenodes, lots have changed…
if memory serves the errors are when it starts up before it finished downloading the most recent version allowed for your storagenode.
so those can be disregarded.
mocallins:
I cannot open the :14002 webpage.
the local storagenode web access should always work, even if the storagenode doesn’t get web access… this indicates so other kind of problem, again routing / firewall related usually.
maybe antivirus… some antivirus software’s come with firewalls today.
the 14002 webdash board is configurable and uses the local ip, if that isn’t working then nothing else certainly will…
getting that to work might be a good place to start…
i am pretty sure the node will keep rebooting until it gets online, but pretty sure the dashboard would work regardless, even if the node is in a restart loop until it gets connected to the storj network.
so i’m fairly certain the dashboard should work, most of the time…
but again its been a while since i tinkered with this…
however that would be where i would start, because its the closest and simplest.
fix that and maybe you will figure out why the rest of the setup stopped working…
personally my money is still on your lan ip of your storagenode changed, because you replaced your router with a cable modem and thus got a new dhcp server.
or don’t have a dhcp server at all
i guess is also an option but then i suspect nothing would work.