Upgrade your 'PGSamsTorNode' Tor relay?
Hi, You are running a Tor exit relay, which is great: http://rougmnvswfsmd4dq.onion/rs.html#details/B92168B497A17F97D4EF8DD1FE1E72... First: 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! Second: let us know if there is any way to help you bump up the bandwidth that you are allocating to the Tor relay. :) You can find Tor packages for your distro / OS here: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecific... Ideally you will switch to keeping up with our stable releases, but if you need a stable that is especially stable, the Tor 0.3.5 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. 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
Hi Roger Thank you for your email. I tried upgrading as you suggested, however, my server is so outdated the upgrade killed my database and web servers as the configs are not compatible. I had to roll back to a backup. I have set up another relay, PGSams2TORNode (version 0.3.10), with much the same config on a new server. I will either update the current server or just migrate its content to the new one and host the exit relay there. Regards Paul On Mon, Sep 2, 2019 at 10:49 AM Roger Dingledine <arma@torproject.org> wrote:
Hi,
You are running a Tor exit relay, which is great:
http://rougmnvswfsmd4dq.onion/rs.html#details/B92168B497A17F97D4EF8DD1FE1E72...
First: 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!
Second: let us know if there is any way to help you bump up the bandwidth that you are allocating to the Tor relay. :)
You can find Tor packages for your distro / OS here:
https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecific...
Ideally you will switch to keeping up with our stable releases, but if you need a stable that is especially stable, the Tor 0.3.5 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.
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
-- Paul Greeff email@paulgreeff.com Office: +27 86 100 3117 Cell: +27 83 954 3453 Fax: 086 659 0511 Winlink: zs6io@winlink.org
On Thu, Sep 05, 2019 at 11:39:57AM +0200, Paul Greeff wrote:
I tried upgrading as you suggested, however, my server is so outdated the upgrade killed my database and web servers as the configs are not compatible. I had to roll back to a backup.
I have set up another relay, PGSams2TORNode (version 0.3.10), with much the same config on a new server. I will either update the current server or just migrate its content to the new one and host the exit relay there.
Hi Paul, Sounds like a great plan -- but it looks like the newer relay isn't running at this point either? You mention above that it's "version 0.3.10", which isn't really a Tor version, but if it's version 0.3.0 through 0.3.4, we ended up removing those from the network last week: https://blog.torproject.org/removing-end-life-relays-network Let us know if we can help further! :) Thanks, --Roger
Hi Roger Apologies, it is version 0.3.2.10, not 0.3.10. [image: image.png] However, if you've removed all nodes versions 0.3.0 through 0.3.4 then it will not work. I've added the PPA to get the latest version on the new server. It seems Ubuntu doesn't update their version regularly. [image: image.png] Regards Paul On Sun, Oct 13, 2019 at 11:08 AM Roger Dingledine <arma@torproject.org> wrote:
On Thu, Sep 05, 2019 at 11:39:57AM +0200, Paul Greeff wrote:
I tried upgrading as you suggested, however, my server is so outdated the upgrade killed my database and web servers as the configs are not compatible. I had to roll back to a backup.
I have set up another relay, PGSams2TORNode (version 0.3.10), with much the same config on a new server. I will either update the current server or just migrate its content to the new one and host the exit relay there.
Hi Paul,
Sounds like a great plan -- but it looks like the newer relay isn't running at this point either?
You mention above that it's "version 0.3.10", which isn't really a Tor version, but if it's version 0.3.0 through 0.3.4, we ended up removing those from the network last week: https://blog.torproject.org/removing-end-life-relays-network
Let us know if we can help further! :)
Thanks, --Roger
-- Paul Greeff email@paulgreeff.com Office: +27 86 100 3117 Cell: +27 83 954 3453 Fax: 086 659 0511 Winlink: zs6io@winlink.org
On Sun, Oct 13, 2019 at 01:27:07PM +0200, Paul Greeff wrote:
Apologies, it is version 0.3.2.10, not 0.3.10. [image: image.png]
However, if you've removed all nodes versions 0.3.0 through 0.3.4 then it will not work.
I've added the PPA to get the latest version on the new server. It seems Ubuntu doesn't update their version regularly.
Awesome, looks like it's working and happily on 0.4.1.6 now. Great. (And yes, Ubuntu is alas famous for including packages from Debian and then never bothering to update them. Sad but true.) Thanks, --Roger
participants (2)
-
Paul Greeff -
Roger Dingledine