Bug: [http server] 200 GET /portforwarded wrote 15B to 127.0.0.1:XXXXX

[nebb00]

Is this urgent?

None

Host OS

No response

CPU arch

None

VPN service provider

ProtonVPN

What are you using to run the container

Unraid

What is the version of Gluetun

Running version latest built on 2024-08-09T09:37:47.759Z (commit 01aaf2c)

What's the problem 🤔

Just been setting up port forwarding with Gluetun and ProtonVPN, together with QBIT and ghcr.io/t-anc/gsp-qbittorent-gluetun-sync-port-mod:main.

I believe this is working, as if I test with portchecker.co with port 52794, its open, and QBIT changes to Connected. But the Gluetun logs show the /portforwarded wrote another port every minute?

Am I understanding the log? These ports listed are not open.

Share your logs (at least 10 lines)

2024-08-15T05:57:42+01:00 INFO [port forwarding] port forwarded is 52794
2024-08-15T05:57:42+01:00 INFO [firewall] setting allowed input port 52794 through interface tun0...
2024-08-15T05:57:42+01:00 INFO [port forwarding] writing port file /tmp/gluetun/forwarded_port
2024-08-15T05:57:44+01:00 INFO [http server] 200 GET /portforwarded wrote 15B to 127.0.0.1:48234 in 27.253µs
2024-08-15T05:58:44+01:00 INFO [http server] 200 GET /portforwarded wrote 15B to 127.0.0.1:59404 in 18.414µs
2024-08-15T05:59:44+01:00 INFO [http server] 200 GET /portforwarded wrote 15B to 127.0.0.1:35510 in 19.817µs
2024-08-15T06:00:44+01:00 INFO [http server] 200 GET /portforwarded wrote 15B to 127.0.0.1:40324 in 16.27µs
2024-08-15T06:01:44+01:00 INFO [http server] 200 GET /portforwarded wrote 15B to 127.0.0.1:33712 in 15.086µs
2024-08-15T06:02:44+01:00 INFO [http server] 200 GET /portforwarded wrote 15B to 127.0.0.1:52812 in 13.956µs
2024-08-15T06:03:44+01:00 INFO [http server] 200 GET /portforwarded wrote 15B to 127.0.0.1:51688 in 19.917µs

### Share your configuration

_No response_

[github-actions]

@qdm12 is more or less the only maintainer of this project and works on it in his free time.
Please:

• do not ask for updates, be patient
• 👍 the issue to show your support instead of commenting
  @qdm12 usually checks issues at least once a week, if this is a new urgent bug,
  revert to an older tagged container image

[qdm12]

But the Gluetun logs show the /portforwarded wrote another port every minute?

That's the http control server saying something queried it at the /portforwarded path, which is likely ghcr.io/t-anc/gsp-qbittorent-gluetun-sync-port-mod:main I would guess. This doesn't renew or do anything port forwarding related, except returning back the port forwarded {"port": 52794} to that sync container.

Closing this as unplanned, since this is behaving as expected. If I misunderstood, please re-create an issue referencing this one! Thanks!

[github-actions]

Closed issues are NOT monitored, so commenting here is likely to be not seen.
If you think this is still unresolved and have more information to bring, please create another issue.

This is an automated comment setup because @qdm12 is the sole maintainer of this project
which became too popular to monitor issues closed.