Download Laragon 5.0 64 Bit

[Vira Bhakta]

Yes, it's me, the chief whinger and moaner ?. You are probably aware that my fling with Linux came to an abrupt (and permanent) stop. I've gone back to my first love Windows. I am using Laragon for my dev needs. For some reason, I am finding it a bit slow....or maybe it's just me? On local dev, Tracy is recording execution time of 1300ms. Visually, page loads seem even slower. Is it just me? I think Laragon used to be faster than this for me? Maybe because I'm coming back from Linux and the page loads seemed to be faster? (that was a docker box). Google and the Laragon forums haven't helped much, mainly telling me to switch to Nginx, others blaming MySQL, etc. Xdebug is not enabled and it is not Tracy slowing things down. Which brings me to my second point. In Laragon I'm stuck with MySQL 5.1. If I switch to 5.7 I get internal server errors.

For me Tracy is showing a page load time of 163ms for the Home page on the front-end with the core blank profile. It would of course depend on how much you have going on in your site (template, modules, ready.php, etc) but your load time does sound slow.

I read something about compatibility but I've not found a list. Funny thing is that even Laragon's own quick add mysql 5.7 (version is 5.7.24) doesn't work. The Apache that shipped with Laragon is VC14. Let try that with MySQL 5.7.19.

I have an Win7 64-bit i7-6700k, 32GB RAM, SSD machine. The laragon is the latest full one, laragon mint. Changing PHP versions has not improved the issue. I'll get this version (.19) of MySQL since it is working for both you and Robin and report back. If it is still slow then I'll try docker using Devilbox.

No combination of Apache/MySQL worked other than 2.4.xx and 5.1! I gave up and set up Devilbox instead (a bit of a pain to set up in Windows 7) but it is up and running. The speeds are still not great, coming it at about 800ms but at least better than the 1300 I was getting with Laragon.

Once I set up SSL, that was the end of being able to log in. For some reason, the TOKEN set on the login page was always different from the one stored server-side that sessionCSRF compared with. Maybe a PHP thing?

Wow! A lot has changed since I last used WAMP! It looks sleek and packs a mean punch. It has lots of settings hidden away neatly in its menus. You can change PHP ini settings (stuff like memory, etc) right from within the menu. One is not restricted to one www folder. Each project can have its own folder anywhere on your system. The mysql/data directory can also point to whatever location you want (I know one can do this in Laragon as well).

Regarding Linux, what distro have your tired? I am on Kubuntu and super happy with it. Started using it beginning of this year. Yes sure it is an uphill battle at first but then when you get into it it is just fab. I have been (and still use it as times) a long time Windows user, XP, 7 then 10. Used Macrium Reflect a lot to have clean images and not suffer from Windows rot, restrictive firewall rules and Pana cloud. With this it all works fine to this day. Though lately for web development my workflow shifted from UI tools to command line tools. I started to use Cygwin a lot, well to do stuff that I could natively do on a Linux box. A couple month later when I had to get a new laptop for work I slapped on dual boot onto that, Windows 10 and Kubuntu. Well so far I booted into Windows about 3 or 4 times, the rest of the time I am on Linux. Even have a shared partition for my data so that I can develop from both OS and have the files and folders working. Why am I saying this? I am not trying to convince you are tell you that Windows is bad. Just saying I did switch and just find it very convenient to work with. Also I am sure there is quite a few people here as well as other places on the web that can/will help you if you have something that does not work.

Regarding Devilbox. Docker. Yes. Super nice to use. If you know how to. If.. Upon discovery of Docker I thought "oh great I can have my entire development setup in there, start it up and never think about it again". I was so wrong. Months and months of time invested, time not lost since I learned a lot, but time spent being really quite frustrated. Just like you say. PHP modules. Connecting hosts. Config files missing. Nginx config. And so on and on and on.. I always thought, "yes nice I can learn this and set it up myself". Well for smaller things it did work, but for something like I want to be able to do, i.e. freely switch components while having my work files and configs left intact, well that was a whole different league. Also, I always thought, "nah I don't need something from someone else, I don't need another tool, I can do this myself". Turns out, it was too much for me to get right. Just like you say, error messages during build, those lead to SO questions with no answer, going to GitHub to file an issue only to have that closed the next day with a kind note "go ask in the Docker community or on SO", going in circles, mad times, unhappy times, and most of all times without writing a single line of PHP, HTML, CSS or JS. And that in the end was what got to me the most. Not being able to get on with work but having to fiddle with some damn settings that in order to understand those I would have to read books on.

