I'm on laragon 3.2.3, its stable and running great for quite some time. About 2-3 years on Laragon itself.

Currently, I have php 7.1 and 7.2, I've right now installed 7.3 to test it with my php application, and Laragon discovers the folder and php so I can switch to it using Laragon menu. However once I have switched when I go to php/extensions I see a list of extensions but clicking on any extensions does not do anything, the menu disappears but extension has not been deselected or selected.

Php version I've downloaded is this one: https://windows.php.net/downloads/releases/php-7.3.12-Win32-VC15-x64.zip

I'm running Laragon on Win10. My php application stops working when I switch laragon to 7.3 I took a quick look inside php_errors.log and noticed a bunch of these lines at the end

[16-Dec-2019 00:48:30 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'fileinfo' (tried: C:\php\ext\fileinfo (The specified module could not be found.), C:\php\ext\php_fileinfo.dll (The specified module could not be found.)) in Unknown on line 0 [16-Dec-2019 00:48:30 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'gd2' (tried: C:\php\ext\gd2 (The specified module could not be found.), C:\php\ext\php_gd2.dll (The specified module could not be found.)) in Unknown on line 0 [16-Dec-2019 00:48:30 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'intl' (tried: C:\php\ext\intl (The specified module could not be found.), C:\php\ext\php_intl.dll (The specified module could not be found.)) in Unknown on line 0 [16-Dec-2019 00:48:30 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'mbstring' (tried: C:\php\ext\mbstring (The specified module could not be found.), C:\php\ext\php_mbstring.dll (The specified module could not be found.)) in Unknown on line 0 [16-Dec-2019 00:48:30 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'mysqli' (tried: C:\php\ext\mysqli (The specified module could not be found.), C:\php\ext\php_mysqli.dll (The specified module could not be found.)) in Unknown on line 0 [16-Dec-2019 00:48:30 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'openssl' (tried: C:\php\ext\openssl (The specified module could not be found.), C:\php\ext\php_openssl.dll (The specified module could not be found.)) in Unknown on line 0 [16-Dec-2019 00:48:30 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'pdo_mysql' (tried: C:\php\ext\pdo_mysql (The specified module could not be found.), C:\php\ext\php_pdo_mysql.dll (The specified module could not be found.)) in Unknown on line 0 [16-Dec-2019 00:48:30 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'xsl' (tried: C:\php\ext\xsl (The specified module could not be found.), C:\php\ext\php_xsl.dll (The specified module could not be found.)) in Unknown on line 0

What can I do about this problem? Any suggestions @leokhoa? I'd like to test php 7.3 on my application but currently stuck with the above problem.

Como resolver estre problema?.
Obg.

With Laragon, adding another Apache version is very easy.

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

Very easy huh. That's all forks!

I think I successfully update my cmder inside laragon from version 1.3.2 to 1.3.13.967 by doing below steps:

Download latest cmder_mini portable version from https://cmder.net/ Do not delete the original cmder inside laragon extract the latest cmder_mini inside C:\laragon\bin, by giving it a new folder name; eg. cmder_mini so that you have 2 cmder apps installed Open file C:\laragon\bin\cmder\vendor\init.bat (original) and copy code from line 168 - 215 (from :: Laragon Start until :: Laragon End) Open file C:\laragon\bin\cmder_mini\vendor\init.bat (latest version) and paste that line after:

323 | :: Set home path
324 | if not defined HOME set "HOME=%USERPROFILE%"
325 | %lib_console% debug_output init.bat "Env Var - HOME=%HOME%"

[paste that code below here]

~Done~

The only problem that I can't seems to configure is how to change root directory when cmder start
The old cmder that included in laragon start at
C:\laragon\www
but the new cmder root folder start at
C:\laragon\bin\cmder_mini

Can anyone help?

Developer can advice if this steps is the right way to update cmder?

Thanks.

You can read about Procfile here at Heroku: https://devcenter.heroku.com/articles/procfile

However, Laragon makes Procfile more convenient to use with GUI. On Laragon all processes on Procfile will be displayed on Menu > Laragon
Some other differences on Laragon are:

A process name can have spaces. For example: My Cool App You can add autorun to make the process auto triggered when Laragon starts You can hide (don't show Console) a process if you quote its command. For example: "php artisan serve" You can set PWD=xxx - xxx is Path of current processs You can have env_file=yyy - yyy is Path to your Environment File.

Here is format of a Procfile:

# Format: ; Program Name: autorun COMMANDS env_file=PATH_OF_FILE pwd=PATH_OF_WORKING_DIR ENV_VAR1=VALUE ENV_VAR2="VALUE WITH SPACE" # Help: ; Program Name: Will be displayed on Procfile or Tools' Menu (can contains space) ; autorun: Your COMMANDS will be run automatically when Laragon starts ; COMMANDS: A command or a series of commands (separated by & ) ; env_file: You can set environment variables directly or put them to the file ; PWD: Current working directory - where the COMMANDS run # Examples: ; My Cool App: autorun node start $PORT PORT=9000 env_file=usr\my_file.env PWD=usr/proj/myapp DB_HOST=1.2.3.4 DB_PORT=9999 DB_USER=user DB_PASS="!$Ab.cs3cre1" DB_NAME=cooldb ; Awesome Tool: "PATH HAS SPACES SHOULD BE QUOTED LIKE THIS" ------------------------------------------------------------------------------

Note:

pwd is case-insensitive. autorun is case-insensitive. Your env_file may look like this: VAR1="VALUE WITH SPACE" DB_HOST=1.2.3.4 DB_PORT=9999 DB_USER=user DB_PASS=!$Ab.cs3cre1

Hello, i very like use this service,
but i was looking to understand if was possible add some switch for autorun mysql - postgresql, like img

i know that i can use it from option, enable and disable it from service & port, but was more "friendly" if was in first page like image, from the switch if we have more sql can ON/OFF more easy.

atm i use mysql and postgresql, and i use togheter ON(like img), if we can switch in this way that is more simple, i can very appreciate it

then idk if is a bug or is normal, but if we put ON ssl, then click on padlock (green), it will disable SLL, but for active i need enable, is possible add a padlock(gray) and with a click enable it?

thanks always for your work and sorry to my bad english

Hi everyone, quick question!

Is there a way to install a specific Laravel version from the Quick app tool?
For example specify the name and after the version.

Thanks!

I have some sites running with mariadb-10.2.27-winx64 and some with mysql-5.7.24-winx64. When I try to switch to one using MariaDB I get an error message saying MariaDB cannot start. The mysqld.log says

Loading buffer pool(s) from K:\laragon\data\mariadb-10.2\ib_buffer_pool
[Note] Plugin 'FEEDBACK' is disabled.
[Note] Recovering after a crash using mysql-bin
[Note] Starting crash recovery...
[Note] Crash recovery finished.
[Note] Server socket created on IP: '::'.
[ERROR] mysqld: Index for table '.\mysql\user' is corrupt; try to repair it
[ERROR] mysqld: Index for table 'user' is corrupt; try to repair it
[ERROR] Fatal error: Can't open and lock privilege tables: Index for table '.\mysql\user' is corrupt; try to repair it

PhpMyAdmin runs fine with mysql and user “root” with no password, but obviously can’t run with mariaDB, the error message being

mysqli_real_connect(): (HY000/2002): No connection could be made because the target machine actively refused it.

Running Laragon with admin rights makes no difference. I saw the answer given here

https://forum.laragon.org/topic/521/service-mariadb-can-not-start/3

but then I encounter a problem with all my (Drupal 7) sites because they cannot connect to the DB due to a problem with lock, i.e. no connection available. The only way around this problem is to recreate the databases manually and import the backups. That’s quite a chore to just change DB engine. I would use mysql exclusively and avoid mariaDB, but the servers for some of my sites are locked to mariaDB and I need to run it for my development environment.

Hi,
I'm new to Laragon.. hope I haven't mess with it

I've installed Laragon full 4.0.16 (190914). I noticed that the php.ini that I place in this folder:
C:\laragon\bin\php\php-7.2.19-Win32-VC15-x64

sometimes disappears, sometimes it contains only the following lines:

[mail function]
sendmail_path="C:/laragon/bin/sendmail/sendmail.exe"

Am I doing something wrong? I'm trying to modify it because I want to add the xdebug extension, but it keeps erasing it...

Thanks!

I would guess many of us here are Wordpress developers. How many of us run a project and then have to add wp-admin in the browser to then edit the project? Surely there is a demand to add a parameter to the project url? (ensuring that it can be immediately after the url without a space ie ...projectname/wp-admin

Currently, when clicking a project under the "www" menu list, Laragon takes us to the projects' main home page for the CMS (WordPress) install.

http://localhost/(WordPress Project Name)/

I am trying to find how I can change it, to make the "www" menu link go directly to the WordPress "wp-login.php" page instead.

http://localhost/(WordPress Project Name)/wp-login.php

Is this possible?

Thanks

I've configured procfile and it works well with multiple jobs but it stops after one heavy job task, has someone faced this?

I'm declaring the process like this:
AppName: autorun php artisan queue:work --tries=3 PWD=C:\laragon\www\app

I Installed Laragon 3.2.3 (Also tried with 3.1 as well)
I updated to latest mysql 8 from the following link in pic

But I get error after switching to new mysql and starting it.

0_1527594583748_mysqllog.txt

Currently the default setting for the "www" link in Laragon's menu is to go straight to the installed WordPress project front (home) page. As far as I can find, there is no place to set the "www" link to go to the WordPress login page for any specific project.

Hence this feature request,

"Provide the option to set the www link to go to the WordPress login page".

Reason: installing WordPress onto a localhost environment is not for public access, it is primarily for development and editing. This requires our access to have the default location as the login page for the WordPress install, not the front/home page.

The featured "www option" allows us to set it to where we want to go each time.

When I started using Laragon this past month, I installed the portable version instead of the full install.

Now the update (v4.0) arrived and I used the installer exe file to update Laragon.

When I tried to use Laragon via the icon on the desktop, which was installed by the regular installer, I got the error,

"Failed: Apache httpd-2.4.35-win64-VC15"

with a pop-up that said,

"Service Apache can not start. Reason: Port 80 is in use!"

I used the netstat to find what is using Port 80 and found that it was the Portable version, yet the I did not start the portable version specifically, I used the icon installed by the installer.

It appears the installer installed the update over the portable install, yet I seem to be getting 2 instances active, the portable and the regular install.

I would rather not change port numbers, because I only want 1 laragon installed, not both.

What do I do to clean this up, to remove the portable version completely, so when I start Laragon only the one I installed as the update is the one working and uses Port 80?

Thanks

I have an old legacy word press site running an older PHP version. I have installed 7.2 but I cannot upgrade my version of Word Press it tells me that it needs an upgraded PHP. Any idea or suggestion on what I'm doing wrong.

Laragon is a useful tool, but not useful enough, since it crashes if the PHP Opcode Cache is enabled (and configured). Even phpMyAdmin quits. I didn't find any workaround. Her are some opcode related topics, but no answer by the developer given. This way you can't use Laragon for serious development. It seems to be only a playground for beginners. That's a pity.

Hello all, I recently downloaded and installed Laragon in my my PC which has Windows 8.1 64 bits. But when I start Apache I get the following 2 errors.

httpd.exe - Entry Point Not Found The procedure entry point SSL_CTX_set_post_handshake_auth could not be located in the dynamic link library C:\laragon\bin\php\php-7.4.0-Win32-vc15-x64\ext\php_curl.dll. OK httpd.exe - System Error The program can't start because icuuc65.dll is missing from your computer.
Try reinstalling the program to fix this problem.

OK

I can not solve the problems. Please help me. Thanks a lot,

Hasan

Hello, first of all, I love Laragon, thank you very much leokhoa for developing this excellent tool.
I want to know if in the future the application will be updated, and if so, when it is scheduled.
I think it has some tools that need updating like the cmder or quick installs among other things.
Thanks for the program, it makes my day a lot easier.
Sorry for my English that is a little rusty.

Hi leokhoa thanks for this beautiful local development environment software.
I am using it from early release of this software.

I am wondering if you can make same for production vps server.
I is tedious to make production vps working with lots of commands and configurations, if you can make it automatic it will be easy to manage and monitor production servers.

For this feature i am ready to pay for software even others will also pay if you make it.

There is another software for production server management is claver https://getcleaver.com it is good software but has very less amount of features and not actively developed. As i know you are very active in community you can make it much better. I hope you can take it to higher level.

thanks.