You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+36-3Lines changed: 36 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,12 +78,18 @@ services:
78
78
79
79
## Troubleshooting
80
80
81
-
### Check the logs
81
+
Here's some tips for troubleshooting :
82
+
83
+
<details>
84
+
85
+
<summary>Check the logs</summary>
86
+
82
87
The mod's logs are visible in the container's log :
83
88
```bash
84
89
docker logs -f qbittorrent
85
90
```
86
91
92
+
87
93
<details>
88
94
89
95
<summary>Qbittorrent docker logs</summary>
@@ -150,7 +156,11 @@ Connection to localhost (::1) 8080 port [tcp/http-alt] succeeded!
150
156
151
157
To (*drastically*) increase the log level, you can set the `GSP_DEBUG` var to `true`.
152
158
153
-
### Check Gluetun's control server
159
+
</details>
160
+
161
+
<details>
162
+
163
+
<summary>Check Gluetun's control server and forwarded port</summary>
154
164
155
165
If the log indicates `Error retrieving port from Gluetun API.` then try to get the port mannually (replace the container's name and `localhost:8000` if needed) :
156
166
@@ -163,7 +173,30 @@ and you should get this (with your port number) :
163
173
{"port":34981}
164
174
```
165
175
166
-
If not, then the issue is from your gluetun's configuration, you can get help [on the wiki](https://github.com/qdm12/gluetun-wiki/blob/main/setup/advanced/vpn-port-forwarding.md) or [open an issue](https://github.com/qdm12/gluetun/issues).
176
+
> If you get `0` it means gluetun's port forwarding is misconfigured.
177
+
178
+
If you get anything else, then the issue is from your gluetun's configuration, you can get help [on the wiki](https://github.com/qdm12/gluetun-wiki/blob/main/setup/advanced/vpn-port-forwarding.md) or [open an issue](https://github.com/qdm12/gluetun/issues).
167
179
168
180
**Note :** even with `openvpn` in the URL, this is also valid for wireguard.
169
181
182
+
</details>
183
+
184
+
185
+
<details>
186
+
187
+
<summary>[mod-init] (ERROR) digest could not be fetched from ghcr.io</summary>
188
+
189
+
190
+
This is due to the fact that at startup, qBittorrent container does not have internet access. Since the container gets the connexion from Gluetun, you have to tell Docker to wait for an established VPN connexion before starting qBittorrent.
191
+
192
+
To do that, the solution is quite simple, just add the following to your qBittorrent's `docker-compose.yml` file section (according to the [example](#docker-compose-example)) :
193
+
194
+
```yaml
195
+
depends_on:
196
+
gluetun:
197
+
condition: service_healthy
198
+
```
199
+
200
+
This is thanks to [Gluetun's healthcheck](https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md) being healthy only when the connexion is set.
0 commit comments