Clarification on VPN Restart via Control Server (WireGuard)

[AndaPlays]

Hello,

I'm working on a qBittorrent Port Manager that dynamically updates the listening port in qBittorrent based on the forwarded port provided by Gluetun. My solution relies on the Control Server API to retrieve the forwarded port and VPN public IP.

To ensure connectivity, I also verify the port status with nmap. If the port appears closed or filtered, I want to restart the VPN connection using the Control Server API.

Question:
The Control Server documentation mentions the following endpoints for OpenVPN and WireGuard:

• PUT /v1/openvpn/status with {"status":"running"} starts OpenVPN (and stops WireGuard).
• PUT /v1/openvpn/status with {"status":"stopped"} stops OpenVPN.
• GET /v1/openvpn/status returns the current OpenVPN status.

However, there is no mention of a WireGuard-specific API (e.g., /v1/wireguard/status).
Does the OpenVPN status API also apply to WireGuard, meaning it will restart WireGuard if OpenVPN is not in use? If not, is there a proper way to restart WireGuard using the Control Server API?

Any clarification would be greatly appreciated.

Thanks in advance!

[AndaPlays]

I looked through the project and under https://github.com/qdm12/gluetun/blob/master/internal/server/handlerv1.go I couldn't find anything that is specific to wireguard, so I guess currently only really openvpn is support this way.