| Port | 1194 |
|---|---|
| Transport | UDP |
| Service | OpenVPN |
| Category | VPN |
| Range | registered (1024–49151) |
| Encrypted | Yes, always (TLS or equivalent) |
| Exposure | Designed to face the internet |
Port 1194 OpenVPN · UDP
OpenVPN's default port, UDP by default and TCP when UDP is blocked. It is the most widely deployed VPN protocol in commercial VPN apps and home routers, now with WireGuard (51820) as the lighter alternative.
What runs on port 1194
OpenVPN's default port, UDP by default and TCP when UDP is blocked. It is the most widely deployed VPN protocol in commercial VPN apps and home routers, now with WireGuard (51820) as the lighter alternative. Many operators run it on 443/TCP instead to pass restrictive networks.
Software that uses it: OpenVPN Community/Access Server · pfSense/OPNsense · router firmware (OpenWrt, DD-WRT, ASUS, Synology) · commercial VPN clients
Should port 1194 be open?
Designed to face the internet. This port exists to be reachable from anywhere, so the usual question is not whether to open it but how the service behind it is configured and patched.
- UDP is faster and avoids TCP-over-TCP meltdown; only fall back to TCP when you must.
- tls-auth / tls-crypt keys make the port invisible to scanners (no response without the key).
Check port 1194
# on the host: is anything listening, and which process? ss -lunp 'sport = :1194' sudo lsof -i :1194 # from another machine: is it reachable? nc -zuv host 1194 sudo nmap -sU -p 1194 host
A port that answers from the internet when it should not is the finding; nmap from a machine outside your network (or a VPS) is the honest test, because scans from inside the LAN pass the firewall you are trying to verify.
Allow or block port 1194
# ufw (Ubuntu/Debian) sudo ufw allow from 10.0.0.0/8 to any port 1194 proto udp sudo ufw deny 1194/udp # nftables nft add rule inet filter input ip saddr 10.0.0.0/8 udp dport 1194 accept nft add rule inet filter input udp dport 1194 drop # iptables (legacy) iptables -A INPUT -p udp --dport 1194 -s 10.0.0.0/8 -j ACCEPT iptables -A INPUT -p udp --dport 1194 -j DROP # firewalld sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=1194 protocol=udp accept'
Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 1194" with no source is just "open".
Related ports
Part of the port number reference. Ports are 16-bit numbers; see also the subnet calculator and the packet decoder, which shows ports inside TCP and UDP headers.
Questions
Is port 1194 TCP or UDP?
UDP. OpenVPN is datagram-based; TCP 1194 is not used by it.
Is port 1194 encrypted?
Yes, always (TLS or equivalent). The port number does not make it safe by itself: certificate validation, authentication and patching still decide.
How do I check whether port 1194 is open?
On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 1194 and which process. From another machine, nc -zv host 1194 -u or nmap -p 1194 -sU host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).
Can OpenVPN run on a different port?
Yes; the number is a convention, not a requirement. Changing it reduces log noise from scanners but does not add security, and every client, firewall rule and monitoring check then needs the new number. Keep the default unless you have a concrete reason.