Hello!

First, thank you for an amazing piece of software; I've used Laragon more times than I can count and am still discovering new things that are built-in that continue to impress me.

My issue is this: after using the Laragon right click menu to change the version of a managed dependency / bundled application, let's say changing NodeJS from v12 to v14, the Laragon config file (/user/laragon.ini) gets updated immediately, but the file that contains the string to get injected into the system PATH (/bin/laragon/laragon.cmd) remains stale until I manually click the "Terminal" button in the Laragon UI.

Is there any chance that Laragon could be updated so that laragon.cmd gets immediately updated after a version change, the same way that the laragon.ini file is? Or, expose a command to trigger a refresh of this file, instead of requiring me to press the terminal button?

Some more technical background:

I'm trying to use Laragon with an alternative terminal program (Windows Terminal). I've already poked around and figured out most of what I need - in fact, I can run Cmder as the shell inside my terminal, complete with injected values, by:

Having my terminal program call cmder.bat cmder.bat calls vendor/init.bat vendor/init.bat calls laragon.cmd as part of its setup process This is where the problem lies. I can run this init script as many times as I want after a version change, and unless I've manually clicked the "Terminal" button in the UI, the laragon.cmd file still has the old version values, so my PATH is incorrect

PS: I've filed this under Help Wanted? in the chance that there is already an option to have this happen, or a command I can call. Apologies if there isn't and this should instead be a feature request.

Just curious to make sure I am doing this properly could someone here give me exact instructions (what to edit, config and enable) for fastcgi to function with apache for Laragon ??

With other software i never bothered to use fastcgi but why not i can now start here.

OK I am not a professional here but because I have worked with all types of online open source software for hosting on windows for 20 years or so I pretty much know how to get the website live and configure, tweak and secure for the most part but so far there has been many issues here that I have personally took the time to address and discovered, obviously tried everything to work it out on my own like i been doing for so many years for the most part but with 5.0 Laragon I am disappointed because im running out of ideas and solutions to issues and ongoing problems.

Yes I seem to be having a few issues with your new version Laragon 5.0 (other parts of the forum I have also mentioned and stated the specific issues related to the new 5.0 software)

I noticed you still haven't mentioned anything on how to use your software as a Live Production Server (which i managed to work out on my own for the most part) but you did mention to me in another post that you would make a tutorial for us all on how we can use your Laragon 5.0 software for hosting You did get me excited i won't lie but remember we have all been patiently waiting now for roughly 2 weeks + ago.

I notice you been answering other forum members but it's like you have completely ignored me for what reason I don't know but please do tell me if I have said anything to offend you.

In the meantime I have posted the error I am receiving when trying to enable module deflate on apache.
click here

So much future potential for this software but lack of support for the most part. I do understand we all have jobs outside of this but when I see the Developer/Admin has been active answering other posts but ignoring mine you start wondering why..... am I correct

With Laragon, adding another Apache version is very easy.

Download Apache (64-bit):
https://www.apachelounge.com/download/VS16/binaries/httpd-2.4.48-win64-VS16.zip Extract the downloaded to: {LARAGON_ROOT}\bin\apache\httpd-2.4.48-win64-VS16 C:\laragon -- bin -- apache -- httpd-2.4.48-win64-VS16 -- ............. Select the new version at: Laragon Menu > Apache > Version > httpd-2.4.48-win64-VS16

Very easy huh. That's all forks!

Ref: https://www.apachelounge.com/download/

I was using Laragon 4.x, yesterday I installed MySQL Workbench, but I don't think it messed anything up.
Upgraded to Laragon 5.x now, but still can't start mysql.
log:

