homestead | Laravel Homestead is an official , pre-packaged Vagrant box | Database library

Your Homestead.yaml file indicates that your ssh key file is in its typical location: ~/.ssh/id_rsa. However, the debug output shows that ssh is looking in another location for the key:

I think this is the fix, but I couldn't get it running until now:

Anything in the 192.68.56.0/21 range will work out-of-the-box without any custom configuration per VirtualBox's documentation.

https://github.com/laravel/homestead/issues/1717

Found some more related information here:

https://discuss.hashicorp.com/t/vagrant-2-2-18-osx-11-6-cannot-create-private-network/30984/16

update 29.10.2021:
I downgraded virtualbox to 6.1.26 and it's working again.

Try running

// Storage::assertExists(public_path() . '/docs/clothing/existing_file.pdf');

// this assertion fails, what's weird is the path in the exception message does actually exist

The Storage facade uses the storage that is active in your config files (config/filesystems.php). Note that this defaults to local. The root path is set for each storage option. In the case of local, it's pointing to storage/app out of my head. - @bobbybouwmann

In addition, the right way to search through the storage path, is to first specify the filesystem "disk". I.e, for a file residing in storage/app/public/demo.js:

Storage::disk("public")->assertExists("demo.js");

With that out of the way, since your desired test file(s) reside in the pubic folder, these could be tested using:

$this->assertFileExists(public_path() . '/docs/clothing/existing_file.pdf');

//usually I'd get the page urls dynamically with Dusk, but for simplicity sake I'm just testing with this link that I know it exists and can curl it from withing Homestead

$this->get('/docs/clothing/Hoodies.pdf')->assertStatus(200); //failes (404)

The above snippet of code doesn't work because $this->get(...) is essentially searching for an explicitly defined route in the application's route file(s) corresponding to this path which is not found.

You must use a browser test framework (I.e Laravel Dusk) to test static files on a web server.

More to that can be found here: How to test for static files located in the web folder in symfony with phpunit?

Nonetheless, since you're using Laravel Dusk already, this can be achieved by:

you can create new project without Initialize repository with a README file.

and follow "Push an existing folder" look like:

I was struggiling with the same issue on my windows machine and found someone has opened this as an issue on the homestead github:

It's because the prepareHeaders property - as the error message says - accepts a function, not an object. You can see from the example here.

I finally resolved this issue by entering the "Path to composer.json" in the PhpStorm settings under "PHP -> Composer" and enabling the setting "Synchronize IDE Settings with composer.json"

Update: This answer only partially solved the issue.

Using tcpdump on the server, I found that the server is indeed receiving data (even though Lumen was saying that it was not receiving data), and the amount of data seemed to correspond with whether a file is attached or not. From this, it seemed the problem was occurring with Apache, PHP, or Lumen.

I also enabled mod_dumpio, and tested the requests with and without a file and both appear to send data normally. The file request was clearly sending a large amount more, and the Content-Length reported seemed accurate, even though Lumen was reporting no data.

Sorting through error.log I did find the error, however. It was just that PHP was dropping the data because it exceeded the post_max_size size of 8MB. Once editing php.ini for that and upload_max_filesize, the application worked fine.

What's funny is that's usually the first error that occurs with file uploads and PHP servers, so it's weird I didn't suspect it. It would be nice if PHP issued a 413 Response by default.