I’ve been trying to run a new relay for the last two weeks, however my relay never receives flags after publishing descriptors. I have seen in my logs that my ORPort is reachable:
[notice] Performing bandwidth self-test…done.
[notice] Self-testing indicates your ORPort 91.230.41.32:9053 is reachable from the outside. Excellent. Publishing server descriptor.
[notice] Now checking whether IPv4 ORPort 91.230.41.32:9053 is reachable… (this may take up to 20 minutes – look for log messages indicating success)
I believe that my torrc file is configured correctly:
I’m not sure what to do, I had run my relay for ~5 days but never received flags. When I check nyx it just shows flags: none. I have since been trying to reconfigure the relay to see if its a configuration issue, but all relays I had run in the past would receive flags within a day.
I’ve been trying to run a new relay for the last two weeks, however my relay never receives flags after publishing descriptors. I have seen in my logs that my ORPort is reachable:
[notice] Performing bandwidth self-test…done.
[notice] Self-testing indicates your ORPort 91.230.41.32:9053 is reachable from the outside. Excellent. Publishing server descriptor.
[notice] Now checking whether IPv4 ORPort 91.230.41.32:9053 is reachable… (this may take up to 20 minutes – look for log messages indicating success)
I believe that my torrc file is configured correctly:
I’m not sure what to do, I had run my relay for ~5 days but never received flags. When I check nyx it just shows flags: none. I have since been trying to reconfigure the relay to see if its a configuration issue, but all relays I had run in the past would receive flags within a day.
If you check on https://consensus-health.torproject.org/ (enter you
nickname or fingerprint on the bottom of the page) you can see that your
relay gets the V2Dir and Valid flags, so that’s good. The problem is,
though, that it only gets the Running flag from 3 directory authorities
indicating that they have trouble reaching your node. It seems your
relay is in UAE and they might block connections to the other 6
directory authorities? You could check on your server whether it’s
actually able to reach any of them as a next step in your debugging process.
In my debug logs, I see that connections to some authorities fail:
[info] connection_dir_client_request_failed(): Giving up on serverdesc/extrainfo fetch from directory server at 128.31.0.39:9231; retrying
[info] connection_dir_client_request_failed(): Giving up on serverdesc/extrainfo fetch from directory server at 204.13.164.118:80; retrying
[info] connection_dir_client_request_failed(): Giving up on serverdesc/extrainfo fetch from directory server at 171.25.193.9:443; retrying
[info] connection_dir_client_request_failed(): Giving up on serverdesc/extrainfo fetch from directory server at 193.23.244.244:80; retrying
[info] connection_dir_client_request_failed(): Giving up on serverdesc/extrainfo fetch from directory server at 131.188.40.189:80; retrying
While this relay is running in the UAE, it is running on an unfiltered network at a university, so there are no issues with connections being blocked on our end. Is it possible that the directory authorities are blocking connections from the UAE? If so, is there a way to get our relay whitelisted? We would like to run a high bandwidth guard and eventually an exit node.
In my debug logs, I see that connections to some authorities fail:
[info] connection_dir_client_request_failed(): Giving up on serverdesc/extrainfo fetch from directory server at 128.31.0.39:9231; retrying
[info] connection_dir_client_request_failed(): Giving up on serverdesc/extrainfo fetch from directory server at 204.13.164.118:80; retrying
[info] connection_dir_client_request_failed(): Giving up on serverdesc/extrainfo fetch from directory server at 171.25.193.9:443; retrying
[info] connection_dir_client_request_failed(): Giving up on serverdesc/extrainfo fetch from directory server at 193.23.244.244:80; retrying
[info] connection_dir_client_request_failed(): Giving up on serverdesc/extrainfo fetch from directory server at 131.188.40.189:80; retrying
While this relay is running in the UAE, it is running on an unfiltered network at a university, so there are no issues with connections being blocked on our end. Is it possible that the directory authorities are blocking connections from the UAE? If so, is there a way to get our relay whitelisted? We would like to run a high bandwidth guard and eventually an exit node.
No, directory authorities do not block connections from UAE. You could
do some traceroutes from your server to them to figure out where the
block is happening.