You see "Something Went Wrong" (error 500)
A page or a save fails with Something Went Wrong and a reference such as ERR-8F2A1C94. Pass the reference on, and find the cause in the server's log.
- Applies to
- Core 12.7 and later
- Who can do this
- Platform owner, Administrator, Team member
On this page
Symptom
One of these:
-
A full page: 500 · Internal Server Error, Something Went Wrong, "An unexpected error occurred on our servers. We have logged this issue and our engineering team is investigating it." It shows a Reference, such as
ERR-8F2A1C94, with Copy reference. -
When you save a form: "The server could not complete the save. Nothing you typed has been lost — try again."
If you're not the one who runs Laramin
- Select Copy reference, if the page shows one.
- Note the time and what you were doing.
- Send both to your administrator, or raise a ticket. The reference lets them find this exact error.
Trying again once is fine. If the same thing fails again, wait for the fix.
Check these, in order
These are for whoever runs your Laramin.
1. Find the error in the log
The reference is written into the server's log next to the full error. Search the logs for it:
Couldn't copy. Select the code and press Ctrl+C (⌘+C on a Mac).
grep -r "ERR-8F2A1C94" /path/to/laramin/storage/logsReplace the highlighted values with your own.
The lines around it name the cause. The checks below are the most common ones.
2. Laramin can't write to its folders
Open Extra Utilities and look at Write Permissions. A red badge next to Storage, Cache or Public means Laramin can't write there.
Fix: whoever runs the server lets the web server's user write to storage and bootstrap/cache.
3. The code on the server is incomplete
The files were copied or updated without installing their dependencies or building the front end, so pages fail as soon as they load.
Fix: whoever runs the server installs the dependencies and builds the front end again, as described in Install Laramin from the command line.
4. A database change is waiting
After new code is put on the server, the database must be updated to match.
Fix: run the upgrade. See Run a system upgrade.
5. You need more detail
If the log isn't enough, a super admin can select Enable Developer Mode on Extra Utilities and repeat the action to see the full error on screen.
Danger: Developer mode can show anyone who sees an error page your configuration, including database passwords. Turn it on only while you reproduce the error, then select Disable Developer Mode straight away.
Only in the mobile app
If every app sign-in fails with error 500 and "Mobile authentication is not configured.", see Someone can't sign in to the mobile app. For other integrations, see An integration stopped working.
Still not working?
Raise a ticket from Support Center in your Laramin app. Include this page's link, the reference, the time, what you were doing, and the log lines around the reference with any passwords removed.
Thanks. That helps us decide what to write next.
Thanks for telling us what was missing.
You already answered for this article today. Thanks.
We got a lot of answers from your network just now. Try again in a few minutes.
We couldn't send that. Check your connection and try again.
Links in this article
Printed from help.laramin.in. The online article may have changed since.