Open mediaman88 opened 1 year ago
Our Dev has recommended NSSM, but I have always used Task Scheduler and a simple .bat file. We can't support NSSM since it's a program ran by others.
I understand the NSSM support part, but why would it starting via that service cause it to ignore existing configuration files and open up as if it were completely new instance even though it had already been fully configured and working for many days in a row?
I have no idea since I don't use NSSM.
I can tell you a simple Task Scheduler App that runs at Start up works.
C:\Windows\System32\cmd.exe /c C:\Users\me\Documents\xteve.exe
xteve.bat
I am running the latest version of xTeve and have a backup instance of it running on another computer. I am using it to feed Plex. Once computer is running W10 and the other W11. I have tried running it as a service NSSM and just in the Startup folder. I spend the time building out all the mappings and things work great for about a week, then out of the blue it resets. When I login to the web portal I am presented with the Configuration screen and cannot move past it without starting as a new server.
This happens on both my main server and my backup server.
This started happening when I installed it via NSSM.