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-boun...@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, li...@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 _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