2021-06-12T05:06:22.401449Z 0 [Note] C:\laragon\bin\mysql\mysql-5.7.24-winx64\bin\mysqld (mysqld 5.7.24) starting as process 13476 ... 2021-06-12T05:06:31.931078Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path. 2021-06-12T05:06:31.931483Z 0 [Note] C:\laragon\bin\mysql\mysql-5.7.24-winx64\bin\mysqld (mysqld 5.7.24) starting as process 4228 ... 2021-06-12T05:06:31.946567Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2021-06-12T05:06:31.947246Z 0 [Note] InnoDB: Uses event mutexes 2021-06-12T05:06:31.947667Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier 2021-06-12T05:06:31.948287Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2021-06-12T05:06:31.949083Z 0 [Note] InnoDB: Number of pools: 1 2021-06-12T05:06:31.949625Z 0 [Note] InnoDB: Not using CPU crc32 instructions 2021-06-12T05:06:31.952577Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2021-06-12T05:06:31.958923Z 0 [Note] InnoDB: Completed initialization of buffer pool 2021-06-12T05:06:31.993206Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 2021-06-12T05:06:32.212811Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2021-06-12T05:06:32.213672Z 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2021-06-12T05:06:32.221412Z 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB. 2021-06-12T05:06:32.227158Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active. 2021-06-12T05:06:32.227940Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active. 2021-06-12T05:06:32.229119Z 0 [Note] InnoDB: Waiting for purge to start 2021-06-12T05:06:32.293386Z 0 [Note] InnoDB: 5.7.24 started; log sequence number 300522968 2021-06-12T05:06:32.294310Z 0 [Note] InnoDB: Loading buffer pool(s) from C:\laragon\data\mysql\ib_buffer_pool 2021-06-12T05:06:32.294413Z 0 [Note] Plugin 'FEDERATED' is disabled. 2021-06-12T05:06:32.302857Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key 2021-06-12T05:06:32.303266Z 0 [Note] InnoDB: Buffer pool(s) load completed at 210612 10:51:32 2021-06-12T05:06:32.303923Z 0 [Note] Server hostname (bind-address): '*'; port: 3306 2021-06-12T05:06:32.305273Z 0 [Note] IPv6 is available. 2021-06-12T05:06:32.305701Z 0 [Note] - '::' resolves to '::'; 2021-06-12T05:06:32.306226Z 0 [Note] Server socket created on IP: '::'. 2021-06-12T05:06:32.306766Z 0 [ERROR] Can't start server: Bind on TCP/IP port: No such file or directory 2021-06-12T05:06:32.307465Z 0 [ERROR] Do you already have another mysqld server running on port: 3306 ? 2021-06-12T05:06:32.308178Z 0 [ERROR] Aborting 2021-06-12T05:06:32.308552Z 0 [Note] Binlog end 2021-06-12T05:06:32.308941Z 0 [Note] Shutting down plugin 'ngram' 2021-06-12T05:06:32.309522Z 0 [Note] Shutting down plugin 'partition' 2021-06-12T05:06:32.310041Z 0 [Note] Shutting down plugin 'BLACKHOLE' 2021-06-12T05:06:32.310563Z 0 [Note] Shutting down plugin 'ARCHIVE' 2021-06-12T05:06:32.311056Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA' 2021-06-12T05:06:32.311648Z 0 [Note] Shutting down plugin 'MRG_MYISAM' 2021-06-12T05:06:32.312206Z 0 [Note] Shutting down plugin 'MyISAM' 2021-06-12T05:06:32.312708Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL' 2021-06-12T05:06:32.313298Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES' 2021-06-12T05:06:32.313849Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES' 2021-06-12T05:06:32.314435Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' 2021-06-12T05:06:32.315040Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' 2021-06-12T05:06:32.315602Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' 2021-06-12T05:06:32.316225Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' 2021-06-12T05:06:32.316837Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES' 2021-06-12T05:06:32.317413Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS' 2021-06-12T05:06:32.318000Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES' 2021-06-12T05:06:32.318558Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE' 2021-06-12T05:06:32.319142Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE' 2021-06-12T05:06:32.319730Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG' 2021-06-12T05:06:32.320282Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED' 2021-06-12T05:06:32.320864Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED' 2021-06-12T05:06:32.321430Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD' 2021-06-12T05:06:32.322068Z 0 [Note] Shutting down plugin 'INNODB_METRICS' 2021-06-12T05:06:32.322602Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO' 2021-06-12T05:06:32.323219Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS' 2021-06-12T05:06:32.323831Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU' 2021-06-12T05:06:32.324524Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE' 2021-06-12T05:06:32.325102Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET' 2021-06-12T05:06:32.325670Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX' 2021-06-12T05:06:32.326212Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET' 2021-06-12T05:06:32.326707Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM' 2021-06-12T05:06:32.327218Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET' 2021-06-12T05:06:32.327788Z 0 [Note] Shutting down plugin 'INNODB_CMP' 2021-06-12T05:06:32.328245Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS' 2021-06-12T05:06:32.328727Z 0 [Note] Shutting down plugin 'INNODB_LOCKS' 2021-06-12T05:06:32.329198Z 0 [Note] Shutting down plugin 'INNODB_TRX' 2021-06-12T05:06:32.329743Z 0 [Note] Shutting down plugin 'InnoDB' 2021-06-12T05:06:32.330288Z 0 [Note] InnoDB: FTS optimize thread exiting. 2021-06-12T05:06:32.330950Z 0 [Note] InnoDB: Starting shutdown... 2021-06-12T05:06:32.435195Z 0 [Note] InnoDB: Dumping buffer pool(s) to C:\laragon\data\mysql\ib_buffer_pool 2021-06-12T05:06:32.437303Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 210612 10:51:32 2021-06-12T05:06:33.854554Z 0 [Note] InnoDB: Shutdown completed; log sequence number 300522987 2021-06-12T05:06:33.855368Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2021-06-12T05:06:33.855943Z 0 [Note] Shutting down plugin 'MEMORY' 2021-06-12T05:06:33.856387Z 0 [Note] Shutting down plugin 'CSV' 2021-06-12T05:06:33.856793Z 0 [Note] Shutting down plugin 'sha256_password' 2021-06-12T05:06:33.857270Z 0 [Note] Shutting down plugin 'mysql_native_password' 2021-06-12T05:06:33.857851Z 0 [Note] Shutting down plugin 'binlog' 2021-06-12T05:06:33.861659Z 0 [Note] C:\laragon\bin\mysql\mysql-5.7.24-winx64\bin\mysqld: Shutdown complete```

Hi, my first message here and have a question.
I managed to get ssl working with the private.key and certificate.crt i have from ZeroSSL.
On my PC it's working ok with every browser but on some mobile browsers it's telling me "invalid SSL certificate".
I have 3 files from ZeroSSL and i was reading that you need to set also the file ca_bundle.crt in php.ini.
I did and restarted server but it's still not working.

Any idea's ?

Laragon is designed to be a portable app, therefore it makes sense to open multiple versions, in different locations. When the main window is closed Laragon is still running, in the background. However, the icon will, by default, be in the hidden group.

It's not always easy to spot Laragon in the middle of these icons. This can lead to multiple versions of Laragon being opened.

The solution I use is to always show the Laragon icon in the main notification area. This is how:

Right-click an empty area on the Taskbar and select Taskbar settings:

Scroll down and choose Select Which icons appear on the taskbar

Scroll down and turn Laragon to On

The icon will always show in the main taskbar notification area:

I hope this helps others.

I was using Xampp for local development until about a year ago when I found Laragon & I haven't looked back since. This is seriously the most powerful local development tool I have in my entire "developer toolkit".
I started working for a new company about 2 months ago & their entire team was using various setups for local dev and were always encountering problems. Setting up a new project locally was always a nightmare for them due to mysql version conflicts, having to change php versions, etc. When I introduced Laragon to them, they were amazed at how easy it was to install, maintain and how flexible it was to update/switch their dependencies. My manager told me that since the team has started using Laragon for local dev, project setup time has gone down from an average of 6 HOURS, to less than 30 mins. AMAZING.
In the opensource community, people sometimes forget the amount of time, effort and hard work that goes into creating something like this. So the reason why I'm posting this is just to say thank you to @leokhoa for developing & maintaining such an incredible piece of software. Your amazing efforts are very much appreciated!

When trying to speed up your PHP web applications, it sure helps to know where the bottle necks are. That’s where Xdebug and Q Cache Grind can help: they can tell you which functions and class methods are taking up the most time and memory, how many times they’re called, and who called them. With this information, it’s far easier to speed up your code than “shooting in the dark” by just trying to optimize everything. Read article on my blog.

Hello, I'm working on multiple projects with different PHP versions.
When I'm going to work on project with different PHP version, I change PHP version in Laragon. The web then works on change PHP version.

But, when I'm using cmder inside IDE (PHP Storm), PHP version will stay the old one. I can restart laragon, restart termial in PHP Storm, no change.

PHP version in CLI will change, only if I click on Terminal icon inside Laragon.
I'm guessing it is becouse of Enviroment settings, which are refreshed/reloaded after click on Terminal icon.

Is it possible to make something, what will help me to, no to have to click the Terminal icon?

Now I have in PHP storm set to open CMDER like this:

Thanks

Adding another MySQL version is very easy and safe with Laragon.
Hint: This tutorial also applies for MariaDB.
https://downloads.mariadb.org/mariadb/10.2.6/#os_group=windows
[Download the MariaDB 64-bit version]

Download MySQL 5.7 (64-bit) or 32-bit:
https://dev.mysql.com/get/Downloads/MySQL-5.7/mysql-5.7.18-winx64.zip Extract the downloaded to: {LARAGON_ROOT}\bin\mysql\mysql-5.7.18-winx64 (see below Note for MariaDB) C:\laragon -- bin -- mysql -- mysql-5.7.18-winx64 -- ............. Select the new version at: Laragon Menu > MySQL > Version > mysql-5.7.18-winx64

Very easy huh. That's all forks!

Note: If you use MariaDB, extract it to: {LARAGON_ROOT}\bin\mysql\mariadb-10.2.6-winx64, Laragon will automatically create correspond DataDir for MariaDB on data/mariadb

Hi,
I am currently on Laragon v 4.0.16 with multiple WP instances which are crucial.

Is there any SAFE way to upgrade to v 5.0 without losing everything OR the need to migrate?

Please guide.

Thanks

It is easy and safe to upgrade to Laragon 5:

Backup laragon.exe (rename to laragon.exe.bak) Replace it with the file download from github:
https://github.com/leokhoa/laragon/releases/download/5.0.0/laragon.exe

That's all folks.

Re: Connecting to MYSQL through HeidiSQL

Hola yo tengo una duda, cuando inicio data base en laragon me aparece para iniciar sesion en el navegador y no la interfaz de HeidiSql, tengo que descargarla aparte? a mis compañeros no les pasa por eso mi duda.

Does Laragon include tools to dump postgresql db with data ?

I tried backup from pgadmin but it requires python3.8.
I cannot install it because of some critical dependencies on my machine who need >= 3.9

Problem

Backup via pgadmin cannot work because it search for python38.dll

So I installed python into laragon into the path C:\laragon\bin\python\python-3.8.9-x64

The I opened the file C:\laragon\bin\postgresql\postgresql-13.2-1-windows-x64-binaries\pgAdmin 4\venv\pyvenv.cfg

I entered this configs

home = C:\laragon\bin\python\python-3.8.9-x64 implementation = CPython version_info = 3.8.3.final.0 virtualenv = 20.0.20 include-system-site-packages = false base-prefix = C:\laragon\bin\python\python-3.8.9-x64 base-exec-prefix = C:\laragon\bin\python\python-3.8.9-x64 base-executable = C:\laragon\bin\python\python-3.8.9-x64\python.exe

Restarted all (Laragon itself but also the pc)

I still have the pythonw.exe error which cannot find python38.dll

I tried with pgAdmin 4 configuration, without success

[error] connect() failed (10061: - nginx
Any solutions to this ?
click here

Hi,

I am trying to do lighthouse tests on my local site (https://t21.test/), and its recommended to "Use HTTP/2".

How can I implement this on laragon 4.0.16?

The reason is - it makes a huge difference in scores, and I'm trying to improve speed.

Thanks,

Robert