Re: [tor-relays] Tor relay says it is reachable, but is not appearing on the network.

Hi, so I am now auto upgrading tor using the method at https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntuUpdates Upon testing, this is what I got. Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: []

Re: [tor-relays] Tor relay says it is reachable, but is not appearing on the network.

Hello, My bust, confirmation bias. Thanks, Conrad On Thu, May 23, 2019 at 11:45 PM teor wrote: > Hi, > > > On 24 May 2019, at 14:08, Conrad Rockenhaus > wrote: > > > > In April 2018 Google released an update that caused VPNs and Tor > services to stop working on GCE and App Engine. It was a

Re: [tor-relays] Tor relay says it is reachable, but is not appearing on the network.

Hi, > On 24 May 2019, at 11:41, Keifer Bly wrote: > > Hi all, so I believe I found the problem. In my torrc file, there was a rogue > line which read "PublishServerDescriptor" with nothing after it. I removed > this line and restarted the relay, now it is saying "May 24 01:38:16.000 >

Re: [tor-relays] Tor relay says it is reachable, but is not appearing on the network.

Hi, > On 24 May 2019, at 14:08, Conrad Rockenhaus wrote: > > In April 2018 Google released an update that caused VPNs and Tor services to > stop working on GCE and App Engine. It was a long planned network update. > > The following ticket refers: >

Re: [tor-relays] Tor relay says it is reachable, but is not appearing on the network.

Hi, I apologize for top posting, but it’ll be the simplest way to convey the message. In April 2018 Google released an update that caused VPNs and Tor services to stop working on GCE and App Engine. It was a long planned network update. The following ticket refers:

Re: [tor-relays] Tor relay says it is reachable, but is not appearing on the network.

Hi all, so I believe I found the problem. In my torrc file, there was a rogue line which read "PublishServerDescriptor" with nothing after it. I removed this line and restarted the relay, now it is saying "May 24 01:38:16.000 [notice] Self-testing indicates your ORPort is reachable from the

Re: [tor-relays] Tor relay says it is reachable, but is not appearing on the network.

Hi, > On 24 May 2019, at 09:19, Keifer Bly wrote: > > Hi all, so this is the tor log since the last restart. It includes the relay > fingerprint. The tor version is (0.2.9.16-1). The log you posted is missing a few lines at the start, including the lines that tell us the tor version. We need

Re: [tor-relays] Tor relay says it is reachable, but is not appearing on the network.

Hi all, so this is the tor log since the last restart. It includes the relay fingerprint. The tor version is (0.2.9.16-1). When I tried updating tor I got a message saying that was the newest version. The relay has an assigned static ip and port which are both allowed by the firewall. It seems

Re: [tor-relays] Tor relay says it is reachable, but is not appearing on the network.

Hi, > On 23 May 2019, at 18:41, Dmitrii Tcvetkov wrote: > > On Tue, 21 May 2019 23:36:28 -0700 > Keifer Bly wrote: > >> Hi, so the relay in question does indeed have a reserved Static IP >> (104.154.93.253), and the traffic is allowed by the firewall, but the >> relay is still not appearing

Re: [tor-relays] Tor relay says it is reachable, but is not appearing on the network.

On Tue, 21 May 2019 23:36:28 -0700 Keifer Bly wrote: > Hi, so the relay in question does indeed have a reserved Static IP > (104.154.93.253), and the traffic is allowed by the firewall, but the > relay is still not appearing in the consensus. The port it's running > on is 65534. This is starting

Re: [tor-relays] Tor relay says it is reachable, but is not appearing on the network.

Hi, so the relay in question does indeed have a reserved Static IP (104.154.93.253), and the traffic is allowed by the firewall, but the relay is still not appearing in the consensus. The port it's running on is 65534. This is starting to seem odd.any thoughts are appreciated. Thanks. --Keifer

Re: [tor-relays] Tor relay says it is reachable, but is not appearing on the network.

Yes, the reserved external ip is 104.154.93.253 , and the port is allowed on the firewall. So the relay should appear now. Please check if it is reachable and I will keep checking it over the next few hours. Thanks. --Keifer On Tue, May 21, 2019 at 1:16 AM teor wrote:

Re: [tor-relays] Tor relay says it is reachable, but is not appearing on the network.

Hi, > On 21 May 2019, at 16:11, Keifer Bly wrote: > > Hi all, something very strange is going on with my relay called torworld. This looks like the same question as your previous thread: https://lists.torproject.org/pipermail/tor-relays/2019-May/017317.html Did you assign a static address to