[smakovits]

however, if I test the path that "timed out" it opens fine, so apparently this could be related to me not being able to access emby when it is running. I can't and neither can kodi...but when script isnt running it is fine, so the question is, why in emby docker locked up when the script is executed.

15 threads is probably too high, try 1 download thread and work upwards from there until emby no longer responds.

Does emby have a log? If so maybe it has information that explains why emby has keeled over.

That did it. Set threads to 1 and it works. Any idea why this is? Is it a docker restriction you think or computer hardware running docker?

Now to get things executed with a cron task.

Also, is there ever a time where I would need to run big c over little c? Like a use case, since big c is disabled unless overridden, just curious.

And thanks!