[tor-relays] First time configuring a bridge - no log - doesnt work
Hi, I want to configure a tor obfs4 bridge on a raspberry pi 3B+. My system is Kali Linux. I followed this documentation: https://community.torproject.org/relay/setup/bridge/debian-ubuntu/ Actually, when i want to check the log in /var/log/tor, the folder is empty. TOr is running but nothing happens. here's my torrc file : RunAsDaemon 1 BridgeRelay 1 Log notice file /var/log/tor/notices.log Log debug file /var/log/tor/debug.log Log notice syslog Log debug stderr # Replace "TODO1" with a Tor port of your choice. This port must be externally # reachable. Avoid port 9001 because it's commonly associated with Tor and # censors may be scanning the Internet for this port. ORPort 4433 ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy # Replace "TODO2" with an obfs4 port of your choice. This port must be # externally reachable and must be different from the one specified for ORPort. # Avoid port 9001 because it's commonly associated with # Tor and censors may be scanning the Internet for this port. ServerTransportListenAddr obfs4 0.0.0.0:1234 # Local communication port between Tor and obfs4. Always set this to "auto". # "Ext" means "extended", not "external". Don't try to set a specific port number, nor listen on 0.0.0.0. ExtORPort auto # Replace "" with your email address so we can contact you if there are problems with your bridge. # This is optional but encouraged. ContactInfo # # Pick a nickname that you like for your bridge. This is optional. Nickname RageAgainstTheMachine ExitPolicy reject *:* I've tried to check everything but i can't find why it doesn't work. Any help / advice would be appreciated. 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
Re: [tor-relays] First time configuring a bridge - no log - doesnt work
Hi, I finally found the reason. My nickname was way to long. I changed it and now it is working. Thanks for your reply. Envoyé depuis ProtonMail mobile Message d'origine On 3 nov. 2019 à 17:47, Volker Mink a écrit : > Can you please check your syslog and journalctl? > > Gesendet: Donnerstag, 31. Oktober 2019 um 23:58 Uhr > Von: "David Strappazon" > An: "tor-relays@lists.torproject.org" > Betreff: [tor-relays] First time configuring a bridge - no log - doesnt work > Hi, > I want to configure a tor obfs4 bridge on a raspberry pi 3B+. My system is > Kali Linux. > > I followed this documentation: > https://community.torproject.org/relay/setup/bridge/debian-ubuntu/ > > Actually, when i want to check the log in /var/log/tor, the folder is empty. > TOr is running but nothing happens. > > here's my torrc file : > > RunAsDaemon 1 > BridgeRelay 1 > > Log notice file /var/log/tor/notices.log > Log debug file /var/log/tor/debug.log > Log notice syslog > Log debug stderr > > # Replace "TODO1" with a Tor port of your choice. This port must be > externally > # reachable. Avoid port 9001 because it's commonly associated with Tor and > # censors may be scanning the Internet for this port. > ORPort 4433 > > ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy > > # Replace "TODO2" with an obfs4 port of your choice. This port must be > # externally reachable and must be different from the one specified for > ORPort. > # Avoid port 9001 because it's commonly associated with > # Tor and censors may be scanning the Internet for this port. > ServerTransportListenAddr obfs4 0.0.0.0:1234 > > # Local communication port between Tor and obfs4. Always set this to "auto". > # "Ext" means "extended", not "external". Don't try to set a specific port > number, nor listen on 0.0.0.0. > ExtORPort auto > > # Replace "" with your email address so we can contact you > if there are problems with your bridge. > # This is optional but encouraged. > ContactInfo # > > # Pick a nickname that you like for your bridge. This is optional. > Nickname RageAgainstTheMachine > > ExitPolicy reject *:* > > I've tried to check everything but i can't find why it doesn't work. > > Any help / advice would be appreciated. > > 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___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Tor stopped suddenly - clock/time issue
Hi, while checking my (new)or not this is what i saw in notices.log Nov 05 05:18:57.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Nov 05 10:44:17.000 [notice] Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now. Nov 05 10:44:18.000 [notice] Delaying directory fetches: We are hibernating or shutting down. Nov 05 10:44:47.000 [notice] Clean shutdown finished. Exiting. Apr 11 18:28:44.000 [notice] Tor 0.4.1.6 opening log file. Apr 11 18:28:44.103 [notice] Tor 0.4.1.6 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.4.3. Apr 11 18:28:44.103 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Apr 11 18:28:44.103 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Apr 11 18:28:44.103 [notice] Read configuration file "/etc/tor/torrc". Apr 11 18:28:44.125 [notice] Based on detected system memory, MaxMemInQueues is set to 694 MB. You can override this by setting MaxMemInQueues by hand. Apr 11 18:28:44.128 [notice] Opening Socks listener on 127.0.0.1:9050 Apr 11 18:28:44.128 [notice] Opened Socks listener on 127.0.0.1:9050 Apr 11 18:28:44.128 [notice] Opening OR listener on 0.0.0.0:4433 Apr 11 18:28:44.128 [notice] Opened OR listener on 0.0.0.0:4433 Apr 11 18:28:44.128 [notice] Opening Extended OR listener on 127.0.0.1:0 Apr 11 18:28:44.128 [notice] Extended OR listener listening on port 40247. Apr 11 18:28:44.128 [notice] Opened Extended OR listener on 127.0.0.1:40247 Apr 11 18:28:44.000 [notice] Bootstrapped 0% (starting): Starting Apr 11 18:28:44.000 [warn] Received local state file with skewed time (/var/lib/tor/state): It seems that our clock is behind by 207 days, 17 hours, 16 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings. Apr 11 18:28:44.000 [warn] Problem bootstrapping. Stuck at 0% (starting): Starting. (Clock skew -17946963 in local state file from /var/lib/tor/state; CLOCK_SKEW; count 1; recommendation warn; host ? at ?) Nov 05 10:45:34.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. Nov 05 10:45:35.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. Nov 05 10:45:35.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. Nov 05 10:45:43.000 [notice] Your Tor server's identity key fingerprint is 'citizenfour B839503CA8F877D0263A38103DAF47EF302FBCF7' Nov 05 10:45:43.000 [notice] Your Tor bridge's hashed identity key fingerprint is 'citizenfour 9D1CCBE7EEF99FCCA6F767838FA08B23DDFABB3A' Nov 05 10:45:44.000 [warn] Our clock is 207 days, 16 hours, 31 minutes behind the time published in the consensus network status document (2019-11-05 09:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings! Nov 05 10:45:44.000 [warn] Received ns flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 207 days, 16 hours, 31 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings. Nov 05 10:45:44.000 [warn] Problem bootstrapping. Stuck at 0% (starting): Starting. (Clock skew -17944276 in ns flavor consensus from CONSENSUS; CLOCK_SKEW; count 2; recommendation warn; host ? at ?) Nov 05 10:45:45.000 [warn] Our clock is 207 days, 15 hours, 31 minutes behind the time published in the consensus network status document (2019-11-05 08:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings! Nov 05 10:45:45.000 [warn] Received microdesc flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 207 days, 15 hours, 31 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings. Nov 05 10:45:45.000 [warn] Problem bootstrapping. Stuck at 0% (starting): Starting. (Clock skew -17940676 in microdesc flavor consensus from CONSENSUS; CLOCK_SKEW; count 3; recommendation warn; host ? at ?) Nov 05 10:47:44.000 [notice] Starting with guard context "default" Nov 05 10:47:44.000 [notice] Signaled readiness to systemd Nov 05 10:47:44.000 [notice] Registered server transport 'obfs4' at '[::]:1234' Nov 05 10:47:45.000 [notice] Bootstrapped 5% (conn): Connecting to a relay Nov 05 10:47:45.000 [notice] Opening Socks listener on /run/tor/socks Nov 05 10:47:45.000 [notice] Opened Socks listener on /run/tor/socks Nov 05 10:47:45.000 [notice] Opening Control listener on /run/tor/control Nov 05 10:47:45.000 [notice] Opened Control listener on /run/tor/control Nov 05 10:47:45.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay Nov 05 10:47:47.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay Nov 0
[tor-relays] Tor stop / reboot by itself + weird logs (hacking?)
Hello everyone, i'm running a bridge on a raspberry Pi 3B+ on Kali Linux. Everything looks fine but after checking the logs i noticed that the service rebooted by itself in the middle on the night: Nov 06 03:51:09.000 [notice] Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now. Nov 06 03:51:10.000 [notice] Delaying directory fetches: We are hibernating or shutting down. Nov 06 03:51:39.000 [notice] Clean shutdown finished. Exiting. etc... Then after that, it works again (will check tonight /tomorrow if it reboots again). I'm trying to find why it is rebooting but without success. I checked all logs possible and also notice this in journalctl -xe: nov. 06 19:37:58 kali-pi sshd[15920]: Failed password for root from X port 37494 ssh2 nov. 06 19:38:03 kali-pi sshd[15920]: Failed password for root from port 37494 ssh2 nov. 06 19:38:08 kali-pi sshd[15920]: Failed password for root from X port 37494 ssh2 nov. 06 19:38:13 kali-pi sshd[15920]: Failed password for root from X port 37494 ssh2 nov. 06 19:38:18 kali-pi sshd[15920]: Failed password for root from X port 37494 ssh2 nov. 06 19:38:18 kali-pi sshd[15920]: error: maximum authentication attempts exceeded for root from 21> nov. 06 19:38:18 kali-pi sshd[15920]: Disconnecting authenticating user root 2 port 37494: > nov. 06 19:38:18 kali-pi sshd[15920]: PAM 5 more authentication failures; logname= uid=0 euid=0 tty=ss> nov. 06 19:38:18 kali-pi sshd[15920]: PAM service(sshd) ignoring max retries; 6 > 3 nov. 06 19:38:21 kali-pi sshd[15950]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid> nov. 06 19:38:22 kali-pi sshd[15953]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid> nov. 06 19:38:23 kali-pi sshd[15950]: Failed password for root from port 64786 ssh2 nov. 06 19:38:23 kali-pi sshd[15953]: Failed password for root from X port 6739 ssh2 There's two different IP that i don't know. A whois says it's a Chinese provider... Should i consider that someone is trying to break into my home network? 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
[tor-relays] Newbie question about bridge
Hi, all I configure a bridge on October the 31th. On the first days I had to reboot it multiple times but few days later I had all the necessary flags, fast and stable include. Now I'm at 9+ days of uptime, I lost the fast and stable flags and the advertised bandwidth is at 792 KiB/s when my bandwidth is configured at 3 MB/s with burst at 6 MB. Of course I haven't seen a single client. My question is: is it normal and part of a relay/bridge lifecycle or is there something wrong? Ps: on metrics.torproject.org, everything is fine. Nothing wrong in my logs either and I can use it when configuring my it in a tor browser. Any opinions or advices would be welcome. David. Envoyé depuis ProtonMail mobile___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] bridge relay search is "wrong"
Hi, My bridge appears down when checking "tor relay search" on smartphone and up when checking the site from a laptop. Is there a reason? does someone already had the same issue? 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
Re: [tor-relays] bridge relay search is "wrong"
Yes, sure. Here is the URL : https://metrics.torproject.org/rs.html#details/9D1CCBE7EEF99FCCA6F767838FA08B23DDFABB3A I should have said that despite the fact that the bridge was "red" and down for 2 hours (even is that was not the case), there's no trace of it. I'm going to take a look at the ticket. Envoyé depuis ProtonMail mobile Message d'origine On 23 nov. 2019 à 23:30, Roger Dingledine a écrit : > On Sat, Nov 23, 2019 at 05:04:07PM +, David Strappazon wrote: >> Hi, >> >> My bridge appears down when checking "tor relay search" on smartphone and up >> when checking the site from a laptop. >> >> Is there a reason? does someone already had the same issue? > > Can you post the relay-search url so we can see it happening? > > (relay-search urls, even for bridges, should be safe to post, because > they don't have any information that could be used to find (and therefore > block) the bridge.) > > See also > https://bugs.torproject.org/31763 > for a ticket that might be related (or might not be -- it depends what > you are seeing). > > --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
Re: [tor-relays] bridge relay search is "wrong"
I just noticed that when it was down on my smartphone, it was up on my laptop. But yeah, mine still shows an uptime of 11+ days. Envoyé depuis ProtonMail mobile Message d'origine On 23 nov. 2019 à 23:58, Toralf Förster a écrit : > On 11/23/19 6:04 PM, David Strappazon wrote: >> My bridge appears down when checking "tor relay search" on smartphone >> and up when checking the site from a laptop. > You're sure that this is related to smartphone/laptop? > > Because 2 weeks ago my my bridge was marked as "down" too, but after few > hours is was marked as "up" and showed an uptime of about 100 days (as > expected). > > -- > Toralf > > ___ > 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
Re: [tor-relays] New operator
Hi, Thank for your advices. Device: Raspberry pi 3B+ OS: Linux kali-pi 4.19.66-Re4son-v7+ Bandwith (tested on the raspberry with speedtest-cli): - Download: 308.94 Mbit/s - Upload: 267.11 Mbit/s torrc file: RunAsDaemon 1 BridgeRelay 1 Log notice file /var/log/tor/notices.log #Log debug file /var/log/tor/debug.log #Log notice syslog #Log debug stderr # Replace "TODO1" with a Tor port of your choice. This port must be externally # reachable. Avoid port 9001 because it's commonly associated with Tor and # censors may be scanning the Internet for this port. ORPort 4433 ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy # Replace "TODO2" with an obfs4 port of your choice. This port must be # externally reachable and must be different from the one specified for ORPort. # Avoid port 9001 because it's commonly associated with # Tor and censors may be scanning the Internet for this port. ServerTransportListenAddr obfs4 0.0.0.0:1234 # Local communication port between Tor and obfs4. Always set this to "auto". # "Ext" means "extended", not "external". Don't try to set a specific port numb er, nor listen on 0.0.0.0. ExtORPort auto # Replace "" with your email address so we can contact you if there are problems with your bridge. # This is optional but encouraged. ContactInfo ## # Pick a nickname that you like for your bridge. This is optional. Nickname citizenfour RelayBandwidthRate 3 MB RelayBandwidthBurst 6 MB ExitPolicy reject *:* I don't have "PublishServerDescriptor" in my conf. Should i? Tor logs (notices.log) look ok: Nov 23 15:41:35.000 [notice] New control connection opened. Nov 23 17:45:38.000 [notice] New control connection opened. Nov 23 20:31:41.000 [notice] Heartbeat: Tor's uptime is 11 days 0:00 hours, with 5 circuits open. I've sent 134.74 MB and received 1.01 GB. Nov 23 20:31:41.000 [notice] Heartbeat: In the last 6 hours, I have seen 1 unique clients. Nov 24 02:31:41.000 [notice] Heartbeat: Tor's uptime is 11 days 6:00 hours, with 0 circuits open. I've sent 136.02 MB and received 1.01 GB. Nov 24 02:31:41.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Nov 24 08:31:41.000 [notice] Heartbeat: Tor's uptime is 11 days 12:00 hours, with 0 circuits open. I've sent 137.11 MB and received 1.02 GB. Nov 24 08:31:41.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Nov 24 14:31:41.000 [notice] Heartbeat: Tor's uptime is 11 days 18:00 hours, with 14 circuits open. I've sent 138.59 MB and received 1.02 GB. Nov 24 14:31:41.000 [notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients. Bridge is listed as up on tor relay search: https://metrics.torproject.org/rs.html#details/9D1CCBE7EEF99FCCA6F767838FA08B23DDFABB3A Nyx says: 14:49:17 [NOTICE] New control connection opened. [1 duplicate hidden] x 14:31:41 [NOTICE] Heartbeat: In the last 6 hours, I have seen 0 unique clients. [2 x duplicates hidden] x 14:31:41 [NOTICE] Heartbeat: Tor's uptime is 11 days 18:00 hours, with 14 circuits x open. I've sent 138.59 MB and received 1.02 GB. [2 duplicates hidden] xlq November 23, 2019 qk xx20:31:41 [NOTICE] Heartbeat: In the last 6 hours, I have seen 1 unique clients. x xx20:31:41 [NOTICE] Heartbeat: Tor's uptime is 11 days 0:00 hours, with 5 circuits x xx open. I've sent 134.74 MB and received 1.01 GB. [3 duplicates hidden] etc. Sometime i see many circuits and "connectons" but right now everything is blank or at 0 (bandwith use). i just shared the connexion from my smartphone to connect to tor with my laptop (that the only thing i can do right now). i'm connected to my bridge and can browse. If i download a file ( 1GB) i can see some connections (10 outbound) in nyx and the bandwith use increases. I don't know..despite the fact that everthing looks fine to me, i lost the fast and stable flag, sometime tor relay search says the bridge is down and in 11 days nobody connected to my bridge (ecepted me). Sent with [ProtonMail](https://protonmail.com) Secure Email. ‐‐‐ Original Message ‐‐‐ Le dimanche 24 novembre 2019 12:17, a écrit : > > On Thursday, November 21, 2019 at 7:29 PM, Mario Costa > wrote: > >> >> >>> Il giorno 21 nov 2019, alle ore 15:49, Matt Traudt >>> ha scritto: >>> >>> Thanks for running a bridge. >>> >>> Check Tor's logs to make sure it is actually running and doesn't report >>> issues. Search its hashed fingerprint on >>> https://metrics.torproject.org/rs.html and make sure it is listed as up. >>> Verify you did *not* set 'PublishServerDescriptor 0'. Verify you can use >>> your bridge from outside your home. I once had a residential ISP that >>> blocked inbound port 80 but not 443. >> >> This actually made me realize that my home router would not properly forward >> ports 80 and 443 from outside. I could connect to my bridge from the LAN >> (even using my external
[tor-relays] Stable and fast flags
Hi, How long is it supposed to take to get the stable and fast flags? My bridge is up since 13 days. At the beginning I had both flags then I lost them because of a reboot I think. Since, they never came back. Envoyé depuis ProtonMail mobile___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Accounting limits seem to cause permanent hibernation
Hi, i could be wrong but I think as soon as the limite is reached, the server is going to hibernate until the next day. Envoyé depuis ProtonMail mobile Message d'origine On 2 déc. 2019 à 12:00, Manuel Wiesinger a écrit : > Hello everyone, > > I configured an accounting limit on my tor relay. 1-2 days after restarting > the tor service the relay seems to go into permanent hibernation. Once I > restart the service traffic is sent and received as expected, however after > 1-2 days it seems to go into permanent hibernation again until I restart the > service. The longest hibernation period was for about three month(!). > > My configuration: > > Tor 0.4.1.6, on FreeBSD 12.1. (nothing else running on the machine) > > My relevant settings: > > AccountingMax 128 GBytes > AccountingStart day 00:00 > > RelayBandwidthRate 2560 KBytes > RelayBandwidthBurst 5120 KBytes > > Logs since the last restart: https://pastebin.com/wk04zDC8 > > Metrics: > https://metrics.torproject.org/rs.html#details/A3BB86337E003A2668E016466EA3AAA6222E50A8 > (The peeks in the graphs match the times when I manually restarted the > service) > > Since I experience this 'permanent hibernation' since at least last August, I > wonder if it's expected behavior, e.g., caused by the small limit of 128 GB > per day, or if it's a bug (possibly related to this one: > https://lists.torproject.org/pipermail/tor-relays/2019-October/017862.html ?). > > Best, > Manuel > ___ > 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
Re: [tor-relays] Stable and fast flags
Ok, thank you. Envoyé depuis ProtonMail mobile Message d'origine On 4 déc. 2019 à 01:48, teor a écrit : > Hi, > >> On 27 Nov 2019, at 09:21, David Strappazon >> wrote: >> >> Hi, >> >> How long is it supposed to take to get the stable and fast flags? >> >> My bridge is up since 13 days. At the beginning I had both flags then I lost >> them because of a reboot I think. Since, they never came back. > > Bridge clients don't use the Stable and Fast flags. So it's not > worth worrying about them. > > Maybe we could adjust Relay Search to make that clearer? > > T > ___ > 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
Re: [tor-relays] Can anyone help with this issue?
Webmin is very, VERY, insecure. I just used it on Hackthebox to hack a machine (version 18.1.1 if I remember well). Avoid it at all cost. Envoyé depuis ProtonMail mobile Message d'origine On 7 janv. 2020 à 10:36, a écrit : > On 06.01.2020 10:41, John Csuti wrote: > >> Ign:5 http://download.webmin.com/download/repository sarge InRelease > > Debian sarge? Is at least 10-20 years old! I was still young when I had > that on the record ;-) > Webmin is very insecure and can mess up your config. > >> Ign:6 https://deb.torproject.org/torproject.org xenial InRelease >> Err:8 https://deb.torproject.org/torproject.org xenial Release >> server certificate verification failed. CAfile: >> /etc/ssl/certs/ca-certificates.crt CRLfile: none >> Reading package lists... Done >> E: The repository 'https://deb.torproject.org/torproject.org xenial >> Release' does not have a Release file. > > This sometimes happens when the repo is being updated. > Or the certificate in the repo has expired. You can choose another > Tor-mirror to test. > > -- > ╰_╯ Ciao Marco! > > My family:6D6EC2A2E2ED8BFF2D4834F8D669D82FC2A9FA8D > ___ > 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
[tor-relays] Relay keeps crashing (raspberry)
Hi, I've been running a bridge since october without issue. But two days ago i realized that my raspberry keep craching like every two hours or so. Nothing changed. I'm running kali linux (re4son kernel) on a raspberry PI 3 +. The logs don't show anything. Sometime on screen i have a thermometer icon but when i check the temperature in real time it is never over 60°C. I have updated and upgrading everything: same problem. My power supply looks ok. Any idea of what i should check or do to fix the problem? It worked very well for months. does saving my "key" and reinstalling everything could help? any tips would be welcome. regards, David 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
Re: [tor-relays] Relay keeps crashing (raspberry)
Hi, Thanks for your reply. You will find my answer below. Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ Le dimanche 17 mai 2020 23:11, Alexander Færøy a écrit : > Hello, > > On 2020/05/17 09:55, David Strappazon wrote: > > > I've been running a bridge since october without issue. But two days > > ago i realized that my raspberry keep craching like every two hours or > > so. > > Does the RPi crash? Or does Tor crash? The RPI craches (it is frozen). When > it happens i'm disconnected from SSH, i can't ping the RPI and if i check the > screen i can see the Desktop but can't move the mouse. I have to use the > switch to turn it off and on. > > What happens when the crash happens? Does the device reboot? Does it > stay in some unrecoverable, sad state? Or something entirely different? No, > it is just frozen. > > > I have updated and upgrading everything: same problem. My power supply > > looks ok. > > Are you sure the power supply is able to supply the RPi during longer > peak periods of CPU activity? I don't know how to check it (will look for > answer). it is the power supply i had when i ordered my ABOX kit. It is > supposed to be a 5,1V - 3A power supply with a switch. > > Have a look at this table[1] and make sure that your power supply allows > enough current for the RPi to run in a stable manner. I have seen some > stability issues with an RPi where I used a random power supply that was > not powerful enough. For what i understand it seems ok. > > You could try to artificially create CPU load on the system and see if > it becomes unstable after a while. Haven't done it yet but i will. Anyway i > doubt it is the problem. It's a very "small" bridge and the best i had is 10 > connexions a day. > > > does saving my "key" and reinstalling everything could help? > > Difficult to say at this point. We need a bit more information here. > > All the best, > Alex. > > [1]: > https://www.raspberrypi.org/documentation/hardware/raspberrypi/power/README.md > > - > > Alexander Færøy > > 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
[tor-relays] warn message in notices .log after reinstallation of the relay (and restore of torrc and "keys" folder)
Hi, I had issues with my bridge who is running on a Raspberry pi 3+ so i've decided to completely reinstall it. First i saved my torrc file and my "keys" folder from /var/lib/tor. First thing i did after a clean install of the server was to copy and paste my torrc file in /etc/tor/ and the files "ed25519_master_id_secret_key" and "secret_id_key" in the keys directory. Anyway after starting Tor i had the following messages in notices.log: [warn] http status 400 '"looks like your keypair has changed?...etc...etc... i decided to completely replace the content of the keys folder by my backup but i still have the same message. When i go to Tor relay search i see my bridge with two different identities and both are offline ( one of the hashed fingerprints is the right one). Anyway if i run "nyx" i can see that Tor is working, reachable from the outside and some circuits are built. I suspect i make a mistake with the "keys" but i'm a little bit lost. Can you guys help me please ? 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
