If they’re blocking Wireguard/OpenVPN at the protocol level, there may not be anything you can do (running on a different port, etc).
If HTTPS works, between a cloud VPS and your home connection, you might be able to setup Nginx + VPN-WS on your cloud host to make a websocket-based VPN.
I haven’t tried this, but it looks solid enough. Just make sure you configure Nginx correctly for authentication since it doesn’t do that on its own (intentionally since most web servers already have a solid authentication framework / plugin system).
You may also try SSH port forwarding. Basically your home device maintains a persistent connection to the cloud server over SSH and forwards one or more ports (its SSH, for example) over that, and the cloud server makes that available.
Wireguard doesn’t obfuscate its traffic so non-standard ports may not help depending on how sophisticated the blocking is (they could recognize the protocol and block your traffic regardless of port).
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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:
selfh.st Newsletter and index of selfhosted software and apps
Find a cheap hosting solution that provides a fixed IP address, then host your own VPN or proxy server there.
Edit: if you use a non-standard port for the VPN, it should be less likely to be blocked.
To add on to this answer:
If they’re blocking Wireguard/OpenVPN at the protocol level, there may not be anything you can do (running on a different port, etc).
If HTTPS works, between a cloud VPS and your home connection, you might be able to setup Nginx + VPN-WS on your cloud host to make a websocket-based VPN.
https://github.com/unbit/vpn-ws
I haven’t tried this, but it looks solid enough. Just make sure you configure Nginx correctly for authentication since it doesn’t do that on its own (intentionally since most web servers already have a solid authentication framework / plugin system).
You may also try SSH port forwarding. Basically your home device maintains a persistent connection to the cloud server over SSH and forwards one or more ports (its SSH, for example) over that, and the cloud server makes that available.
This is the case unfortunately. They are blocked at protocol level.
Wireguard doesn’t obfuscate its traffic so non-standard ports may not help depending on how sophisticated the blocking is (they could recognize the protocol and block your traffic regardless of port).