I’ve setup Ubuntu Server on one of my servers and installed docker along with storjlabs/storagenode:beta I got everything setup and ran docker exec -it storagenode /app/dashboard.sh.
This works and gives me almost all the information I want but I’d like to see a day by day record of Ingress:Egress traffic since it seems storjlabs/watchtower does not always do it’s job. My storage node in previous testing has failed to update as it should causing Ingress:Egress to drop to 0 but I can’t clearly see if that occurs from the CLI version of dashboard.
Is there a CLI utility for viewing day by day traffic or any argument I can add to view this information?
I’m using Ubuntu Server. No GUI. CLI only. I’ve tried remoting into the WebUI by pointing my desktops browser to the servers IP:14002 but all I get is a refused connection.
do you have firewall on node?
what is your docker init string?
I have also on node on raspberry pi, with docker, and it by default has Web dashboard acceseble from network.
Add -p 14002:14002 to your docker command, and then open that port up on your firewall. I have a Ubuntu node that I connect into using the dashboard and this works for me. Using localhost in the -p command will limit connections to just the local host.
Yep, here is what you need to do to enable that port.
sudo ufw allow 14002
If you don’t have ufw installed, install it using sudo apt install ufw
You might also have to enable the other port for SNO, if you install ufw. So here are the rest…
sudo ufw allow 26967 (I think that is the default port for SNO. I run on custom ports)
Adding -p 14002:14002 but going to restart storagenode:beta docker threw an error.
Replacing -p 127.0.0.1:14002:14002 with -p 14002:14002 I now have remote access to the WebUI.
This is an edit to the launcher I’ll have to remember to make for the future.
I would not mind enabling a firewall just to prevent any hijacking. UFW is installed by default on Ubuntu Server but it’s also disabled by default.
I’m going to make the assumption enabling it blocks all(most) ports then I make exceptions for the ports that I want allowed correct? (as the commands you outlined state)
That is mostly correct. It seems to know some of the standard ports, and opens them up, but for SNO you’d have to add the exceptions. If I were doing this, I’d watch the port status using a port scanner from the web and make sure it comes up once you run the command. I’ve not had trouble doing this, but always check.
If you want to learn more about ufw here is a good link that goes into some details on the commands, and some advanced settings like limiting access to only particular IPs, etc.