Node dashboard won't load. Setup failure?

Node Operators troubleshooting
, ,
21

@RandallStevens If you migrated a worked node to the Linux, you must not generate a new identity and perform a setup step, otherwise you will destroy your old node, what you seems almost did. And this is good, that it cannot start.
I hope that you at least did not generate a new identity, otherwise you need to copy your previous identity from the Windows PC again.

Please also make sure that you migrated all data to the /mnt/STORJ/storagenode/data/storage/ (note the subdirectory storage, this is important!).
If you migrated to the /mnt/STORJ/storagenode/data/ path, not to the /mnt/STORJ/storagenode/data/storage/, then you need to move all data from /mnt/STORJ/storagenode/data/ to /mnt/STORJ/storagenode/data/storage/.

You must never execute the docker run command with SETUP=true for existing node!

In your docker run command you will use /mnt/STORJ/storagenode/data (note here the storage subdirectory must absent).

22

@peem

Yes I did run that command

@Alexey

No I did not generate a new identity

I did run this set up command

sudo docker run --rm -e SETUP="true" \
    --user $(id -u):$(id -g) \
    --mount type=bind,source="/mnt/STORJ/storagenode/identity/storjidentity",destination=/app/identity \
    --mount type=bind,source="/mnt/STORJ/storagenode/data",destination=/app/config \
    --name storagenode storjlabs/storagenode:latest

What does that mean?

Doe that mean I’m screwed?

Or can I rerun the setup command with soemthing different for SETUP?

Or should I rerun the setup command with SETUP deleted altogether?

I moved the data from /mnt/STORJ/storagenode/data to…

/mnt/STORJ/storagenode/data/storage

so that much is taken care of

23

@peem @Alexey

Okay!!!

We are making progress.

I stopped the container and then reran it after relocating the files like Alexey said and now the dashboard loads but says offline misconfigured

Screenshot from 2022-10-29 16-19-21
Screenshot from 2022-10-29 16-19-211171×498 32.5 KB

24

Please provide the last 20 lines from your logs (text please, not a screenshot).
To prettify the look, place logs lines here between two new lines with three backticks, like this

```
log lines here
```
26

@Alexey @peem

Is says the port is closed…

Screenshot from 2022-10-29 21-33-13

27

Do you have a working firewall on this linux system?

And of course on the router have you changed the port forwarding on the PC now used for SN?

1 Like
28

@peem

I don’t know if I have a working firewall on linux.

I never set one up. Is it set up by default?

29

@peem @Alexey

If I run:

udo ufw status

it says “inactive”

30

@peem

yes I changed port forwarding on my router. Is the type supposed to be “DNS”?

31

Don’t you already have a redirect to SN under Windows? It would be sufficient to change the LAN IP
the type supposed to be “custom”

32

@peem

Yes that’s what I did on my router.

I changed it to “custom”

I get this error message when trying to restart

randall@GoodRig:~$ sudo docker restart -t 300 storagenode
Error response from daemon: Cannot restart container storagenode: permission denied
33 
history | grep usermod
34

@peem

randall@GoodRig:~$ history | grep usermod
   82  history | grep usermod
35

OK
now:

sudo usermod -aG docker $USER
36

@peem

done but was I supposed to change the $user to $randall?

also it still says port is closed

37

The port is closed because SN is not working…

$USER add randall (or rather who is now logged in) into the docker group

you will do the same:

sudo usermod -aG docker randall
38

Now stop the SN container:

sudo docker stop -t 300 storagenode

remove it:

sudo docker rm storagenode
39

@peem

that command worked just fine but now the dashboard won’t even load again.

This is so frustrating. Is this because I ran “SETUP=true”???

That’s what the directions say to do…

40

@peem

randall@GoodRig:~$ sudo docker stop -t 300 storagenode
[sudo] password for randall: 
storagenode
randall@GoodRig:~$ sudo docker rm storagenode
storagenode
randall@GoodRig:~$
41

Now start the container but without sudo:

docker run -d --restart unless-stopped --stop-timeout 300 \
    -p 28967:28967/tcp \
    -p 28967:28967/udp \
    -p 127.0.0.1:14002:14002 \
etc....