mrhead

edit: I fixed the problem, but unfortunately can be of little help to anyone who might also have the problem. I did the no-no of doing many things at once, and am unsure what finally righted it... I renamed my shares (removed leading caps, removed spaces), changed my apps folder to the more-standard "appdata" rather than a hidden ".Apps" folder, deleted the transmission docker and re-installed it. After all that, I also adjusted my umask value to the default "2" in settings.json. Things now persist after a docker (or server) restart. I've just switched over to this dockerized version of Transmission after using the plug-in version for years. I have it installed to my cache drive, within /mnt/cache/.Apps/. Likewise, all of its main system paths are set up to be there. It also has a number of paths set up so that it can see my main media user shares. The relevant Docker paths as configured are: /config /mnt/cache/.Apps/transmission /downloads /mnt/cache/.Apps/transmission/downloads /watch /mnt/cache/.Apps/transmission/torrents/ /Music /mnt/user/Music/ ...etc media... ...etc... Spent the better part of a day re-downloading and re-adding all my torrent files to it so that I could resume seeding, after which point everything was running good and fine. About a day later (yesterday), I updated the server from OS 6.1.7 to 6.1.9, and rebooted. Came back to an empty list of active torrents in both the web GUI and in Transmission Remote GUI. The /transmission/torrents/ path is still populated with "*.torrent.*added" files, the /transmission/resume/ folder still has "*.resume" files. None are actively running anymore, though. As a simple troubleshooting step, I added back a torrent file (just one this time!), had it successfully verify and resume seeding, then restarted the docker. Same symptom, the list of torrents in the GUI was completely empty. So, it seems unrelated to the server reboot and simply a result of rebooting the docker container. Any insights? Let me know if I left out any settings or other details that might be necessary to help troubleshoot. Thanks.