Tor bridge on Windows 10 going down for a reason I cannot detect?
Hello all, for some reason my tor bridge at https://metrics.torproject.org/rs.html#details/148BD64BED9F2C27637D986DE032E... is randomly removed from the network. Tonight when I went to check it, tor metrics said it had said it was offline for the last 11 hours. This is very strange as I had not closed the tor software and my internet had not disconnected at all. Below is the tor log file, it is tor 0.3.4.8 on Windows 10, any thoughts would be great. Thanks. Oct 19 23:33:16.910 [notice] Tor 0.3.4.8 (git-da95b91355248ad8) running on Windows 8 with Libevent 2.1.8-stable, OpenSSL 1.0.2p, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A. Oct 19 23:33:16.910 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Oct 19 23:33:16.957 [notice] Read configuration file "C:\Users\keife\AppData\Roaming\tor\torrc.txt". Oct 19 23:33:16.972 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Users\keife\AppData\Roaming\tor\<default>. Is this what you wanted? Oct 19 23:33:16.972 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Users\keife\AppData\Roaming\tor\<default>. Is this what you wanted? Oct 19 23:33:16.972 [notice] Based on detected system memory, MaxMemInQueues is set to 2048 MB. You can override this by setting MaxMemInQueues by hand. Oct 19 23:33:16.972 [notice] Scheduler type KISTLite has been enabled. Oct 19 23:33:16.972 [notice] Opening OR listener on 0.0.0.0:9002 Oct 19 23:33:16.972 [notice] Opening Extended OR listener on 127.0.0.1:0 Oct 19 23:33:16.972 [notice] Extended OR listener listening on port 56515. Oct 19 23:33:57.000 [notice] Parsing GEOIP IPv4 file C:\Users\keife\AppData\Roaming\tor\geoip. Oct 19 23:33:57.000 [notice] Parsing GEOIP IPv6 file C:\Users\keife\AppData\Roaming\tor\geoip6. Oct 19 23:33:57.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now. Oct 19 23:33:58.000 [notice] Your Tor server's identity key fingerprint is 'torland 8C6C18F8D95918F9DC90A09827DAD285064F8872' Oct 19 23:33:58.000 [notice] Your Tor bridge's hashed identity key fingerprint is 'torland 148BD64BED9F2C27637D986DE032ECF14E5B9E9A' Oct 19 23:33:58.000 [notice] Bootstrapped 0%: Starting Oct 19 23:35:03.000 [notice] Starting with guard context "default" Oct 19 23:35:03.000 [notice] Bootstrapped 5%: Connecting to directory server Oct 19 23:35:05.000 [notice] Bootstrapped 10%: Finishing handshake with directory server Oct 19 23:35:05.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection Oct 19 23:35:05.000 [notice] Registered server transport 'obfs4' at '[::]:9002' Oct 19 23:35:05.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus Oct 19 23:35:06.000 [notice] Bootstrapped 50%: Loading relay descriptors Oct 19 23:35:06.000 [notice] Guessed our IP address as 174.87.240.59 (source: 136.243.176.148). Oct 19 23:35:15.000 [notice] Bootstrapped 80%: Connecting to the Tor network Oct 19 23:35:15.000 [notice] Bootstrapped 90%: Establishing a Tor circuit Oct 19 23:35:18.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Oct 19 23:35:18.000 [notice] Bootstrapped 100%: Done Oct 19 23:35:18.000 [notice] Now checking whether ORPort 174.87.240.59:9002 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) Oct 19 23:35:21.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Oct 19 23:36:44.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 1000 buildtimes. Oct 19 23:36:45.000 [notice] Performing bandwidth self-test...done. Oct 20 05:35:00.000 [notice] Heartbeat: Tor's uptime is 5:59 hours, with 0 circuits open. I've sent 3.08 MB and received 14.49 MB. Oct 20 05:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 20 11:35:00.000 [notice] Heartbeat: Tor's uptime is 11:59 hours, with 1 circuits open. I've sent 4.38 MB and received 19.35 MB. Oct 20 11:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 20 17:35:00.000 [notice] Heartbeat: Tor's uptime is 17:59 hours, with 0 circuits open. I've sent 5.74 MB and received 23.84 MB. Oct 20 17:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 20 20:49:17.000 [notice] Channel padding timeout scheduled 180307ms in the past. Oct 20 23:35:00.000 [notice] Heartbeat: Tor's uptime is 23:59 hours, with 1 circuits open. I've sent 7.19 MB and received 28.20 MB. Oct 20 23:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 21 05:35:00.000 [notice] Heartbeat: Tor's uptime is 1 day 5:59 hours, with 0 circuits open. I've sent 8.77 MB and received 34.02 MB. Oct 21 05:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 21 11:35:00.000 [notice] Heartbeat: Tor's uptime is 1 day 11:59 hours, with 0 circuits open. I've sent 10.16 MB and received 38.10 MB. Oct 21 11:35:00.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 21 17:35:00.000 [notice] Heartbeat: Tor's uptime is 1 day 17:59 hours, with 1 circuits open. I've sent 11.54 MB and received 43.60 MB. Oct 23 00:47:29.000 [notice] Diagnostic for issue 8387: Found 1 one-hop circuits more than 1800 seconds old! Logging 1... Oct 23 00:47:29.000 [notice] #0 created at 2018-10-21 17:34:12. open, General-purpose client. Not marked for close. Package window: 1000. usable for new conns. Dirty since 2018-10-21 17:34:13 (112396 seconds vs 600-second cutoff). Oct 23 00:47:29.000 [notice] It has been 112368 seconds since I last called circuit_expire_old_circuits_clientside(). Oct 23 00:47:29.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 23 00:47:29.000 [warn] Your system clock just jumped 112349 seconds forward; assuming established circuits no longer work. Oct 23 00:47:31.000 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent usable consensus. Oct 23 00:48:29.000 [notice] Heartbeat: Tor's uptime is 1 day 18:00 hours, with 1 circuits open. I've sent 11.54 MB and received 43.60 MB. Oct 23 00:48:29.000 [notice] Diagnostic for issue 8387: Found 1 one-hop circuits more than 1800 seconds old! Logging 1... Oct 23 00:48:29.000 [notice] #0 created at 2018-10-21 17:34:12. open, General-purpose client. Marked for close. Package window: 1000. Not usable for new conns. Dirty since 2018-10-21 17:24:13 (113056 seconds vs 600-second cutoff). Oct 23 00:48:29.000 [notice] It has been 59 seconds since I last called circuit_expire_old_circuits_clientside(). Oct 23 00:48:29.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Oct 23 00:48:32.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus. Oct 23 00:48:35.000 [notice] We now have enough directory information to build circuits. Oct 23 00:48:36.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Oct 23 00:48:36.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
On Tue, Oct 23, 2018 at 01:13:53AM -0700, Keifer Bly wrote:
Tonight when I went to check it, tor metrics said it had said it was offline for the last 11 hours.
Two thoughts, based on your log:
Oct 19 23:33:16.972 [notice] Opening OR listener on 0.0.0.0:9002 Oct 19 23:35:05.000 [notice] Registered server transport 'obfs4' at '[::]:9002'
It looks like your ORPort is 9002, and also your ServerTransportListenAddr is trying to use 9002? That could result in weirdness.
Oct 21 17:35:00.000 [notice] Heartbeat: Tor's uptime is 1 day 17:59 hours, with 1 circuits open. I've sent 11.54 MB and received 43.60 MB. Oct 23 00:47:29.000 [warn] Your system clock just jumped 112349 seconds forward; assuming established circuits no longer work.
Something weird happened here -- it's like the process went to sleep for 31 hours. This is the sort of thing that happens when you close your laptop and then open it 31 hours later. There are not many Windows relays (or bridges), so it could be all sorts of things -- a libevent bug? A thing that Microsoft chose to implement in a surprising way that's different from every other platform? An antivirus app that tried to hook the Tor process and ended up wedging it for 31 hours? A clock that jumped backwards by 31 hours? I wonder if it's https://trac.torproject.org/26360 --Roger
Something weird happened here -- it's like the process went to sleep for 31 hours. This is the sort of thing that happens when you close your laptop and then open it 31 hours later.
Good point out, but that seems very strange as it is a desktop computer my relay runs on, which is set (via the Windows sleep settings) to not turn fully off and only put the screen to sleep. The relay was online for a few days without interruption beforehand. I use Avast as my antivirus software, which notifies me if it detects something as a virus which it has not done. Strange. I am running the newest version of both tor and obfs4, and I keep Windows up to date as well. My web browser was playing a video the whole time which did not get interrupted at all, so it doesn't look like my internet stopped..? Thanks for the thoughts and help. Wonder what could have caused it out of the blue....
you should've redact Tor log to remove external IP address and unhashed fingerprint as this mailing list is public and can be read by anyone.
Ahhh... darn that's a good point. The good news is I have a dynamic ip (from my ISP) which shouldn't be too difficult to change if needed. On Tue, Oct 23, 2018 at 1:34 AM Roger Dingledine <arma@mit.edu> wrote:
On Tue, Oct 23, 2018 at 01:13:53AM -0700, Keifer Bly wrote:
Tonight when I went to check it, tor metrics said it had said it was offline for the last 11 hours.
Two thoughts, based on your log:
Oct 19 23:33:16.972 [notice] Opening OR listener on 0.0.0.0:9002 Oct 19 23:35:05.000 [notice] Registered server transport 'obfs4' at '[::]:9002'
It looks like your ORPort is 9002, and also your ServerTransportListenAddr is trying to use 9002? That could result in weirdness.
Oct 21 17:35:00.000 [notice] Heartbeat: Tor's uptime is 1 day 17:59 hours, with 1 circuits open. I've sent 11.54 MB and received 43.60 MB. Oct 23 00:47:29.000 [warn] Your system clock just jumped 112349 seconds forward; assuming established circuits no longer work.
Something weird happened here -- it's like the process went to sleep for 31 hours. This is the sort of thing that happens when you close your laptop and then open it 31 hours later.
There are not many Windows relays (or bridges), so it could be all sorts of things -- a libevent bug? A thing that Microsoft chose to implement in a surprising way that's different from every other platform? An antivirus app that tried to hook the Tor process and ended up wedging it for 31 hours? A clock that jumped backwards by 31 hours?
I wonder if it's https://trac.torproject.org/26360
--Roger
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I noticed that the system is running Windows10? If this is the situation then you might want to downgrade the server to anything. Not knowing the ISP service I cannot say for certain, but, ATT and most of the cable companies have signed agreements with NSA and DHS to interrupt services to the dark web, or at least report and track access. MS Win10 is actually copying everything back to the MS servers furthering Bill Gates dream of having "Every Computer in the World on a single peer to peer network". See if there is a "Router" log that might identify an external access problem or "Denial of access" issue. Good Luck!!! On Tue, Oct 23, 2018 at 1:47 PM Keifer Bly <keifer.bly@gmail.com> wrote:
Something weird happened here -- it's like the process went to sleep for 31 hours. This is the sort of thing that happens when you close your laptop and then open it 31 hours later.
Good point out, but that seems very strange as it is a desktop computer my relay runs on, which is set (via the Windows sleep settings) to not turn fully off and only put the screen to sleep. The relay was online for a few days without interruption beforehand. I use Avast as my antivirus software, which notifies me if it detects something as a virus which it has not done. Strange. I am running the newest version of both tor and obfs4, and I keep Windows up to date as well. My web browser was playing a video the whole time which did not get interrupted at all, so it doesn't look like my internet stopped..?
Thanks for the thoughts and help. Wonder what could have caused it out of the blue....
you should've redact Tor log to remove external IP address and unhashed fingerprint as this mailing list is public and can be read by anyone.
Ahhh... darn that's a good point. The good news is I have a dynamic ip (from my ISP) which shouldn't be too difficult to change if needed.
On Tue, Oct 23, 2018 at 1:34 AM Roger Dingledine <arma@mit.edu> wrote:
On Tue, Oct 23, 2018 at 01:13:53AM -0700, Keifer Bly wrote:
Tonight when I went to check it, tor metrics said it had said it was offline for the last 11 hours.
Two thoughts, based on your log:
Oct 19 23:33:16.972 [notice] Opening OR listener on 0.0.0.0:9002 Oct 19 23:35:05.000 [notice] Registered server transport 'obfs4' at '[::]:9002'
It looks like your ORPort is 9002, and also your ServerTransportListenAddr is trying to use 9002? That could result in weirdness.
Oct 21 17:35:00.000 [notice] Heartbeat: Tor's uptime is 1 day 17:59 hours, with 1 circuits open. I've sent 11.54 MB and received 43.60 MB. Oct 23 00:47:29.000 [warn] Your system clock just jumped 112349 seconds forward; assuming established circuits no longer work.
Something weird happened here -- it's like the process went to sleep for 31 hours. This is the sort of thing that happens when you close your laptop and then open it 31 hours later.
There are not many Windows relays (or bridges), so it could be all sorts of things -- a libevent bug? A thing that Microsoft chose to implement in a surprising way that's different from every other platform? An antivirus app that tried to hook the Tor process and ended up wedging it for 31 hours? A clock that jumped backwards by 31 hours?
I wonder if it's https://trac.torproject.org/26360
--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
Source?
On 23. Oct 2018, at 23:13, Mike Mitch <cointrio@gmail.com> wrote:
I noticed that the system is running Windows10? If this is the situation then you might want to downgrade the server to anything. Not knowing the ISP service I cannot say for certain, but, ATT and most of the cable companies have signed agreements with NSA and DHS to interrupt services to the dark web, or at least report and track access. MS Win10 is actually copying everything back to the MS servers furthering Bill Gates dream of having "Every Computer in the World on a single peer to peer network". See if there is a "Router" log that might identify an external access problem or "Denial of access" issue. Good Luck!!!
which part? MS statement by Bill Gates was a Article published in I think it was '95 or 6. The contracts with cable companies are published via trades over the last several years (6-7) AT&T does not like the idea of a part of the I'net they don't control and have stated that "Anytime we find a user on a TOR network we will slow down their connection" this about 8 years ago. Access with DHS and NSA are strictly participatory and like with "Facebook in 2016" questionably illegal based on "FISA" warrants and your 6th amendment right to face your accuser. All this, of course is the reason Julian Asange and Edward Snowden have been forced to flee the country. But then again, I am no one... On Tue, Oct 23, 2018 at 2:15 PM niftybunny <abuse@to-surf-and-protect.net> wrote:
Source?
On 23. Oct 2018, at 23:13, Mike Mitch <cointrio@gmail.com> wrote:
I noticed that the system is running Windows10? If this is the situation then you might want to downgrade the server to anything. Not knowing the ISP service I cannot say for certain, but, ATT and most of the cable companies have signed agreements with NSA and DHS to interrupt services to the dark web, or at least report and track access. MS Win10 is actually copying everything back to the MS servers furthering Bill Gates dream of having "Every Computer in the World on a single peer to peer network". See if there is a "Router" log that might identify an external access problem or "Denial of access" issue. Good Luck!!!
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 23. Oct 2018, at 23:26, Mike Mitch <cointrio@gmail.com> wrote:
which part?
All of them. Because I cant find (quick duckduckgo search) anything about this. And Wireshark would notice some packets on the wire if Windows 10 would copy anything back to MS. Also can´t find anything about AT&T.
MS statement by Bill Gates was a Article published in I think it was '95 or 6. The contracts with cable companies are published via trades over the last several years (6-7) AT&T does not like the idea of a part of the I'net they don't control and have stated that "Anytime we find a user on a TOR network we will slow down their connection" this about 8 years ago. Access with DHS and NSA are strictly participatory and like with "Facebook in 2016" questionably illegal based on "FISA" warrants and your 6th amendment right to face your accuser. All this, of course is the reason Julian Asange and Edward Snowden have been forced to flee the country. But then again, I am no one...
On Tue, Oct 23, 2018 at 2:15 PM niftybunny <abuse@to-surf-and-protect.net <mailto:abuse@to-surf-and-protect.net>> wrote: Source?
On 23. Oct 2018, at 23:13, Mike Mitch <cointrio@gmail.com <mailto:cointrio@gmail.com>> wrote:
I noticed that the system is running Windows10? If this is the situation then you might want to downgrade the server to anything. Not knowing the ISP service I cannot say for certain, but, ATT and most of the cable companies have signed agreements with NSA and DHS to interrupt services to the dark web, or at least report and track access. MS Win10 is actually copying everything back to the MS servers furthering Bill Gates dream of having "Every Computer in the World on a single peer to peer network". See if there is a "Router" log that might identify an external access problem or "Denial of access" issue. Good Luck!!!
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays <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
➢ “AT&T does not like the idea of a part of the I'net they don't control and have stated that "Anytime we find a user on a TOR network we will slow down their connection" this about 8 years ago. “ The isp is not AT&T, which I agree would be a bad idea with the profiling they’ve been doing on users since at least 2006. The ISP is Charter. I have been running a relay for some time without much issue, and tor browser works fine on the same PC (it seems to me like the tor browser would not work either if it were an issue with tor being frowned upon). From: niftybunny Sent: Tuesday, October 23, 2018 2:33 PM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Tor bridge on Windows 10 going down for a reason Icannot detect? On 23. Oct 2018, at 23:26, Mike Mitch <cointrio@gmail.com> wrote: which part? All of them. Because I cant find (quick duckduckgo search) anything about this. And Wireshark would notice some packets on the wire if Windows 10 would copy anything back to MS. Also can´t find anything about AT&T. MS statement by Bill Gates was a Article published in I think it was '95 or 6. The contracts with cable companies are published via trades over the last several years (6-7) AT&T does not like the idea of a part of the I'net they don't control and have stated that "Anytime we find a user on a TOR network we will slow down their connection" this about 8 years ago. Access with DHS and NSA are strictly participatory and like with "Facebook in 2016" questionably illegal based on "FISA" warrants and your 6th amendment right to face your accuser. All this, of course is the reason Julian Asange and Edward Snowden have been forced to flee the country. But then again, I am no one... On Tue, Oct 23, 2018 at 2:15 PM niftybunny <abuse@to-surf-and-protect.net> wrote: Source?
On 23. Oct 2018, at 23:13, Mike Mitch <cointrio@gmail.com> wrote:
I noticed that the system is running Windows10? If this is the situation then you might want to downgrade the server to anything. Not knowing the ISP service I cannot say for certain, but, ATT and most of the cable companies have signed agreements with NSA and DHS to interrupt services to the dark web, or at least report and track access. MS Win10 is actually copying everything back to the MS servers furthering Bill Gates dream of having "Every Computer in the World on a single peer to peer network". See if there is a "Router" log that might identify an external access problem or "Denial of access" issue. Good Luck!!!
_______________________________________________ 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
UPDATE: When I came home today, tor had been down for 1 hour, when I checked the pc the tor software (the tor expert bundle cmd application) had exited, which is strange as I never closed it. Perhaps there is something with the Windows command line that causes tor to quit? Your thoughts are appreciated, thank you. From: Keifer Bly Sent: Wednesday, October 24, 2018 5:39 PM To: tor-relays@lists.torproject.org Subject: RE: [tor-relays] Tor bridge on Windows 10 going down for a reasonIcannot detect? ➢ “AT&T does not like the idea of a part of the I'net they don't control and have stated that "Anytime we find a user on a TOR network we will slow down their connection" this about 8 years ago. “ The isp is not AT&T, which I agree would be a bad idea with the profiling they’ve been doing on users since at least 2006. The ISP is Charter. I have been running a relay for some time without much issue, and tor browser works fine on the same PC (it seems to me like the tor browser would not work either if it were an issue with tor being frowned upon). From: niftybunny Sent: Tuesday, October 23, 2018 2:33 PM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Tor bridge on Windows 10 going down for a reason Icannot detect? On 23. Oct 2018, at 23:26, Mike Mitch <cointrio@gmail.com> wrote: which part? All of them. Because I cant find (quick duckduckgo search) anything about this. And Wireshark would notice some packets on the wire if Windows 10 would copy anything back to MS. Also can´t find anything about AT&T. MS statement by Bill Gates was a Article published in I think it was '95 or 6. The contracts with cable companies are published via trades over the last several years (6-7) AT&T does not like the idea of a part of the I'net they don't control and have stated that "Anytime we find a user on a TOR network we will slow down their connection" this about 8 years ago. Access with DHS and NSA are strictly participatory and like with "Facebook in 2016" questionably illegal based on "FISA" warrants and your 6th amendment right to face your accuser. All this, of course is the reason Julian Asange and Edward Snowden have been forced to flee the country. But then again, I am no one... On Tue, Oct 23, 2018 at 2:15 PM niftybunny <abuse@to-surf-and-protect.net> wrote: Source?
On 23. Oct 2018, at 23:13, Mike Mitch <cointrio@gmail.com> wrote:
I noticed that the system is running Windows10? If this is the situation then you might want to downgrade the server to anything. Not knowing the ISP service I cannot say for certain, but, ATT and most of the cable companies have signed agreements with NSA and DHS to interrupt services to the dark web, or at least report and track access. MS Win10 is actually copying everything back to the MS servers furthering Bill Gates dream of having "Every Computer in the World on a single peer to peer network". See if there is a "Router" log that might identify an external access problem or "Denial of access" issue. Good Luck!!!
_______________________________________________ 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 --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
On Tue, 23 Oct 2018 01:13:53 -0700 Keifer Bly <keifer.bly@gmail.com> wrote:
Hello all, for some reason my tor bridge at https://metrics.torproject.org/rs.html#details/148BD64BED9F2C27637D986DE032E... is randomly removed from the network. Tonight when I went to check it, tor metrics said it had said it was offline for the last 11 hours. This is very strange as I had not closed the tor software and my internet had not disconnected at all. Below is the tor log file, it is tor 0.3.4.8 on Windows 10, any thoughts would be great. Thanks.
<Log snip>
Giving metrics link with hashed fingerprint is fine, but you should've redact Tor log to remove external IP address and unhashed fingerprint as this mailing list is public and can be read by anyone.
participants (5)
-
Dmitrii Tcvetkov -
Keifer Bly -
Mike Mitch -
niftybunny -
Roger Dingledine