Back but have some Q's

Yes. Think i have checked 10 times now

Don’t waste time with multinode dashboard bugs. No one will fix it. :roll_eyes:

at least i know its a bug

and to be hones i watch the individual dashboards more than the multinode one so might even delete it

hmm if no one chimes in then i might look at doing a gracefull exit on 3 of the nodes and wait for them to delete data and then allocate space to the first node instead, just need to figure how to do that in a compose file

EDIT:

so it cant be undone…. some thoughts: if i ever want to setup a node behind another Ip is is better just to start fresh again ? why i thought of gracefull exit is more because i want to behave nice and civil and not being an ā€œA55HOLā€

EDIT2:

so if shorter than that (which) is my case then i just stop and delete the node?

For the network it doesn’t matter if exit was graceful or not, repair work will be the same. So ask yourself if accumulated payment (cents I guess) is worth to do a graceful exit.

i dont mind if it takes 30 days, but if i cant do it due to the nodes being less than 6 months its a no brainer to me… it would just be pull the plug

According to stats only 4 percent of exits are graceful.

so not a lot do it…. but if i want to take the plunge, should i do it with a command in cli/prompt? or can i edit my compose file and do it that way? just like the setup option when setting up the node?

Remove node from compose file and delete data folder.

yes, but as a test or learning experience how would i have started the exit procedure from either compose file or cli

EDIT: the guides says: storagenode exit-satellite

but is that a command to be entered after ssh in to the node? or how? feels like the guide is missing a step

There should be four - two on the one page and two on the next one. Perhaps you do not see a scrolling.

Yes, you need to open a terminal and use the provided commands, see

hmm, worked as the guide said…. i assume the error is due to the low age of the node

root@bo-omv:~# docker exec -it storagenode2 /app/bin/storagenode exit-satellite --config-dir /app/config
2025-11-21T08:26:11Z    INFO    Configuration loaded    {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2025-11-21T08:26:11Z    INFO    Anonymized tracing enabled      {"Process": "storagenode"}
2025-11-21T08:26:11Z    INFO    Identity loaded.        {"Process": "storagenode", "Node ID": "1ueCWYzkFRWX4CgZ8gJ4XMhMEcGoyfi6DdP3eEpM35sNHwWGnV"}
By starting a graceful exit from a satellite, you will no longer receive new uploads from that satellite.
This action can not be undone.
Are you sure you want to continue? [y/n]
 :y
Domain Name                  Node ID                                              Space Used
saltlake.tardigrade.io:7777  1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE   3.78 GB
ap1.storj.io:7777            121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6  5.90 GB
us1.storj.io:7777            12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S  126.28 GB
eu1.storj.io:7777            12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs  30.50 GB
Please enter a space delimited list of satellite domain names you would like to gracefully exit. Press enter to continue:
saltlake.tardigrade.io:7777 ap1.storj.io:7777 us1.storj.io:7777 eu1.storj.io:7777
You are not allowed to initiate graceful exit on satellite for next amount of months:
Error: You are not allowed to graceful exit on some of provided satellites