If I change Protocol under Global Settings from UDP to TCP, will this affect existing users/connections? Will I have to regenerate client packages?
I did a test - it looks like changing the server protocol to tcp
will require a change in the client’s .ovpn confiuration file.
Regards
Darn it. I wanted to switch but if it means redoing 25 configuration files, it’s probably not worth it.
It’s quite simple editing the configuration…
from proto udp to proto tcp
as an easy workaround, this notation
#proto udp
proto tcp
will disable UDP and will use TCP, deleting the second row and the leading # for revert.
For several reasons, use TCP for VPNs is in to the “do not do that”.
1 Like
Yes, but going to 25 different machines is the painful part, not editing the config.
I only wanted to try TCP for one user. His home internet (Starlink) was not working with VPN, and one of the potential solutions I found was to switch to TCP. But I don’t think it’s a feasible solution since I’d have to switch everyone else to TCP as well.
Thank you for your help.
Thanks for sharing this important detail.
I’d contact ISP for any kind of best practices if available.
Anyway, OpenVPN is not “exotic” or new at all, I’d assume that Starlink should not be the actual issue (unless specific filtering of protocols/destination ports)
There are others online that have posted similar issues with Starlink. It may be related to them using CG-NAT. At any rate, he is able to connect to VPN if he uses his phone hotspot, and his need for VPN is low, so that workaround will be our solution. If he wants to call his ISP, he can, but that’s not part of my responsibility.
1 Like
IDK and I don’t have any experience with Starlink connections.
However.
In Italy a lot of Mobile phone providers massively use CG-NAT and I can use OpenVPN without issues as client.
However, using a CG-NAT Internet connection, IPFire as OpenVPN server would not work as far as I know.