Hi Olaf,
 Thank you for offering your help. I installed "ufw" and unblocked my ORPort, but still I am getting the same issue. Can you please suggest what else could be the problem ?

Thank you,
Yash

On Thu, 24 May 2018 at 23:31, <tor-relays-request@lists.torproject.org> wrote:
Send tor-relays mailing list submissions to
        tor-relays@lists.torproject.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
or, via email, send a message with subject or body 'help' to
        tor-relays-request@lists.torproject.org

You can reach the person managing the list at
        tor-relays-owner@lists.torproject.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of tor-relays digest..."


Today's Topics:

   1. Re: Unable to confirm my ORPort is reachable (Luca Tortiglione)
   2. Re: Unable to confirm my ORPort is reachable (Matt Traudt)
   3. Re: Why adding more Nodes won't help? (teor)
   4. Re: Unable to confirm my ORPort is reachable (Olaf Grimm)
   5. Re: Tor Software Update Question (Keifer Bly)


----------------------------------------------------------------------

Message: 1
Date: Thu, 24 May 2018 16:56:15 +0200
From: Luca Tortiglione <luca.tortiglione@gmail.com>
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] Unable to confirm my ORPort is reachable
Message-ID:
        <CABvHF-vHSQUGQwpp3iu_vat1gv3gRtoi2ra_ASOi6ZchGLYzQw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

what about port forwarding on the router / modem adsl ?
Il giorno gio 24 mag 2018 alle ore 16:54 Yash Kumar <yashkr.99@gmail.com>
ha scritto:

> Hi all,
>   I have set up a tor relay on my Ubuntu machine by following the
instructions given in the link. To confirm whether the setup was done
properly, I checked the status using the command:

> $ sudo service tor status

> and was getting status as "Active".
> Further, I looked into the log file /var/log/tor/notices.log using the
command:

> $ tail -f /var/log/tor/notices.log

> and following was the output:

> May 24 18:24:54.000 [notice] Starting with guard context "default"
> May 24 18:24:54.000 [notice] Bootstrapped 80%: Connecting to the Tor
network
> May 24 18:24:54.000 [notice] Signaled readiness to systemd
> May 24 18:24:55.000 [notice] Guessed our IP address as x.x.x.x (source:
204.13.164.118).
> May 24 18:24:55.000 [notice] Bootstrapped 85%: Finishing handshake with
first hop
> May 24 18:24:56.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
> May 24 18:24:59.000 [notice] Tor has successfully opened a circuit. Looks
like client functionality is working.
> May 24 18:24:59.000 [notice] Bootstrapped 100%: Done
> May 24 18:24:59.000 [notice] Now checking whether ORPort x.x.x.x:9001 is
reachable... (this may take up to 20 minutes -- look for log messages
indicating success)
> May 24 18:44:55.000 [warn] Your server (x.x.x.x:9001) 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.

> Can anyone please help me with this issue?
> I am not able to figure out the reason behind this error message "Your
server (x.x.x.x:9001) has not managed to confirm that its ORPort is
reachable".
> Please also let me know if you feel there is any issue with the tor
configuration.

> Thank you,
> Yash Kumar
> _______________________________________________
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays



--




L.


------------------------------

Message: 2
Date: Thu, 24 May 2018 10:56:42 -0400
From: Matt Traudt <pastly@torproject.org>
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] Unable to confirm my ORPort is reachable
Message-ID: <00717b22-2471-5dc5-f4d1-352a455f6e73@torproject.org>
Content-Type: text/plain; charset=utf-8

On 5/24/18 10:53, Yash Kumar wrote:
> Hi all,
>  I have set up a tor relay on my Ubuntu machine by following the
> instructions given in the link
> <https://trac.torproject.org/projects/tor/wiki/TorRelayGuide>. To
>
> [...]
>
> Can anyone please help me with this issue?
> I am not able to figure out the reason behind this error message "Your
> server (x.x.x.x:9001) has not managed to confirm that its ORPort is
> reachable".
> Please also let me know if you feel there is any issue with the tor
> configuration. 
>

