Hmm. Well, if you don't mind the risk of breaking the rules...
-
Try Tor? The nodes there may be ephemeral enough for them to be hard to block.
-
If you still have the server and it's Linux and you can handle the technical side, set up an SSH tunnel and dump traffic through that. Something like
ssh -L 127.0.0.1:8080:127.0.0.1:8080 myusername@foreignserver.com. Then install a SOCKS proxy on the server, have it listen on 127.0.0.1 (not on 0.0.0.0, especially since they could scan the server to see if it has a SOCKS proxy, but also to keep random people from using it). Then tell your web browser that you're using a SOCKS proxy on 127.0.0.1 on your local machine. If all you need is web browsing, that should work. They may not allow VPNs, but they may not kill SSH.
What you really need is some kind of encrypted transport that has legit -- well, legit in terms of state censorship, anyway -- bidirectional high-bandwidth use.
I wonder if anyone's done a VPN that masquerades as a BitTorrent client? That should fit the bill.
googles
https://github.com/danoctavian/bit-smuggler
That guy apparently put together a VPN that runs over BitTorrent for his masters thesis, targets the state censorship use case. Doesn't look like it's seen much work for a long time, though. That might be a bit of a project.
EDIT: Also, regarding the SOCKS proxy approach, it sounds like forcing DNS-over-HTTP always on is probably a good idea. I dunno how the UAE has things rigged up, but it sounds like Firefox, at least, defaults to doing a DoH lookup, then if that fails, falling back to standard DNS, and a state that can control traffic at the edge of their networks is gonna be able to probably monitor DNS lookups and cause DoH lookups to sporadically fail, which would cause DNS queries to be leaked, and I reckon that having DNS queries about dubious sites like lemmy.blahaj.zone going out of your computer occasionally is a likely a good way to get the attention of whatever monitoring stuff they have.