[BUG] Prowlarr should not be passed to the vpn.

[Keenan-Nicholson]

Describe the bug Prowlarr does not need to run through the VPN. Only the download client (qbittorrent) should be have the tag network_mode: service:vpn

Expected behavior If running Prowlarr through the vpn indexers fail at a very high rate due to DNS issues.

Docker compose file

  prowlarr:
    profiles: ["vpn", "no-vpn"]
    container_name: prowlarr
    image: linuxserver/prowlarr:latest
   
    network_mode: service:vpn # Uncomment this line if vpn is enabled

    environment:
      - PUID=1000
      - PGID=1000
      - TZ=UTC
    volumes:
      - prowlarr-config:/config

    restart: unless-stopped

Additional context I tried for quite a while to diagnose why I was getting DNS errors. I realized that Prowlarr does not need to, and actually should NOT be using the service:vpn tag as it is not dealing with sensitive information.

The download client is the only service that NEEDS to be inside this container.

For 2 weeks my I could not download a single movie or tv show, as soon as I took Prowlarr out of the vpn everything worked.

Please let me know if I can make a pull request to the docker-compose.yml and update the readme to reflect these suggested changes.

[Vanheden]

How do I fix this? Seems to be related.

Pending - Download client is unavailable

[Keenan-Nicholson]

@Vanheden I just gave it its own address

  prowlarr:
    profiles: ["vpn", "no-vpn"]
    container_name: prowlarr
    image: linuxserver/prowlarr:latest

    networks:
      mynetwork:
        ipv4_address: 172.20.0.40

I did a write up of my stack here: https://blog.pirated.tech/posts/servarr/

[Aur0nd]

Thank you @Keenan-Nicholson - isn't prowlarr literally connecting to indexers and runs queries for what you're looking for? My understanding is that it's as sensitive as seeding.

Btw I'm having the same DNS issues with some indexers.

[Keenan-Nicholson]

@Aur0nd its my understanding that indexers or providers or legal to use, so prowlarr does not need to be behind a vpn.

When I was experiencing dns issues it was due to using flaresolverr, which is currently facing issues. If you are using flaresolverr, i suggest getting rid of it and deleting indexers that require it.

[Vanheden]

@Vanheden I just gave it its own address

  prowlarr:
    profiles: ["vpn", "no-vpn"]
    container_name: prowlarr
    image: linuxserver/prowlarr:latest

    networks:
      mynetwork:
        ipv4_address: 172.20.0.40

I did a write up of my stack here: https://blog.pirated.tech/posts/servarr/

Also having trouble with Unable to communicate with qBittorrent. Connection refused (vpn:5080)

Do you mind reaching out to me on discord? roddan95