-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
500 Internal Server Error nginx issue #17
Comments
Do you have a huge amount of files do scan ? Are you using
Bridge is usually the choice. In fact, you should be able to use the container with default template settings. |
Yes, I will try to reduce the folder to scan
No, using the default WEBUI link by right click on the docker which is :5800 |
Do you see a high CPU usage when it freezes? Do you have an idea of how many files you have to scan ?
The default port is 7821, unless you changed the network type to something else than Bridge ? |
CPU usage seem to be still in working state around a average of 50% work load each threads (14 threads) first tried got around 4m files get stuck at 100% Current Stage / 67% All stages (Analyzed Partial Hash ) using the duplicate files search
I reinstalled the docker and its now showing 7821 instead of the 5800 when I go to the WEBUI |
Hi,
so using the latest Docker version on UnRaid 6.11.5
issue:
when the docker freeze (get stuck when scanning duplicate files, I am new and first time using it and still unable to finish a complet scan yet lol) or when I stop the container, I always got 500 Internal Server Error nginx issue on my UnRaid WebGUI and/or freeze my UnRaid WebGUI (can takeseveral time before unfreeze)
I am not using the Reverse Proxy and don't know how to use it either
is it better using this docker on Bridge or Host?
any clue why that happen?
Thanks
Best Regards
The text was updated successfully, but these errors were encountered: