A SSL CERTIFICATE VERIFY ERROR

[sjdyqyl-collab]

when I run the code:
config = ag.ConfigManager.get_from_registry( app_slug=app_slug, variant_slug=variant_slug, variant_version=variant_version )
I meet this ERROR:
httpx.ConnectError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'cloud.agenta.ai'. (_ssl.c:1017).
How do I resolve it?

[dosubot[bot]]

Hi @sjdyqyl-collab! I'm Dosu and I’m helping the agenta team.

The SSL certificate verify error with a hostname mismatch usually means the certificate presented by the server doesn't match the URL you're connecting to. For Agenta, make sure your registry URL includes the /api/ prefix, like https://cloud.agenta.ai/api/...—using the wrong format can cause certificate issues because the request may be routed incorrectly and the certificate won't match the expected hostname. You can set the correct registry URL using the AGENTA_REGISTRY_URL environment variable. More details on the correct format are here: source.

If you're still seeing the error after fixing the URL, check your SSL verification settings. By default, SSL verification is enabled for security. You can disable it by setting AGENTA_REGISTRY_SSL_VERIFY=false in your environment, but this is not recommended for production. If you need to use a custom certificate authority, set the CA_BUNDLE_PATH environment variable to point to your CA bundle.

In summary: double-check your registry URL format, ensure it matches the certificate, and review your SSL verification settings if needed.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[jp-agenta]

Hi @sjdyqyl-collab,
Thank you for reaching out.

Our cloud.agenta.ai certificate is currently active 👇

and operational 👇

% openssl s_client -connect cloud.agenta.ai:443 -servername cloud.agenta.ai | openssl x509 -noout -dates -subject -issuer
...
notBefore=Jul 26 00:00:00 2025 GMT
notAfter=Aug 24 23:59:59 2026 GMT
...

Could you please :

• share the exact host or api_url that you are using ?
• refresh the certificates on your machine ?

We'll be standing by.