There's a long-standing bug for this scenario [1]. Apparently, this
"confuses clients". But as you've fixed this now, there shouldn't be any
problems.
[1] https://trac.torproject.org/projects/tor/ticket/608
On 26/02/2015 14:31, catchthemall wrote:
Hi all,
tl;dr:
Due to a config error my rel
I thought the link to atlas page:
https://atlas.torproject.org/#details/5A9B5923F4937C3ED76B0AD4CF1030C11FCAF1FA
might be enough since it includes the fingerprint:
AllquanTor 5A9B5923F4937C3ED76B0AD4CF1030C11FCAF1FA
And as a prove that I am in control of the respective IP I included your
respon
You didn't include your fingerprint or IP's, so there isn't any way for
someone to check.
On 02/26/2015 02:31 PM, catchthemall wrote:
> Hi all,
>
> tl;dr:
>
> Due to a config error my relay [1] was running on two different IPs at
> the same time for about half a day. Now the traffic has dropped.
>
You didn't include your fingerprint or IP's, so there isn't any way for
someone to check.
On 02/26/2015 02:31 PM, catchthemall wrote:
> Hi all,
>
> tl;dr:
>
> Due to a config error my relay [1] was running on two different IPs at
> the same time for about half a day. Now the traffic has dropped.
>
You didn't include your fingerprint or IP's, so there isn't any way for
someone to check.
On 02/26/2015 02:31 PM, catchthemall wrote:
> Hi all,
>
> tl;dr:
>
> Due to a config error my relay [1] was running on two different IPs at
> the same time for about half a day. Now the traffic has dropped.
>
Hi all,
tl;dr:
Due to a config error my relay [1] was running on two different IPs at
the same time for about half a day. Now the traffic has dropped.
I just wanted to make sure that it is not flagged as malicious or
something ...
Additionally I am curious about the policy in such a case. What ha
