Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

Scotalia's avatar

Cashier (11.2) Error in Live Laravel (6.16)

So i finally finished my MVP app and pushed the working files from my Local to Live server overnight. Super excited to wake up and see my site running only to be hit with a White Screen with no errors. :(

The only error i find is 'Symfony\Component\Debug\Exception\FatalErrorException: Trait 'Laravel\Cashier\Billable' not found in file /var/www/eurotripr.com/app/User.php on line 13' ( i found this in the Source tab of dev tools)

I have Cashier 11.2 running on Laravel 6.16. My local and live environments mirror each other in terms of OS and PHP versions. It worked flawlessly on Local, but i can't for the life of me figure out why it does not on Live. An alpha LIVE version was even working (without payments) yesterday with no issues.

User class definitiely is using Billable trait:

use Laravel\Cashier\Billable; // for STRIPE billings

class User extends Authenticatable implements MustVerifyEmail
{
    use Notifiable;
    use Billable; // for STRIPE billings

The Cashier folder is in Vendor/Laravel as needed.

I pushed all of my files up from my local to LIVE, edited my env accordingly for the stripe keys and environments et al. Imported my local DB to live server with a full overwrite. I generated a new Key for the laravel site when completed

I've spent a couple hours today already trying to troubleshoot, but most 'solutions' i find are for older versions and are several years old.

What I've tried (among things i may not remember): made sure my Storage dir has proper permissions (i set it to 777) php artisan key:generate (to generate a new key for live) composer dump-autoload cleared caches chmod public/index.php to -755 removed bootstrap/cache/services.php removed bootstrap/cache/packages.php php artisan cache:clear php artisan route:clear php artisan config:clear php artisan view: clear

It's probably something super small and stupid but at this time i can not figure it out and the more i 'panic' the less i figure out :/

Any help would be greatly appreciated...if you'd like to see any of my code, let me know.

Thanks!!!

0 likes
1 reply
Scotalia's avatar
Scotalia
OP
Best Answer
Level 7

SOLVED: my server was bombing out of memory. I am not certain why my server could not allocate sufficient memory yet, BUT i finally noticed that my Laravel versions were SLIGHTLY out of sync (local: 6.18.13, live: 6.12.??). I attempted

composer update

but received this error:

mmap() failed: [12] Cannot allocate memory

I had to stop Apache and MySQL services, THEN rerun composer update, THEN restart Apache and MySQL. Composer updated to 6.18.14 and the site is working again!

Next task: increase memory or optimize the site/server.

1 like

Please or to participate in this conversation.