On Tue, 21 May 2019 23:36:28 -0700 Keifer Bly <keifer....@gmail.com> wrote:
> Hi, so the relay in question does indeed have a reserved Static IP > (104.154.93.253), and the traffic is allowed by the firewall, but the > relay is still not appearing in the consensus. The port it's running > on is 65534. This is starting to seem odd.....any thoughts are > appreciated. Thanks. --Keifer > Indeed, I don't have any problem connecting to your relay with openssl from multiple locations (at least Russia, Netherlands and Germany): $ openssl s_client -connect 104.154.93.253:65534 <snip> Certificate chain 0 s:CN = www.tvxaieaqsu6ibfe54.net i:CN = www.ak737rvyioit.com <snip> --- No client certificate CA names sent Peer signing digest: SHA512 Peer signature type: RSA Server Temp Key: ECDH, P-256, 256 bits --- SSL handshake has read 801 bytes and written 419 bytes Verification error: unable to verify the first certificate --- New, TLSv1.2, Cipher is ECDHE-RSA-AES256-GCM-SHA384 Server public key is 1024 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : ECDHE-RSA-AES256-GCM-SHA384 So far it seems it has to work. _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays