xistal_ 0 Posted ... For awhile now, it has been very inconsistent to connect to AirVPN with Eddie. It doesn't matter if I switch the protocol port, it still gets stuck on checking authorization. I am on an enterprise network at my university and am opening a ticket because the bootstrap fails and it says to open one if you're behind a restrictive firewall, which it appears I am. I have attached logs. Thank you Eddie_20250327_155105.txt Quote Share this post Link to post
OpenSourcerer 1467 Posted ... TCP/443 should always work, otherwise HTTPS wouldn't work anywhere. Try that. Quote Hide OpenSourcerer's signature Hide all signatures NOT AN AIRVPN TEAM MEMBER. USE TICKETS FOR PROFESSIONAL SUPPORT. LZ1's New User Guide to AirVPN « Plenty of stuff for advanced users, too! Want to contact me directly? All relevant methods are on my About me page. Share this post Link to post
Staff 10111 Posted ... 11 hours ago, OpenSourcerer said: TCP/443 should always work, otherwise HTTPS wouldn't work anywhere. Hello! Unfortunately not, OpenVPN over TCP to port 443, even when OpenVPN works over tls-crypt, is discernible from HTTPS if you know where to look at. 3 hours ago, xistal_ said: TCP/443 does not work OpenSourcerer In this case you can try a better approximation with OpenVPN over stunnel (TLS), again to port 443 but also to port 53. It's not impossible, but it's harder to distinguish this connection mode to port 443 from HTTPS; also, sometimes packets to outbound port 53 are not blocked. If both attempts fail, you can try OpenVPN over SSH: if SSH is not restricted and if the VPN server entry-IP addresses are not blocked this connection mode will work. Kind regards Quote Share this post Link to post