@tatoosh You can do it manually with instructions from our friend @leokhoa here: https://forum.laragon.org/topic/455/laragon-auto-startup-on-windows-server-2008/2

@leokhoa Thanks!

I updated Node by renaming the folder c:\laragon\bin\nodejs to c:\laragon\bin\nodejs_old and downloaded a new copy of nodejs from the node website and dropped it into c:\laragon\bin\nodejs.

Now when I run node -v I get v7.10.0 which is great!

However, my npm version hasn't updated? When I run npm -v I get 3.10.8 is this running the global npm?

If I run C:\laragon\bin\nodejs>npm -v I get 4.2.0

Any advice on getting Laragon/Cmder to run npm within Laragon, i.e. c:\laragon\bin\nodejs\npm?

Thanks!

@leokhoa

Thank you! Your efforts are greatly appreciated.

@leokhoa Thanks so much for your reply!

I'll look more into what these commands are doing before I use them and then try experimenting.

By the way, do you have a way Laragon users can contribute a donation to the Laragon project? I have benefitted a lot from this tool and the support on the forum is fantastic. I would be happy to make a small donation if possible. Thank you.

Hi,

I'm using Laragon 2.2.2 on Windows Server 2008 R2 Enterprise and I would like to get Laragon to start automatically when the server is restarted. If it's of any further help I am using MariaDB (running on port 3306) and Apache (running on port 8000).

I have tried the following:

1. Switching on the following settings in Laragon:

• "Preferences > General > Run Laragon when Windows starts"
• "Preferences > General > Start All automatically"

However, Laragon does not start even after logging in via remote desktop.

2. Looking for Apache and MariaDB/MySQL in services.msc and setting the "Startup Type" to automatic, but I could not find any of these services?

I've also found I have to right click on Laragon and to run as administrator to get it to run properly, otherwise, I receive lots of errors once Laragon starts.

Any suggestions on how I could get this to work?

Thank you!

@leokhoa Still no change, sorry! See screenshot below...

I don't think Ngrok is running properly to be honest, see the error "Could not detect Ngrok tunnel link".

I think I am going to give up on this now. Thanks a lot for your help and assistance it's really appreciated.

@leokhoa I didn't try that because it didn't appear ngrok was functioning correctly so why try Dusk. I just tried it anyway and dusk is still returning error and outputting the Laragon splash page.

Anytime I run dusk, even when I remove the Laravel app from C:/laragon/www/ticket to some other folder and use php artisan serve, dusk always returns the Laragon splash page. Any idea why this happens?

@leokhoa I have tried Menu > Ngork > share -> ticket.dev

With ngrok, I am getting the same issue with the Laragon splash page displaying instead of http://ticket.dev. I am guessing it is down to my proxy again. Any workarounds for this?

Here's a screen shot of the result after running Ngrok