Based on the information provided, most likely port 9001 is not
forwarded correctly at your router.

Matt



------------------------------

Message: 3
Date: Thu, 24 May 2018 08:30:16 -0700
From: teor <teor2345@gmail.com>
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] Why adding more Nodes won't help?
Message-ID: <1B7BFAE4-778C-4D57-9E8D-0A9E0ECA8FDE@gmail.com>
Content-Type: text/plain; charset="utf-8"



> On 24 May 2018, at 05:00, dave` dave <daved7082@gmail.com> wrote:
>
> i saw that is a way to change the numbers of nodes in this site http://thesprawl.org/research/tor-control-protocol/#creating-really-fast-one-hop-circuits
> any one knows how it works, there is not enough information how to use it.

"Since we will use the same node for both entry and exit, we must find a node which supports appropriate exist policy"

By default, recent Tor versions do not allow single hop exits, because the exit learns the client's IP address and the destination domain.

If you want this feature, run your clients and exits in a test network with:

RefuseUnknownExits 0

T
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20180524/9106be01/attachment-0001.html>

------------------------------

Message: 4
Date: Thu, 24 May 2018 18:40:43 +0200
From: Olaf Grimm <jeep665@posteo.de>
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] Unable to confirm my ORPort is reachable
Message-ID: <00bedebc-1c37-dc37-4a4a-88909a2668f6@posteo.de>
Content-Type: text/plain; charset=utf-8

Perhaps you can have the following problem if you use Linux:

On some Linux system the iptable firewall block incoming connections by
default. If I remember correctly, CentOS is a candidate for this behavior.

After a general reset and configuring open ports I had success with my
relay. An easy way to do this is the software "ufw", which is an overlay
to iptables.


Olaf



Am 24.05.2018 um 16:56 schrieb Matt Traudt:
> On 5/24/18 10:53, Yash Kumar wrote:
>> Hi all,
>>  I have set up a tor relay on my Ubuntu machine by following the
>> instructions given in the link
>> <https://trac.torproject.org/projects/tor/wiki/TorRelayGuide>. To
>>
>> [...]
>>
>> Can anyone please help me with this issue?
>> I am not able to figure out the reason behind this error message "Your
>> server (x.x.x.x:9001) has not managed to confirm that its ORPort is
>> reachable".
>> Please also let me know if you feel there is any issue with the tor
>> configuration. 
>>
> Based on the information provided, most likely port 9001 is not
> forwarded correctly at your router.
>
> Matt
>
> _______________________________________________
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays




------------------------------

Message: 5
Date: Thu, 24 May 2018 11:01:10 -0700
From: Keifer Bly <keifer.bly@gmail.com>
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] Tor Software Update Question
Message-ID: <4073D91E-7FFB-427B-BBE3-504D3E5FEBAA@gmail.com>
Content-Type: text/plain;       charset=utf-8

“killall tor” to stop the process then “tor” to start it again usually works, but I wonder if there is a way to do this without loosing uptime as this does? Thank you.

Sent from my iPhone

> On May 24, 2018, at 4:30 AM, Ralph Seichter <m16+tor@monksofcool.net> wrote:
>
>> On 24.05.18 08:17, Valter Jansons wrote:
>>
>> I have not worked on macOS services, but as I understand it, executing
>> `sudo launchctl stop servicename && sudo launchctl stop servicename`
>> should do the job for restarting the service [...]
>
> That might not work as intended, depending on macOS version and service
> configuration details. Both "stop" and "start" are legacy subcommands
> aimed at on-demand services and older launchd implementations.
>
>> Maybe just restarting the box is an easier method of restarting the
>> Tor service.
>
> Probably.
>
> -Ralph
> _______________________________________________
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


------------------------------

Subject: Digest Footer

_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


------------------------------

End of tor-relays Digest, Vol 88, Issue 45
******************************************