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
>
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:
>
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:
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
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
Oh sorry, I already opened a new discussion on this which is titled " Tor
relay says it is reachable, but is not appearing on the network." Yes, I
checked that and there is no other tor process running. Thanks.
--Keifer
On Thu, May 23, 2019 at 5:54 PM Conrad Rockenhaus
wrote:
>
> > On May 16,
> On May 16, 2019, at 10:31 PM, Keifer Bly wrote:
>
> Hi all,
>
> So I am running a new tor middle relay via a Google Cloud VPS but after the
> relay running for 1 day I am seeing this error
>
> May 16 18:23:50.000 [notice] Heartbeat: It seems like we are not in the
> cached consensus.
>
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
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
Hi,
> On 22 May 2019, at 16:24, tor-re...@riseup.net wrote:
>
> Do you think would be feasible to use SSH to forward all connections, except
> DNS queries, between my Lime2 and the remote VM in order to use an additional
> VM's IP?
I just wanted to highlight the DNS queries from your home
> On May 23, 2019, at 3:54 AM, tor-re...@riseup.net wrote:
>
> I think that a network based to much on remotes VMs, with closed source
> software running on the most deep machine level, is not very resilient and
> secure.
>
Actually, it’s very secure. By default, Tor doesn’t log anything but
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
I think that a network based to much on remotes VMs, with closed source
software running on the most deep machine level, is not very resilient
and secure.
So the reason why I was thinking to do so is that I wanted to run a
small exit relay on a device running only open source software, like
13 matches
Mail list logo
