Closed Berry-95 closed 4 days ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
I've just seen similar issues with linuxserver-sonarr, -readarr & -speedtest-tracker images so I've pinned them all to their previous releases for now.
Post some hardware information
CPU: Intel(R) Celeron(R) N5095A @ 2.90 Memory: 16GiB (SODIMM DDR4 8GiBx2 2667 MHz) Disk: Hikvision E100N 512GB M.2 2280 SSD
@Berry-95 what builds did you find to be working? I'm trying to understand why I'm getting http timeouts with readarr and prowlarr and the upstream discussion suspects a ".net networking issue". Wondering if a previous version is known to be working.
@andrewgdunn "Do you have a better idea of what's happening then?"
I suspect the issue being due to .NET because it started to appear after the bump to 6.0.19 or so, and now I don't have the same issue with 8.0. I still get rare occurrences of Http request timeout
that I can't fix with a test indexer but the issue fixes itself eventually even if I don't restart the container.
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.
Is there an existing issue for this?
Current Behavior
Running latest version results in a ConsoleApp: EPIC FAIL! loop.
Expected Behavior
Running previous version 1.17.2.4511-ls69 results in successful startup
docker run -d \ --name=prowlarr \ -e PUID=1000 \ -e PGID=1000 \ -e TZ=Etc/UTC \ -p 9696:9696 \ -v ./data:/config \ --restart unless-stopped \ lscr.io/linuxserver/prowlarr:1.17.2.4511-ls69
Docker log:
Steps To Reproduce
docker logs prowlarr
Environment
CPU architecture
x86-64
Docker creation
Container logs