My Tor exit node not visible
Hi there, I've set up a new Tor exit node around 15 hours ago but despite it had been such a time and my exit is visible from outside world I still get little to no traffic at all. I also cannot see my servers IP on bulk tor exit node list. I checked the logs and everything seems alright too: [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Can you please tell me what I am missing here? Thank you Sent with [ProtonMail](https://protonmail.com) Secure Email.
Hi, You can expect traffic, but it usually takes up to 24 hours to begin. Your experience is usual. Patience is the key. Thanks for setting up an exit. Zim On Sun, 18 Oct 2020 at 22:25, netaudit <netaudit@protonmail.com> wrote:
Hi there,
I've set up a new Tor exit node around 15 hours ago but despite it had been such a time and my exit is visible from outside world I still get little to no traffic at all. I also cannot see my servers IP on bulk tor exit node list.
I checked the logs and everything seems alright too: [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Can you please tell me what I am missing here? Thank you
Sent with ProtonMail <https://protonmail.com> Secure Email.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Your traffic wouldn't be very high in the first 15 hours. As for bulk tor exit node list, I'm not sure how long to expect before that is updated. But to make sure nothing wrong, does your IP appear on tor relay search? And have you tried using nyx to view traffic? Oct 18, 2020, 09:44 by netaudit@protonmail.com:
Hi there,
I've set up a new Tor exit node around 15 hours ago but despite it had been such a time and my exit is visible from outside world I still get little to no traffic at all. I also cannot see my servers IP on bulk tor exit node list.
I checked the logs and everything seems alright too: [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Can you please tell me what I am missing here? Thank you
Sent with > ProtonMail <https://protonmail.com>> Secure Email.
On Sun, Oct 18, 2020 at 01:44:31PM +0000, netaudit wrote:
I've set up a new Tor exit node around 15 hours ago but despite it had been such a time and my exit is visible from outside world I still get little to no traffic at all. I also cannot see my servers IP on bulk tor exit node list.
relay-search (atlas.torproject.org) is a better way to search Tor relays than the bulk exit node list. But that said, if it has published its relay descriptor, but it isn't getting enough "Running" votes to make it into the consensus, it won't be on atlas. In that case, you can look it up by putting the identity fingerprint onto the form at the bottom of https://consensus-health.torproject.org/#relayinfo My guess is that it's the same situation as the person asking this question a few days ago -- it has an IPv6 address listed, but that IPv6 address is not reachable, so the relay isn't getting enough "Running" votes to get listed. Hope this helps! --Roger
Hi thank you for your reply As per your suggestion I checked it on the link you provided. I can see my exit relay here: https://consensus-health.torproject.org/consensus-health.html Its cyrexlinuz EEDDDD9C (the exit one) and its on the list and it looks okay to me. I am hosting 2 node relays with nickname cyrexlinuz. One of them is exit relay other one is middle relay. Middle relay Im not experiencing any problems with it so far. The exit relay has this fingerprint EEDDDD9C8D0CE02449BA17DF99E0285CACA467B5 But when I check this link for my exit node: https://metrics.torproject.org/rs.html#details/EEDDDD9C8D0CE02449BA17DF99E02... Its not there for some reason. I don't know. I also checked the exit relay logs for IPv6 configuration and it didn't log anything about IPv6. Thank you Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, October 19, 2020 4:57 AM, Roger Dingledine <arma@torproject.org> wrote:
On Sun, Oct 18, 2020 at 01:44:31PM +0000, netaudit wrote:
I've set up a new Tor exit node around 15 hours ago but despite it had been such a time and my exit is visible from outside world I still get little to no traffic at all. I also cannot see my servers IP on bulk tor exit node list.
relay-search (atlas.torproject.org) is a better way to search Tor relays than the bulk exit node list.
But that said, if it has published its relay descriptor, but it isn't getting enough "Running" votes to make it into the consensus, it won't be on atlas.
In that case, you can look it up by putting the identity fingerprint onto the form at the bottom of https://consensus-health.torproject.org/#relayinfo
My guess is that it's the same situation as the person asking this question a few days ago -- it has an IPv6 address listed, but that IPv6 address is not reachable, so the relay isn't getting enough "Running" votes to get listed.
Hope this helps! --Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hello Netaudit, I was having the same issue as you are currently. Check your IPv4 and IPv6 some authority's are stating your relay is running and others are not. My issue was i opened ports on IPv4 but not through IPv6. Please check this and let me know what you find. Thanks, John Csuti postmaster@coolcomputers.info On 10/20/2020 8:01 AM, netaudit wrote:
Hi thank you for your reply
As per your suggestion I checked it on the link you provided. I can see my exit relay here: https://consensus-health.torproject.org/consensus-health.html Its cyrexlinuz EEDDDD9C (the exit one) and its on the list and it looks okay to me.
I am hosting 2 node relays with nickname cyrexlinuz. One of them is exit relay other one is middle relay. Middle relay Im not experiencing any problems with it so far. The exit relay has this fingerprint EEDDDD9C8D0CE02449BA17DF99E0285CACA467B5
But when I check this link for my exit node: https://metrics.torproject.org/rs.html#details/EEDDDD9C8D0CE02449BA17DF99E02...
Its not there for some reason. I don't know. I also checked the exit relay logs for IPv6 configuration and it didn't log anything about IPv6.
Thank you
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, October 19, 2020 4:57 AM, Roger Dingledine <arma@torproject.org> wrote:
On Sun, Oct 18, 2020 at 01:44:31PM +0000, netaudit wrote:
I've set up a new Tor exit node around 15 hours ago but despite it had been such a time and my exit is visible from outside world I still get little to no traffic at all. I also cannot see my servers IP on bulk tor exit node list. relay-search (atlas.torproject.org) is a better way to search Tor relays than the bulk exit node list.
But that said, if it has published its relay descriptor, but it isn't getting enough "Running" votes to make it into the consensus, it won't be on atlas.
In that case, you can look it up by putting the identity fingerprint onto the form at the bottom of https://consensus-health.torproject.org/#relayinfo
My guess is that it's the same situation as the person asking this question a few days ago -- it has an IPv6 address listed, but that IPv6 address is not reachable, so the relay isn't getting enough "Running" votes to get listed.
Hope this helps! --Roger
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 Thanks, John Csuti (216) 633-1279
Hi, By looking at the descriptor of your relay, I found it tries to bind [::2]:9001. If I'm not mistaken this IPv6 address is in a reserved, unroutable range. That is probably why authorities supporting IPv6 can't reach your server and vote it not running. You should make sure your configuration does not contain `ORPort [::2]:9001` or something similar. Regards, Trinity Pointard Le mar. 20 oct. 2020 à 14:34, netaudit <netaudit@protonmail.com> a écrit :
Hi thank you for your reply
As per your suggestion I checked it on the link you provided. I can see my exit relay here: https://consensus-health.torproject.org/consensus-health.html Its cyrexlinuz EEDDDD9C (the exit one) and its on the list and it looks okay to me.
I am hosting 2 node relays with nickname cyrexlinuz. One of them is exit relay other one is middle relay. Middle relay Im not experiencing any problems with it so far. The exit relay has this fingerprint EEDDDD9C8D0CE02449BA17DF99E0285CACA467B5
But when I check this link for my exit node: https://metrics.torproject.org/rs.html#details/EEDDDD9C8D0CE02449BA17DF99E02...
Its not there for some reason. I don't know. I also checked the exit relay logs for IPv6 configuration and it didn't log anything about IPv6.
Thank you
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, October 19, 2020 4:57 AM, Roger Dingledine <arma@torproject.org> wrote:
On Sun, Oct 18, 2020 at 01:44:31PM +0000, netaudit wrote:
I've set up a new Tor exit node around 15 hours ago but despite it had been such a time and my exit is visible from outside world I still get little to no traffic at all. I also cannot see my servers IP on bulk tor exit node list.
relay-search (atlas.torproject.org) is a better way to search Tor relays than the bulk exit node list.
But that said, if it has published its relay descriptor, but it isn't getting enough "Running" votes to make it into the consensus, it won't be on atlas.
In that case, you can look it up by putting the identity fingerprint onto the form at the bottom of https://consensus-health.torproject.org/#relayinfo
My guess is that it's the same situation as the person asking this question a few days ago -- it has an IPv6 address listed, but that IPv6 address is not reachable, so the relay isn't getting enough "Running" votes to get listed.
Hope this helps! --Roger
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
participants (6)
-
John Csuti -
kaliania＠tutanota.com -
netaudit -
Roger Dingledine -
trinity Pointard -
zimmer linux