Why does my Laravel app 500 across every page right after deploy with a vague service/translator error? #40
Answered
by
Kevinchamplin
Kevinchamplin
asked this question in
Q&A
-
|
Why does my Laravel app 500 across every page right after deploy with a vague service/translator error? |
Beta Was this translation helpful? Give feedback.
Answered by
Kevinchamplin
Jun 13, 2026
Replies: 1 comment
-
|
config:cache (often via |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
Kevinchamplin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
config:cache (often via
artisan optimize) bakes the entire config into one cached file. If anything it references is wrong at cache time — a path that no longer exists, a deleted directory, a bad env read — every request boots from that broken snapshot and 500s site-wide. Runphp artisan config:clear(and avoid blanketoptimizein fragile deploy setups; clear individual caches instead).