Join 40 million developers who use GitHub
issues to help identify, assign, and keep track of the features and
bug fixes your projects need.
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?
to your account
v6 is throwing 404 errors on my production env, but localhost works fine.
Downgraded to v5.1 working again?
No idea why that would happen. You would have to debug it.
I was facing the same error. run php artisan module:v6:migrate after laravel upgrade
I ran the migrate command, made no difference.
Same docker environment, local and production, only difference is the I'm going through a proxy on AWS end. Any ideas @nWidart where to start the stack debug back to that?
#836 This could be related to this issue also, Vapor doesn't seem to be the issue.
This is just a standard docker containerised application also.
if you upgrade from 5.x, update your config also.
laravel-modules has new config for activator
I got same error before, update config and it's working, remember clean config cache
The same issue happens even if i use laravel 5.8
Checked, nothing to do with the cache/configs. Clean install same issue.
Somehow the new installation works fine but it only happens when it is used on another machine with git. Now the same issue keeps happening on all the Laravel versions > 5.6