[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-relays] Cherryservers (formerly balticservers) account terminated for exit relay



If you want an alternative exit relay host (other than the common ones like OVH, Scaleway, or Hetzner), one option is Server Room/Primcast (same company). I use Primcast for a 300 Mbps FreeBSD exit and have been happy with them.

Server Room/Primcast is not the "best" provider, but they are good enough for the purpose of an exit and being less popular (as of now) helps with relay diversity.

However, you will need a reduced exit policy with SR/Primcast. I have a **very** restrictive exit policy only allowing Ports 53, 80, 443, and 8080 (so I get less complaints). If you want a custom OS, you will need iLO (HP/HPE's remote management, Primcast uses HP/HPE servers). An older server (pre-2011) may mean you'll need Windows and Internet Explorer (NOT MS Edge) to use the console, while a newer server will work with HTML5 on Windows/Mac/Linux/BSD/etc.

-Neel

===

https://www.neelc.org/

On 2019-07-30 02:15, Chris Kerr wrote:
I just heard from the hosting provider cherryservers.com that they are
terminating my account (after 2.5 years) where I run the exit relay
"ostwaldripening" (46.166.162.53), because they no longer wish to host tor
exit nodes.

I tried to create an account on trac.torproject.org to edit the "GoodBadISPs"
wiki page, but the spam blocking stopped me from doing so.
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays