Ports and firewalls
OpenVPN profiles commonly use port 1194 or port 443, but the best choice depends on network filtering, protocol, freshness and server quality. Port 1194 is historically associated with OpenVPN, while port 443 is popular because many networks allow HTTPS traffic.
Use this guide when choosing between public profiles that advertise UDP 1194, TCP 443 or another OpenVPN port.
If the network blocks unknown ports, TCP 443 is often the practical first choice.
UDP 1194 can perform well on open networks and is common in OpenVPN deployments.
Speed, latency and freshness matter more than the port number alone.
Check visible IP, DNS and stability after connecting to any port.
Port 1194 is the well-known default OpenVPN port. Many OpenVPN deployments use UDP 1194 because UDP often gives better latency and throughput for tunnel traffic.
The problem is that public Wi-Fi, corporate guest networks, schools and some mobile networks may block UDP 1194 or unknown VPN ports. A profile can be technically correct but unreachable from your current network.
If UDP 1194 works and metrics are good, it can be a strong choice for performance testing. If it times out, do not keep retrying forever; switch to a more firewall-friendly option.
Port 443 is normally used by HTTPS websites. OpenVPN over TCP 443 is popular because many networks allow outbound TCP 443 even when they block UDP or unusual ports.
This does not mean OpenVPN TCP 443 is invisible or guaranteed to bypass every firewall. It simply has a better chance on many restrictive networks. Deep packet inspection, captive portals and proxy rules can still block it.
TCP 443 can be slower than UDP because TCP-over-TCP can amplify packet loss effects. Use live speed and latency metrics to decide whether the reliability tradeoff is worth it.
Public OpenVPN profiles can use many ports: 1194, 443, 995, 1701, 1723 and custom high ports are all possible. A non-standard port is not automatically bad; it only means you should check whether your network allows it.
The PublicVPNList table shows protocol and port together so you can compare rows quickly. A row like TCP 443 is different from UDP 443, and UDP 1194 is different from TCP 1194.
On open home or mobile networks, try the freshest high-speed UDP row first. On restricted public Wi-Fi, try TCP 443 first. If both exist for the same country, compare latency and checked time before downloading.
If the port connects but browsing is unstable, test another server. Public endpoints can be overloaded, rate-limited or temporarily broken even when the port is reachable.