Level 3
I recently had the same error and found out that the route that was being called actually was a closure (and not a method in a controller class). Seems like Vapor does not like those.
7 likes
Nov 16, 2020
3
Level 3
Opis\Closure\SecurityException on Laravel Vapor
Hi, I'm running for the first time a project in Laravel Vapor. After the deploy the application return an error 500. When I go to the logs section I see this error appear:
Opis\Closure\SecurityException
Your serialized closure might have been modified and it's unsafe to be unserialized. Make sure you use the same security provider, with the same settings, both for serialization and unserialization.
/var/task/vendor/opis/closure/src/SerializableClosure.php:213
Any hint?
Level 3
So, I've had this same error message occur twice on recent projects I was working on. There's not much on Laracasts or elsewhere about it. What I found to be the quickest way to resolve it was to completely remove the project folder and get a fresh copy from source control. After that, I was able to deploy to vapor again with no problems.
Level 2
I have had this a few times on various projects but it is definitely vapor not liking route closure, so all my routes are actioned in a controller.
1 like
Please or to participate in this conversation.