Hi,
You are running a fast Tor relay, which is great: http://rougmnvswfsmd4dq.onion/rs.html#details/2D82EF77EB07AF2B3B1BC140AAB527...
But that Tor version is obsolete, and because of old bugs, we will soon cut relays running those versions out of the network. Please consider upgrading!
The Tor 0.3.5 long-term-stable branch will be maintained until Feb 2022: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorR... and you can see the lifetimes of other Tor versions on that table too.
You can find Tor packages for your distro / OS here: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecific...
Let us know if we can do anything to make the process easier.
And lastly, I am cc'ing the new network health mailing list (which has public archives), to help us stay synced: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkHealthTeam
Thanks! --Roger
I am unable to up grade to a newer version do to the error i am getting below and I am not a wiz at Unbuntu
Err:3 https://deb.torproject.org/torproject.org bionic InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 74A941BA219EC810 Reading package lists... Done N: Ignoring file 'tor' in directory '/etc/apt/sources.list.d/' as it has no file name extension W: GPG error: https://deb.torproject.org/torproject.org bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 74A941BA219EC810 E: The repository 'https://deb.torproject.org/torproject.org bionic InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default.
--
On 08/28/2019 11:53 PM, Roger Dingledine wrote:
Hi,
You are running a fast Tor relay, which is great: http://rougmnvswfsmd4dq.onion/rs.html#details/2D82EF77EB07AF2B3B1BC140AAB527...
But that Tor version is obsolete, and because of old bugs, we will soon cut relays running those versions out of the network. Please consider upgrading!
The Tor 0.3.5 long-term-stable branch will be maintained until Feb 2022: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorR... and you can see the lifetimes of other Tor versions on that table too.
You can find Tor packages for your distro / OS here: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecific...
Let us know if we can do anything to make the process easier.
And lastly, I am cc'ing the new network health mailing list (which has public archives), to help us stay synced: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkHealthTeam
Thanks! --Roger
I attempted yo upgrade my server and get this reeoe
*[keith@ubuntuserver ~]# sudo apt update && sudo apt install -y --only-upgrade tor*
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease Get:2 https://deb.torproject.org/torproject.org bionic InRelease [4,244 B] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Err:2 https://deb.torproject.org/torproject.org bionic InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 74A941BA219EC810 Reading package lists... W: GPG error: https://deb.torproject.org/torproject.org bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 74A941BA219EC810 E: The repository 'https://deb.torproject.org/torproject.org bionic InRelease' is not signed.
[keith@ubuntuserver ~]#
Thanks
Keith
On 08/28/2019 11:53 PM, Roger Dingledine wrote:
Hi,
You are running a fast Tor relay, which is great: http://rougmnvswfsmd4dq.onion/rs.html#details/2D82EF77EB07AF2B3B1BC140AAB527...
But that Tor version is obsolete, and because of old bugs, we will soon cut relays running those versions out of the network. Please consider upgrading!
The Tor 0.3.5 long-term-stable branch will be maintained until Feb 2022: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorR... and you can see the lifetimes of other Tor versions on that table too.
You can find Tor packages for your distro / OS here: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecific...
Let us know if we can do anything to make the process easier.
And lastly, I am cc'ing the new network health mailing list (which has public archives), to help us stay synced: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkHealthTeam
Thanks! --Roger
On Sat, Oct 19, 2019 at 07:47:20PM -0400, Keith Walters wrote:
I attempted yo upgrade my server and get this reeoe The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 74A941BA219EC810
It sounds like you skipped the step where you import the gpg signature key for the repository.
Did you do the "curl | gpg --import" line, and the "gpg --export|apt-key add" line, from https://support.torproject.org/apt/tor-deb-repo/ ?
--Roger
I ran the 2 lines and receive the error can only be used by root. But I am $
keith@ubuntuserver:~$ curl https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CD BA8F512EE8CBC9E886DDD89.asc | gpg --import % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 19665 100 19665 0 0 39647 0 --:--:-- --:--:-- --:--:-- 39647 gpg: key EE8CBC9E886DDD89: 36 signatures not checked due to missing keys gpg: key EE8CBC9E886DDD89: "deb.torproject.org archive signing key" not changed gpg: Total number processed: 1 gpg: unchanged: 1
keith@ubuntuserver:~$ gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | apt-key add - E: This command can only be used by root. keith@ubuntuserver:~$ curl https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CD BA8F512EE8CBC9E886DDD89.asc | gpg --import % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 19665 100 19665 0 0 26646 0 --:--:-- --:--:-- --:--:-- 26610 gpg: key EE8CBC9E886DDD89: 36 signatures not checked due to missing keys gpg: key EE8CBC9E886DDD89: "deb.torproject.org archive signing key" not changed gpg: Total number processed: 1 gpg: unchanged: 1 keith@ubuntuserver:~$ gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | apt-key add - E: This command can only be used by root. keith@ubuntuserver:~$
On 10/20/2019 7:21 AM, Roger Dingledine wrote:
On Sat, Oct 19, 2019 at 07:47:20PM -0400, Keith Walters wrote:
I attempted yo upgrade my server and get this reeoe The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 74A941BA219EC810
It sounds like you skipped the step where you import the gpg signature key for the repository.
Did you do the "curl | gpg --import" line, and the "gpg --export|apt-key add" line, from https://support.torproject.org/apt/tor-deb-repo/ ?
--Roger
On Sun, Oct 20, 2019 at 10:30:46AM -0400, Keith Walters wrote:
I ran the 2 lines and receive the error can only be used by root. But I am $
Hi Keith,
Yes, you need to be running that "apt-key add" command as root. That's how apt knows how to check (and how to trust) the deb.torproject.org repository.
Are you somehow unable to become root on this computer? If so, maybe you need to talk to the administrator for it?
Thanks! --Roger
Ok, I was able to get it to upgrade (I think as i received no error messages during the install) Now when i check my log file I receive error
Oct 24 21:42:25.000 [notice] Now checking whether ORPort 208.38.243.113:9001 and DirPort 208.38.243.113:9030 are reachable... (this may take up to 20 minutes -- look for log messages indicating success) Oct 24 21:42:27.000 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. Oct 24 21:42:27.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Oct 24 21:43:24.000 [warn] http status 400 ("Bad Request") response from dirserver '154.35.175.225:80'. Please correct. Oct 24 21:43:24.000 [warn] http status 400 ("Bad Request") response from dirserver '199.58.81.140:80'. Please correct. Oct 24 21:43:24.000 [warn] http status 400 ("Bad Request") response from dirserver '204.13.164.118:80'. Please correct. Oct 24 21:43:24.000 [warn] http status 400 ("Bad Request") response from dirserver '131.188.40.189:80'. Please correct. Oct 24 21:43:24.000 [warn] http status 400 ("Bad Request") response from dirserver '86.59.21.38:80'. Please correct. Oct 24 21:43:24.000 [warn] http status 400 ("Fingerprint is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver '171.25.193.9:443'. Please correct. Oct 24 21:43:26.000 [notice] Performing bandwidth self-test...done.
On 10/24/2019 1:00 AM, Roger Dingledine wrote:
On Sun, Oct 20, 2019 at 10:30:46AM -0400, Keith Walters wrote:
I ran the 2 lines and receive the error can only be used by root. But I am $
Hi Keith,
Yes, you need to be running that "apt-key add" command as root. That's how apt knows how to check (and how to trust) the deb.torproject.org repository.
Are you somehow unable to become root on this computer? If so, maybe you need to talk to the administrator for it?
Thanks! --Roger
Still not working time is correct on my server. Fingerprint rejected. Not sure how to correct.
Nov 03 09:51:10.000 [warn] Received directory with skewed time (DIRSERV:86.59.21.38:80): It seems that our clock is ahead by 11 hours, 1 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time, timezone, and date settings. Nov 03 10:12:10.000 [warn] Received directory with skewed time (DIRSERV:131.188.40.189:80): It seems that our clock is ahead by 1 days, 12 hours, 25 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time, timezone, and date settings. Nov 03 10:29:10.000 [warn] http status 400 ("Bad Request") response from dirserver '154.35.175.225:80'. Please correct. Nov 03 10:29:10.000 [warn] http status 400 ("Bad Request") response from dirserver '199.58.81.140:80'. Please correct. Nov 03 10:29:11.000 [warn] http status 400 ("Bad Request") response from dirserver '204.13.164.118:80'. Please correct. Nov 03 10:29:11.000 [warn] http status 400 ("Bad Request") response from dirserver '131.188.40.189:80'. Please correct. Nov 03 10:29:11.000 [warn] http status 400 ("Bad Request") response from dirserver '86.59.21.38:80'. Please correct. Nov 03 10:29:11.000 [warn] http status 400 ("Fingerprint is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver '171.25.193.9:443'. Please correct. Nov 03 10:53:10.000 [warn] Received directory with skewed time (DIRSERV:154.35.175.225:80): It seems that our clock is ahead by 13 hours, 13 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time, timezone, and date settings. Nov 03 11:30:11.000 [warn] Received directory with skewed time (DIRSERV:45.66.33.45:80): It seems that our clock is ahead by 1 days, 10 hours, 19 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
On 10/24/2019 1:00 AM, Roger Dingledine wrote:
On Sun, Oct 20, 2019 at 10:30:46AM -0400, Keith Walters wrote:
I ran the 2 lines and receive the error can only be used by root. But I am $
Hi Keith,
Yes, you need to be running that "apt-key add" command as root. That's how apt knows how to check (and how to trust) the deb.torproject.org repository.
Are you somehow unable to become root on this computer? If so, maybe you need to talk to the administrator for it?
Thanks! --Roger
On 03 Nov (11:39:55), Keith Walters wrote:
Still not working time is correct on my server. Fingerprint rejected. Not sure how to correct.
Sorry about the delays! We've pushed the unreject rule today. Your relay should be able to join the network as soon as a majority of directory authorities apply the rule.
Maximum a couple days.
Big thanks again for running a relay and sticking with us!
David
network-health@lists.torproject.org
-
David Goulet -
Keith Walters -
Roger Dingledine