search

WordPress / meta-environment

A collection of scripts that provision the official WordPress.org websites into a Varying Vagrant Vagrants installation.
190 stars 69 forks source link

403 forbidden to wordpressorg.dev network sites #80

Open vineettalwar opened 8 years ago

vineettalwar commented 8 years ago

Issue is similar to #67 However, I was receiving 403 Forbidden on Wordpressorg.dev network sites. Workaround I did to be able to access is,


$ vagrant ssh
$ cd /srv/www/wordpress-meta-environment/wordpressorg.dev/public_html/wordpress
vagrant@vvv:/srv/www/wordpress-meta-environment/wordpressorg.dev/public_html/wordpress$ wp  core download
vagrant@vvv:/srv/www/wordpress-meta-environment/wordpressorg.dev/public_html/wordpress$rm -rf  wp-content/
iandunn commented 8 years ago

Hmmm, was the wordpress directory empty before you ran wp core download?

If you still have the provision log in your terminal backscroll, would you mind dumping it into a Gist and adding a link here?

vineettalwar commented 8 years ago

Yes, wordpress/ directory was empty before . Terminal was closed so nothing was in backscroll, But I have reproduced the error and here are the provision logs. https://gist.github.com/vineettalwar/8a4d4df71e1ba7fd16f2b4cc814c685a

vineettalwar commented 8 years ago

Found same issue with wordpresstv.dev as well. on $vagrant ssh vagrant@vvv:/srv/www/wordpress-meta-environment/wordpresstv.dev/public_html/wordpress$ this folder is found empty.

iandunn commented 8 years ago

Unfortunately that Gist just shows what's happening when the provisioner tries to update an existing site. What we need is to see what happens when it tries to create the site for the first time.

To do that, you'll need to:

...and then

vagrant provision

grappler commented 7 years ago

@iandunn What needs to be fixed here? I have created an issue so that we can see that new features get applied to existing installations #110