There definitely something wrong with the QNap app even when using the folder picker. Stuck on the last page of the wizard. Moved identity files out initial folder no luck played for 2 hours.
I felt courageous Managed to get a remote ssh working and installed node through docker instead ! Success or so I thought! Node ran for 24h downloaded 100gb I was happy as Larry !!! On a first attempt!
Tonight I had to stop the container ( gracefully) to add the autorestart in gui and now indenty.ca cannot be found. I changed nothing and other than slider button, stop and started button. Restarted the NAS, replaced identify with originals. Still the identy folder can’t be found. Even though it here.
I do not recommend to use GUI. They usually does not provide a consistent experience and you cannot be confident that during update they do not break something.
However, I think, the change was made earlier, but the container were not re-created: if follow the CLI, you need to stop and remove the container, then run it again with all your parameters, include changed ones.
So, the change was made, but container not re-created. When you specified start after reboot - they actually added a new parameter to the resulted docker run command, so this time the container were re-created and applied changed parameters altogether.
Very often a GUI just a wrapper around the CLI commands (especially in Linux), I think this is the case for the GUI on QNAP.
So I believe the GUI “forgot” some parameters when it re-created a container. This is not the last bug and you likely will meet more if you would continue to use it.
Usually the GUI uses not recommended parameters for binding, for example - they uses a very dangerous -v docker option instead of safe --mount, earlier our software did not detect that data location is empty and started container from scratch, if the OS did not mount the disk for any reason, the docker were happy to create an empty volume instead (because the -v option is designed to do so). As result - your node were disqualified for lost data. Now we detect if mount point is empty and crash the container if it is empty (this is why there a SETUP step - it creates special file, and it can be created only with SETUP, so if file is missing or not readable or not writeable - we crash the container to safe the node from disqualification).
Thus I recommend to avoid using a GUI and use a CLI instead, where you control what parameters for your container will be specified.
Also you must have a static ip to the outside and open the doors of the router. If you don’t have a static ip you can use noip.
The nas also has a fixed ip in the local network, it is not in dhcp, otherwise it changes 192.168.1.2