Hi - so I upgraded to Laragon 4 and used the quick install for PostgreSql. I added an empty database from pgAdmin and once I got it to allow me to click the "restore" button I tried restoring an existing database. (I'm new to PostgreSql)
But I get an error dialog with "The program can't start because python36.dll is missing from your computer".
I've restarted and then done a separate install of Python to the computer plus a restart, but same error.
Any ideas?

FYI: the quick install of PostgreSql seems to miss anything to do with setting a password, or showing a dialog to add one - I got stuck till I added my own "pgpass.conf" file in the PostgreSql directory.

Thanks for the great work making Laragon!

I have two WordPress installs running on my machine:

staging.test testing.test

When I'm browsing both sites simultaneously staging.test keeps redirecting to testing.test/wp-admin/install.php, while both are loading.

This happens when I'm logged in or not, doesn't matter.

My notes:

I don't wanna use MailHug as Gmail is perfect for me Apache's SSL port are enabled. Mailcatcher is displaying notification correctly but email is not received in gmail. Laragon Mail Analyzer is working as expected and received email. Since my Google account is 2FA, so using App Password. Will distributing laragon.ini in public leaks App password, asking because can it be decrypted or not.

Content from debug.log

18/12/18 01:32:52 ** --- MESSAGE BEGIN --- 18/12/18 01:32:52 ** To: dev.shivapoudel@gmail.com 18/12/18 01:32:52 ** Subject: Test 18/12/18 01:32:52 ** 18/12/18 01:32:52 ** Hello! 18/12/18 01:32:52 ** --- MESSAGE END --- 18/12/18 01:32:52 ** Failed to load SSL libraries: Could not load SSL library. 18/12/18 01:32:52 ** Connecting to smtp.gmail.com:587 18/12/18 01:32:52 ** Connected. 18/12/18 01:32:53 << 220 smtp.gmail.com ESMTP a73sm21547549pfa.7 - gsmtp<EOL> 18/12/18 01:32:53 >> EHLO laragon.org<EOL> 18/12/18 01:32:53 << 250-smtp.gmail.com at your service, [103.232.231.206]<EOL>250-SIZE 35882577<EOL>250-8BITMIME<EOL>250-STARTTLS<EOL>250-ENHANCEDSTATUSCODES<EOL>250-PIPELINING<EOL>250-CHUNKING<EOL>250 SMTPUTF8<EOL> 18/12/18 01:32:53 ** Authenticating as dev.shivapoudel@gmail.com 18/12/18 01:32:53 >> MAIL FROM: <dev.shivapoudel@gmail.com><EOL> 18/12/18 01:32:53 << 530 5.7.0 Must issue a STARTTLS command first. a73sm21547549pfa.7 - gsmtp<EOL> 18/12/18 01:32:53 ** Disconnecting from smtp.gmail.com:587 18/12/18 01:32:53 ** Disconnected. 18/12/18 01:32:53 ** Disconnected. 18/12/18 01:32:53 ** Must issue a STARTTLS command first. a73sm21547549pfa.7 - gsmtp<EOL>

Content from error.log

18/12/18 01:32:53 : Must issue a STARTTLS command first. a73sm21547549pfa.7 - gsmtp<EOL>

After installing WordPress via Quick app, in config file it adds two lines:

define('WP_SITEURL', $_SERVER['REQUEST_SCHEME'] . '://' . $_SERVER['HTTP_HOST']); define('WP_HOME', $_SERVER['REQUEST_SCHEME'] . '://' . $_SERVER['HTTP_HOST']);

Because of that, In WP CLI we receive notice while executing commands:

$ wp plugin activate woocommerce Notice: Undefined index: REQUEST_SCHEME in phar://C:/laragon/usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1150) : eval()'d code on line 29 Call Stack: 0.2760 393544 1. {main}() C:\laragon\usr\bin\wp:0 0.4327 879272 2. include('phar://C:/laragon/usr/bin/wp/php/boot-phar.php') C:\laragon\usr\bin\wp:4 0.4462 886408 3. include('phar://C:/laragon/usr/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php') phar://C:/laragon/usr/bin/wp/php/boot-phar.php:11 0.4556 897896 4. WP_CLI\bootstrap() phar://C:/laragon/usr/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php:23 1.2518 8162048 5. WP_CLI\Bootstrap\LaunchRunner->process() phar://C:/laragon/usr/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php:74 1.2519 8162088 6. WP_CLI\Runner->start() phar://C:/laragon/usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php:23 1.2646 8162992 7. WP_CLI\Runner->load_wordpress() phar://C:/laragon/usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1111 1.3066 8180096 8. eval('/** ... ... ... ') phar://C:/laragon/usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1150 Plugin 'woocommerce' activated. Success: Activated 1 of 1 plugins.

I have enabled Apache's SSL Port and PHPMyAdmin is installed but while clicking Databse it redirects to http://localhost/phpmyadmin/index.php and not lauched HTTPS phpmyadmin page.

Additionally, you can see Quick app creating sandbox.test and pretty URL is missing HTTPS.

Also found all the htdocs document root site are also launched without https.

Is there any settings available for launching theme in HTTPS environment or HTTP environment. Also can phpmyadmin link be mapped to specific domain.

Okay, I'm feeling really stupid right now but after installing Laragon 4.0 I see it has it's own versions of Apache (2.4.35), PHP (7.2.11) and mySQL (5.7.24). I also have Wamp installed but before starting Laragon, I made sure that all Wamp versions were terminated. Yet, Laragon keeps starting the Wamp version of mySQL. I know this first as the old password works using phpMyAdmin but also all of my old databases are there.

Now sharing the same version isnt the most terrible thing but not knowing is (having apps starting automatically and thinking one should be loading when a different version is. How is this managed with Laragon? Is there a .config file or using Windows PATH?

Cheers, Billie

Hey Guys,

I dont manage to get the Pretty Urls working. I checked my HOSTS file and it is added in there. But my Mozilla poops out an error.

Image:
. I've googled for a bit and couldnt find a proper answer to my problem.

Thanks in advance

Edit: Image wouldnt work properly. Had to re-upload

Re: Laragon 4.0 released! - with "Quick add" feature

I prefer dotbot to create symlinks for dotfiles. If this packages.conf file is symlink then on next reload it do create data from that manifest. Need help

Hello,

I'm new to Laragon and very satisfied. However, I already have a question:

Is it possible with "Quick Create" to deposit two download links at once? Once the resource directly and then my project (git) folder (template)?

Thanks

With Laragon 2.1.0, you can use your favourite editor with Laragon and add it to the Right-Click Menu for quick access. In this article, we will add VS Code.

Download VS Code:
https://code.visualstudio.com/Docs/?dv=win Extract the downloaded to: {LARAGON_ROOT}\bin\code Open laragon.ini in Menu > Laragon > Settings file: laragon.ini Put Editor=PATH-TO-EXE under [preferences] [preferences] Editor=bin\Code\code.exe

Note: If you extract outside Laragon's installation dir, you must put full path. For example:

[preferences] Editor=C:\editor\Code\code.exe (Optional) Add to Right-Click Menu: Click Tools > Right-Click Menu > Add/Update Code & Terminal
Note: You must run Laragon as Administrator to do that.

Very easy huh. That's all forks!

Suppose I am creating development.test site for WordPress then can't I have a certain prefix to database table. I always do create wordpress_development in XAMPP to showcase all my DB table in a collection in PHPMyAdmin. If laravel app was created the DB name like laravel_development

Installing ImageMagick is really pain on other systems. However, it is trivial with Laragon if you follow these below steps (works with both Apache & Nginx):

Download links:
PHP Extension (PECL):
https://pecl.php.net/package/imagick/3.4.3/windows
Imagick Binaries & Dlls:
http://windows.php.net/downloads/pecl/deps

*IMPORTANT: Choose the right packages (version, x86 or x64, VC, Thread Safe (ts) or Non Thread Safe (nts)).
Even your OS is 64-bit, you should depend on the suffix -x86 or -x64 of the PHP version to select the correct ones.

To be more specific: if you are using php-7.1.7-Win32-VC14-x64 you should download:*
PECL:
http://windows.php.net/downloads/pecl/releases/imagick/3.4.3/php_imagick-3.4.3-7.1-ts-vc14-x64.zip
ImageMagick Binaries & Dlls:
http://windows.php.net/downloads/pecl/deps/ImageMagick-6.9.3-7-vc14-x64.zip

After downloading the right packages, the next steps are easy.

Extract: PECL: Extract php_imagick-3.4.3-7.1-ts-vc14-x64.zip to a tmp dir, then put just php_imagick.dll to PHP Extension dir (Menu > PHP > dir:ext) Imagick Binaries & Dlls: Extract ImageMagick-6.9.3-7-vc14-x64.zip to a tmp dir, then put all dlls in bin (CORE_RL_*.dll, FILTER_analyze_.dll, IM_MOD_RL_*.dll, ImageMagickObject.dll) to PHP dir where the php7ts.dll is located (Menu > PHP > Version > dir:php-7.1.7-Win32-VC14-x64)

Enable:
Just click Menu > PHP > Extensions > imagick

Restart Apache/Nginx

That's all forks.

I have looked at some of the discussions regarding deleting a WordPress project. I found the answers somewhat terse, but hope I have done it correctly. (In Windows) I deleted the folder in ...\www with the project name and similarly the folder in ...\data\mysql. Hopefully, that is correct. Please confirm.

I was doing it in this instance because I had what may have been a corruption problem with the project and wanted to start over.
I recreated the project, using the identical name, from the QuickAdd menu for WordPress. After the project was created, I went to the site in the browser and was greeted by the expected "install WP" language menu. After selecting the language, I got 24 pages of WordPress errors. I will try to upload a pdf of the errors. 0_1544364468250_WordPress › InstallationErrors.pdf

The name of the project is Gutenberg or gutenberg, with an internal name of "Gutenberg test", as I created it to test the new release on existing websites.

I went through this twice and had the same results. In the second try, I found that there was a "Success" message at the bottom of the errors and a link to login. Hitting that took me back to the language selection screen.

Any help and guidance is much appreciated. I do ask that the responses lean a little more towards verbose than not, otherwise I find myself guessing as to what actually has to be done.

Hello everyone , i would like to change mod_rewrites method on nginx on laragon portable. I use the NGiNX 1.14 with PHP 5.6.39 and i have already transform a website inside virtual host. Everytime who calling static methods as like index.php or alternative structures i get the default index On administrator page returned 404 ERROR if call login method , what must i do to enable the index.php rewrites on my local webserver ?

Many thanks

Hi, I use Laragon 4.0.2 with NodeJS.
I ve also an portable version of Git. I use it through Git bash, works fine.

I try to use ungit, I install it:

npm install -g ungit

ungit@1.4.36

Then, I try to launch ungit:

ungit

But I ve this error:

Error: Command failed: git --version
'git' n'est pas reconnu en tant que commande interne

There is a way to "tell" to NodeJS Where is the git portable version?

Thx you for your help, and sorry for my basic english.

Preferences > General > Document Root

I just installed Laragon Lite 4.0.3 on Windows 10 without any problems and it started right up. From the initial welcome screen I clicked the gear icon (preferences) and set to configuring Laragon. But I need to change Document Root as our workflow/Gitflow is set-up, tried and tested and will be expecting a public_html. But the prefs form field is a file/directory picker that doesn't allow keystrokes and that's a bit useless for setting/using variables. In fact I can't even get it to return to the default value..

I just installed version 4.0.3.181210 version on windows 10. When I try do add ruby for example, I have a modal with Downloading. The progress don't fill

I get error when try to install gem therubyracer due to libv8 gem:

λ cat C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/extensions/x64-mingw32/2.4.0/libv8-3.16.14.19/gem_make.out current directory: C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/ext/libv8 C:/laragon-ruby/bin/ruby/Ruby24-x64/bin/ruby.exe -r ./siteconf20181213-6584-1x9zdft.rb extconf.rb creating Makefile find: â?~outâ?T: No such file or directory GYP_GENERATORS=make \ build/gyp/gyp --generator-output="out" build/all.gyp \ -Ibuild/standalone.gypi --depth=. \ -Dv8_target_arch=ia32 \ -S.ia32 -Dv8_enable_backtrace=1 -Dv8_can_use_vfp2_instructions=true -Darm_fpu=vfpv2 -Dv8_can_use_vfp3_instructions=true -Darm_fpu=vfpv3 GYP_GENERATORS=make \ build/gyp/gyp --generator-output="out" build/all.gyp \ -Ibuild/standalone.gypi --depth=. \ -Dv8_target_arch=x64 \ -S.x64 -Dv8_enable_backtrace=1 -Dv8_can_use_vfp2_instructions=true -Darm_fpu=vfpv2 -Dv8_can_use_vfp3_instructions=true -Darm_fpu=vfpv3 Patching out/build/All.target.ia32.mk... Patching out/build/All.target.x64.mk... Patching out/Makefile.ia32... Patching out/Makefile.x64... Patching out/preparser/preparser.target.ia32.mk... Patching out/preparser/preparser.target.x64.mk... Patching out/samples/lineprocessor.target.ia32.mk... Patching out/samples/lineprocessor.target.x64.mk... Patching out/samples/process.target.ia32.mk... Patching out/samples/process.target.x64.mk... Patching out/samples/shell.target.ia32.mk... Patching out/samples/shell.target.x64.mk... Patching out/src/d8.target.ia32.mk... Patching out/src/d8.target.x64.mk... Patching out/src/d8_js2c.host.x64.mk... Patching out/src/d8_js2c.target.ia32.mk... Patching out/tools/gyp/js2c.host.x64.mk... Patching out/tools/gyp/js2c.target.ia32.mk... Patching out/tools/gyp/mksnapshot.host.x64.mk... Patching out/tools/gyp/mksnapshot.target.ia32.mk... Patching out/tools/gyp/postmortem-metadata.target.ia32.mk... Patching out/tools/gyp/postmortem-metadata.target.x64.mk... Patching out/tools/gyp/preparser_lib.target.ia32.mk... Patching out/tools/gyp/preparser_lib.target.x64.mk... Patching out/tools/gyp/v8.host.x64.mk... Patching out/tools/gyp/v8.target.ia32.mk... Patching out/tools/gyp/v8.target.x64.mk... Patching out/tools/gyp/v8_base.host.x64.mk... Patching out/tools/gyp/v8_base.target.ia32.mk... Patching out/tools/gyp/v8_base.target.x64.mk... Patching out/tools/gyp/v8_nosnapshot.host.x64.mk... Patching out/tools/gyp/v8_nosnapshot.target.ia32.mk... Patching out/tools/gyp/v8_nosnapshot.target.x64.mk... Patching out/tools/gyp/v8_shell.host.x64.mk... Patching out/tools/gyp/v8_shell.target.ia32.mk... Patching out/tools/gyp/v8_snapshot.host.x64.mk... Patching out/tools/gyp/v8_snapshot.target.ia32.mk... Patching out/tools/gyp/v8_snapshot.target.x64.mk... make[1]: Entering directory '/c/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/vendor/v8/out' CXX(target) /c/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/vendor/v8/out/x64.release/obj.target/preparser_lib/src/allocation.o ../src/allocation.cc:123:3: fatal error: opening dependency file C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/vendor/v8/out/x64.release/.deps/c/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/vendor/v8/out/x64.release/obj.target/preparser_lib/src/allocation.o.d.raw: No such file or directory } } // namespace v8::internal ^ compilation terminated. make[1]: *** [tools/gyp/preparser_lib.target.x64.mk:87: /c/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/vendor/v8/out/x64.release/obj.target/preparser_lib/src/allocation.o] Error 1 make[1]: Leaving directory '/c/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/vendor/v8/out' make: *** [Makefile:195: x64.release] Error 2 C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/ext/libv8/location.rb:36:in `block in verify_installation!': libv8 did not install properly, expected binary v8 archive 'C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/vendor/v8/out/x64.release/obj.target/tools/gyp/libv8_base.a'to exist, but it was not found (Libv8::Location::Vendor::ArchiveNotFound) from C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/ext/libv8/location.rb:35:in `each' from C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/ext/libv8/location.rb:35:in `verify_installation!' from C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/ext/libv8/location.rb:26:in `install!' from extconf.rb:7:in `<main>' Applying C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/patches/disable-building-tests.patch Applying C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/patches/disable-werror-on-osx.patch Applying C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/patches/disable-xcode-debugging.patch Applying C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/patches/do-not-imply-vfp3-and-armv7.patch Applying C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/patches/do-not-use-MAP_NORESERVE-on-freebsd.patch Applying C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/patches/do-not-use-vfp2.patch Applying C:/laragon-ruby/bin/ruby/Ruby24-x64/lib/ruby/gems/2.4.0/gems/libv8-3.16.14.19/patches/fPIC-for-static.patch Compiling v8 for x64 Using python 2.7.13 Using compiler: c++ (GCC version 7.3.0) Beginning compilation. This will take some time. Building v8 with env CXX=c++ LINK=c++ make x64.release extconf failed, exit code 1

Hi,

Everything else works great but when I try to change my active PHP version 7.1.20 to versions 7.2.* I get "Fatal error: Uncaught Error: Call to undefined function mysql_connect() in..." type of error when I visit local sites and a white screen. Then I revert back to 7.1.* versions and everything loads fine.

Is there a simple way to upgrade PHP without crashing WordPress installations?

Hi everyone! Before i downloaded laragon i usually used the 3.2.1 Version of Xampp. I have many sites in Xampp which they are used the 5.6.11 Version of PHP and since i have transfered them to laragon i have too many warnings. Where can i found the 5.6.11 version of Php or 5.5?