A final fix for the issue with auto-gen SSL certs missing SAN error.

w33zy

I recently started using Laragon for its SSL feature. I noticed that when I visited the HTTPS version of a domain is created with Laragon is an getting errors from Chrome 64.

I didn't searching here and found some post about the error. The thing is some of the solutions are for earlier versions of Laragon and the all have different solutions.

So this post is to find out if these issues were fixed in a newer version of the program or which solution should i be using.

timi

I have the same problem

AH00526 syntax error

w33zy

@timi Nope! No syntax errors, I could fixed that myself it that was the case.

timi

Well its not really a syntax error but can't find the .crt file or its missing

only .key is in the folder

Can you share how you would fix that if you don't mind

rizaldywirawan

Hi @timi

Here is the solution:

Download makecert.bat (created by @bantya ), here is the link:

https://github.com/bantya/MakeCert

After you download it, move the makecert.bat to

your_local_disk:\laragon\bin\apache\your_apache_version\bin

My location is C:\laragon\bin\apache\httpd-2.4.29-Win64-VC15\bin.

Why do you place it there? Because there's an openssl there.

Press enter, then follow the instruction (please do not use space, use underscore instead!
After that, the application will create 3 files, which .crt, .key, and .cnf. Move those items to your_local_disk:\laragon\etc\ssl.
Import the certificate from browser, for example, we will use Chrome.
- Go to Setting
- search for Certificate choose Manage Certificate
- Please choose tab Trusted Root Certification Authorities then press Import
- Press next, and choose browse to locate the .crt file.
- Please restart your browser, and reload the Laragon.

Enjoy the https locally

P.S: for more information, you can find it here

matthiku

@rizaldywirawan
Thanks for your detailed solution. So I have followed all your steps and have created a new root certificate and added it to the trusted root cert authorities.

I just don't quite understand how this cert will be used?

What about my existing SSL-enabled pages? Should I remove all auto-generated certs and let Laragon create them again?

How does Laragon knows when it auto-generates new certs that it has to base them on my new root authority (the cert created and installed according to your solution)?

Apologies if these are dumb questions.

rizaldywirawan

Hola @matthiku

I just don't quite understand how this cert will be used?

When you import it through your browser, you can access them using https for now. But that's a self-assigned, you have to import the ssl to everybrowser which you use.

What about my existing SSL-enabled pages? Should I remove all auto-generated certs and let Laragon create them again?

Yeah i delete, and then create them again,

How does Laragon knows when it auto-generates new certs that it has to base them on my new root authority (the cert created and installed according to your solution)?

I guess we should ask directly to the master @leokhoa :p.

clover

you can refer to this post.

https://forum.laragon.org/topic/958/your-connection-to-this-site-is-not-secure-strikethrough-https

I had similar issues before.