@mac os trying to get ssl for local site

I’m trying to get https version of my site with local.

I’m using an old version of local Version 9.0.5+6706 at mac os ( big sur).

I followed localwp’s helpdoc with respect to getting ssl certificate on mac os for the local site.

I’m facing two issue, first I cannot get the ssl. I’ve followed all steps.

Second, I’m getting the command not found for any command by using siteshell.

Here’s what I’m getting at the terminal:

/Library/Application\ Support/Local/ssh-entry/PLG_M-SQO.sh
-n -e 
Setting Local environment variables...

WP-CLI:   WP-CLI 2.10.0
Composer: 2.6.2 2023-09-03
PHP:      8.1.23
MySQL:    mysql  Ver 8.0.16 for macos10.14 on x86_64 (MySQL Community Server - GPL)

Launching shell: /bin/zsh ...
/etc/zshrc:7: command not found: locale
/etc/zshrc_Apple_Terminal:104: command not found: mkdir
my@my-MacBook-Air public % ls
zsh: command not found: ls

Please suggest how to overcome this issue.

Thank You,
VG

Can you share your Local Log here @bles?

Retrieving Local’s Log File

Thanks Nick for your reply. Here are the logs.
local-details.json (1.3 KB)
local-lightning-verbose0.log (56.3 KB)

I tried mkcert too and it got bit messy, as the site won’t show https nor I was able to remove mkcert. Hopefully, 'll get the solution.

Best,

@bles as a first step here could you try upgrading your Local version to our latest 9.2.2?

If you don’t have a lot of sites in Local and want to a bigger refresh, you could run through these steps:

  • Export any sites that you have on Local and save them to a folder somewhere on your computer: Backup a Local Site - Local

  • Fully uninstall Local from your computer using the MacOS specific steps here: Uninstall Local - Local

  • Install the latest version of Local on this link: Releases - Local

  • Once installed, please restart the computer.

  • When the computer is restarted and turned on, close any applications that automatically run in the background (AntiVirus, Firewall, and other Developer applications included).

  • Check and see if the issue still persists. If so, please provide us with an updated log: Retrieve Local’s Log File - Local

1 Like