Hmmm. I think it's time to change to another provider.
Quintin
On Fri, Jan 26, 2018 at 12:43 PM nusenu wrote:
> If your hoster suspends your server if you exceed 10k concurrent
> connections
> I'm afraid it is probably not suitable for an exit relay (regardless of
> your own iptables ruleset).
Thanks for the fast reply!
> Your relay has probably chosen some overloaded guards.
> The problem comes from the extra load on those machines, not your relay.
> Your relay will eventually try other guards.
>
> Are you sure it's not overloaded?
> It might be worth checking the logs, inbound connec
If your hoster suspends your server if you exceed 10k concurrent connections
I'm afraid it is probably not suitable for an exit relay (regardless of
your own iptables ruleset).
A non-exit (single instance) relay would fit into a 10k limit.
--
https://mastodon.social/@nusenu
twitter: @nusenu_
> On 26 Jan 2018, at 19:55, Dark Matter wrote:
>
> Hello,
>
> I'm running a tor-relay with Tor version 0.3.2.9 (stable). I had to do some
> daemon restarts, because of connection limit issues.
There has been extra load on the network since December.
We are working on some relay defences:
htt
> On 26 Jan 2018, at 18:23, Andreas Krey wrote:
>
> But mine (5B1F0DAF378A1FAFCFD5FA9CDC66D1023DC0276E) lost guard status
> as well in december, and I have no idea as to why either - except
> possibly because of running a non-recommended tor version (i.e. too
> bleeding edge release branch stat
Hello,
I'm running a tor-relay with Tor version 0.3.2.9 (stable). I had to do some
daemon restarts, because of connection limit issues. Since the last two
restarts the Tor process issues a lot of warnings while bootstrapping, because
it could not create a (client) circuit. Relay functionality
