Bug: control server returns forwarded port 0 when using wireguard

[Schaka]

What's the feature 🧐

Currently, it seems that the control-server doesn't support Wireguard at all. Many of the endpoints do send the necessary info via /openvpn even when using Wireguard.

However, when using ProtonVPN with port forwarding, the /v1/openvpn/portforwarded endpoint just returns 0.

I'm not quite sure if this a quickly fixed bug or if I should rather request a feature to have all wireguard relevant endpoints added to the control server.

Extra information and references

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]

This was updated in the wiki. Most endpoints work with both vpn protocols, some (I think 1) don't.
The port forwarded endpoint should work independently of the vpn protocol, can you please share your logs?