Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

skeith22's avatar

laravel new app-name curl error 6. this should not happen.

laravel installer version is 1.4

*NOTE I turned off the internet intentionally after caching all the required packages of Laravel. It means that I run the "laravel new app-name" with internet to cache the packages before doing this.

I tried installing it with no internet and this is the result. it should just install normally by using the cache packages but instead it spits out this error

I'm getting an error when using the laravel new command

cURL error 6: Could not resolve host: cabinet.laravel.com (see 
http://curl.haxx.se/libcurl/c/libcurl-errors.html)
0 likes
7 replies
Yamen's avatar

Because It needs to check the latest live versions and if they are symmetric it will load it from cache. Just turn on the internet buddy.

skeith22's avatar

@Yamen hi yamen, I turned off the internet intentionally to test if the installer would run without internet. it should work without internet. it should cause that's what it does before. it should just load it from cache.

and I know it checks for the latest live versions, but then again it should just load the cache if there is no internet but instead it spits out error, that's the purpose of the installer to install the latest cache if there is not internet.

ChristophHarms's avatar

This is intentional, you can find the code responsible for the behaviour here.

Only the composer dependencies are cached (by composer's own caching mechanism). Before the laravel new command can do a composer install, it first has to download an empty laravel application (with a composer.json file). This empty laravel application gets downloaded as a zip file and doesn't get cached anywhere.

If you want complete caching, don't use the laravel installer, instead use purely composer like this:

composer create-project laravel/laravel my_project 5.5.* 

(or similar)

I haven't tested this, but it should work, since composer does cache all it's packages.

1 like
ChristophHarms's avatar

Because It needs to check the latest live versions

That is not correct, it automatically downloads the latest stable or development release, depending on whether you provided the "--dev" flag or not, without checking anything.

You can check the code of the install command to verify, maybe I overlooked something...

Please or to participate in this conversation.