-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error 404s new Laravel Setup + WP CLI Valet #15
Comments
This looks like an issue with Laravel Valet v2, not the wp command. There are a few known issues around 404s with WP using the new version. I would take a look at the issues over on the valet repo and see if any of those sound like what you're seeing. |
Yeah, OK. Well , setting domain once more, restarting and starting from scratch seems to have done the trick. All good now. Thanks! |
I know this issue is closed, but thought I'd drop a comment in case someone is struggling with this. After running |
@cdils Great tip. Should be added to readme @aaemnnosttv |
This is similar to #22. Valet supports "parked" directories, that is - a parent directory in which all children directories are considered sites in the same way as a "linked" site, automatically. This is a powerful feature which eliminates the need to do this automatically. There is some value in adding it as an option which is what that issue is requesting and it will likely be added in the future, I just haven't had a chance to do it. In the meantime, I'm happy to consider PRs for updates to the readme or properly implementing #22 as a feature. |
See aaemnnosttv#15 where we ran into 404 issues due to not having done a valet park in the directory the installation was done nor a `valet link`.
I have the new setup with Laravel - uninstalled all following instructions at https://laravel.com/docs/5.3/valet - with now NGINX running instead of Caddy. Nice upgrade by Valet.
wp valet works:
But I cannot load the site getting Valet 404s
Valet logs only show things from the day before:
nginx-error.log is empty:
Any ideas?
The text was updated successfully, but these errors were encountered: