SSL has a huge issue with multisite WordPress installations. Option to trust SSL for the website in local works, but only for the main site in the network has valid SSL, and other blogs in the network can’t use this SSL. How this can be fixed?
Yes, if the network is created to domain.tld, SSL is OK. If the network is created and main domain set to www.domain.tld, then the SSL is not valid. This should be obvious for Local to handle, but it doesn’t.
I guess I’m not understanding fully – I was able to get a certificate to cover the www.domain.local site for the example site in the above screenshot.
You’re right that the certificate isn’t generated to handle *.domain.local when the network is created with www.domain.local – this isn’t a use case that Local has been developed for. Local is currently set up to create a certificate for the Site Domain set in local as well as a wildcard for any subdomain under that domain.
This is exactly what is happening for me. I created a multisite multisite.local, and the only domain name that has SSL support is multisite.local. I can’t access demo.multisite.local. I can’t even access www.multisite.local without an error:
The certificate is not a wildcard. This is on 5.2.2+2248.
Does someone know of a workaround at least? My multisite install in Local also did NOT create a wildcard SSL cert, so my subdomain sites don’t work properly.
In the old version of Local I was able to manually create an SSL cert and route, but with the new version anything you put in the ~/Application Support/Local/run/router/nginx/certs folder gets automatically removed.