Look in File Station to make sure that the identity files are at the path you selected in the app. Can you share screen shots of both FIle Station(expanded to show the directory tree of your identity files) and the path selected in the app?
But still not working, now seems that the container not able to start.
I have the port forwarding and If I open the port 8080 I can login in to my QNAP. ¿What am I missing?
You need to specify the different port for the storagenode container. The default port is 28967, so, please, use it. The 8080 port is used by something other.
I have no QNAP on my hands so, I cannot guide you through UI.
It’s much simpler to just run a CLI setup instead of any GUI, just login via ssh: https://documentation.storj.io/setup/cli/storage-node
I created the identity and put it on /share/Public/Identity/storagenode but it is not finding it. Where do I have to move it? /app/identity Where is this path?
Also make sure to do not use any word processors to form the docker run command - they converts double dash -- to hyphen –, straight quotes " to curly ones like “ and ”, those symbols are not valid for the command line. Thus please use a plain text editor instead, for the bash it’s nano.
With this procedure there is no reason that your node does not work.
And I forgot, start by removing the QNAP STORJ application, it doesn’t work well and I think it’s obsolete.
Also delete all Storj containers already created.
I spent a lot of time with this application and lost a lot of time.
I have 3 nodes and made at least 10 to 15 installations before I fully understand how it works. The simplest is the procedure I just described.
@enrique@vincetheblackPlease, do not use a GUI! You can lose the node using it!
The reason is simple - any GUI on any NAS is used dangerous option -v to mount storage to the container instead safe option --mount type=bind. The outcome of -v option is - if your disk is not mounted for some reason, the -v option will create an empty temporary volume to store customers’ data!
When the container got deleted, the temporary volume will be deleted too, include customers’ data. Thus your node will start to fail audits and finally can be disqualified.
The current version of the storagenode should stop, if the data mount point doesn’t have a special file and structure which are created only on setup, however, if you run setup in the second time, when the mount point is empty you can start the node and node could be disqualified for losing customers’ data.
So, please, be extremely careful, if your working node which you run via GUI is occasionally stopped and complains about missed special file and/or structure - do not run the setup in the second time!
I will follow the manual update guide for stop and restart the container but with the rights commands. I am seeing that the containers launched with beta version of storagenode so I will try again with the latest.
Hello @Alexey
Thank you very much for your help and involvement.
On my Qnap the volumes are not deleted when I delete the container, this is already a good thing. Before I put watchtower on, to upgrade I would delete the container and then create a new one, luckily my volumes have never been deleted.
Is there a docker command to know how the mounts were done?
How does Watchtower do the update? Removing and re-installing a container or updating Storj inside the existing container?