-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Bazaar failing to load and getting timeouts since last update. #136
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Get the docker run for the container. https://docs.linuxserver.io/general/how-to-get-support/#how-to-get-support |
I'm experiencing the same issue. Here is the link to my docker run. https://gist.github.com/wcorybeck/816b8049d9c731c3a55d9163611f3916 |
I'm also experiencing this. Tried pulling the image minutes before posting but did not change the result: bazarr:
container_name: bazarr
image: linuxserver/bazarr:latest
restart: always
environment:
PUID: 1000
PGID: 1000
TZ: America/New_York
volumes:
- ./bazarr:/config
- media:/media This is the config I've had since I started using bazarr a few months ago. I see this error message for every file in my library:
At the bottom of the output, I see this:
It looks like this bug has already been fixed in the latest release of the dependency: ratoaq2/knowit#87 Seems Bazarr needs to upgrade. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has definitely not been resolved |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Dunno if it's the same issue, but I'm getting this error on start up, and it doesn't work.
|
Is there an existing issue for this?
Current Behavior
Docker timing out or not loading, image is starting in unraid but not accessible have to restart docker to get access Errors in logs.
Expected Behavior
expected to run and be accessible no responsive since last update.
Steps To Reproduce
Faulty since last update.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: