You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
There's an inconsistency in the documentation and the example configuration file for AIVPN regarding the protocol used in the SERVER_PUBLIC_URL for both OpenVPN and WireGuard services. Specifically, the documentation instructs to use TCP for OpenVPN and UDP for WireGuard, while the example config file (config.ini.example) has these protocols swapped: it lists OpenVPN with UDP and WireGuard with TCP.
Observe the discrepancy in the SERVER_PUBLIC_URL protocol specification: UDP is mentioned for OpenVPN and TCP for WireGuard in the example config file, contrary to the documentation.
Expected behavior
The documentation and the example configuration file should consistently specify the correct protocols to be used for OpenVPN and WireGuard in the SERVER_PUBLIC_URL
Screenshots
The text was updated successfully, but these errors were encountered:
Describe the bug
There's an inconsistency in the documentation and the example configuration file for AIVPN regarding the protocol used in the
SERVER_PUBLIC_URL
for both OpenVPN and WireGuard services. Specifically, the documentation instructs to use TCP for OpenVPN and UDP for WireGuard, while the example config file (config.ini.example
) has these protocols swapped: it lists OpenVPN with UDP and WireGuard with TCP.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The documentation and the example configuration file should consistently specify the correct protocols to be used for OpenVPN and WireGuard in the
SERVER_PUBLIC_URL
Screenshots
The text was updated successfully, but these errors were encountered: