<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr">Hi,<br><div><br></div></div><div dir="ltr">On 23 May 2019, at 18:41, Dmitrii Tcvetkov <<a href="mailto:demfloro@demfloro.ru">demfloro@demfloro.ru</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><span>On Tue, 21 May 2019 23:36:28 -0700</span><br><span>Keifer Bly <<a href="mailto:keifer.bly@gmail.com">keifer.bly@gmail.com</a>> wrote:</span><br><span></span><br><blockquote type="cite"><span>Hi, so the relay in question does indeed have a reserved Static IP</span><br></blockquote><blockquote type="cite"><span>(104.154.93.253), and the traffic is allowed by the firewall, but the</span><br></blockquote><blockquote type="cite"><span>relay is still not appearing in the consensus. The port it's running</span><br></blockquote><blockquote type="cite"><span>on is 65534. This is starting to seem odd.....any thoughts are</span><br></blockquote><blockquote type="cite"><span>appreciated. Thanks. --Keifer</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><span></span><br><span>Indeed, I don't have any problem connecting to your relay with openssl</span><br><span>from multiple locations (at least Russia, Netherlands and Germany):</span><br><span></span><br><span></span><br><span>$ openssl s_client -connect 104.154.93.253:65534</span><br><span><snip></span><br><span>Certificate chain</span><br>...</div></blockquote><br><div>I can't find a relay called "torworld" or at "<span style="background-color: rgba(255, 255, 255, 0);">104.154.93.253" on the tor network:</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">* using consensus health, which shows relays with votes:</span></div><div> <a href="https://consensus-health.torproject.org/">https://consensus-health.torproject.org/</a></div><div> * or relay search, which shows relays in the consensus:</div><div> <a href="https://metrics.torproject.org/rs.html#search/104.154.93.253">https://metrics.torproject.org/rs.html#search/104.154.93.253</a></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Please copy and paste the latest logs from your relay the last time you started</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">it up. We need to see logs that </span><span style="background-color: rgba(255, 255, 255, 0);">cover your relay's:</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">* tor version,</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">* role (relay or bridge),</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">* nickname,</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">* fingerprint,</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">* IPv4 address,</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">* reachability self-test, and</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">* descriptor posts to authorities.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">We might need info-level logs to see some of these things.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Do you know if Google supports tor relays?</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">They could be blocking some connections.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">T</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div></body></html>