Level 75
Check letter case, linux is case sensitive. And check storage permissions.
Jan 15, 2019
7
Level 2
Login works on local server but not on production [HELP]
Hi,
I am facing an odd issue. My school uses my website and so I want to get the login back up and running as soon as possible.
When I log in to my website locally, I successfully do so but on my production website, I get the following error below. I put debug = true for forge env for my site to see if any more descriptive text would appear but none. I am perplexed because I did not recently alter anything to my login flow so as to cause this issue. What's even weirder is I can successfully log in on my local server so I am thinking maybe the issue is isolated to me using digital ocean + forge stack.
Has anyone experienced this issue before or have any steps they suggest I take?
Also, I added a dd statement to the beginning of my login function in my LoginController and I don't believe the request hits that code.
Browser shows
This page isn’t working If the problem continues, contact the site owner.
HTTP ERROR 400
The console shows
Failed to load resource: the server responded with a status of 400 (Bad Request)
Level 2
@jlrdw Thank you for your response. Can you clarify? Where should I check the letter case? I use Laravel Forge to manage my Digital Ocean servers. I have not changed my server provisions since I first created them.
Level 75
You develop on linux, if so that's not the problem. If you develop on Windows, then check things like class names, etc.
Windows MyController = mycontroller
Linux MyController does not = mycontroller
Usually that's a 500 error.
Edit: If you changed something have you tried:
php artisan config:cache
php artisan config:clear
Even a server restart as last resort.
Level 67
Check the error log. /storage/logs/laravel.log as well as your nginx log.
Level 2
Hi,
I solved the issue the 400 request error issue. First, this article helped: https://airbrake.io/blog/http-errors/400-bad-request
One of the steps it suggested was "Uninstall New Extensions, Modules, or Plugins". I knew I had introduced the bug in the last 24 hours and I had installed a package for cors stuff specifically "Neomerx\Cors-illuminate" in that time period. So I took the file out of my composer.json, ran composer update, and tested on my prod website and the issue was resolved.
I am assuming there was a package conflict somewhere with the Laravel login.
Thanks for the help everyone. This one really snuck by me and has motivated me to invest into a robust testing suite so critical issues like these don't flow into production.
Level 75
Good to hear you got it.
1 like
Level 1
The 400 (Bad Request) status code indicates that the server cannot or will not process the request because the received syntax is invalid, nonsensical, or exceeds some limitation on what the server is willing to process. It means that the request itself has somehow incorrect or corrupted and the server couldn't understand it. The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method . Therefore, it prevents the website from being properly displayed. The main thing to understand is that the 400 Bad Request error is a client-side error. The cause of a 400 error can be a wrongly written URL or a URL that contains unrecognizable characters. Another cause of the error might be an invalid or expired cookie. Also, if you try to upload a file that's too large. If the server is programmed with a file size limit, then you might encounter a 400 error.
Please or to participate in this conversation.