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.
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
===
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@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Actually, Server Room/Primcast will allow you to operate with an unrestricted exit policy if you use their Data Center in Romania of if you want to use a server in the NYC datacenter, you could use one of my IP ranges I have out there.
--Conrad
-----Original Message----- From: tor-relays tor-relays-bounces@lists.torproject.org On Behalf Of Neel Chauhan Sent: Tuesday, July 30, 2019 12:18 PM To: tor-relays@lists.torproject.org Subject: 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
===
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@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hello Chris,
Thanks for updating the relay community. Could you give trac another chance and update the wiki page?
thanks, Gus
On Tue, Jul 30, 2019 at 08:23:49PM -0500, conrad@rockenhaus.com wrote:
Actually, Server Room/Primcast will allow you to operate with an unrestricted exit policy if you use their Data Center in Romania of if you want to use a server in the NYC datacenter, you could use one of my IP ranges I have out there.
--Conrad
-----Original Message----- From: tor-relays tor-relays-bounces@lists.torproject.org On Behalf Of Neel Chauhan Sent: Tuesday, July 30, 2019 12:18 PM To: tor-relays@lists.torproject.org Subject: 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
===
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@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
The 2019 wiki has outdated keys!
Sent from ProtonMail mobile
-------- Original Message -------- On 31 Jul 2019, 12.30, gus wrote:
Hello Chris,
Thanks for updating the relay community. Could you give trac another chance and update the wiki page?
thanks, Gus
On Tue, Jul 30, 2019 at 08:23:49PM -0500, conrad@rockenhaus.com wrote:
Actually, Server Room/Primcast will allow you to operate with an unrestricted exit policy if you use their Data Center in Romania of if you want to use a server in the NYC datacenter, you could use one of my IP ranges I have out there.
--Conrad
-----Original Message----- From: tor-relays tor-relays-bounces@lists.torproject.org On Behalf Of Neel Chauhan Sent: Tuesday, July 30, 2019 12:18 PM To: tor-relays@lists.torproject.org Subject: 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
===
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@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org
-
Chris Kerr -
conrad＠rockenhaus.com -
David Poulsen -
gus -
Neel Chauhan