Have you looked for the previous home directory and removed files from it? The files to back up and remove are config.xml, cert.pem, key.pem, https-cert.pem, https-key.pem, and the index directory. Google tells me that Syncthing files by default should be in a Docker-specific location such as /var/syncthing.
Under Synology, the packages are located at /var/packages/ but there is no folder “syncthing**”** as with another NAS.
I removed all fragments with the results of
find / -name “*syncthing*”
Your post gave me the idea to do this, thank you!
I also fixed the fact that the previous installation was on volume1 and now volume2 is the default for packages (to do this, change the symbolic links under /usr/syno/etc/packages/ the link.
However, deleting the old reference there did not help either.
Unfortunately, the log centre only contains information about successful downloads/installations of packages.
Now I can only conclude that there is still a database entry that cannot be found using find.
And what exactly do you see when “installation fails”? Have you tried with the synopkg manager on the command line? Does it work when installing from the spk file after downloading it manually from SynoCommunity?
You may have better chances getting help on the SynoCommunity channels, e.g. Discord, regarding installation troubles.
I can’t imagine anything “leftover” from the previous installation being the cause here, unless you have a specific error message hinting toward that.
When I was on the community page before posting here to perform the manual installation you mentioned, I didn’t recognise the system of different spk files (the downloads were just tags to me ).
Thanks to your tip, I now recognise this error, have downloaded the correct file and been able to install it manually.
And YES!
Syncthing is now back on the NAS.
So it was a problem in the package manager, but I don’t care about that now…