# Self-Hosted Zrok with TCP/UDP support

**URL:** <https://openziti.discourse.group/t/self-hosted-zrok-with-tcp-udp-support/2218>\
**Category:** zrok\
**Created:** [March 6, 2024, 2:22pm UTC](https://openziti.discourse.group/t/self-hosted-zrok-with-tcp-udp-support/2218 "2024-03-06T14:22:02Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![qrkourier](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/qrkourier/32/52_2.png) [@qrkourier](https://openziti.discourse.group/u/qrkourier)\
**Post date:** [March 6, 2024, 2:27pm UTC](https://openziti.discourse.group/t/self-hosted-zrok-with-tcp-udp-support/2218/2 "2024-03-06T14:27:33Z")

</div>

There's a more straightforward option than self-hosting your zrok instance that works with a cheap VPS to enable a TCP or UDP proxy (like a port forward).

On the VPS, you run this to expose your private zrok share on a public port:

```bash
zrok access private {token} --bind 0.0.0.0:4321

```

If the backend has mode `tcpTunnel` then it will open a TCP port, and a UDP port if backend mode `udpTunnel`.

Ensure the VPS's firewall allows the bind port you choose for the correct transport protocol: TCP or UDP.

---

_[View the full topic](https://openziti.discourse.group/t/self-hosted-zrok-with-tcp-udp-support/2218)._