Primero debes configura que dominio quieres en mi caso elegi .oo ya que .dev está tomada por GOOGLE Creo mi proyecto Laravel
C:\laragon\www
λ laravel new jilik Me voy a esta URL https://github.com/bantya/MakeCert y me bajo el archivo makecert.bat y lo coloco en esta dirección
C:\laragon\bin\apache\httpd-2.4.27-win64-VC14\bin Ahora lo ejecuto desde esa terminal y me pedirá los siguientes datos
• Hostname: nombre de la carpeta que sea creado en c/laragon/www en mi caso yo le nombre jilik
• domain: En mi caso yo le puse .oo por configuración de Laragon que esta por defecto
• Todo los demás por defecto
• Email : administrador@hostname@domain Como ven me genero tres archivos
jilik.key
jilik.crt
jilik.cnf
• Debe agregarlo como certificado de confianza ... En Chrome, vaya a
chrome: //
• Configuración Configuración avanzada HTTPS / SSL
Administrar certificados.
• Seleccione importar y seleccione el archivo jilik.crt que creó
anteriormente
Importante: Ahora debe seleccionar el almacén de certificados donde
desea almacenar este certificado.
• Seleccione Colocar todos los certificados en la siguiente tienda y en el
Almacén de certificados: seleccione Autoridades de certificación raíz de
confianza
Haga clic en Finalizar / Aceptar y reinicie su navegador. Ahora puede
navegar
• Reinicie el servidor APACHE
• a https://jilik.oo sin que el navegador fastidie el certificado

Phew... I have tried everything I can think of to connect from other LAN computers to Laragon.

When I install Laragon, and then WordPress, I can access WP with no issues so long as I am on the computer where Laragon is located. However, all attempts to connect from other computers fails with "cannot connect" messages.

I have removed and reinstalled all a few times to no avail. I have dropped all firewalls and still no change. The odd thing is that I can ping to the IP addy 192.168.1.5 with no issues, but cannot even get the Laragon screen at that IP address.

I am not using Nginx and prefer to just access without it since this all on localhost. And, I have had Laragon in the past working fine, but something is obviously at work blocking things. Any suggestions and ideas solicited and appreciated.

Thanks

This morning, from remote on LAN to computer with Laragon:

Ping Laragon address 192.168.1.5 Passes

Accessed server computer over LAN by computer name in Windows Explorer Passes - Displayed&Accessed all drives properly.

Access Laragon over LAN in browser as http://computername Passes and displays Laragon screen

Access Laragon over LAN in browser as 192.168.1.5 Fails: ... can't establish a connection to the server at 192.168.1.5

Access Laragon over LAN in browser as http://computername/eco1 Fails - Changes address to:
http://192.168.1.5/eco1?password-protected=login&redirect_to=http%3A%2F2Fcomputername%2Feco1%2F
Then returns ... can't establish a connection to the server at 192.168.1.5

In httpd.conf changed <Directory /> "Allow Override to all" No Change fails to connect

Attempted to upload phpinfo() but do not not have enough privileges.

This topic from Laragon menu is with access denied "https://forum.laragon.org/topic/1018":

I try to share my vhost site with ngrok. but ngrok just show my root directory if I access that ngrok-url..
i use laragon 4.0..
can someone help me ?

Hi @leokhoa , I tried to see the page Quick app> How to manage "Quick app" but I get a Forbidden access page: https://forum.laragon.org/topic/1019 : please, is there a working URL?
Thanks

Hello,

May you update .dev to the new one .oo as found on the Setup Wizard/s please?
Please see below:

Kind regards,

Mic Sumner

Hello,

There's a typo on the homepage:

Petty urls Pretty URLs

Kind regards,

Mic Sumner

Hello to all friends
When I run the program on the nginx web server, I'm seeing the 403 error message
where is the problem from

Run the following error occurs composer
fatal error: class 'phar' not found in c:\laragon\bin\composer\composer.phar on line 23
where is the problem from???

I did a fresh install of Laravel but I am unable to run gulp.

It first eats up around 2 gb of memory then crashes with the following message:

<--- Last few GCs ---> 31244 ms: Mark-sweep 624.1 (716.6) -> 623.9 (716.6) MB, 843.2 / 0 ms [allocation failure] [GC in old space requested]. 32099 ms: Mark-sweep 623.9 (716.6) -> 623.9 (716.6) MB, 854.2 / 0 ms [allocation failure] [GC in old space requested]. 32982 ms: Mark-sweep 623.9 (716.6) -> 623.9 (716.6) MB, 883.8 / 0 ms [last resort gc]. 33848 ms: Mark-sweep 623.9 (716.6) -> 623.9 (716.6) MB, 865.3 / 0 ms [last resort gc]. <--- JS stacktrace ---> ==== JS stack trace ========================================= 2: arguments adaptor frame: 0->2 Security context: 2A27857D <JS Object> 3: loggingCallbackWrapper [Z:\Installed\laragon\www\myApp\node_modules\enhanced-resolve\lib\createInnerCallback.js:31] [pc=17490A42] (this=2A28703D <JS Global Object>) 4: applyPluginsAsyncSeriesBailResult1 [Z:\Installed\laragon\www\myAPp\node_modules\tapable\lib\Tapable.js:~106] [pc=174ACA98] (this=391C3421 <a Resolver with map 24C85AC1>,name=13A459F1 <S... FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

I tried running with the windows console and it just took longer to crash.

Any thoughts?