"Oops! We ran into some problems": find the real error
That message hides the real error from visitors. Here is where XenForo keeps the details, and what to send us so we can fix it fast.
Updated 4 min read By the D.C Style team
On this page
Oops! We ran into some problems. is XenForo's polite way of saying "something failed, and I am not going to show the details to a visitor". The details are not lost. XenForo records every error in the server error log, with the exact message and where in the code it happened. Five minutes there usually tells you which add-on is involved and what went wrong.
Two versions of the message
- Oops! We ran into some problems. on a full page means the error happened on the server while building the page. The details are in the server error log.
- Oops! We ran into some problems. Please try again later. More error details may be in the browser console. usually appears in a pop-up after you click a button or submit a form. The request behind the button failed. Check the server error log first, then your browser console. How to open the browser console.
Read the server error log
- In the Admin CP, open Logs > Server error log. The newest errors are at the top.
- Find the entry from the moment you saw the error. If you are not sure, reproduce the error, then reload the log. The new entry is the one at the top.
- Click it. The page shows the error message, a Stack trace and the Request state, which includes the page address and the member who hit it.
You do not need to understand PHP to use this. Two parts matter:
- The first line: the error message itself, such as a missing table, a missing class or a database error.
- The file paths in the stack trace: a path such as
src/addons/DC/Thumbnail/…tells you which add-on the error came from. Paths starting withsrc/XF/are XenForo itself, which is often called by an add-on further down the trace.
Tip: Once you have fixed a problem, click Clear to empty the log. Next time, anything in it is new, and you will not have to wonder whether an entry is from last month.
What the common errors mean
| You see | It usually means |
|---|---|
| A table or column "doesn't exist" | An install or upgrade did not finish. Run the upgrade again, from the command line if it timed out. Command line guide. |
| A class or file "not found" | Files are missing or from different versions. Upload the add-on again and run the file health check. |
| An error inside a template | Often a style's customized template clashing with an add-on. See Template modification errors. |
| Memory or time limit exceeded | The task was too big for your server's PHP limits. Run it from the command line, or ask your host to raise the limits. |
When the log is empty
XenForo can only log an error if it gets far enough to start. If the whole site shows a blank page, a bare "500" error, or a message that is not XenForo's own, the problem happened before XenForo could record it. Two common causes:
- A PHP version that is too old for an add-on. For example, Google Drive Attachments needs PHP 8.1 or newer, and on older PHP every page shows Composer detected issues in your platform.
- An add-on error so early that the Admin CP will not open either.
In both cases, follow Site down after installing an add-on? Your host's PHP error log will have the details too. Your hosting control panel usually shows it, or your host can send it.
What to send us
When the error involves one of our add-ons, a ticket with the right details usually gets solved in one reply. Include:
- The full error message from the server error log, plus the first ten or so lines of the stack trace.
- What you were doing when it happened, and the page address from Request state.
- Your XenForo version, PHP version and the add-on version. Where to find them.
Still stuck? Open a support ticket with those details and we will take it from there. More tips are in Get help fast.