Yes it did: once I'd renamed my folder that was causing the problem each time.
@bantya See you in Thailand!
The problem was in the auto.openssl.conf file which Laragon creates. I had a directory in my document root with an invalid character in its name, which got carried through into the DNS entries in this file, and clearly this could not be processed. I've renamed that directory and all is ok now.
Thanks for the pointers!
I created a certificate manually using https://github.com/bantya/MakeCert, with some modifications to allow it to create laragon.crt as it otherwise will only create based on a tld, e.g. laragon.local.crt. Apache then loads ok.
However I'm still stuck in Chrome with ERR_CERT_COMMON_NAME_INVALID "This server could not prove that it is domain.local; its security certificate is from *.local.". Not sure if I've created the certificate incorrectly?
I've just got a new PC and have setup Laragon from scratch with the latest version 3.3. I am using auto virtual hosts and attempting to use SSL: it is Enabled in Menu > Apache > SSL.
Although sites-enabled are populated apparently correctly for all my domains, they all refer to C:/laragon/etc/ssl/laragon.crt. This does not exist however, hence Apache does not start.
I have tried the option to Add laragon.crt to Trust Store, but it does not show in Certificate Manager.
How can I get SSL certificate(s) to auto-generate properly?
Thanks. Done the symlink for now and works fine.
Looks like your connection to Laragon was lost, please wait while we try to reconnect.