hi all, my I ask why was the naming convention for VPNs (and WireGuard peers) suddenly changed? I now can't make any changes to the Wireguard VPN itself / add new peer / delete peer till I don't...

Hi @Gabriel-TP, while writing the anwer to the support case, I've found my own error in the URL - I have forgotten one "/" character in Update-URL:...

Hi @Gabriel-TP, WAN on site 1 is using static IP address, on site 2 DHCP is used and both are working fine. no advanced settings are used.

Hi @Vincent-TP, it seems, that the API call PATCH /openapi/v2/{omadacId}/sites/{siteId}/vpn/site-to-site-vpns/{vpnId} expects the whole information set inclusive VPN name, VPN type, service port,...

Hi @Gabriel-TP, answers can be found in the thread header and in text, but to summarize (I've added the Gateway info too): Controller type: Windows version Software version: 6.2.10.15 Gateway type:...

hi all, today I have made upgrade to the 6.2.10.15 version of Controller and somehow I don't understand the change made in naming convention of (at least) WireGuard tunnels and peers. Suddenly only...