iam4x / iam4x/bobarr

bobarr-api ECONNREFUSED with VPN

Open
#211 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
1.7k
Forks
89
PR merge metrics
No merged PRs in 30d

Description

I've configured bobarr with my media directories and VPN credentials and am running with the `start:vpn` flag. Bobarr runs fine for a few minutes but when I try to start downloading TV, the episodes sit in transmission with 0 trackers (I have setup trackers in Jackett and am choosing torrents with lots of peers). After about a minute, I get a connection error message on the bobarr and transmission web clients and see this error repeatedly in the console

```shell
bobarr-api | 2021-08-19 16:25:22.577 [error] ExceptionsHandler - connect ECONNREFUSED 172.20.0.3:9091 - {"stack":["Error: connect ECONNREFUSED 172.20.0.3:9091\n at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)"]}
```

Any ideas why this would be happening?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by examining the bobarr-api and Transmission containers, the VPN-enabled startup path, and the connection to 172.20.0.3:9091. Reproduce the failure while starting a TV download and inspect the Docker networking and service logs. Done means the API and Transmission web client remain reachable and downloads no longer fail with ECONNREFUSED.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, typescript
Domain
backend, devops, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.