forest vapor
Hey. Today I found myself with Jellyseer unable to connect to Radarr, in the "Services" tab when I press the "Test" button. It worked when I set it up, and Sonarr is working just fine. All Jellyseerr, Radarr and Sonarr are in the same subnetwork, and I don't have any proxy or anything setup. Is this a known issue? And, is there any fix for this?
Thank you very much
wise linden
This is a configuration issue. Not a bug. Radarr works fine. Without logs cant tell though
Please send logs
And compose.
forest vapor
Hello! Thanks for your response. After a while I decided to restart my NAS, and now it's Sonarr the one not working, and Radarr is just fine. Here is my Sonarr, Radarr, etc. compose:
version: "3.8"
services:
sonarr:
image: lscr.io/linuxserver/sonarr:latest
container_name: sonarr
environment:
- PUID=1000
- PGID=10
- TZ=Europe/Madrid
volumes:
- /volume1/docker/arr-stack/sonarr/config:/config
- /volume1/Media:/Media
ports:
- "8989:8989"
restart: unless-stopped
networks:
- media-net
radarr:
image: lscr.io/linuxserver/radarr:latest
container_name: radarr
environment:
- PUID=1000
- PGID=10
- TZ=Europe/Madrid
volumes:
- /volume1/docker/arr-stack/radarr/config:/config
- /volume1/Media:/Media
ports:
- "7878:7878"
restart: unless-stopped
networks:
- media-net
prowlarr:
image: lscr.io/linuxserver/prowlarr:latest
container_name: prowlarr
environment:
- PUID=1000
- PGID=10
- TZ=Europe/Madrid
volumes:
- /volume1/docker/arr-stack/prowlarr/config:/config
ports:
- "9696:9696"
restart: unless-stopped
networks:
- media-net
flaresolverr:
image: ghcr.io/flaresolverr/flaresolverr:latest
container_name: flaresolverr
environment:
- TZ=Europe/Madrid
ports:
- "8191:8191" # Default API port for Prowlarr/Sonarr/Radarr
restart: unless-stopped
security_opt:
- no-new-privileges:true
networks:
- media-net
networks:
media-net:
external: true
Jellyseerr:
version: "3.8"
services:
jellyseerr:
image: ghcr.io/fallenbagel/jellyseerr:latest
container_name: jellyseerr
environment:
- PUID=1000
- PGID=10
- TZ=Europe/Madrid
- LOG_LEVEL=debug
volumes:
- /volume1/docker/jellyseerr/config:/config
ports:
- "5055:5055"
restart: unless-stopped
networks:
- media-net
networks:
media-net:
external: true
Logs:
> jellyseerr@2.7.3 start /app
> NODE_ENV=production node dist/index.js
2025-12-23T17:47:43.228Z [info]: Commit Tag: $GIT_SHA
2025-12-23T17:47:46.528Z [info]: Starting Jellyseerr version 2.7.3
2025-12-23T17:47:50.345Z [debug][Settings Migrator]: Checking migration '0001_migrate_hostname.js'...
2025-12-23T17:47:50.348Z [debug][Settings Migrator]: Checking migration '0002_migrate_apitokens.js'...
2025-12-23T17:47:50.351Z [debug][Settings Migrator]: Checking migration '0003_emby_media_server_type.js'...
2025-12-23T17:47:50.353Z [debug][Settings Migrator]: Checking migration '0004_migrate_region_setting.js'...
2025-12-23T17:47:50.354Z [debug][Settings Migrator]: Checking migration '0005_migrate_network_settings.js'...
2025-12-23T17:47:50.356Z [debug][Settings Migrator]: Checking migration '0006_remove_lunasea.js'...
2025-12-23T17:47:50.385Z [info][Notifications]: Registered notification agents
2025-12-23T17:47:50.485Z [info][Jobs]: Scheduled jobs loaded
2025-12-23T17:47:50.714Z [info][Server]: Server ready on port 5055
2025-12-23T17:48:00.006Z [debug][Jobs]: Starting scheduled job: Download Sync
2025-12-23T17:48:29.361Z [debug][Image Cache]: Something went wrong caching image. {"errorMessage":"connect ECONNREFUSED PUBLICIP:8096"}
2025-12-23T17:48:31.267Z [error][Sonarr]: [Sonarr] Failed to retrieve system status: connect EHOSTUNREACH PUBLICIP:8989
2025-12-23T17:49:00.008Z [debug][Jobs]: Starting scheduled job: Download Sync
2025-12-23T17:49:53.083Z [error][Sonarr]: [Sonarr] Failed to retrieve system status: connect EHOSTUNREACH PUBLICIP:8989
Again, thank you very much for your help
wise linden
If you put them in same docker subnet
Why are you using public ip to connect?
Use the container name
That should work
You can confirm too by docker exec -it jellyseerr ping radarr
If it works then its in same subnet properly
forest vapor
I tried with the container name as well, but didn't work either
I'm not too sure why
Also the fact that one works and the other doesn't, and switch when I restart my NAS is really weird
wise linden
Also the fact that one works and the other doesn't, and switch when I restart my...
Its docker networking related
Can you show me the output of docker exec -it jellyseerr ping google.com
forest vapor
Okay I think its more or less sorted out. As you pointed out, it was a network/firewall issue.
bridge-nf-call-iptables = 1
Was set to one, instead of 0
