8
Wildcard SSL certificate not being created for subdomain Multisite
complete
Benjamin Turner
This was first reported in this Forum post:
To replicate:
- Create a new WordPress Subdomain Multisite within Local
- Log into the WP admin for the site and create at least one subsite
- Within Local, click the "Sync Multi-site Domains to Hosts file"
- Click the "Trust" button for the site's SSL certificate
- Navigate to the subsite's url over HTTPS and examine the certificate.
Note that the certificate does not cover the subsite because there is not wild-card certificate. This is a regression since previous versions of Local did create this wildcard certificate (see attached screenshots taken from the forum thread)
Activity Feed
Sort by
William 'Bahia' Bay
Ben: Sure, I'll open a support ticket.
I did in fact attempt that. Deleted it, and re-trusted it. Still no good. This computer is not running Big Sur either.
Ben
William 'Bahia' Bay: Can you create a new support topic in the forums so we can take a closer look?
My guess is that you might need to delete the old certificate from Keychain (if you're on a Mac) and then re-trust a new certificate from Local.
William 'Bahia' Bay
Benjamin Turner: I'm still having an issue with this. It appears that my migrated multisite from the old Local By Flywheel cannot obtain a wildcard SSL cert.
I appear to have no problem with brand new networks, but the one I've been using for ALL my local development, which has 100+ sites, that I use for testing my production multisite.
I also had no SSL issues on the old Local By Flywheel.
I'd appreciate a closer look into this issue. I can't be the only one that has this problem.
Benjamin Turner
This was fixed in the 5.9.0 version of Local:
> Addressed a bug where the SSL certificate was not being generated for subdomains