Skip to content

Connect your apps to each other

How-toDeployrr v6.0+CurrentApp networkingDockerMedia

Apps like Sonarr, Radarr and Prowlarr ask you for a host name and a port when you add a download client, an indexer or another app. This page tells you what to type.

  • Both apps are installed with Deployrr and running. See the Quick start.
  • You can open the web page of the app where you enter the connection. For example, Prowlarr, if you want to add Sonarr to it.

Use the container name of the other app and its internal port, joined with a colon:

container-name:internal-port

This works when both apps are on the same Docker network. Most apps installed with Deployrr are on the default network, so this is the normal case. The same rule applies to the Forward Hostname / IP box in Nginx Proxy Manager.

Do not type localhost or 127.0.0.1. Inside a container, those point to the container itself and not to the other app.

To understand how container names and the Docker host IP work together, read UDMS part 14: connecting apps by container name or Docker host IP (manual setup; it builds its own Compose file, not the Deployrr files).

  1. Look up the container name and internal port of the app you want to reach. Use the table below for the common media apps, or the App reference for every app.

    App Enter this Container name Internal port
    Radarr radarr:7878 radarr 7878
    Sonarr sonarr:8989 sonarr 8989
    Lidarr lidarr:8686 lidarr 8686
    Bazarr bazarr:6767 bazarr 6767
    Prowlarr prowlarr:9696 prowlarr 9696
    qBittorrent qbittorrent:8080 qbittorrent 8080
    SABnzbd sabnzbd:8080 sabnzbd 8080
    Plex plex:32400 plex 32400
  2. Open the web page of the app that needs the connection.

  3. Enter the container name as the host and the internal port as the port.

  4. Turn SSL or HTTPS off.

  5. Use the Test button, then save.

Example: Prowlarr to Sonarr, Radarr and Lidarr

Section titled “Example: Prowlarr to Sonarr, Radarr and Lidarr”

