[BUG] Laragon 3.1.6 - SSL / HTTPS

  • | 240 points

    Some info to all: Google owns .dev and are planning to use it soon, they are stricting up SSL for it.

    Even though I've gone through the process of adding the cert (Windows) to my trusted root .. I 'm still getting this.

    **This site can’t be reached
    This site on the company, organization or school intranet has the same URL as an external website.

    Try contacting your system administrator.

    Is there any temp fix for this?

  • | 7046 points

    Did you get the same output as me?


  • | 240 points

    Yes, that is right.

  • | 7046 points

    I suspect you must have the Auto virtual hosts setting unchecked as shown in image below:


    If so, open hosts file by clicking the h on Laragon window :


    accept the UAC popup:


    Check that the opened hosts file contains the entry of the URL you are trying to connect.
    If it's not there, then add the entry manually as shown in the image below by changing the youprojectname to your desired name.


    Save the hosts file. Close it.

    Reload the Apache/Nginx if required and see if this fixes your problem.

  • | 240 points

    THanks, but I don't see how this solves fixing HTTPS?

  • | 7046 points

    What do you use? Apache or Nginx?
    Do you have the virtual host registered in the hosts file?

  • | 240 points

    I use Apache. I have the virtual hosts registered. But its missing a SAN it says.

    From Chrome Dev tools:

    *This page is not secure (broken HTTPS).

    Subject Alternative Name missing
    The certificate for this site does not contain a Subject Alternative Name extension containing a domain name or IP address.*

  • | 7046 points

    Please refer to this URL for the stated problem and see if it solves your problem

  • | 240 points

    @bantya I followed the process. No luck :\ I have a TON of sites on my local, any idea why the auto SSL does not work?

  • | 4363 points

    It's probably due this Chrome change: https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts

    So changing hostname to use .localhost or .test gTLD should solve this issue.

    edit: Maybe I was too quick to reply..dunno if this is the root cause of this, but it doesn't hurt to try :)

Log in to reply

Looks like your connection to Laragon was lost, please wait while we try to reconnect.