It could be related to a transient bug:
Hi @dmp @EvilMalamute
Could you check the dashboard - let me know if its starting to update for you?
I’m force fetching the node data now to update the dashboard - it might take an hour.
Apologies for the outage !
I do have some background work to do on the platform to mitigate these blips
Donations:
Very kind of you to bring it up / mention this
To support the up keep of servers and time to spend developing it further we do accept donations
The address is a valid L1 ETH (which is found in the support us page)
Let me know if your data has now started to show.
Cheers
Hass
Thank you. Everything works now. Exept one of my nodes that died the day before yesterday (5Tb lost).
вт, 21 янв. 2025 г., 15:06 ItsHass via Storj Community Forum (official) <noreply@forum.storj.io>:
It seems that everything has become normal, although the payment amount is displayed as zeros, but this is not important. Thank you!
Yes there is a few improvements to make to the dashboard, I will be looking to make those next month ![]()
Please try also to fix the Avg reporting (if something is missing or incomplete (the diff is more than 10%), please - ignore and make it linear).
Sure , thanks for feedback - I will look into that
All you had to do was donate a little for the development of the project, and after a couple of days the system stopped letting you into the control panel =). Accuses of using VPN for access. But I don’t use VPN to log into the control panel either at home or at work, and it doesn’t authorize me from both places. Strange innovations. Am I the only one having this problem?
Ah ! We recently put in place a method to stop bots hitting the site.
Primarily for sign ups - I will take the thing that’s checking that off the login … apologies
The team appreciate your contribution to the up keep !
In other news - we will be running a survey soon to ask users what they would like to see most…
Just need to work out best way to do the survey.
Thanks
Hass
Blocker is now removed from login - let me know if you have any issues.
Now everything works well! Thank you!
I noticed that you removed some of the statistics in speed for days for a separate node. Will this statistics be returned or is it permanent?
Hi @dmp can you drop me a screenshot ? or reply with one here?
Vetted Status is now implemented on this page and we removed some data which was no long able to be fetched by /api/… endpoints .. example: individual satellite storage
Let me know if you need me to look at anything else for you ![]()
StorjDashboard V2 — A new version built around SNO feedback
Hi everyone,
It’s been a while since I last updated this thread, but StorjDashboard has now had a pretty significant rebuild.
Over the years, there has been a lot of useful feedback in this thread and from people actually using the dashboard. A few of the recurring requests were:
-
Easier installation and setup
-
No requirement to expose a node to the internet
-
Better support for multiple nodes
-
Historical data rather than only current statistics
-
Better alerts and monitoring
-
More useful payout information
-
Better performance and a faster interface
-
Something that works easily behind CGNAT / changing IP addresses
-
Less configuration and maintenance for the SNO
So rather than continuing to add features to the original implementation, I decided to rebuild the dashboard from the ground up.
V2 is currently in testing
The new V2 dashboard is currently in the testing phase.
I would really like to get as many SNOs as possible using it and trying it out. If you’ve got a Storj node (or multiple nodes), you’re very welcome to sign up and give V2 a try.
The more people who use it during testing, the more useful the feedback will be for finding bugs, improving performance and making the experience better before V2 is considered fully ready.
Please don’t be afraid to report bugs, suggest changes or tell me if something doesn’t make sense. This is exactly what the testing period is for.
What has changed?
The aim with V2 is much more straightforward:
Every node you run, on one dashboard.
The node itself reports its statistics out to StorjDashboard, meaning there is nothing that needs to be exposed publicly.
There is no port forwarding, no firewall rule, no dynamic DNS requirement and it works behind CGNAT.
The setup is now essentially:
-
Create an account
-
Add a node
-
Copy the command provided
-
Run it on the machine hosting your Storj node
-
That’s it
The reporting agent reads the node locally and sends the required statistics out.
Historical data
One of the biggest changes is that V2 is designed around history rather than just the current state of the node.
You can track things such as:
-
Daily storage usage
-
Daily ingress / egress
-
Average throughput
-
Audit scores
-
Suspension scores
-
Online scores
-
Payout history
-
Estimated earnings
-
Wallet balances
-
Node version changes
This makes it much easier to spot gradual changes in a node rather than only discovering something when the current value looks wrong.
Monitoring & alerts
V2 also has monitoring built into the service.
The dashboard can notify you when things change, including:
-
Node stops reporting
-
Audit score changes
-
Suspension score changes
-
Online score changes
-
Node version changes
-
zkSync balance changes
Notifications can currently be sent by email or Discord.
The idea is that you shouldn’t have to constantly open a dashboard and manually check every node.
Payout analytics
Payout information has also been expanded.
V2 tracks estimated earnings as the month progresses and then uses the satellite settlement information once the month has closed.
It also tracks wallet balances and gives you a historical view rather than just showing the latest value.
Website speed & performance
I’ve also put considerably more focus into the performance of the website itself.
The V2 frontend and backend have been rebuilt with the aim of keeping the dashboard responsive even when you’re monitoring multiple nodes and have a large amount of historical data.
Rather than loading everything at once, the application is designed around retrieving the information that is actually required for the current view.
The goal is for the dashboard to remain fast as the amount of data grows — rather than becoming progressively slower as you add more nodes and history.
Performance is also something I’d particularly like feedback on during the testing phase.
If you notice something loading slowly, behaving strangely or simply think something could be made more efficient, please let me know.
Privacy / security
This is another area where the original thread had some very valid concerns.
The new architecture means your Storj node does not need to accept incoming connections from StorjDashboard.
The agent runs alongside your node, reads the information locally and sends the monitoring information out.
This means it can work with:
-
CGNAT
-
Dynamic IP addresses
-
Residential connections
-
Multiple nodes
-
Nodes on different networks
without needing to expose the node itself.
Network statistics
V2 also brings Storj network statistics into the dashboard so that you can compare what your own nodes are doing against the wider network.
This should make it easier to put changes in your own node’s performance into context.
Why V2?
This isn’t really intended to replace the existing Storj node dashboard.
The idea is to provide something complementary for SNOs who want a centralised monitoring and analytics dashboard for their own nodes.
The original StorjDashboard started several years ago from this thread, and a lot of the direction of the project has actually come from the feedback here.
Some of the requests made years ago — historical data, better alerts, multiple nodes, easier setup and a locally reporting architecture — have now effectively become core parts of V2.
There is still plenty more I want to add, and the testing phase is a big part of deciding what comes next.
If you’ve previously tried StorjDashboard and stopped using it, I’d particularly like to know why and whether V2 addresses the reason you stopped.
If you’re currently using another dashboard, I’d also be interested in what information or functionality you think is missing.
Give V2 a try
V2 Website: https://v2.storjdashboard.com
Documentation: https://v2.docs.storjdashboard.com
Dashboard: https://v2.my.storjdashboard.com
If you’d like to try it, please do — V2 is open for testing and I’d love to have as many SNOs as possible using it.
And if you find a bug, have an idea, dislike something or simply think something could be done better, please let me know.
The feedback from this community has helped shape StorjDashboard from the beginning, and I’d like V2 to continue in the same way.
Thanks to everyone who has tested, provided feedback and supported the project so far.
Cheers,
ItsHass
