# SSL unable to trust on Mac Ventura 13.7.2

**URL:** <https://community.localwp.com/t/ssl-unable-to-trust-on-mac-ventura-13-7-2/46322>\
**Category:** Support\
**Created:** [January 7, 2025, 12:01am UTC](https://community.localwp.com/t/ssl-unable-to-trust-on-mac-ventura-13-7-2/46322 "2025-01-07T00:01:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![peteski](https://avatars.discourse-cdn.com/v4/letter/p/97f17d/32.png) [@peteski](https://community.localwp.com/u/peteski)\
**Post date:** [January 7, 2025, 12:01am UTC](https://community.localwp.com/t/ssl-unable-to-trust-on-mac-ventura-13-7-2/46322/1 "2025-01-07T00:01:45Z")

</div>

# Bug Summary

Any attempt to trust any of my websites come up with error:

Heads-up! we ran into an issue trusting the Local SSL certificate

# Steps to reproduce

Click the Trust link alongside SSL

# Environment Info

Describe your environment.

- MacOS Ventura 13.7.2
- What nginx PHP 8.1.23
- What version of Local is installed?

# Supporting info

If I eventually get the site shown as trusted, Safari still complains of a none Secure Connection

The Log file contains and entry which tends to indicate a startup command error

{“class”:“Process”,“level”:“warn”,“message”:“nginx: [warn] the "listen … http2" directive is deprecated, use the "http2" directive instead in %%router.runPath%%/nginx/conf/server-block-ssl.conf:2”,“process”:“nginx”,“thread”:“main”,“timestamp”:“2025-01-06T23:56:15.119Z”}

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [January 7, 2025, 1:50pm UTC](https://community.localwp.com/t/ssl-unable-to-trust-on-mac-ventura-13-7-2/46322/2 "2025-01-07T13:50:16Z")

</div>

Have you been through our guides here already @peteski?

> **[SSL Certificate on macOS](https://localwp.com/help-docs/getting-started/managing-local-sites-ssl-certificate-in-macos/)**
>
> In most cases, Local makes getting your offline development environment running HTTPS easy by providing a one-click solution for trusting a site’s SSL certificate. Occasionally, if that “trust”…

> **[SSL in Local](https://localwp.com/help-docs/getting-started/ssl-in-local/)**
>
> This doc will go over SSL basics, using SSL in Local, and some common issues. If you are experiencing issues and are also using macOS check out this doc. Table of Contents: Secure Sockets Layer (SSL)…

We do have some known SSL bugs with MacOS filed already as well I’ll share here in case you want to vote and follow for updates:

> [@"One Click Admin" not working with SSL](https://community.localwp.com/t/one-click-admin-not-working-with-ssl/38564):
>
> “One Click Admin” feature is not working when using SSL, it works if we dont trust SSL. Basically it works when we use http , as soon as we enable SSL and click on trust SSL, one click admin doesnt redirect to Dashboard. It redirects to LOGIN page and username field is pre-filled with USERNAME and PASSWORD field is empty. Environment Info Describe your environment. Windows 10 LocalWP Latest (7.1.2) Enviorment is Preffered (default by LOCAL) (ngnix) Please help me to resolve this issue, it …

> [@Site opens in http only](https://community.localwp.com/t/site-opens-in-http-only/41890):
>
> Bug Summary The WP-admin and the Open Site button opens the site in question only via http not https, even though a SSL is set and the cert is trusted in OS X. You CAN change the protocol manually. Once changing the home and siteurl options in the db manually. I can use the WP-admin to force the site via https but not the Open Site button/link. This is both for existing and NEW sites. Apache and NginX do not seem to make a difference. Why is this important? To ensure that remote loaded asset…