Few questions about a new relay

[Heartbleed]

1. Hello, after 6 hours of uptime Tor metrics isn’t showing my relay, is this normal?

Nov 25 16:05:46.000 [notice] Now checking whether IPv4 ORPort 93.95.228.38:443 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Nov 25 16:05:46.000 [notice] Now checking whether IPv4 DirPort 93.95.228.38:80 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Nov 25 16:05:46.000 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Nov 25 16:09:01.000 [notice] Self-testing indicates your ORPort 93.95.228.38:443 is reachable from the outside. Excellent. Publishing server descriptor.

2. In my notices.log i get this message “Heartbeat: It seems like we are not in the cached consensus.” is this a problem?

Nov 25 22:01:15.000 [notice] Heartbeat: It seems like we are not in the cached consensus.
Nov 25 22:01:15.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 0 circuits open. I've sent 3.72 MB and received 34.39 MB. I've received 463 connections on IPv4 and 0 on IPv6. I've made 433 connections with IPv4 and 0 with IPv6.
Nov 25 22:01:15.000 [notice] While bootstrapping, fetched this many bytes: 9537832 (server descriptor fetch); 1087146 (consensus network-status fetch); 14102 (authority cert fetch); 3436621 (microdescriptor fetch)
Nov 25 22:01:15.000 [notice] While not bootstrapping, fetched this many bytes: 4260790 (server descriptor fetch); 2932 (server descriptor upload); 367977 (consensus network-status fetch); 141885 (microdescriptor fetch)

Tor version: 0.4.5.9

torrc config:

User tor
PIDFile /var/run/tor/tor.pid
SocksPort 0
Log notice file /var/log/tor/notices.log
Log warn file /var/log/tor/warns.log
DataDirectory /var/lib/tor
ControlPort 9051
HashedControlPassword 16:XXXXXX
ORPort 443 IPv4Only
Address 93.95.228.38
Nickname Heartbleed
ContactInfo Heartbleed <heartbleed-tor AT proton dot me>
DirPort 80
ExitPolicy reject *:*

[Vort]

Looks like something is blocking TLS connection to your relay.
Port is open, connection starts establishing, but then hangs.

Result of my connection attempt:

Nov 26 10:34:54.000 [notice] Bootstrapped 0% (starting): Starting
Nov 26 10:34:54.000 [notice] Starting with guard context "bridges"
Nov 26 10:34:54.000 [notice] Delaying directory fetches: No running bridges
Nov 26 10:34:56.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Nov 26 10:34:56.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Nov 26 10:34:56.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Nov 26 10:38:41.000 [warn] Problem bootstrapping. Stuck at 14% (handshake): Handshaking with a relay. (IOERROR; IOERROR; count 1; recommendation warn; host 0000000000000000000000000000000000000000 at 93.95.228.38:443)
Nov 26 10:38:41.000 [warn] 1 connections have failed:
Nov 26 10:38:41.000 [warn]  1 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN

[Heartbleed]

Thanks for the replay.
Looking better the logs i found this:

Nov 26 12:58:11.424 [notice] We compiled with OpenSSL 20000000: LibreSSL 3.2.2 and we are running with OpenSSL 20000000: LibreSSL 3.2.6. These two versions should be binary compatible.

[Vort]

Some versions of LibreSSL are not compatible with Tor:

Libressl 3.2.1 with compatibility issues to Tor relays (#40128) · Issues ·...