forwarded port not defined / jq parse error?

[tamsinadriane]

I'm a beginner in Docker Compose - attempting to run this solution on an OpenMediaVault 7 system hosted on a Raspberry Pi 5.

Following all other instructions to the letter and going through the command line as indicated, the "monitor" container never becomes healthy. When I follow the logs, the following repeats every 10 seconds:

2025-12-08 19:27:43 INFO ○ Running monitor
2025-12-08 19:27:43 DBUG * Requesting forwarded port from Gluetun
jq: parse error: Invalid numeric literal at line 1, column 3
2025-12-08 19:27:43 ERRO ! Forwarded port is not defined according to Gluetun
2025-12-08 19:27:43 TRAC ↩ <a href="/v1/portforward">Moved Permanently</a>.
2025-12-08 19:27:43 DBUG * Retrying in 10s

If you have any ideas, or need more information, let me know. I've tried just about every solution I can find for running a torrent client through ProtonVPN, and none of them seem to work.

[SnathanP]

Hello there,

If you have any ideas, or need more information, let me know. I've tried just about every solution I can find for running a torrent client through ProtonVPN, and none of them seem to work.

So I dug into the gluetun documentation, the monitor script and experimented myself to come to this conclusion:
Since gluetun v3.40.0, three things changed:

• internal routes (such as the one used here for dynamic forward port discovery) MUST now be protected by authentication
• a HTTP 301 redirect now occurs in gluetun
• the endpoint for port forward info seems to be now GET /v1/portforward

These three changes introduces three new challenges. My guess is you updated/installed recently the stack using the latest gluetun(tunnel) version, eg >= v3.40.0

To patch this, a few things to do:

• alter the tunnel/config.toml to include auth in the /v1/portforward endpoint, as documented here.
• change the endpoint url to /v1/portforward in both tunnel's config.toml and monitor's script
• introduce api-key or basic auth to the cURL call made in the monitor's script, with ENV vars if we wanted to do it properly.
• introduce the --follow directive to the previously mentionned cURL call.

If I have additional time ahead I will submit a PR

[tamsinadriane]

I'm only finding the time to review this now, but this makes sense - thank you for taking a look!

The first two points you suggested were pretty straightforward, but even after reading through the gluetun documentation, altering the monitor script seems a little out of my depth (I'm still a beginner, and not yet used to bash scripts of this complexity). If you have time, could you maybe provide a few more pointers on how to properly set up the environment variables and modify the cURL call appropriately?

Thanks again!