# Internal Server Error in IFS Cloud: How to Diagnose It > Source: https://netray.co/erp-help/internal-server-error-ifs-cloud > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer An internal server error (HTTP 500) in IFS Cloud means a request reached the middleware but something behind it failed: a projection, a PL/SQL call, the database, or a pod that was restarting. The fastest route is to capture the failing request in the browser, read the error body, then match it to the middleware and database logs. ## Kind error ## System ifs ## Erp IFS Cloud ## Module Platform / Aurena / Projection ## Query internal server error ifs cloud ## Alternate Queries - ifs cloud 500 internal server error aurena - ifs cloud projection returns 500 - ifs cloud something went wrong server error ## Applies To IFS Cloud (Aurena client, OData projections) on IFS Managed Cloud, customer-hosted Kubernetes/OpenShift and on-prem installs. Log access differs by hosting model. ## Steps ### How to diagnose an IFS Cloud internal server error **Items:** Reproduce the error with the browser developer tools open (Network tab) and note the failing URL, HTTP status and the response body. Aurena pages call projections under /main/ifsapplications/projection/v1/. Read the response body. Application errors normally return a JSON error with a message from the PL/SQL layer; a bare 500 or an HTML page points to infrastructure rather than business logic. Decide the scope: one user, one page, one projection, or everything. If every page fails, check platform health first (pods, database, ingress) before touching application data. Self-hosted: check that the middleware pods are Running and not in CrashLoopBackOff or OOMKilled, then read their logs around the timestamp of the error. Look for an ORA- error in the logs. A package state error, an invalid object after an upgrade or deployment, or a locked or missing row is the most common root cause. Check for invalid database objects and recent deployments or customisation (custom fields, event actions, projections extended with a customisation) that touch the failing page. Test the same record or call as another user. If it works, the problem is permission-set or user data specific, not the platform. If you cannot see the logs (managed cloud), raise a support case with the URL, UTC timestamp, user, projection name and full response body. ## Sections ### Where the 500 can come from **Body:** An IFS Cloud request passes through the ingress, the identity layer, the client or projection middleware, and finally the Oracle database where the business logic lives in PL/SQL. A 500 can be raised at any of those layers, which is why the response body matters more than the status code. Business errors that the logic layer raises on purpose are usually returned as readable messages, sometimes with a 400-class status. A true 500 tends to mean an unhandled exception, a timeout, an unavailable dependency or a defect. ### Typical causes in practice **Body:** After an upgrade or deployment, invalid database objects or a mismatch between the deployed client and the deployed middleware produce errors on pages that worked yesterday. Compare behaviour across pages: if only pages that use one component fail, suspect that component's deployment. Customisations are the next suspect. A custom event action, a custom field with bad configuration, or a Lobby information source with a broken query can fail only for certain users or data. Disable the customisation in a test environment and retry to confirm. Resource problems appear as intermittent 500s or 502/504 on long operations. Large exports, heavy reports and slow queries hit timeouts, and pods under memory pressure get restarted mid-request. ### What to collect before escalating **Body:** A useful support case contains the exact URL, the UTC time, the user, the IFS Cloud version and update, the response body and any trace or request identifier shown in the error. Add whether it reproduces for other users and whether anything was deployed or changed recently. Do not paste tokens or session cookies into tickets. Redact the Authorization header from any HAR file you attach. **Code:** # Self-hosted Kubernetes: find and read the pods (names vary by release) kubectl get pods -n kubectl logs -n --since=30m | grep -i -E "error|ORA-|exception" ## Pitfalls - Restarting everything before capturing logs destroys the evidence you need to find the real cause. - Assuming the platform is at fault when a recent customisation touches the failing page. - Testing only as an administrator; permission-set issues and user-specific data issues will not show up. - Treating a timeout on a heavy report as an application bug instead of a query or resource problem. - Sending support a screenshot of the error banner only, without the response body and timestamp. ## Ai Angle An assistant grounded in IFS Cloud logs and documentation can take the pasted response body, extract the ORA- code, projection name and timestamp, and propose the matching log lines and likely cause, so the first triage takes minutes. Netray runs this kind of assistant on private models next to the IFS installation, so logs and data never leave your network. It is a triage aid, not a replacement for IFS support on defects. ## Faq ### Does an HTTP 500 in IFS Cloud always mean a bug? **Answer:** No. It means an unhandled failure somewhere behind the request. Causes include a bad customisation, invalid database objects after a deployment, a timeout, or resource pressure on the middleware. Read the response body and logs before deciding whether it is a defect. ### Where are the IFS Cloud logs? **Answer:** On self-hosted Kubernetes or OpenShift, the logs are in the middleware pod logs and the Oracle alert and trace files. On IFS Managed Cloud you typically do not have direct access and request them through support. ### Why does the error only happen for one user? **Answer:** Usually a permission-set difference, a user-specific default, or data that only that user touches. Reproduce as another user on the same record to separate user issues from platform issues. ### Can a customisation cause an internal server error? **Answer:** Yes. Event actions, custom fields, custom projections and information sources all run code or queries in the request path. Disable the customisation in a test environment and retry. ## Search terms internal server error ifs cloud, ifs cloud 500 error, ifs aurena server error, ifs projection 500, ifs cloud logs, ifs cloud troubleshooting, ifs ora error, ifs managed cloud support --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json