This should fix the issue you @girtsf were seeing. Thanks for reporting. A long time ago, we required users to specify which root-certificate should be bundled with the service. For Supabase that used to be Baltimore Cybertrust. After "the big incident" where Supabase quietly changed the certificate, we switched to using all common root certificates instead. However, we kept the certificate name in the configs. It wasn't really used anymore (because of the common root certificates), and was left as a cleanup. That came back to bite us: in the latest version of the certificate root package, "Baltimore Cybertrust" was completely removed, and a lookup for the certificate then crashed the executable.