Skip to content
This repository has been archived by the owner on Oct 5, 2021. It is now read-only.

How to add an new host? - everytime redirect to local.dev #126

Open
dermatz opened this issue Jun 18, 2015 · 11 comments
Open

How to add an new host? - everytime redirect to local.dev #126

dermatz opened this issue Jun 18, 2015 · 11 comments

Comments

@dermatz
Copy link

dermatz commented Jun 18, 2015

My current steps.

  1. add file in data_bags > sites > "magento.json"
  2. add content in magento.json

{
"id": "magento",
"host": "magento.dev",
"aliases": [
"www.magento.dev",
"magento.dev"
]
}

  1. add folder in public > magento.dev

clear my dns-cache and call in my browser the new domain: magento.dev
after this - my browser redirect to local.dev (local.dev works how expected)

What i have to add in /etc/hosts ? - what is missing?

@eelkeblok
Copy link
Contributor

The data bags are only parsed when the Vagrant box is provisioned. You have two options:

  • Destroy the box and re-provision (or use the --provision flag when reloading, but I'm not sure whether that will actually work)
  • Manually add a site in /etc/apache/sites-available and enable it with a2enmod (leave your databas json for the next time you want to recreate your box). That's not as daunting as it sounds, just copy an existing file and modify it. Take note that at least te version I am using duplicates the information in the vhost file. You can safely delete the duplicate stuff.

@dermatz
Copy link
Author

dermatz commented Jun 18, 2015

Thank you :) i will try 👍

@dermatz
Copy link
Author

dermatz commented Jun 18, 2015

I tried 2 methods.
Try 1 - $ vagrant reload --provision
Try 2 - destroy the box and vagrant up again ...

but it will also redirect to local.dev. :-/

@eelkeblok
Copy link
Contributor

Not sure what is going on. Investigate the entries in sites-available that are created.

@mattcremerband
Copy link

Have you set your hosts file to point to the relevant url?
currently my /etc/hosts file has the following records, which all work as necessary:
192.168.33.10 local.dev
192.168.33.10 dev.magento1.9.1.1.local

@dermatz
Copy link
Author

dermatz commented Jun 21, 2015

My windows\system32\drivers\etc\hosts
192.168.33.10 local.dev
192.168.33.10 magento.dev

local.dev works
but magento.dev not .. it redirect to local.dev

@eelkeblok
Copy link
Contributor

Have you checked the vhost configuration inside the box? What is in /etc/apache2/sites-available? What's in /etc/apache2/sites-enabled? Were there any error messages when having the box provision that could point to trouble creating the vhost?

If magento.dev ends up on local.dev there is nothing wrong with your hosts file, because it gets to the correct IP address. Something goed wrong on the vagrant box while mapping the domain name to the relevant vhost.

@theclue
Copy link

theclue commented Aug 1, 2015

same here. I've used vagrant-lamp for a long time but with the latest checkout it stopped working.

In sites-enabled and sites-available I correctly see my vhost "9thcircle.dev", although the files have three identicalcopy of the <VirtualHost *:80> block inside (which sounds weird to me at first place)

but 9thcircle.dev redirects to local.dev

@pessato
Copy link

pessato commented Sep 6, 2015

Having the same issue, did anyone overcome this?

@eelkeblok
Copy link
Contributor

I have seen the duplicate blocks in the vhost configurations as well, but it hasn't caused me a lot of trouble. It could be related, though. It looks like something goes wrong generating the vhost configs from the data bags.

Something else that may be foiling you is the "canonical host redirection" that was added fairly recently (and which is probably responsible for the actual redirecting to local.dev); whenever a vhost gets activated, it will check the hostname against the "canonical" host name for that vhost and redirect to it. At least it sometimes helps figuring out there is an issue with your vhosts; for some reason, you local.dev vhost gets activated and not the one you're expecting. The answer must be in the vhost definition, most likely in the one that is not working. Could you post both your local.dev and 9thcircle.dev vhost here? Are either of them altered in any way? When did you last completely destroy and recreate your vagrant box?

@JanVerkoyen
Copy link

$ vagrant reload --provision
Worked! Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants