linuxserver / docker-radarr

GNU General Public License v3.0
611 stars 103 forks source link

[BUG] Connection refused (api.radarr.video:443) #204 #217

Closed madereddy closed 10 months ago

madereddy commented 10 months ago

Is there an existing issue for this?

Current Behavior

[v5.0.1.7993] System.Net.Http.HttpRequestException: Connection refused (api.radarr.video:443)

Expected Behavior

Tried to comment on issue: https://github.com/linuxserver/docker-radarr/issues/204 but its been marked closed. Found the resolution to the issue.

Create a new rule in traffic management to allow radarr to connect to the api.

Action: Allow Category: Domain Name Domain Name: +Add: api.radarr.video Target: (select the radarr server) Schedule: Always

Steps To Reproduce

Add from Ombi to Radarr

Environment

- OS: Synology DSM 7
- How docker service was installed: Synology Container Manager

CPU architecture

x86-64

Docker creation

Default run mounting drives and opening port 7878

Container logs

[v5.0.1.7993] System.Net.Http.HttpRequestException: Connection refused (api.radarr.video:443)
 ---> System.Net.Sockets.SocketException (111): Connection refused
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
   at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.attemptConnection(AddressFamily addressFamily, SocketsHttpConnectionContext context, CancellationToken cancellationToken) in ./Radarr.Common/Http/Dispatchers
github-actions[bot] commented 10 months ago

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

j0nnymoe commented 10 months ago

This "issue" isn't anything to do with the container and as documented in the previous issue that its outside factors that users have in place causing the problem.

madereddy commented 10 months ago

@j0nnymoe I just wanted to be able to update the previous ticket with the solution. Would you be able to update it in ticket for other users run across the same issue? Im fine with this ticket being closed.

j0nnymoe commented 10 months ago

Personally, I would expect to see something like this in an faq of radarr itself because you'd experience this same issue regardless of it being in a container or not. I would see if they have an faq you can submit it to.

Roxedus commented 10 months ago

This is already covered in radarrs documentation.

j0nnymoe commented 10 months ago

Even better.