Why always these 1 errors

Node Operators troubleshooting
1

So i get this error while setting up my node.

stat config/storage/blobs: no such file or directory
— stat config/storage/temp: no such file or directory
— stat config/storage/trash: no such file or directory
AND NO MATTER WHAT I DO I FAIL ofcourse cause im a noob in anything linux
if you’d like i would give anyone of you SSV access so you could fix it cause my coder brother doesn’t wanna.
heres what ai asked me to do and i did.

Filesystem and Permissions Troubleshooting

  • Checked existence and permissions of your storage directory (/home/catdrout/storj-ultimatetest/storage).
  • Manually created missing subdirectories (blobs, temp, trash) when the node failed to create them.
  • Fixed ownership and permissions recursively on your storage and config directories using:
    • sudo chown -R catdrout:catdrout ...
    • sudo chmod -R u+rwX ...
  • Removed problematic files (storage-dir-verification, trust-cache.json) that were created with the wrong permissions or empty content.

3. Clean Directory and Config Attempts

  • Tested file creation in the storage directory to confirm it was writable.
  • Created a fresh storage directory and set correct permissions.
  • Tried running the node with a new, empty config directory.

4. Process and System Checks

  • Ensured no other Storj node processes or Docker containers were running.
  • Checked for SELinux/AppArmor denials (none found).
  • Confirmed there were no disk space or inode issues.

5. Node Command Adjustments

  • Attempted running the node both as your user and as root (to isolate permissions problems).
  • Discovered the need to specify --storage.path explicitly, since without it, the node tries to use a storage subdirectory under the config directory.

6. Current Status

  • The node is now failing with errors about missing blobs, temp, and trash directories in the storage path.
  • The root cause: The node needs the --storage.path flag to be set to your intended storage directory.
  • Please help me im just a kid.
2

What instructions did you follow to install your node (like what web page)? Was it this?

The very general steps are to get an Auth Token (basically a string from a web page). Then create your Identity Files (that make your node unique) and apply your Auth Token to them. Then run the Setup command (docker run --rm -e SETUP=“true” …) . Then start the node (docker run -d --restart unless-stopped …)

If the node is complaining that it can’t find directories… my guess is you may have skipped that Setup step.

1 Like
3

nope it worked perplexity used old outdated data
i spent hours on end trying to fix this thanks ! but one problem im having now is accessing its web dashboard. yes i have porrforwarded and i asked my isp for a public ip they gave me

4

The main/default port that the node uses (28967) that you want accessible from the internet… is different from the web-dashboard port (14002) the you DON’T want on the Internet.

The default docker run command will only allow you to see that dashboard from the same system running the node. If you want to see it from other computers in your home network: you can change the run command (remove the “127.0.0.1:” restriction)

To be clear: you will need port 28967 port-forwarded in through your firewall/router. But you DON"T want to port-forward port 14002. You don’t need random strangers on the web looking at your dashboard too :slight_smile:

2 Likes