Hello, im having a problem with arm.
Everytime i open it it apears this: [ARM_WARN] The torrc differs from what tor's using. You can issue a x sighup to reload the torrc values by pressing x. qj - torrc values differ on lines: 2, 3
Even by restarting tor service it shows the same error again and again
Could it be a problem with my config?
BandwidthBurst 8MBytes BandwidthRate 7MBytes ORPort 9001 DirPort 9030 ExitPolicy reject *:* ContactInfo administrator@anonmail.me Nickname AnonMailMe DisableDebuggerAttachment 0
A week has passed since i started my relay and i cant see it on tor globe yet: F40FEF3A1326EFC5D73E4FE6DB6EB0791E4082A1
Is it possible that the Tor service uses the config from /etc and that arm reads a torrc created under the user who runs arm? That's how I explain the same message on my server...
Your server isn't shown on globe/atlas... what says your tor logfile? Everything ok there?
Am 21.03.2017 um 20:09 schrieb Javier Benito Santoni javierbs@anonmail.me:
Hello, im having a problem with arm.
Everytime i open it it apears this: [ARM_WARN] The torrc differs from what tor's using. You can issue a x sighup to reload the torrc values by pressing x. qj - torrc values differ on lines: 2, 3
Even by restarting tor service it shows the same error again and again
Could it be a problem with my config?
BandwidthBurst 8MBytes BandwidthRate 7MBytes ORPort 9001 DirPort 9030 ExitPolicy reject *:* ContactInfo administrator@anonmail.me Nickname AnonMailMe DisableDebuggerAttachment 0
A week has passed since i started my relay and i cant see it on tor globe yet: F40FEF3A1326EFC5D73E4FE6DB6EB0791E4082A1
-- My PGP Public Key: https://box.anonmail.me/javikey.txt
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Mar 21 06:27:37.000 [notice] Tor 0.2.4.27 (git-412e3f7dc9c6c01a) opening new log file. Mar 21 06:31:19.000 [warn] Your server (51.15.9.105:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. Mar 21 06:31:19.000 [warn] Your server (51.15.9.105:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
This is the logfile, the relay is hosted on a private server, maybe its firewall? I dont have a lot of expirience with ubuntu firewall could you explain me which command should i run please.
Thank you for your help!
El 21/03/2017 a las 20:36, Sebastian Hoffmann escribió:
Is it possible that the Tor service uses the config from /etc and that arm reads a torrc created under the user who runs arm? That's how I explain the same message on my server...
Your server isn't shown on globe/atlas... what says your tor logfile? Everything ok there?
Am 21.03.2017 um 20:09 schrieb Javier Benito Santoni javierbs@anonmail.me:
Hello, im having a problem with arm.
Everytime i open it it apears this: [ARM_WARN] The torrc differs from what tor's using. You can issue a x sighup to reload the torrc values by pressing x. qj - torrc values differ on lines: 2, 3
Even by restarting tor service it shows the same error again and again
Could it be a problem with my config?
BandwidthBurst 8MBytes BandwidthRate 7MBytes ORPort 9001 DirPort 9030 ExitPolicy reject *:* ContactInfo administrator@anonmail.me Nickname AnonMailMe DisableDebuggerAttachment 0
A week has passed since i started my relay and i cant see it on tor globe yet: F40FEF3A1326EFC5D73E4FE6DB6EB0791E4082A1
-- My PGP Public Key: https://box.anonmail.me/javikey.txt
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
Javier Benito Santoni:
Mar 21 06:27:37.000 [notice] Tor 0.2.4.27 (git-412e3f7dc9c6c01a) opening new log file. Mar 21 06:31:19.000 [warn] Your server (51.15.9.105:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. Mar 21 06:31:19.000 [warn] Your server (51.15.9.105:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
This is the logfile, the relay is hosted on a private server, maybe its firewall? I dont have a lot of expirience with ubuntu firewall could you explain me which command should i run please.
your public IP (autodetected): 51.15.9.105
this command shows us your interfaces and IP addresses:
ifconfig
this command shows us your iptables ruleset:
sudo iptables -vnL
Hello i was able to open the port by reading a guide in digitalocean thank you for helping me realizing it was a firewall problem
El 21/03/2017 a las 20:55, nusenu escribió:
Javier Benito Santoni:
Mar 21 06:27:37.000 [notice] Tor 0.2.4.27 (git-412e3f7dc9c6c01a) opening new log file. Mar 21 06:31:19.000 [warn] Your server (51.15.9.105:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. Mar 21 06:31:19.000 [warn] Your server (51.15.9.105:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
This is the logfile, the relay is hosted on a private server, maybe its firewall? I dont have a lot of expirience with ubuntu firewall could you explain me which command should i run please.
your public IP (autodetected): 51.15.9.105
this command shows us your interfaces and IP addresses:
ifconfig
this command shows us your iptables ruleset:
sudo iptables -vnL
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Javier Benito Santoni:
Hello, im having a problem with arm.
Everytime i open it it apears this: [ARM_WARN] The torrc differs from what tor's using. You can issue a x sighup to reload the torrc values by pressing x. qj - torrc values differ on lines: 2, 3
Even by restarting tor service it shows the same error again and again
Could it be a problem with my config?
BandwidthBurst 8MBytes BandwidthRate 7MBytes ORPort 9001 DirPort 9030 ExitPolicy reject *:* ContactInfo administrator@anonmail.me Nickname AnonMailMe DisableDebuggerAttachment 0
A week has passed since i started my relay and i cant see it on tor globe yet: F40FEF3A1326EFC5D73E4FE6DB6EB0791E4082A1
Has this relay a public IP or is it behind NAT?
What is the public IP of this relay?
Is the ORPort/DirPort externally reachable? Do you see anything like this in your logs after starting your relay:
"Self-testing indicates your ORPort is reachable from the outside. Excellent. Self-testing indicates your DirPort is reachable from the outside. Excellent. Publishing server descriptor."
Hello,
your experience with ARM I have it on my different systems too. A new version of this tool is in active development.
Some minutes ago I was on one of my servers an used ARM. After some seconds the tool had a freeze. It is not possible to use it over a longer time.
In the past I had problems with the globe website. Now I use atlas.torproject.org to check my systems.
Olaf
On 21.03.2017 20:09, Javier Benito Santoni wrote:
Hello, im having a problem with arm.
Everytime i open it it apears this: [ARM_WARN] The torrc differs from what tor's using. You can issue a x sighup to reload the torrc values by pressing x. qj - torrc values differ on lines: 2, 3
Even by restarting tor service it shows the same error again and again
Could it be a problem with my config?
BandwidthBurst 8MBytes BandwidthRate 7MBytes ORPort 9001 DirPort 9030 ExitPolicy reject *:* ContactInfo administrator@anonmail.me Nickname AnonMailMe DisableDebuggerAttachment 0
A week has passed since i started my relay and i cant see it on tor globe yet: F40FEF3A1326EFC5D73E4FE6DB6EB0791E4082A1
tor-relays@lists.torproject.org
-
Javier Benito Santoni -
nusenu -
Olaf Grimm -
Sebastian Hoffmann