And so after this, I might call it a bit of a dark time, I gave in and gave Devilbox a shot. And there it was. I read 2 pages of the manual, not more and it is running. Every time I start it up I have all the things and certs created automatically, am on https, everything is super fast and super smooth and now, at times, I keep asking myself, "why have you not tried this first". Some things are left for people who have been doing that for ages and know the score. I do web development and do not setup servers or backend environments, have no clue about PHP modules or whatever else is needed to make neat and nice sites with whatever I am working at the moment. Some things a better left to people that know this stuff in and out.

So given your issues with Devilbox and https, have you seen this?
Or have you tried opening an issue with Cytopia. That person is an animal. I do not see a single issue not answered and even if it might be a tiny bit off Devilbox there is still some help given. Perhpas give that a shot and see how it pans out?

To conclude, I guess all I want to say is "I feel your trouble" as I have been there and me too I was close to giving up and giving in. But then at the very last moment there was ray of light at the end of this dark tunnel, I clinged onto that and today I stand on a lovely glade and can enjoy the scenery.

I was on Solus. Please see my thread about that here. I still have it running on a not-so-powerful touch device that came with Win 10. For this touch device, I have subsequently looked around for lighter distros and ended up with Kubuntu and Puppy. I'm yet to replace Solus on the device as I've not been able to make the device boot from the USB! This is off topic but a real puzzler. To install Solus, I booted from a USB stick. Now, to replace it, the computer is refusing to boot from USB! Sigh...

True, and I have sought help here and elsewhere. What I don't have unfortunately is a lot of time to try out things and hope they work. Sure, Windows has its quirks (duh! :-)), but they are quirks I know how to deal with and have learnt to live with. Solus worked mostly fine (to my delightful surprise) until it didn't.

So given your issues with Devilbox and https, have you seen this?
Or have you tried opening an issue with Cytopia. That person is an animal. I do not see a single issue not answered and even if it might be a tiny bit off Devilbox there is still some help given.

I read all the docs! Some of the best docs I've seen, btw. He/she has done a great job. I'm quite happy with WampServer though, so I don't think I am going back to docker, or anything else for that matter.

It worked on my Win 7. I don't have Hyper-V. It worked fine with VirtualBox running off (the legacy) Docker Toolbox. You can get it on here on GitHub. I hit the request forged issue and gave up on Dbox. Otherwise, it installed fine. The forged issue arose because the token in the hidden input in the login screen somehow gets a different value to the one server-side.

For some reason, MalwareBytes flags the URL vtf.createit.pl, whenever we open any development sites running under laragon, as well as the httpd.exe file in the apache folder. It points the httpd.exe file in path: w;laragon\bin\apache\httpd-2.4.54-win64-vs16\bin\httpd.exe. MalwareBytes states it's a "Malware.Ransom.Agent.Generic. See: -ransom-agent-generic." Also, the MS Windows Defender SmartScreen stops any opening of the httpd.exe file. Obviously, there is a problem.

So, ... I'm hoping you can add the weight of your organization in approaching them as well as if anyone here can provide a solution, it would be appreciated. If any other info is needed, please let me know.

While you are waiting for the next qualified/approved malware removal expert helper to weigh in on your topic, and even though you may have run the following Malwarebytes utility, or its subsets, please carefully follow these instructions:

For the short time between when you post the diagnostic logs, and when your helper weighs in, please take no further self-directed remedial actions that will invalidate the diagnostic logs you will have posted.

The version of PHP will therefore depend on how close to your production environment you want to get. If you are notsure then download the NTS version, Laragon will switch Apache to use mod_fastcgi.

The easiest way to navigate to the Laragon area of your computer is to click the Root button in the bottom rightcorner of Laragon. Laragon will open Windows Explorer in the laragon > www directory.