Unabled to Access New Site
opened this issue · comments
It seems like its skipping a step where it should be installing database and htdocs etc. but its not. I tried so many times and it still doesn't work. is there a solution for this.
Even I tried several times it successfully complete the process but it doesn't create htdocs folder and when I check phpmyadmin it creates empty database.
I tried all the fixes mentioned here but none worked for me.
please help us
same here
I haven't figured it out yet, still ahving issues, but what am doing right for those who wants to try. I'm using a MacOS and here's what im trying to do right now.
I downgraded VirtualBox to 5.1.6
I downloaded the latest development version of VVV
I also downloaded the latest development version of VV
I went this route because on my PC, this works fine for some reason, but the macOS isn't working properly
I will give you the result soon.
So i got my to work finally
Use the following
VirtualBox 5.1.6
VVV version 1.4.0
VV version 1.12 which i believe the latest one.
it was because of the latest development of VVV was causing the problem. so I just decided to test the stable version of VVV which was 1.4.0.
I think we all should use the stable versions not the development versions.
my works now.
@benlumia007
Do you think the problem is with virtualbox version? Im using 5.1.8
@VWinDev
This happens to be on my Mac, but my PC is already on Virtual Box 5.1.6 with 1.4.0 version of VVV and the latest version of vv which is 1.12
I do because when I was using VirtualBox 5.1.8 and I had a clean Vagrant 1.8.7 with the latest development of VVV and VV, and when I did vagrant up, it give me something about it couldn't let me download the ubuntu/trusty64 box. Then I went and ahead and downgrade to VirtualBox 5.1.6 with the latest development of VVV and VV and I went ahead and did vagrant up and it downloaded the box and continue on to finished, and VVV worked, but with VV, it still didn't work.
From here, since VV didn't work. I end up thinking that, with Virtualbox 5.1.6 and the latest VVV worked. i started to think that maybe the VVV had issues where you try to use vv, so I deleted VVV and downloaded the vvv 1.4.0 version and I installed successfully and did vv and it worked.
I hope that it make sense. What i thought about was, some people would end up doing bleeding versions which are beta versions and think that's where the problem lies. So I decided just use stable versions of virtualbox and VVV and vv that i know it works, i just keep it as it is.
@benlumia007
Ok thanks for your guidance, but how to downgrade the virtualbox?
if you're on MacOS, you should be able just delete it from the /Application
Im using windows, you mean completely uninstall VB and reinstall the older version and then install VVV and VV again?
My problem is vv creates all the necessary files but a blank database and htdocs folder is not getting created. Even tried vagrant provision after vv does its job but all I see is a blank database and neccessary files, and htdocs is still missing.
yeah i had that problem with my MacOS, but my PC works because I was using VirtualBox 5.1.6, so you would have to uninstall VirtualBox 5.1.8 and the extension as well, then you install the older version of VirtualBox 5.1.6 and try again with the same VVV and VV.
Ok how about vagrant version 1.8.7? Im using 1.8.6,
My pc has
virtual box 5.1.8
vagrant 1.8.6
vvv 1.4.0
vv 1.12
i would recommend keeping 1.8.6 because if you get this to work. keep it as it. it is not necessary to upgrade everytime when there's new version. to me that's pointless and leads to problems.
On My PC
I have the following Items
- VirtualBox Version 5.1.6
- Vagrant 1.8.6
- VVV (1.4.0)
- VV (1.12)
Actually it takes more time to do all this steps around 2hrs :-(
but I'll give it a try
Thanks for your support
@benlumia007
The guest additions on this VM do not match the installed version of VirtualBox! Do you get this? and still VVV and VV working fine?
you will need to install that extension version 5.1.6 as well,
http://download.virtualbox.org/virtualbox/5.1.6/Oracle_VM_VirtualBox_Extension_Pack-5.1.6-110634.vbox-extpack and uninstall the 5.1.8 version.
you need to uninstall the 5.1.8 version first than install the one above. :)
Ok and let see what @bradp has to say for issues like this. It would be great if he could come here and guide us with a better solutions.
yeah but just to point out that vv is based on vvv and vvv uses vagrant to do all the work. in other words, vv just extends the feature to allow users to create multiple sites since vvv does not do that.
Since I have a blank database and all the files setting ready in the folder for example test.dev(created during vv create), can we create htdocs folder inside test.dev ourselves and put the latest WordPress files in there and install manually? Is it something we could do when vv create doesn't create htdocs folder?
vv creates everything for you such as creating the folder, adds htdocs, installs WordPress, installs database and creates username and password for database and adds the test.dev to the hosts file that's about it.
No no
What vv creates (example testsite.dev)
- testsite folder in www
- vvv-hosts, vvv-init, wp-cli inside testsite folder
- Create file testsite.conf inside nginx-config/sites/
- Empty database name testsite in phpmyadmin
What vv doesn't create
- htdocs folder inside testsite
How can we install the WordPress manually in the scenario as above.
You could hook in the vv process and install wp manually with a shell script.
But thats not the solution to this problem.
Yeah it is not a right solution but we can follow it until the @bradp help us fix the issue.
BTW how to run the shell script could you please guide me, actually I'm fed up installing the VVV and VV again and again. Im doing this since last Friday and have no more patience or time to work on it.
I think there is a issue with provision.sh
==> default: PHPMyAdmin already installed.
==> default: Network connection detected...
==> default: This is where the site gets created but it doesn't happen instead it remains blank
==> default: This is where the site gets created but it doesn't happen instead it remains blank
==> default: Cleaning the virtual machine's /etc/hosts file...
I dont understand why the VVV doesn't execute the code when it reach the above break point. If it gets fixed then there would no issue.
can anyone help to fix it
Right now i have no time to look at this further.
But you can do it totally manually until brad or someone else can fix this here.
Just create the htdocs folder and pull in wordpress. You just need to do the normal WP setup process. So fill in db credentials and install it. DB and nginx config should be installed right via vv create.
@VWinDev Download vvv 1.3.0
sorry if that didn't work, I've done a lot of testing and I guess it doesn't work for some people. I agree with @Kyaviger try downloading vvv 1.3.0.
Make sure that you have Microsoft Visual C++ 2008 - 2010, 2013, 2014, 2015 just in case, sometimes these make a lot of difference.
After running vv create and no htdocs folder created, I got mine to work by running the script vvv-init.sh from the vagrant server:
cd dev/vagrant-local # Use location of vagrant-local on your machine
vagrant ssh
cd /srv/www/Your-Site-Name
./vvv-init.sh
VirtualBox 5.1.8
Vagrant 1.8.7
VVV 1.4.0
VV 1.12
The tip by @sdulaney is really working. Thanks!
So after I did a lot of testing, trying to figure out what's going on, I finalized the proper sequence and software that are needed, one of them that I install is
- VirtualBox 5.1.6
- Vagrant 1.8.5
- VVV 1.4.0
- vv 1.12
everything works now if you do use this way.. vv create will also run vvv-init.sh by default. I just tested. I also tested @sdulaney way as well, that works too. but like i said, sometimes newer versions may cause problems. Hope everyone is getting better solution and better outcome :)
Thanks @sdulaney you just saved me a lot of time!
sorry @benlumia007 for the thumb down, even if using your same versions still have this issue and the only solution is a manual init like @sdulaney said.
@AdamQuadmon yeah, but i guess like what i said before, it only works if it lets you or finding different solution like what @sdulaney did make sense, but i think there's no root cause because, i have like one mac and 3 pc, but 3 o fmy pc have different configurations so, as long as it works for me, i'm not going to touch it.
ahh so another working scenario which doesn't make no sense to me, I had Visual Studio 2015 installed and it seems like it doesn't work well when i try to use VVV for the first time, but when i did clean install especially the Windows 10, without Visual Studio 2015, and i downloaded the latest software as below. everything works.
VirtualBox 5.1.10
Vagrant 1.9.0
VVV 1.4.0
vvv 1.12
and it works fine... sigh.
Fixed in #326 after reading Varying-Vagrant-Vagrants/VVV#980, lots of cool new VVV features explained there 👍
Just to throw out here, I believe the box also makes a difference too. when you vagrant up for the first time. it downloads a certain box for it. from what i know which one works well is the 20161121.0.0. with the latest software
VirtualBox 5.1.10
Vagrant 1.9.0
VVVV 1.4.0
VV 1.12
Because it hasn’t explicitly been said, the default vvv branch is develop, and switching it to master resolves this error. If you prefer to stay on the develop branch, @sdulaney’s method is the best workaround.
cd path/to/your/vagrant-local
vagrant ssh
cd /srv/www/your-site
./vvv-init.shI’m sorry I don’t yet understand all the changes coming to vvv, but those changes are in the develop branch, and are the cause of these issues with vv. The changes almost seem to replicate functionality in vv, only in a very different way (through git repos?). I’m interested to know; are they intended to replace functionality we currently get from vv, or is vv intending to work using their new methods? Both?