Feature request: Support portforwarded endpoint on the HTTP control server for Wireguard connections

[FlorentLM]

What's the feature 🧐

Title says almost all, according to the wiki there is a /v1/publicip/ip and a /v1/openvpn/portforwarded endpoints on the control server which are usable when connected through OpenVPN, but the port one is not available when connected through Wireguard.

The /v1/openvpn/portforwarded endpoint actually works with Wireguard, I'm an idiot.

Extra information and references

I currently use the /tmp/gluetun/forwarded_port file bind-mounted in my other containers, but it's not as clean as using a http GET request, imo.

[cohenchris]

I'm also looking for this. I can see that my port is forwarded correctly through wireguard, but when I query /v1/openvpn/portforwarded, it responds with {"port":0}

Am I missing something here?

[qdm12]

@FlorentLM

I'm an idiot.

You're 100% not, that route /v1/openvpn/portforwarded is quite misleading. Just keeping it for historical reasons, and not adding more routes for now (eyeing doing a v4 release to remove a bunch of retro-compatibility before adding more things to the server).

@cohenchris subscribe to #2391 this is likely a bug somewhere, I'll check it out soon.

Closing this 😉

[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.