404's for Permalinks in local development about heroku-wp HOT 14 CLOSED

I'm seeing this too. It stems somehow from the configuration in this file:

support/vagrant/root/etc/nginx/sites-available/herokuwp.conf

from heroku-wp.

@xyu any thoughts on this? I'm getting this as well

from heroku-wp.

Something must have changed regarding the dependency versions in this project. The vagrant instance worked flawlessly for me in the same host environment around 2 months ago.

from heroku-wp.

same here. Anyone find a fix?

from heroku-wp.

I've not had time to investigate yet, and I'm unfamiliar with nginx which is where I suspect the problem lies.

from heroku-wp.

Nothing in the nginx error.log and in access.log I can just see the 404, no other info

192.168.50.1 - - [17/Apr/2015:11:16:50 +0000] "GET /best-design-resources HTTP/1.1" 404 49 "http://herokuwp.local/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.118 Safari/537.36"

from heroku-wp.

I suspect that this is due to some change in HHVM, I'll investigate this weekend.

from heroku-wp.

I see that HHVM was updated to version 3.6 in March, probably around the
time this started http://hhvm.com/blog/8849/hhvm-3-6-0

On Fri, 17 Apr 2015 at 14:50 Xiao Yu [email protected] wrote:

I suspect that this is due to some change in HHVM, I'll investigate this
weekend.

—
Reply to this email directly or view it on GitHub
#35 (comment).

from heroku-wp.

FWIW, Heroku is currently on HHVM 3.5.1 / Nginx 1.6.0 in case we find an incompatibility.

from heroku-wp.

Do we need to roll back the version of hhvm and update the composer.json to
3.5 locally too then? If there's no fix for 3.6 yet
On Sat, Apr 18, 2015 at 19:24 Xiao Yu [email protected] wrote:

FWIW, Heroku is currently on HHVM 3.5.1 / Nginx 1.6.0 in case we find an
incompatibility.

—
Reply to this email directly or view it on GitHub
#35 (comment).

from heroku-wp.

It appears this issue is currently being discussed here: facebook/hhvm#4986

It's not clear if this is considered an HHVM bug or configuration issue.

from heroku-wp.

I rolled back the version of HHVM to 3.5.1 and everything works again. This is definitely an issue with HHVM 3.6.

To fix it locally:
$ ssh vagrant
then instructions for rolling back here: https://gist.github.com/dmtintner/566e93ccccfb871774d0

from heroku-wp.

I changed the install.sh to do this automatically for now.

You can see the code in this pull request #40

from heroku-wp.

#40 was merged closing this issue.

from heroku-wp.