"Your server (xxxx:443) has not managed to confirm that its ORPort is reachable."
I see this in syslog: Your server (xxxx:443) has not managed to confirm that its ORPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. torrc: Nickname Contake ORPort 443 ExitRelay 0 SocksPort 0 ControlSocket 0 ContactInfo contakechuyennghicmt@gmail.com What happened and how to fix this?
On 15.09.2020 13:01, Pham Minh Duc wrote:
I see this in syslog:
Your server (xxxx:443) has not managed to confirm that its ORPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, ;-) It's described above ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
What happened and how to fix this?
Please post: sudo cat /etc/iptables/rules.v4 sudo cat /etc/iptables/rules.v6 or whatever you use as a packet filter and port forwarding. Examples for Debian Buster on my Github: https://github.com/boldsuck/tor-relay-bootstrap/tree/master/etc/iptables -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!
I've written some rules for iptables like what on your Github but it didn't work. I also set up virtual server like this: | External port start: 9001 | External port end: 9001 | Internal port start: 9001 | Internal port end: 9001 | Did I configure it right? On 16/09/2020 20:00, lists@for-privacy.net wrote:
On 15.09.2020 13:01, Pham Minh Duc wrote:
I see this in syslog:
Your server (xxxx:443) has not managed to confirm that its ORPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, ;-) It's described above ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
What happened and how to fix this?
Please post:
sudo cat /etc/iptables/rules.v4 sudo cat /etc/iptables/rules.v6
or whatever you use as a packet filter and port forwarding.
Examples for Debian Buster on my Github: https://github.com/boldsuck/tor-relay-bootstrap/tree/master/etc/iptables
If you are on a VPS, a firewall may be external to the server and it is on the VPS panel. Log into your provider account and VPS settings. -----Original Message----- From: tor-relays <tor-relays-bounces@lists.torproject.org> On Behalf Of Pham Minh Duc Sent: 20 September 2020 07:40 To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] "Your server (xxxx:443) has not managed to confirm that its ORPort is reachable." I've written some rules for iptables like what on your Github but it didn't work. I also set up virtual server like this: | External port start: 9001 | External port end: 9001 | Internal port start: 9001 | Internal port end: 9001 | Did I configure it right? On 16/09/2020 20:00, lists@for-privacy.net wrote:
On 15.09.2020 13:01, Pham Minh Duc wrote:
I see this in syslog:
Your server (xxxx:443) has not managed to confirm that its ORPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, ;-) It's described above ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
What happened and how to fix this?
Please post:
sudo cat /etc/iptables/rules.v4 sudo cat /etc/iptables/rules.v6
or whatever you use as a packet filter and port forwarding.
Examples for Debian Buster on my Github: https://github.com/boldsuck/tor-relay-bootstrap/tree/master/etc/iptabl es
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 20.09.2020 08:39, Pham Minh Duc wrote:
I've written some rules for iptables like what on your Github but it didn't work. I also set up virtual server like this:
| External port start: 9001 | External port end: 9001 | Internal port start: 9001 | Internal port end: 9001 |
Did I configure it right?
dynamic IP and virtual server? Please describe how your machine is connected to the internet and is it at home or in the data center? Which operating system? You need 2 ports forwarding. Did you add the DirPort to torrc? (& reload tor daemon) Relays do not publish descriptors until their ORPort and DirPort are reachable. -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!
I'm running Ubuntu Linux, from home. It connect to the internet without proxy. I'm from Vietnam. I didn't add DirPort to torrc. Can you help me to fix this? On 21/09/2020 18:59, lists@for-privacy.net wrote:
On 20.09.2020 08:39, Pham Minh Duc wrote:
I've written some rules for iptables like what on your Github but it didn't work. I also set up virtual server like this:
| External port start: 9001 | External port end: 9001 | Internal port start: 9001 | Internal port end: 9001 |
Did I configure it right?
dynamic IP and virtual server? Please describe how your machine is connected to the internet and is it at home or in the data center? Which operating system?
You need 2 ports forwarding. Did you add the DirPort to torrc? (& reload tor daemon) Relays do not publish descriptors until their ORPort and DirPort are reachable.
Running from home is not a good idea as high risk for an exit and in many countries it would get a visit from the police when your hidden users do bad things. Using 4G/5G many land-line and fibre networks might not work, as most of these services are now behind CGNAT for IP4 addresses. The world has runout of those addresses so have to be shared. No ports at your home will then be reachable from the outside. Paying or a fixed IP may fix that and a fixed IP is needed for tor server. If your router and service has IPv6, that will give you a range of fixed IPs. Then you can let any device on your network (using pinholes) have an accessible port(s). Alas, Tor still demands an open IP4port to work. Gerry -----Original Message----- From: tor-relays <tor-relays-bounces@lists.torproject.org> On Behalf Of Pham Minh Duc Sent: 22 September 2020 13:02 To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] "Your server (xxxx:443) has not managed to confirm that its ORPort is reachable." I'm running Ubuntu Linux, from home. It connect to the internet without proxy. I'm from Vietnam. I didn't add DirPort to torrc. Can you help me to fix this? On 21/09/2020 18:59, lists@for-privacy.net wrote:
On 20.09.2020 08:39, Pham Minh Duc wrote:
I've written some rules for iptables like what on your Github but it didn't work. I also set up virtual server like this:
| External port start: 9001 | External port end: 9001 | Internal port start: 9001 | Internal port end: 9001 |
Did I configure it right?
dynamic IP and virtual server? Please describe how your machine is connected to the internet and is it at home or in the data center? Which operating system?
You need 2 ports forwarding. Did you add the DirPort to torrc? (& reload tor daemon) Relays do not publish descriptors until their ORPort and DirPort are reachable.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 22.09.2020 14:01, Pham Minh Duc wrote:
I'm running Ubuntu Linux, from home. It connect to the internet without proxy. I'm from Vietnam. I didn't add DirPort to torrc. Can you help me to fix this?
this is how your torrc should look like: Nickname Contake ORPort 443 DirPort 80 ExitRelay 0 ExitPolicy reject *:* SocksPort 0 ControlSocket 0 ContactInfo contakechuyennghicmt@gmail.com -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!
participants (3)
-
Dr Gerard Bulger -
lists＠for-privacy.net -
Pham Minh Duc