search

alexc7018 / vvv-site-wizard

Automates setting up new WordPress sites in Varying Vagrant Vagrants
GNU General Public License v2.0
347 stars 47 forks source link

403 Forbidden issues getting started #23

Closed amallory closed 9 years ago

amallory commented 9 years ago

Having trouble getting started with vvv-site-wizard. I'm getting this in the output from the --provision started after running the vvv-site-wizard script:

==> Creating database 'wswork' (if it does not exist)... ==> Installing WordPress (release version) in wswork/htdocs... ==> Warning: cURL error 7: Failed to connect to api.wordpress.org port 443: Connection timed out ==> Error: cURL error 7: Failed to connect to api.wordpress.org port 443: Connection timed out ==> Error: This does not seem to be a WordPress install. ==> Pass --path=path/to/wordpress or run wp core download. ==> Error: This does not seem to be a WordPress install. ==> Pass --path=path/to/wordpress or run wp core download.

and the directory /www/wswork contains: htdocs vvv-hosts vvv-init.sh wp-cli.yml

Here's the config info: "New VVV Site Setup Directory /Users/amallory/webdev/nhn/www/ already exists. Name of new site directory: wsworkforce Domain to use (leave blank for wsworkforce.dev): WordPress version to install (leave blank for release version): Load images from live site (y/n): n

About to perform the following:

Provisioning Vagrant will do the following:

Continue (y/n)? y

New VVV setup starting for site wswork" ....

So it looks like things aren't getting processed when the provision is run? Any idea why?

jacobdubail commented 9 years ago

Did you see if Issue 20 is related? https://github.com/aliso/vvv-site-wizard/issues/20

amallory commented 9 years ago

I saw #20 and I did have that issue initially but after removing the file I'm no longer experiencing that error.

Looking at the files that are created by the script it looks like they are not getting created in the correct place. They are all (vvv-hosts, vvv-init.sh, wp-cli.tml, and sample.conf) in the SAMPLE folder in the root folder of the vvv instance, instead of being in the www directory. I would have expected them to be inside of www (and for sample.conf to be in /config/nginx-config/sites) but they are not. I do see a message when running vvv that the www directory exists.

amallory commented 9 years ago

I have this working now. Unfortunately I don't know what was causing my trouble. I think there may be an issue with paths but I couldn't isolate it. I'll keep experimenting and if I come across it I'll open an issue.