<div dir="ltr"><div>I'm back in business!!!! THANK YOU!!<br></div><div><br></div><div>So I changed a couple of ports and also opened those on my router. Previously I only had 9030 & 9001. I've added DirPort on 9051, Socks on 9050. I've actually got 4 ports open on the router for TOR - 9001, 9030, 9050 & 9051.</div><div><br></div><div>I set 9030 as my control port in torrc - does that port need to be open on the router? Or can I remove that port forward? I have one of the authentication methods unhashed, so I believe that protects that somewhat.<br></div><div><br></div><div>netstat -tlpn returns the following:</div><div><br></div><div>Active Internet connections (only servers)<br>Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name <br>tcp 0 0 <a href="http://0.0.0.0:9051">0.0.0.0:9051</a> 0.0.0.0:* LISTEN 9531/tor <br>tcp 0 0 <a href="http://127.0.0.1:9030">127.0.0.1:9030</a> 0.0.0.0:* LISTEN 9531/tor <br>tcp 0 0 <a href="http://0.0.0.0:9001">0.0.0.0:9001</a> 0.0.0.0:* LISTEN 9531/tor <br>tcp 0 0 <a href="http://127.0.0.1:5939">127.0.0.1:5939</a> 0.0.0.0:* LISTEN 1342/teamviewerd <br>tcp 0 0 <a href="http://127.0.0.53:53">127.0.0.53:53</a> 0.0.0.0:* LISTEN 747/systemd-resolve <br>tcp 0 0 <a href="http://127.0.0.1:631">127.0.0.1:631</a> 0.0.0.0:* LISTEN 6055/cupsd <br>tcp 0 0 <a href="http://127.0.0.1:9050">127.0.0.1:9050</a> 0.0.0.0:* LISTEN 9531/tor <br>tcp6 0 0 ::1:631 :::* LISTEN 6055/cupsd<br></div><div><br></div><div>nyx appears to be running fine now. I can see the graph and log messages like previously.</div><div>It pulled my previous Nickname, but I currently have no flags, so I'm guessing that will update later.</div><div><br></div><div>I've got the exit policy set to reject *:* however, as I don't want to blow my ISP off.</div><div><br></div><div>Is that about it? Can anyone think of anything else I need to check?</div><div><br></div><div>Thank you to everyone who offered solutions!<br></div><div><br></div><div><br></div><div><br></div><div class="gmail_quote"><div dir="ltr">On Thu, Sep 20, 2018 at 4:19 AM Chad MILLER <<a href="mailto:chad@cornsilk.net">chad@cornsilk.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div dir="auto">I maintain the tor-middle-relay Snap package. It listens on system-chosen, arbitrary ports. May be useful to you, itself, or to steal ideas from.</div><div dir="auto"><br></div><div dir="auto">$ sudo snap install tor-middle-relay</div><div dir="auto"><br></div><div dir="auto"><br></div><div><br><br><div class="gmail_quote"></div></div></div><div dir="auto"><div><div class="gmail_quote"><div dir="ltr">On Wed, Sep 19, 2018, 04:56 Ben Riley <<a href="mailto:blades1000@gmail.com" target="_blank">blades1000@gmail.com</a>> wrote:<br></div></div></div></div><div dir="auto"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>First off, will outline that I am very much a newbie, but was able to get a relay up and running on a Ubuntu machine. It was running fine for maybe 12 months (MelbTorBox), with a few resets and software updates along the way.</div><div><br></div><div>Just doing my bit to help the network.</div><div><br></div><div>Anyway, after the Ubuntu upgrade, I had to re-install TOR and I believed I did it basically the same way.</div><div><br></div><div>Unfortunately, that appears not to be the case.</div><div>I've posted the error messages on the Ubuntu forum hoping to get assistance, but no joy:</div><div><a href="https://askubuntu.com/questions/1070469/18-04-tor-relay-error-could-not-bind-to-0-0-0-09050-address-already-in-use-i" rel="noreferrer" target="_blank">https://askubuntu.com/questions/1070469/18-04-tor-relay-error-could-not-bind-to-0-0-0-09050-address-already-in-use-i</a></div><div><br></div><div>I'm now coming to the experts to see if I can resurrect relay before I pull the pin on the idea. <br></div><div><br></div><div>I have BASIC Unix knowledge (I can type commands and that's about it). I think I might have a couple of copies installed in different places and I know I have the TOR browser installed (it works fine).</div><div><br></div><div>When I type 'nyx' it replies with:</div><div>Unable to connect to tor. Maybe it's running without a ControlPort?<br><br></div><div>So I type 'tor' and get<br></div><div>Sep 19 21:34:24.819 [notice] Tor 0.3.4.8 (git-5da0e95e4871a0a1) running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.0g, Zlib 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3.<br>Sep 19 21:34:24.819 [notice] Tor can't help you if you use it wrong! Learn how to be safe at <a href="https://www.torproject.org/download/download#warning" rel="noreferrer" target="_blank">https://www.torproject.org/download/download#warning</a><br>Sep 19 21:34:24.819 [notice] Read configuration file "/etc/tor/torrc".<br>Sep 19 21:34:24.823 [notice] Based on detected system memory, MaxMemInQueues is set to 2862 MB. You can override this by setting MaxMemInQueues by hand.<br>Sep 19 21:34:24.824 [notice] Scheduler type KIST has been enabled.<br>Sep 19 21:34:24.824 [notice] Opening Socks listener on <a href="http://127.0.0.1:9050" rel="noreferrer" target="_blank">127.0.0.1:9050</a><br>Sep 19 21:34:24.824 [notice] Opening Control listener on <a href="http://127.0.0.1:9051" rel="noreferrer" target="_blank">127.0.0.1:9051</a><br>Sep 19 21:34:24.824 [notice] Opening OR listener on <a href="http://0.0.0.0:9001" rel="noreferrer" target="_blank">0.0.0.0:9001</a><br>Sep 19 21:34:24.824 [notice] Opening Directory listener on <a href="http://0.0.0.0:9050" rel="noreferrer" target="_blank">0.0.0.0:9050</a><br>Sep 19 21:34:24.824 [warn] Could not bind to <a href="http://0.0.0.0:9050" rel="noreferrer" target="_blank">0.0.0.0:9050</a>: Address already in use. Is Tor already running?<br>Sep 19 21:34:24.824 [notice] Closing partially-constructed Socks listener on <a href="http://127.0.0.1:9050" rel="noreferrer" target="_blank">127.0.0.1:9050</a><br>Sep 19 21:34:24.824 [notice] Closing partially-constructed Control listener on <a href="http://127.0.0.1:9051" rel="noreferrer" target="_blank">127.0.0.1:9051</a><br>Sep 19 21:34:24.824 [notice] Closing partially-constructed OR listener on <a href="http://0.0.0.0:9001" rel="noreferrer" target="_blank">0.0.0.0:9001</a><br>Sep 19 21:34:24.824 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.<br>Sep 19 21:34:24.824 [err] Reading config failed--see warnings above.<br></div><div><br></div><div>I 'think' my original torrc file may have somehow survived the Ubuntu upgrade, but I don't know how as I did a wipe and re-install of Ubuntu. But when I edited it, there were my contact details sitting there.</div><div><br></div><div>Very appreciative of any help!</div><div><br></div><div>Thanks</div><div>Ben.<br></div></div></blockquote></div></div></div><div dir="auto"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
_______________________________________________<br>
tor-relays mailing list<br>
<a href="mailto:tor-relays@lists.torproject.org" rel="noreferrer" target="_blank">tor-relays@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
</blockquote></div></div></div></blockquote></div></div>