arti-hyper: TLS connection failed when trying an HTTPS URL

Same issue as related #569 (closed)

I am on OS X 13.1 on a m1 max chip.

Here is my log:

cargo run --example hyper -- https://icanhazip.com
warning: unused import: `PtTargetAddr`
 --> crates/tor-linkspec/src/traits.rs:9:28
  |
9 | use crate::{ChannelMethod, PtTargetAddr, RelayIdRef, RelayIdType, RelayIdTypeIter};
  |                            ^^^^^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

warning: `tor-linkspec` (lib) generated 1 warning
    Finished dev [unoptimized + debuginfo] target(s) in 0.20s
     Running `/Users/michaelvanstraten/Codebase/arti/target/debug/examples/hyper 'https://icanhazip.com'`
starting Arti...
2023-01-04T11:58:22.187161Z  INFO tor_dirmgr::state: The current consensus is fresh until 2023-01-02 22:00:00.0 +00:00:00, and valid until 2023-01-03 0:00:00.0 +00:00:00. I've picked 2023-01-02 23:38:44.292715964 +00:00:00 as the earliest time to replace it.
2023-01-04T11:58:22.187364Z  INFO tor_dirmgr: Marked consensus usable.
2023-01-04T11:58:22.189902Z  INFO tor_dirmgr: Loaded a good directory from cache.
requesting https://icanhazip.com via Tor...
2023-01-04T11:58:23.139514Z  INFO tor_guardmgr::guard: We have found that [scrubbed] is usable.
2023-01-04T11:58:23.263972Z  INFO tor_dirmgr: Directory is complete.
2023-01-04T11:58:34.352442Z  INFO tor_circmgr::mgr: While waiting on circuit: Ok(Err(CircTimeout)) from circuit we're building
2023-01-04T11:58:34.352735Z  INFO tor_circmgr::mgr: Circuit attempt 1 failed.
2023-01-04T11:58:34.614284Z  INFO tor_circmgr::mgr: While waiting on circuit: Ok(Err(CircTimeout)) from pending circuit
2023-01-04T11:58:34.614389Z  INFO tor_circmgr::mgr: Circuit attempt 1 failed.
2023-01-04T11:58:34.614482Z  INFO tor_circmgr::mgr: While waiting on circuit: Ok(Err(CircTimeout)) from pending circuit
2023-01-04T11:58:34.614493Z  INFO tor_circmgr::mgr: Circuit attempt 1 failed.
2023-01-04T11:58:38.355021Z  INFO tor_circmgr: Flushed persistent state at exit.
Error: error trying to connect: TLS connection failed

Caused by:
    0: TLS connection failed
    1: connection closed via error

log.txt