I've been using Laravel for a while, have gone through a few projects, and never experienced this:
Suddenly my application was having TokenMismatchException and creating new sessions between requests.
After hours of searching for a solution, and tried every session driver i tried to use XAMPP instead of Laravel's built-in server.
php artisan serve / http://localhost:8000
with XAMPP:
http://localhost/myproject/public
And then the CSRF persisted as well as the sessions, and every session driver started to work fine once again.
Strangest thing is, i tried to use php artisan serve again and the problem went away.
I thought i should stick to php artisan serve, but now i'm starting to guess.
Does anyone have a clue about this strange behavior? so we can save people from this headache. Thanks in advance
As a temporary workaround always open your browser in Incognito or Private mode when using php artisan serve
Related
I have been working in an application for month now.
But after running this command
php artisan optimize
I am stuck with the world of laravel cache,
I can't do or test anything locally unless I always have to
clear the cache then run optimize again and again.
sometimes it does work and other times it looks for old code which doesn't even exists. it has stopped my ability to work on and test my code.
I haven't tested my application on production server.
Run php artisan optimize:clear to undo it and don't run php artisan optimize in your local environment.
Only enable caches on your "live" environment and never locally while developing.
This will prevent any weirdness when developing and making sure you are looking at the effects of the code you just written instead of some cached code.
I've got a real head-scratcher for you! I've been working on a Laravel 5.4 application for quite some time now and up until yesterday I had been able to:
develop on my local machine [still works flawlessly],
push my changes to my BitBucket repo [still okay here],
and would subsequently pull those changes to my shared hosting server (RedHat) [still running smoothly],
I then run my dependency managers (npm and composer) to get the project in place and functional
there is some matter with clearing various caches:
php artisan view:clear
php artisan route:clear
php artisan cache:clear
composer dump-autoload
and finally move my '/public' folder to the web root and update index.php to point back to the 'bootstrap/autoload.php' in main project structure,
I am aware there is likely another or several steps I am missing, but I am unsure what they are...
All that being said, I've attempted to deploy a number of applications using Laravel lately and I always seem to run into the same issue come time to deploy an application to production. I've read 30+ tutorials on the matter and nothing seems to explain the issue why my site isn't working any more.
I've checked the error log file maintained by Apache, it's empty.
Was wondering if it's a permissions issue, doesn't seem to be the case (all folders set to 775 and files set to 664 as specified by various sources and owned by serverName:userName)
Browser console simply shows a 500 server error.
All I see if "Whoops, looks like something went wrong." twice.
There must be some way to show better error details (config debug setting already set to true)
Any suggestions at this point would be beneficial to send me looking in the right direction!
======= UPDATES =======
For the sake of thoroughness, and that this save others from severe headaches, I'll be posting actions taken here.
Following tutorial mentioned by #user123456 (permissions applies)
Generate new key for application
Run php artisan config:clear
Off to the races, answer to come!
You need to ensure you have a working .env file.
Once done, run php artisan key:generate to create a key for your application after which you should clear your application's cache as follows php artisan config:clear
I would never recommend using shared hosting for Laravel application. You will face lots of issues for permissions, composer and external dependencies. Instead, you can use cloud servers like DigitalOcean, Linode, vultr and deploy laravel application on them. If you don't know about linux and creating Stacks you can use Cloudways to deploy laravel.
https://dev.to/rizwan_saquib/deploy-laravel-application-on-cloud-easily-with-cloudways
I'm using Laravel 5.4 on Windows 7 and Xampp 3.2.2. A few days ago Laravel started ignoring the changes I was making to the .env file. I couldn't find the solution so I reinstalled Laravel in a different directory and imported my app folder.
Now Laravel just stopped responding to the changes I am making to some PHP files. I added a function to the /vendor/illuminate/support/helpers.php but I could not access it in the view. I deleted the content of the whole file and I could still access the function previously declared in it.
I created a helpers file as instructed here but that too is being ignored.
Any changes to any views is immediately effected and php artisan cache:clear is not doing anything.
How is this happening? Does it even make sense?
Laravel caches config values to improve performance.
You need to run either (recommended)
php artisan config:cache
which will cache the new values you have, or
php artisan config:clear
which will turn off caching. I've had some experience with this causing errors though.
I know it might sound rather stupid, but have you remembered to restart the server because you've edited the .env file?
I have deployed a website made with Laravel to my server. I have changed all the configurations but when I run it on browser, it gives me PDO error.
I figured out that Laravel configuration has not been changed even though I have.
It was certain that laravel was caching my old db configurations, so
I tried
php artisan:cache clear
But it didn't work.
Anyone has a solution?
php artisan config:clear for Remove the configuration cache file
I am developing an application in Laravel 4 using the built-in development server with a SQLite database. After a recent merge from another user in the project repository, the server will crash after certain requests.
I believe I have narrowed it down to a call of Sentry - when it is used on a request the server will crash out and the command line will exit.
$ php artisan serve
Laravel development server started on http://localhost:8000
Dwight at Dwights-MacBook-Pro.local ~/Sites/tmtbl on master*
$
As you can see, there are no error notices.
I've run composer update and ensured that Sentry is still installed correctly. I'm not sure whether this issue is Sentry specific or something else is going on. Is there something I am missing here that is causing the server to crash?
Do you use Chrome? If yes, go to the console and if you have an error, is it the same as: Failed to load resource when using Auth? Because I have the same problem with the php 5.4 server
You can use the Google Chrome browser to see the errors in the console.
Process
First run: php artisan config:cache
Second run: php artisan serve
Finally: go to your localhost and inspect your page, and then go to the console in the upper tab, you might be able to see the error.
Image of console:
Moreover, you can try:
composer dump-autoload