-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Unhandled Exception rises after few seconds, server closes - starting after version V1.5.0-LS280 #149
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
I have the same problem. The last two versions v1.5.0-ls283 and v1.5.0-ls284 don't work, I had to revert to v1.4.5-ls282. |
v1.5.0-ls284 is working fine for me. The exception (
|
In Settings > General > Host > Address I had the IP address of my server. When I changed it to an asterisk in v1.4.5-ls282, it now works in v1.5.0-ls284. Thanks @brycied00d for pointing me in the right direction :) |
I can confirm that was the issue. The IP address in the config was not set to 0.0.0.0, but my internal servers' IPs were. You have to let the container recreate the config file and then copy and paste your Providers, Radarr, and Sonarr, to make it work and keep everything intact. Thanks! [migrations] started [custom-init] No custom files found, skipping... |
Is there an existing issue for this?
Current Behavior
after version V1.5.0-LS280 the container starts, but then after a few seconds the following error arises, server is not accessible but the container keeps running:
2024-12-27 22:58:17,404 - root (7903b5e4bb28) : ERROR (server:73) - BAZARR cannot start because of unhandled exception.
self.server.close()
Expected Behavior
Webserver accessible after container running
Steps To Reproduce
after running a few seconds the webserver closes, permissions on volumes are unchanged, the error disappears on version LS280, after this version the same error appears
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: