I notice an issue with supervisord not being on pid 7 like it was previously: I have tried rolling back all the way to 19.1-1-02 and the same results. Just within the past day or two I can no longer connect to the web ui. Thanks for this, i am having unpacking issues also.ĭo i have to delete the old NZBget, before i use this method to get the old one?
This is because of the change in the appdata location, basically starting fresh. Once you've started the container you will need to configure NZBGet again via its internal settings page (news server, paths, etc). The most important part is the AppData Config Path setting, so make sure you change that form the template value.Ĥ. Make the changes to get the previous tag going - i used 19.1-1-02 ( )īelow is a screenshot of how i changed it. Basically, this just restores all the settings you used last time, but is also the cause of you getting the 404 when checking out the 19.1 tag: you are most likely mixing the config data.ģ. From the template dropdown, select "binhex-nzbget", presuming you havent already deleted the template. Go to your docker page and add a new containerĢ. I havent used SAB in years now, so maybe they improved on that factor since.Īnyway, here are some steps you can try to help get NZBget going:ġ.
I just find NZBget the easiest to configure and use. Does anyone know if SAB has this problem? Any reason to stick with NZBGet? I just went back to the current version and just restart NZBGet every day or two.
Secure cert for nzbget how to#
I don't know what you mean or how to do that. 15:20:23,481 INFO success: nzbget entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)Īnyone have any good ideas on how to troubleshoot/start over/other logs to look in?
15:20:21,471 INFO supervisord started with pid 7 15:20:21,465 INFO Set uid to user 0 succeeded 15:20:21,465 INFO Included extra file "/etc/supervisor/conf.d/nf" during parsing 15:20:18.683927 Permissions already set for volume mappings This is all I see in the log file of the docker:
0 kommentar(er)
