How do I run a Tor relay on a VPS?
Running a Tor relay is a matter of installing the Tor package, setting a handful of torrc options and opening two ports; a middle or guard relay needs very little CPU and is bound almost entirely by bandwidth. NimbusVPS permits relays explicitly — there is a free toggle at checkout that flags the server so abuse reports are handled correctly — and never bills bandwidth overage.
The Tor network runs on relays that volunteers operate. A middle relay — the safest kind to run, because it never talks directly to the open internet on a user's behalf — passes encrypted traffic between other relays. This guide sets one up.
Prerequisites: a KVM VPS (the Nano plan is plenty), root access, and a location where relays are welcome. When ordering, enable the free Tor-relay toggle so the abuse desk knows the server is a relay. Exit relays carry more responsibility and are permitted only in specific locations — this guide covers a middle relay.
- 1
Deploy the server and enable the relay flag
Order a small KVM VPS and switch on the free Tor relay allowance at checkout, which tells the abuse desk this box is a relay so routine relay traffic is not mistaken for abuse.
- 2
Add the official Tor repository
Rather than the distro package, add the Tor Project apt repository so you get current, signed builds, then apt update.
- 3
Install Tor
Install with apt -y install tor deb.torproject.org-keyring. Do not start configuring until the package and its keyring are in place.
- 4
Configure torrc as a middle relay
In /etc/tor/torrc set ORPort 9001, a Nickname, ContactInfo with an email, and crucially ExitRelay 0 so this relay never acts as an exit. Set RelayBandwidthRate/Burst to cap usage if you want to stay within an allowance.
- 5
Open the ports and restart
Allow inbound TCP on ORPort 9001 (and DirPort if set) in any firewall, then systemctl restart tor and systemctl enable tor.
- 6
Confirm the relay is published
Check the Tor log for "Self-testing indicates your ORPort is reachable"; within a few hours the relay appears on Tor Metrics by its fingerprint. It takes days to earn significant traffic as its measured weight rises.
Bandwidth: a relay is bandwidth-bound; set RelayBandwidthRate to stay inside your plan's allowance, though overage here throttles rather than bills. Exit relays: these generate abuse complaints and are permitted only in specific NimbusVPS locations, not the United States site — decide deliberately before switching ExitRelay on.
Frequently asked questions
Is it legal to run a Tor relay?
Running a middle or guard relay is legal in the great majority of jurisdictions and carries little risk, because such relays only pass encrypted traffic between other relays and never connect to destinations on a user's behalf. NimbusVPS permits relays explicitly and provides a free checkout toggle to flag the server.
Can I run a Tor exit relay?
Exit relays are permitted only in specific NimbusVPS locations — the Netherlands, Iceland, Romania and Moldova — and not at the United States site, because an exit relay generates abuse complaints that must be handled in a jurisdiction that tolerates them. Flag the server at checkout and start with a middle relay if you are new to this.
How much bandwidth does a Tor relay use?
As much as you let it: a relay's traffic scales with its measured weight, and a well-connected relay can move several terabytes a month. Cap it with RelayBandwidthRate in torrc. NimbusVPS never bills overage — exceeding the allowance throttles the port to 10 Mbps rather than charging you.
More guides
Deploy a server for this in under 5 minutes — no ID, crypto payment.
Deploy in the next five minutes.
Pick a location, size the box, pay in crypto. No account signup wall, no ID, no waiting on a human.
7-day money-back guarantee · No KYC · Cancel any time from the panel