thanks for reading my question, I installed laravel, virtualbox, and vagrant on my Windows 10 x64 pc, I use wamp to work.
I created my ssh credentials this way
After that I made a homestead make and vagrant up but I always get this error:
The keys are generated and for some reason the vagrant does not detect the private key (I think)
What could be happening and how to make run the homestead without any trouble?
Related
I installed correctly vagrant but when I try to open vvv.test browser don't allow to show me the page
no erros when I initialized vagrant
I work on windows 10, a new installation with no particular environment. I use vagrant on my laptop and no problem incurred. On this new installation if I use the last version of vagrant I can't initialized vagrant because an error of vagrant to download the package. I installed the same version of vagrant on my laptop vagrant_2.2.10_x86_64 and I can do all except for the error of browser.
I can access without problem with ssh.
I don't know why I have this problem
Trying to install laravel homestead in windows but inside a virtualbox. So first I installed VirtualBox which then allows me to install a VM which I called LaravelBox (so this is an empty machine) - which means I need to install ubuntu 16.04, then vagrant (as the documents on the laravel homestead site (https://laravel.com/docs/5.5/homestead#installation-and-setup) - which instruct me to install the homestead vagrant box, then configure, etc. When I get to he final step to run vagrant up, I get the error:
**Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
Vagrant uses the VBoxManage binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
VBoxManage binary and add it to the PATH environmental variable.**
Does this mean then I now need to install virtualbox inside the VM I just created called LaravelBox? - so it's the case of a VM that contains the laravel homestead vagrant box is inside a a VM? Any help is appreciated, thanks.
The first question why you try to install homestead in a VM instead of installing it in Windows directly?
Yes, the problem is that your VM can't find any Virtualbox installation, then you have to install it there and it will be working.
Homestead was meant to provide a Unix like dev environment so that it would be easier to work with symlinks and permissions, it uses Ubuntu vagrant box by default.
So you can either install homestead directly on your host machine i.e windows or as you already have a Ubuntu VM you can setup a basic dev server manually.
It does not make sense to run a VM inside a VM
I currently have Laravel homestead on windows (working on windows 10 and Windows 8)
I am using Laravel version 5.5.3, and I pushed this to bitbucket, and cloned the repo on a mac with Sierra 10.12.6
I have already checked around the questions and tried adding the port in the .env file, but the port is already there as 3360, and it's correct. The db name and pass are also correct. Does the mac user just have to download and use vagrant homestead? Is there an alternative to installing vagrant and homestead to migrate the database for a mac user?
I think part of the problem is that since I uploaded it to bitbucket and the mac user cloned it, it has some settings that are configured to having homestead, so I'm guessing the mac user needs to install those other programs (homestead, vagrant, and vmware).
Thanks!
You are correct. If the database is created via Homestead and the configuration in the .env points to Homestead then the mac-user needs Homestead as well.
Install the necessary software and try again with Homestead up on the mac.
An alternative would be to use another local dev-environment like XAMPP or MAMP or some other local server and database. If you do this you have to change the database-configuration in the mac-users .env-file.
After logging into the VM using vagrant ssh using GitBash on Windows 10, I don't see any directory prompts. While it does run the python web forum (for a tutorial on Udacity on Intro to Relational Databases), it won't let me run psql so I can continue the lesson. I can change directories, list information about the files, and run python but the prompt isn't working like normal.
Screenshot here: screenshot.
Please note the forum is running, this screenshot was taken after I exited and restarted vagrant.
Vagrant version 1.9.6
Ubuntu version 16.04.2 LTS
All programs installed or running in administrator mode.
I had the same problem attempting to set up Laravel Homestead - in my case it seems to be an issue with Git Bash / MINGW64.
My work-around was to use PuTTY
Install PuTTY, PuTTYgen
Create a .ppk of the key you're using to connect to the vagrant vm by loading the private key in PuTTYgen and saving the private key
Create a new PuTTY session with your vagrant details, in my case I just copied what was displayed after running "vagrant up" as far as SSH address, username (my PuTTY session Host Name would be "vagrant#localhost" port: 2222)
specify the ppk in the PuTTY configuration under Connection-> SSH-> Auth-> Private key for authentication
In short, try connecting with PuTTY or some other terminal emulator and see if you have any luck.
I wasn't able to get Git Bash to work, but the show window for the Oracle VM VirtualBox Manager does work just fine. I've been using Git Bash to start the VM, then switch to the Oracle VM UI window.
I had the same issue with truing to connect to a virtual Homestead session (Laravel) using virtual box and I was trying to connect via Gitbash MINGW64 as well.
I tried the same in cmd.exe (command: vagrant ssh) and it worked.
So should be issue with Git bash.
I can't seem to get VMWare support working with Laravel's Homestead on Windows 7.
I've bought and installed VMWare Workstation and Vagrant's VMWare plugin and added the licence for it.
I've downloaded the homestead box via the command in the laravel docs vagrant box add laravel/homestead and selected option 2 for vmware_desktop.
And specified provider: vmware_desktop in my ~/.homestead/Homestead.yml file and run vagrant up from where I downloaded the Homestead Vagrant files.
And I get the message:
C:\Users\Ezra\Desktop\Homestead>vagrant up
The provider 'vmware_desktop' could not be found, but was requested to
back the machine 'default'. Please use a provider that exists.
I've tried different provider names; like: vmware_fusion, vm_desktop, vm_fustion.. etc. Nothing works.
I've got the latest vmware_desktop image at v0.2.7 and visually verified the files exist in the ~/.vagrant.d/boxes directory.
VirtualBox provider works fine. But not VMware. Any ideas? :)
To get Homestead working on Windows, the provider must be set to:
provider: vmware_workstation
Made a PR to the laravel docs, so this shouldn't be an issue for anyone else going forward. :)
For Laravel 5 and Homestead 2.0
Try to run
homestead up
Then
homestead provision
This will reload your ~/.homestead/Homestead.yml for additional sites and/or configuration.