Did find the config.yaml file, changed:
console.address: 0.0.0.0:14002 into console.address: :14002
removed and restarted container but still no dashboard
As suggested by @pangolin you may change -p 127.0.0.1:14002:14002 to -p 14002:14002, however it will allow to connect to your dashboard only in the local network. We do not recommend to expose the dashboard to the internet without any protection, thus there are two alternative solutions:
The first one would allow to connect to the dashboard from anywhere, include your smartphone when you are not in home.
The second one requires to be run on some PC/Mac, but it can allow to monitor more than a one node remotely and secure too.
RPI 3B+, Raspberry Pi OS Lite 64 bit Bookworm
Did a complete new install (OS and Storj). All working.
Config and Identity loaded but still problem with dashboard:
Topic can be closed. Problem solved.
Thank you for the suggestions. I finally got the dashboard working on the small linux test system (RPI).
Storage Node Dashboard ( Node Version: v1.104.5 )
======================
ID ************************************************************
Status ONLINE
Uptime 4m53s
Available Used Egress Ingress
Bandwidth N/A 0 B 0 B 0 B (since Jun 1)
Disk 1.00 TB 0.91 GB
Alexey,
Thank you for your reply. I now have the installation procedure well worked out and can bring up a systemRPI 3B+, bookworm OS, 1 TB disk.
CLI dashboard and web dashboard working. However every night around 02:00 hours, I receive four or five “Your Node has Gone Offline” emails (I suspect my internet provider).
According to Docker ps -a, and the dashboard the process continues to work. Disk has up to now not been used by storagenode.
After about a day I loose connection with the RPI on the LAN but the process seems to continue according to the web dashboard.
Web dashboard shows Status = Offline and QUIC = Misconfigured but uptime still increases.
Somewhere today I will do a new install and keep you informed.
Regards,
René
Unfortunately, this is mean that your node is not available for the customers.
I suppose that you need to use a DDNS service to have the public IP updated in time: Step 3. Setup Port Forwarding - Storj Docs
I had made an error in authorizing my identity! Now the setup is working. Status Online and QUIC OK. FInally up and running.
Thank you for your suggestions.
Had some startup problems but now RPI 3B+ ( 1 TB) is up and running.
RAM usage ~ 75%
SWAP usage ~ 35%
CPU usage ~ 32%
I would say that this simple thing is quite good for this job.
I had a few “node gone offline” messages and had to reboot the RPI. But I have hooked it up to a LAN cable now and will see what is does in the oncoming hours.
Are you tried to run it on WiFi? That’s not a good idea, not all WiFi routers are capable to handle thousands parallel transfers via WiFi.
Yes, it’s expected, because it’s a weak device. However, even in this case it should work correctly.
Plus your node is likely in the vetting process. The vetting node can receive only 1%-3% of the uploads until got vetted. To be vetted, the node should pass 100 audits on the satellite before it would be vetted. For the one node in the /24 subnet of public IPs it should take at least a month.
However, for the SLC it could be faster because of load tests.
Status update for the RPI 3B+ and 1 TB disk. Disk now filled for 0.81 TB and all is going well.
RAM usage ~ 67%
SWAP usage ~ 64%
CPU usage ~ 10%
And more important, the money comes flying in…
