Alternative API endpoint should have other ports

[mkevinstever]

We are happy to answer your questions about the code or discuss technical ideas.

Please complete the following checklist (by adding [x]):

• [x] I have searched open and closed issues for duplicates
• [x] This isn't a feature request
• [x] This is not a report about my app not working as expected

---

Hello, Proton VPN team: Presently, if the primary ProtonVPN API endpoint is inaccessible due to blocking, the application attempts to connect through alternative available endpoints. However, upon examining the backup endpoint, a critical issue emerges: it solely utilizes port 443 for HTTPS connections and lacks additional ports. Consequently, in restricted environments, users may encounter difficulties in establishing a successful connection to the API server, significantly impairing the functionality of the application. To address this concern, it's imperative to include a non-standard HTTPS port for the backup endpoint.

Thanks.

[Anonymous941]

I'm not affiliated with ProtonVPN, but shouldn't 443 be the one port that would be whitelisted? Usually it's always allowed, even in the most restrictive environments (such as the Great Firewall of China), because it's inherently untraceable and blocking it would break most of the Internet...