Yes it is, is there a way to make it faster please?

Hello,

I have windows 10 64 bit with Laragon(latest version) using Laravel 5.5. When I open pages, it is super slow. Is there a way to increase the speed at which Laragon proccesses the queries please?

I am using apache.

Thanks

@leokhoa thanks, super helpful

ok got it, I had to restart apache for it to work.

I do get a lot ot warnings that the connection is insecure in Chrome, is this normal?
Is it because the certificate is local, any idea please?

thanks for the reply.
Yes apache port 443 ssl is enabled.(ticked)

Hello,

In Laragon I clicked on Apache>>SSL>>enabled

What else do I need to add a https to my test site please as when I type the laravel site with https in the front (I have set https in my .ENV file), I get this:

This site can’t be reached

mynewproject.dev refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED

Thanks

Hello,

I was surprised to not see PHPMyadmin in the Laragon package, I know it can be installed separately but will the makers of Laragon ever include it as part of the installation package? This would be fantastic as there is an ER Diagram builder which HeidiSql does not have.

Thank you so much and long continuation to Laragon! What a superb piece of kit compared to Xampp!

Ok Finally Fixed it.....If anyone runs into the same problem please follow this, it was tricky I have to say...

Last night I noticed many of these files:
ib_logfile0-CONFLICT-1
ib_logfile0-CONFLICT-2
ib_logfile0-CONFLICT-3
ib_logfile0-CONFLICT-4

and these

ibdata1-CONFLICT-1
ibdata1-CONFLICT-2
ibdata1-CONFLICT-3
ibdata1-CONFLICT-4

While the ibdata1 and ib_logfile0 were still there, something happened in between.

When you use Laragon and log to mysql at the same time via 2 pcs, there is a problem because mysql will lock the files for either 1 pc or the other.....and this is when these files start to conflict.

I did not really take notice to those and deleted the ones that had an earlier date than today...well this was my mistake. I thought because the files had the exact same size, the same data would have been in ...wrong!

I then used my sync.com retrieval area of each deleted files and took the ones that matched the exact time of my last work (last night). I deleted both the ibdata1 and ib_logfile0 and renamed ibdata1-CONFLICT-3 and ib_logfile0-CONFLICT-3 (and not conflict 4!!! because this was done today after the bug) to their original respective names(ibdata1 and ib_logfile0).

All of this needs to be done with mysql turned off of course.

@laminbarrow Thanks for the tip, I tried that but unfortunately, after that Heisql shoed even less tables.

I have now reset the old path back on and mysql won't boot up and nothings shows up in the logs...oups

@laminbarrow , oh no....

I also have the latest version, my mysql folder is synched on the cloud.

From the research I have done so far this is what I have found......

In the mysql folder, there is a file called "ibdata1" which seems to create the order of the tables and all the important stuff that creates individual tables. If this becomes corrupted(somehow...) then your tables won't show up....

What I am going to try to do now is this....

Stop mysql and laragon, delete the tables manually in that folder and recreate them based on my last migration..lets see if this works.