I have searched and tried everywhere for something that might fix this but whenever I have a new homestead code folder, it doesn't work when I use vagrant and virtualbox. I have checked my hosts files and every file. No error shows up but it clearly doesn't work. I have also enabled virtualization on my CPU. Below is my current homestead.yaml file
---
ip: "192.168.10.10"
memory: 2048
cpus: 2
provider: virtualbox
folders:
- map: C:/Laravel/code
to: /home/vagrant/code
sites:
- map: homestead.test
to: /home/vagrant/code/homestead/public
- map: homestead1.test
to: /home/vagrant/code/homestead1/public
- map: coursework.test
to: /home/vagrant/code/coursework/public
databases:
- homestead
features:
- mariadb: false
- ohmyzsh: false
- webdriver: false
# ports:
# - send: 50000
# to: 5000
# - send: 7777
# to: 777
# protocol: udp
I am trying to just get coursework.test to work but I'm sure its wrong on both of them
Your problem is in the way you use your slashes.
- map: C:/Laravel/code
has to be
- map: C:\Laravel\code
Another problem you will be walking against is that you do not have a database.
Enable mariadb or something else in your features tab
Related
I'm using homestead globally and I'm getting this error when I'm trying to add my database details to datagrip
The specified database user/password combination is rejected: [28000] FATAL: no pg_hba.conf entry for host "192.168.10.1", user "homestead", database "dogs", SSL on
this is my Homestead.yaml file
ip: "192.168.10.10"
memory: 2048
cpus: 2
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: ~/projects/code
to: /home/vagrant/code
sites:
- map: site1.test
to: /home/vagrant/code/site1/public
- map: site2.test
to: /home/vagrant/code/site2/public
- map: site3.test
to: /home/vagrant/code/site3/public
php: "7.4"
- map: dogs.test
to: /home/vagrant/code/dogs/public
php: "7.4"
databases:
- site1
- site2
- site3
- dogs
features:
- mysql: true
- mariadb: false
- postgresql: true
- ohmyzsh: false
- webdriver: false
#services:
# - enabled:
# - "postgresql#12-main"
# - disabled:
# - "postgresql#11-main"
# ports:
# - send: 50000
# to: 5000
# - send: 7777
# to: 777
# protocol: udp
and what I have in my datagrip when I try to connect
Host: 192.168.10.10
Port: 5432
Authentication: User & Password
User: homestead
Password: secret
Database: dogs
Had the same problem once. I was working with grafana local at the time. Some setups which use postgresql cannot work properly localy with the 10.10 adress.
My fix was changing the ip of my vagrant box to 10.11 .
this fixed the issue.
And if you want to revert that for other project's you can easily do:
#ip: "192.168.10.11"
ip: "192.168.10.10"
Not sure if this will be the solution for your problem. But worth a try
I'm running Homestead under Windows 10 using VirtualBox. For some reason, no matter what I try, I get this error:
I only found a single other question similar to my issues, and the resolution there resulted in an error when running vagrant up.
No input file specified.
My homestead.yaml file looked like this:
ip: "192.168.10.10"
memory: 2048
cpus: 2
provider: virtualbox
folders:
- map: D:/code
to: /home/code
sites:
- map: homestead.test
to: /home/code/test/public
sites:
- map: info.test
to: /home/code/info/public
sites:
- map: food.test
to: /home/code/food/public
databases:
- homestead
- food
- info
features:
- mysql: true
- mariadb: false
- postgresql: false
- ohmyzsh: false
- webdriver: f
My hosts file is:
192.168.10.10 homestead.test
192.168.10.10 info.test
192.168.10.10 food.test
The folder mappings appear to be working. If I browse D:/code from the host I can see the Laravel
install under D:/code/test. I if put a file there on the host, it's visible from vagrant ssh.
What am I missing?
Try updating your Homestead.yaml file to this:
sites:
- map: homestead.test
to: /home/code/test/public
- map: info.test
to: /home/code/info/public
- map: food.test
to: /home/code/food/public
Maybe specifying "sites" multiple times is what's breaking it.
Have you tried logging in to your box with vagrant ssh and then doing flip to toggle between nginx and Apache?
See https://laravel.com/docs/8.x/homestead#web-servers
I have just started trying to set up an instance of homestead. I have been successful so far but I am a bit confused on the current step. I am on a windows machine so have mapped my homestead.yaml ssh key paths to the full windows paths and have confirmed their existence/location. Now when I attempt to ssh into my vagrant box, I am prompted for a password. The default "vagrant" password works but I was under the impression that the ssh keys would handle my sign on.
Here is a look at my homestead.yaml
ip: "192.168.10.10"
memory: 2048
cpus: 2
provider: virtualbox //This is my provider
authorize: C:/Users/me/.ssh/id_rsa.pub
keys:
- C:/Users/me/.ssh/id_rsa
folders:
- map: C:/PROGRA~1/Laravel/Homestead/projects/website
to: /home/vagrant/projects/website
sites:
- map: website.test
to: /home/vagrant/code/website/public
databases:
- website
features:
- mariadb: false
- postgresql: false
- ohmyzsh: false
- webdriver: false
# ports:
# - send: 50000
# to: 5000
# - send: 7777
# to: 777
# protocol: udp
If you are on a windows machine you need to fix your slashes.
authorize: C:\Users\me\.ssh\id_rsa.pub
keys:
- C:\Users\me\.ssh\id_rsa
folders:
- map: C:\PROGRA~1\Laravel\Homestead\projects\website
to: /home/vagrant/projects/website
and the rest is correct.
First off: I'm new to using Laravel. I got the homestead VM up and running with Vagrant. I checked my Homestead.yaml file and it checks out, did the additions to the hosts file as well, and created my blog according to the video tutorials on the VM.
When I run the command "php artisan serve" and try the address it returns, I get an error saying "No input file specified".
Anyone have a fix for this?
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: /Users/JeromePapalie/LaravelCode
to: /home/vagrant/Code/Laravel
sites:
- map: homestead.app
to: /home/vagrant/Code/Laravel/public
databases:
- homestead
First, you need to check the folder structure.
This is my folder structure.
Here my Homestead.yaml file
---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: /Users/kelvin/.ssh/kevin.pub
keys:
- ~/.ssh/kevin
folders:
- map: ~/Documents/Work/kevindev/Code
to: /home/vagrant/Code
sites:
- map: homestead.app
to: /home/vagrant/Code/Laravel/public
databases:
- homestead
# blackfire:
# - id: foo
# token: bar
# client-id: foo
# client-token: bar
# ports:
# - send: 50000
# to: 5000
# - send: 7777
# to: 777
# protocol: udp
Hope, you already generated ssh key file in your target folder something like this.
And then, open your host vim /etc/hosts and add your homestead.app host
Finally, go to your Homestead folder and type vagrant up command.
That's is.
For whatever reason I cannot get multiple sites to work with Homestead. Every new site added, returns the same site when I visit it in the browser
I have tried every "solution" I have come across here on stack as well as on larvel.io. None of them solve the problem. Any help would be greatly appreciated.
Below are the contents of both my .yaml file and my hosts file.
Local Directory Structure:
Root directory = WWW
project1 = WWW/project1
project2 = WWW/project2
Homestead.yaml:
---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: ~/WWW
to: /home/vagrant/Code
sites:
- map: /project1.app
to: /home/vagrant/Code/project1/public
- map: /project2.dev
to: /home/vagrant/Code/project2/public
databases:
- project1_db
- project2_db
variables:
- key: 'APP_ENV'
value: 'local'
- key: 'APP_DEBUG'
value: 'true'
# blackfire:
# - id: foo
# token: bar
# client-id: foo
# client-token: bar
# ports:
# - send: 93000
# to: 9300
# - send: 7777
# to: 777
# protocol: ump
/etc/hosts file:
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
192.168.10.10 project1.app
192.168.10.10 project2.dev
I have tried the following:
vagrant provision
vagrant reload --provision
Destroyed box and vagrant up
vagrant global-status, followed by vagrant provision vm#
have also tried to map folders and sites
ex:
folders:
- map: ~/WWW/project1
to: /home/vagrant/Code/project1
- map: ~/WWW/project2
to: /home/vagrant/Code/project2
sites:
- map: /project1.app
to: /home/vagrant/Code/project1/public
- map: /project2.dev
to: /home/vagrant/Code/project2/public
First, one tip: use nfs because windows folder share is very very slow. To add support for this feature on Windows you should install vagrant-winnfsd
vagrant plugin install vagrant-winnfsd
folders:
- map: ~/WWW
to: /home/vagrant/Code
type: nfs
Just in case remove the slash before the site hostname. I don't have sure if this is the reason but was the only thing wrong I found in your configuration.
sites:
- map: project1.app
to: /home/vagrant/Code/project1/public
- map: project2.dev
to: /home/vagrant/Code/project2/public
Another tip: install the vagrant-hostsupdater plugin to add the hostnames to your hosts file automatically.
vagrant plugin install vagrant-hostsupdater
in you Homestead.yaml file:
aliases: ["project1.app", "project2.dev"]
in scripts/homestead.rb file:
config.hostsupdater.aliases = settings["aliases"]
My files: homestead.rb and Homestead.yaml
Got it.
The slashes before the domain where causing the issue.
Changed this:
sites:
- map: /project1.app
to: /home/vagrant/Code/project1/public
- map: /project2.dev
to: /home/vagrant/Code/project2/public
To this:
sites:
- map: project1.app
to: /home/vagrant/Code/project1/public
- map: project2.dev
to: /home/vagrant/Code/project2/public