Wireguard only supports UDP. The main reason being TCP over TCP is extremely slow.
You could try OpenVPN, I think that has a TCP mode though, as said, don't expect good performance.
For my setup, I used UDP port 443. For the vast majority of situations it works well as TCP 443 is for secure internet traffic. It seems admins often blanket 443 port open regardless of protocol 🙃
Try UDP port 123 sometimes that goes through the firewalls
I will try this port. Any other port that could work? (Not 53 as it's being filtered by ISP)
As long as you're certain your wireguard server works from other networks.. You could use nginx as a proxy to have your server accept incoming traffic from UDP port 53 (DNS)... But, be careful!
I would strongly suggest you whitelist the retrictive network for use on UDP port 53. Is the WAN IP static on the restrictive network? Do you know the size of the WAN subnet? I'd try a quick test over UDP port 53 using nginx, then close it up. If it works, create your firewall rule to whitelist only the restrictive network and Bob's your aunt.
I'm 100% sure it works from other networks. UDP 123 is filtered by ISP. Someone mentioned some other low UDP port.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!