> On 23 Oct 2015, at 09:30, Green Dream wrote:
>
> I see this from time to time as well. Here's another example:
>
> Oct 17 23:02:44.000 [notice] Our IP Address has changed from 52.64.142.121
> to [CORRECT IP]; rebuilding descriptor (source: 86.59.21.38).
>
>
Green,>>Can you please elaborate? I may have
missed an earlier discussion, and a quick Google search isn't providing
too much help. I found the ticket >>below, which is interesting reading,
but I'm not sure what specific peculiarities you're referring to.One problem I understood
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi everyone,
I have been running an exit Tor relay for 5 months with a PulseServers
VPS and everything went fine until some days ago Kyle, the provider's
owner, reduced the bandwidth to something above 10 Mbit/s. Adding the
fact that he is an OVH
Hi,
I will explain my experiences with Contabo and Webtropia (both German
providers). Both are providing quite cheap and unmetered VPS, Contabo
with 100mbit/s and Webtropia at 300mbit/s (burst with 500mbit/s).
Contabo is saying that you are responsible for everything you do with
your VPS (they
Sina, the ticket 16205 regarding incorrect IPs coming from Faravahar is 5
months old [1].
Have you had a chance to look into the possible explanation Nick Suan
mentioned earlier in the thread?
It's not exactly confidence-inspiring to see multiple unresolved tickets
about Faravahar going back
Hi Riccardo are you italian?
If you like a good server go here: http://www.tophost.it/
and buy topserver. My relay is here and works very fine.
If you need some tips no problems write to me.
Ciao!
Il 23/10/2015 18:52, Riccardo Mori ha scritto:
> Hi everyone,
> I have been running an exit Tor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
Unfortunately this is not the first time we see this, and it did
happen before Faravahar IP address change and before it was
experiencing very high latency (
https://trac.torproject.org/projects/tor/ticket/17338 ).
See: