Can't connect to radarr/sonarr

[ember niche]

Hi, I have an installation on debian with swizzin and it seems to work fine. I want to add Overseerr so I decided to use docker and when I want to connect Overseer and radarr or sonarr I have the message Failed to connect to Radarr.. I can go on radarr using this : https://my_ip/radarr/ and in settings i have these settings and I entered the good api key. Do you have an idea of why it doesn't work ? thanks

[foggy robin]

From the url you said it looks like you're accessing
https://123.123.123.123/radarr for example

With no port defined and with https

This would mean that you'll need to use the port 443

And make sure to tick use ssl checkbox

[ember niche]

Do I need to use my local ip like 192.168.xx.xx or 127.0.0.1 ?

with these settings it doesn't work. Am I missing something ?

[signal bronze]

Radarr port is not 443

It’s 7878

Sonarr is 8989

[ember niche]

Fallenbagel said to use port 443. What is the difference ?

(it doesn't work too with 7878)

[signal bronze]

443 is the port used for HTTPS internet traffic. All websites use 443, for example.

So if your radarr was hosted at https://website.com/radarr you would use 443

But if you are using your local IP address, you should use radarrs actual port number.

By default, this would be 7878 unless you have changed it.

What exactly do you type in to your browser to get to radarr?

[ember niche]

Ok I understand. Actually I just use this https://192.168.1.62/radarr

[signal bronze]

Try removing /radarr from URL Base and putting it on to the end of the IP address

[foggy robin]

Their setup is through swizzin

They use without port to access using https

Its setup using 443

[foggy robin]

This url is using 443

And https

So it definitely is port 443

They are not using a default radarr setup.

And swizzin uses url base

[foggy robin]

If this is how you access radarr

Then you should definitely check use ssl

And use port 443

With url base /radarr.

[foggy robin]

If this was a default setup that would be true.

And yes you can definitely have an https with ip. That's very common in setups like these

[signal bronze]

Ahh fair enough. Missed that in the OP!

Apologies for causing confusion 🙂

[ember niche]

Do i miss something ?

[foggy robin]

Does test not work still?

[ember niche]

no sadly

[foggy robin]

Do you access radarr with https://192.168.1.62/radarr?

[ember niche]

yes

[foggy robin]

Can you show me how you deployed overseerr

[ember niche]

using docker

with this

services:   
  overseerr:     
    image: sctx/overseerr:latest     
    container_name: overseerr     
    environment:       
      - LOG_LEVEL=debug       
      - TZ=Asia/Tokyo           
    ports:       
      - 5055:5055     
    volumes:       
      - /opt/overseerr/config:/app/config     
    restart: unless-stopped```

and the command docker compose up -d

[foggy robin]

Add network_mode: host

Remove

ports:
   - 5055:5055

And redeploy

[foggy robin]

And try with this

[ember niche]

I'm stuck on Testing..

[ember niche]

Why when I delete this I still acces to overseerr with 192.168.1.62:5055/setup ?

[foggy robin]

Bevause 5055 is default port

[foggy robin]

Check logs

[ember niche]

where can I see them ?

[foggy robin]

Ports is set in yaml when you're using bridge mode. To expose the internal container port which is 5055 to host's 5055

So you didn't change port

[foggy robin]

In your config folder

/opt/overseerr/config/overseerr.log

Or

docker compose logs

Check what error you get after you press test

[ember niche]

I have this error overseerr | 2025-04-23T20:57:28.989Z [error][Radarr]: [Radarr] Failed to retrieve profiles: self-signed certificate

Idk if it's the good one

Maybe I should remove swizzin and create my seedbox from scratch

[foggy robin]

Ah self signed certs

You'll need to allow the cert

[ember niche]

How can I do this ?

[foggy robin]

There are two ways. Safest way, you'll need to find the cert from swizzin to pass it to nodejs

Easiest way is to allow all kinda option tho that should be done with caution

[foggy robin]

Best method is always this

[ember niche]

I'll try the second one just to see if it works and I think I will reinstall everything

How can I allow all option ?

[foggy robin]

Add this as an environment variable to docker compose

NODE_TLS_REJECT_UNAUTHORIZED=0

[ember niche]

I'll try it

It works ! Do you have a good guide to install everything from scratch ?

[foggy robin]

Best would be to look at their docs. You can also use linuxserver.io docs with *arr