# SSL certificates on Mac **URL:** \ **Category:** Support\ **Tags:** mac, ssl-certificates\ **Created:** [November 6, 2025, 2:28pm UTC](https://community.localwp.com/t/ssl-certificates-on-mac/51590 "2025-11-06T14:28:03Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![philby](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/philby/32/4565_2.png) [@philby](https://community.localwp.com/u/philby)\ **Post date:** [November 6, 2025, 2:28pm UTC](https://community.localwp.com/t/ssl-certificates-on-mac/51590/1 "2025-11-06T14:28:03Z")
So yesterday, “inspired” by MAMP Pro 7.2’s perceived slowness with a local copy of a clients multisite install, I installed LocalWP again, and after some wrangling with importing the database, had the site running. As expected, it runs noticeably faster on Local, I’d say about 1/3 faster than on MAMP. But: for every site install, I not only have to say OK with TouchID to some system popup warning, I then also get a warning after telling it to trust the SSL, have to open Keychains and manually set the SSL cert to be trusted (TouchID again), or manually delete a no-longer used certificate (you guessed it: TouchID, once or sometimes twice). And don’t think of using my trusted Firefox Developper Edition to check things, as it doesn’t recognize any of these SSLs. Makes me wonder how MAMP and Laravel Herd manage to do all this without per-site system prompts and faffing around in Keychains… and also if Local’s speed and convenience are really worth it. Is this the expected state of thing on MacOS, or is work planned to make this a bit smoother? ---
**Author:** ![ben.turner](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/ben.turner/32/5366_2.png) [@ben.turner](https://community.localwp.com/u/ben.turner)\ **Post date:** [November 6, 2025, 5:16pm UTC](https://community.localwp.com/t/ssl-certificates-on-mac/51590/3 "2025-11-06T17:16:00Z")
Thanks for giving Local another spin and for the feedback on performance and UX. I agree that the SSL issues are a pain right now in Local. We have a few tickets in the backlog to make things better. I’m not 100% sure how MAMP/Herd do things, but it’s possible that they use [mkcert](https://github.com/FiloSottile/mkcert). Local’s SSL implementation was from before this tool was around and had Windows support, so we had to home-roll some things. Anyway, mkcert is one tool we’re want to explore, after some positive feedback in this forum post: > [@SSL Functionality](https://community.localwp.com/t/ssl-functionality/50790/5): > > Hi Ben Well I’ve done extensive testing on Windows11, Opensuse Slowroll Linux, and macOS Sonoma using localwp. LocalWP certs all throw up errors. Your connection to this site is not secure, This site can’t provide a secure connection. etc On Firefox I get two errors ERR\_SSL\_PROTOCOL\_ERROR and PKIX ERROR CA CERT USED AS END ENTITY. What I’ve done on all operating systems is to find where the LocalWP certs are stored. I’ve created new certs using MKCERT. This creates two files ending in .pem.… I know the steps in there are manual and a hassle, but you might try doing what he mentions, which would mean you can have a faster site using Local and use your ol’ trusty Firefox Developer Edition. One thing to note, for this issue: > [@SSL Functionality](https://community.localwp.com/t/ssl-functionality/50790/5): > > The only issue I have now is when I click open site button or wp admin button. > LocalWP takes me to the http version of the site. _I think_ that is just because the DB still has regular `http://` references in the DB. Things should work after manually searching/replacing the various domains within the DB. If you do go that route, I’d love to hear how it goes! ---
**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/system/32/1_2.png) [@system](https://community.localwp.com/u/system)\ **Post date:** [February 4, 2026, 5:16pm UTC](https://community.localwp.com/t/ssl-certificates-on-mac/51590/4 "2026-02-04T17:16:02Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.