Prowlarr keeps your indexers in one place and sends them to Sonarr, Radarr and Lidarr. You add each of those apps to Prowlarr once.

  1. In Sonarr, go to Settings > General and copy the API Key from the Security section.
  2. In Prowlarr, go to Settings > Apps and click +. Pick Sonarr.
  3. Fill in the form:
    • Sync Level: Full Sync keeps Sonarr’s indexers the same as Prowlarr’s, and overwrites changes you make to them in Sonarr. Add and Remove Only adds and removes indexers when you add or remove them in Prowlarr, and doesn’t sync other changes.
    • Prowlarr Server: http://prowlarr:9696. This is the address Sonarr uses to reach Prowlarr, so use the container name, not localhost.
    • Sonarr Server: http://sonarr:8989. For Radarr and Lidarr, this field is called Radarr Server or Lidarr Server.
    • API Key: the key you copied in step 1.
  4. Click Test, then Save. Prowlarr sends its indexers to Sonarr when you save.
  5. Repeat for Radarr (http://radarr:7878) and Lidarr (http://lidarr:8686), with each app’s own API key.

In Sonarr, Radarr or Lidarr, check Settings > Indexers. The indexers from Prowlarr have (Prowlarr) at the end of their name. Prowlarr only sends an indexer to an app if the indexer has categories for it. For example, a TV-only indexer doesn’t show up in Radarr or Lidarr.

If you added indexers by hand in Sonarr before, you now have each one twice. Turn off the old entries without (Prowlarr) first, then delete them once searches work.

To send the indexers again after a change, click Sync App Indexers on Prowlarr’s Settings > Apps page.

In Sonarr, add qBittorrent as a download client. Use these values:

  • Host: qbittorrent
  • Port: 8080

The port is 8080, not the port you use in your browser. SABnzbd also uses 8080 inside its container. The host name tells them apart.

Each app’s Compose file shows both ports. The files are in the compose/HOSTNAME folder inside your Docker folder, where HOSTNAME is your server’s hostname. Open the file, for example compose/HOSTNAME/sonarr.yml, and find the ports section:

container_name: sonarr
networks:
- default
ports:
- "$SONARR_PORT:8989"
  • container_name is the host name to use.
  • The number on the right of the colon (8989) is the internal port. Use it when connecting apps on the default network.
  • The number on the left ($SONARR_PORT) is the host port. Deployrr asks for it when you install the app and saves it in your .env file. You use it in your browser.

networks: - default tells you the app is on the shared network. If you see it in both apps, use the container name and internal port.

You may also see socket_proxy or traefik_proxy in some files. Deployrr uses three networks. They are defined at the top of your main Compose file, docker-compose-HOSTNAME.yml in your Docker folder, under networks:.

Network Address range Which apps are on it What it is for
default Docker picks one Most apps Apps reach each other by container name.
socket_proxy 192.168.91.0/24 Socket Proxy (192.168.91.254), Traefik, and apps that read Docker’s container list, such as Portainer, Dozzle, Homepage, Homarr, Uptime Kuma and What’s Up Docker Apps reach Docker through the Socket Proxy.
traefik_proxy 192.168.90.0/24 Traefik (192.168.90.254), Authelia, Authentik, TinyAuth, Google OAuth, CrowdSec after the Traefik Bouncer install. Apps you put behind Traefik with labels must join it too. Traefik reaches the login apps and the apps you put behind it with labels.

default and socket_proxy are there from the first install. Traefik Preparation adds traefik_proxy to the main Compose file.

Traefik itself is not on default. For apps you put behind Traefik from the Deployrr menu, the Traefik rules file that Deployrr creates points at the Docker bridge address and the host port, for example http://172.17.0.1:8989. So keep the app’s ports line when it sits behind Traefik. For apps you put behind Traefik with labels, see Protect a custom.yml app with Traefik and a login.

socket_proxy and traefik_proxy don’t matter when you connect apps like Sonarr and qBittorrent. A few apps are only on socket_proxy, which changes how you reach them. See Apps only on the socket_proxy network.

Some apps do not use the container name method.

Some apps have network_mode: host in their file. Examples include Homebridge, Tailscale, ZeroTier, Netdata, Sshwifty and Cloudflare Tunnel. They have no container name on the Docker network.

To connect to one of them from another app, use the IP address of your server and the port the app listens on.

What’s Up Docker, Dockpeek and Dockwatch have only socket_proxy under networks, not default. An app on the default network can’t reach them by container name. For example, wud:3000 fails from Nginx Proxy Manager or from a dashboard that is only on default. Docker GC and Deunhealth are also only on socket_proxy, but they have no web page to connect to.

To reach one of them, use the IP address of your server and its host port, for example WUD_PORT, DOCKPEEK_PORT or DOCKWATCH_PORT from your .env file. See Use the server IP and host port instead.

Apps that list both default and socket_proxy, such as Homepage, Homarr and Uptime Kuma, can still use the container name and internal port. Look up the internal ports in the App reference.

The qBittorrent VPN app has network_mode: "service:gluetun" in its file. To install it, see Install qBittorrent VPN. It shares the network of the Gluetun container. It has no network of its own and no ports section.

To connect another app to it, use gluetun as the host name and 8080 as the port. Other apps can reach gluetun because Gluetun is on the default network.

To see the gluetun host name used from Radarr, watch Gluetun VPN kill switch for qBittorrent: accessing qBittorrent from other services at 27:15 (manual setup; the video uses a network called t3_proxy, not default, and port 8081 on the host).

When you install qBittorrent VPN, Deployrr turns on a port mapping in the Gluetun file and restarts Gluetun. After that, the qBittorrent web page is at http://YOUR_SERVER_IP:QBITTORRENTVPN_PORT. Replace YOUR_SERVER_IP with your server’s local IP address and QBITTORRENTVPN_PORT with the port you picked at install. If that page doesn’t open or says Unauthorized, see qBittorrent web UI says Unauthorized or won’t open.

If the container name method does not work, or the other app is on a different machine, use the IP address of your server and the host port:

YOUR_SERVER_IP:HOST_PORT

Replace YOUR_SERVER_IP with the local IP address of your server. Replace HOST_PORT with the port you use in your browser. You can find it in your .env file, for example SONARR_PORT.

The Test button in the app shows a green check mark or a success message. If it fails, see these points:

“Connection refused” means the name was found, but nothing answered on that port. Check these, most common first:

  • Wrong port. With a container name, use the internal port (the number on the right in ports), not the host port from .env. With the server IP, it’s the other way round: use the host port.
  • The app is still starting. Wait a minute after a start or update, then test again. Run dlogs APP, with APP replaced by the container name, to see when it is ready. Press Ctrl+C to stop following the log.
  • You used a domain name. sonarr.YOUR_DOMAIN goes through your reverse proxy and its login. Use the container name instead. See What to avoid.
  • The apps are on different networks. Compare the networks lines of both apps’ Compose files. If they share no network, use the server IP and host port.

If the test says the host can’t be found or resolved instead, the container name is wrong, the app is not running, or the two apps share no network.