Error when attempting to add Prowlarr

[KenRichards]

Unexpected token 'I', "Internal S"... is not valid JSON

The above is the error I get when attempting to add my prowlarr instance. Prowlarr is in a separate container. Qbittorrent is in a container with gluetun, prowlarr is not on the vpn network. I had to do that because I got the same error when attempting to add qbittorrent when qbitwebui was not in the same container as gluetun and qbittorrent.

[Maciejonos]

Adding prowlarr is quite straightforward, not much to go wrong.

1. Wrong api key
2. Prowlarr not accessible from qbitwebui perspective. Expected if they are not on the same network. In my case I have both on external proxy net (nginx setup). So I just use https.

[KenRichards]

I agree, and I don't have this problem with my other integrations with Prowlarr where Prowlarr is behind a VPN and the other apps are not, like Sonarr and Radarr, for instance. API key is correct, btw. Regards, Ken Richards

…

On Sat, Feb 7, 2026, 8:09 PM Maciej ***@***.***> wrote: Adding prowlarr is quite straightforward, not much to go wrong. 1. Wrong api key 2. Prowlarr not accessible from qbitwebui perspective. Expected if they are not on the same network. In my case I have both on external proxy net (nginx setup). So I just use https. — Reply to this email directly, view it on GitHub <#61 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE7VQCQIAI3RZFS5WT5EMJT4K2EC7AVCNFSM6AAAAACULIEPJKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZTGAYDCNA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Maciejonos]

You could do some debugging with docker to see if qbitwebui can even see prowlarr.

F.e. with docker exec

[KenRichards]

I checked the logs (should have been my first step) and it is complaining about encryption, even though I disabled encryption: - 9 | function getKey(): Buffer { - 10 | if (_key) return _key - 11 | - 12 | const ENCRYPTION_KEY = process.env.ENCRYPTION_KEY - 13 | if (!ENCRYPTION_KEY) { - 14 | throw new Error('ENCRYPTION_KEY environment variable is required') - ^ - error: ENCRYPTION_KEY environment variable is required at getKey (/app/src/server/utils/crypto.ts:14:13) at encrypt (/app/src/server/utils/crypto.ts:45:47) at <anonymous> (/app/src/server/routes/integrations.ts:62:20) at async dispatch (/app/node_modules/hono/dist/compose.js:22:23) Regards, Ken Richards

…

On Sun, Feb 8, 2026 at 4:56 AM Maciej ***@***.***> wrote: You could do some debugging with docker to see if qbitwebui can even see prowlarr. F.e. with docker exec — Reply to this email directly, view it on GitHub <#61 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE7VQCR35XAEP2VRATWUQCD4K4B53AVCNFSM6AAAAACULIEPJKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZTGI4DCOI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[KenRichards]

Nevermind, I see my mistake now. I'll create an encryption key Regards, Ken Richards On Sun, Feb 8, 2026 at 9:49 AM Ken Richards ***@***.***> wrote:

…

I checked the logs (should have been my first step) and it is complaining about encryption, even though I disabled encryption: - 9 | function getKey(): Buffer { - 10 | if (_key) return _key - 11 | - 12 | const ENCRYPTION_KEY = process.env.ENCRYPTION_KEY - 13 | if (!ENCRYPTION_KEY) { - 14 | throw new Error('ENCRYPTION_KEY environment variable is required') - ^ - error: ENCRYPTION_KEY environment variable is required at getKey (/app/src/server/utils/crypto.ts:14:13) at encrypt (/app/src/server/utils/crypto.ts:45:47) at <anonymous> (/app/src/server/routes/integrations.ts:62:20) at async dispatch (/app/node_modules/hono/dist/compose.js:22:23) Regards, Ken Richards On Sun, Feb 8, 2026 at 4:56 AM Maciej ***@***.***> wrote: > You could do some debugging with docker to see if qbitwebui can even see > prowlarr. > > F.e. with docker exec > > — > Reply to this email directly, view it on GitHub > <#61 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AE7VQCR35XAEP2VRATWUQCD4K4B53AVCNFSM6AAAAACULIEPJKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZTGI4DCOI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[KenRichards]

Another issue. I can create a new post if you want. When attempting to use network diagnostics, I get this error: {"error":"missing SID"} The logs say this: - 2026/02/08 14:58:17 GET /health 200 0s - 2026/02/08 14:58:17 auth failed: missing SID for /speedtest/servers - 2026/02/08 14:58:17 GET /speedtest/servers 401 0s - 2026/02/08 14:58:19 auth failed: missing SID for /ip - 2026/02/08 14:58:19 GET /ip 401 0s - 2026/02/08 14:59:03 auth failed: missing SID for /ip - 2026/02/08 14:59:03 GET /ip 401 0s - 2026/02/08 14:59:04 auth failed: missing SID for /dns - 2026/02/08 14:59:04 GET /dns 401 0s - 2026/02/08 14:59:06 auth failed: missing SID for /interfaces - 2026/02/08 14:59:06 GET /interfaces 401 0s Any ideas? Regards, Ken Richards On Sun, Feb 8, 2026 at 9:53 AM Ken Richards ***@***.***> wrote:

…

Nevermind, I see my mistake now. I'll create an encryption key Regards, Ken Richards On Sun, Feb 8, 2026 at 9:49 AM Ken Richards ***@***.***> wrote: > I checked the logs (should have been my first step) and it is complaining > about encryption, even though I disabled encryption: > > > - 9 | function getKey(): Buffer { > - > 10 | if (_key) return _key > - > 11 | > - > 12 | const ENCRYPTION_KEY = process.env.ENCRYPTION_KEY > - > 13 | if (!ENCRYPTION_KEY) { > - > 14 | throw new Error('ENCRYPTION_KEY environment variable is > required') > - > ^ > - > error: ENCRYPTION_KEY environment variable is required > at getKey (/app/src/server/utils/crypto.ts:14:13) > at encrypt (/app/src/server/utils/crypto.ts:45:47) > at <anonymous> (/app/src/server/routes/integrations.ts:62:20) > at async dispatch (/app/node_modules/hono/dist/compose.js:22:23) > > > Regards, > Ken Richards > > > On Sun, Feb 8, 2026 at 4:56 AM Maciej ***@***.***> wrote: > >> You could do some debugging with docker to see if qbitwebui can even see >> prowlarr. >> >> F.e. with docker exec >> >> — >> Reply to this email directly, view it on GitHub >> <#61 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AE7VQCR35XAEP2VRATWUQCD4K4B53AVCNFSM6AAAAACULIEPJKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZTGI4DCOI> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >

[Maciejonos]

Yeah that's an issue with your setup. Please read the wiki - encryption key and net agent setup.

[KenRichards]

The "missing SID" issue persists. I've read the net agent setup and found this: Authentication The agent validates requests by checking the qBittorrent session (SID). Only users with valid qBittorrent sessions can access the agent. Auto-detection: If qBittorrent has authentication disabled (localhost bypass), the agent automatically detects this and skips SID validation. Here is the setting in my qbittorrent: [image: image.png] Regards, Ken Richards

…

On Sun, Feb 8, 2026 at 10:09 AM Maciej ***@***.***> wrote: Yeah that's an issue with your setup. Please read the wiki - encryption key and net agent setup. — Reply to this email directly, view it on GitHub <#61 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE7VQCRX3REVQCWUOTYIGBL4K5GTLAVCNFSM6AAAAACULIEPJKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZTGQ3TKNY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Maciejonos]

See #59 (comment)