@kapa.ai Our on-premise airbyte is throwing Sorry, something went wrong. Minified React error #185; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

This specific UI error (

Minified React error #185

) is mentioned in the knowledge sources only as a symptom: it appears in the Airbyte UI after leaving the connection page idle for some time on an OSS / Helm deployment. [React 185 UI] However, the linked issue was marked stale and closed without a documented root cause or fix, and there is no official troubleshooting guidance for this React error in the docs. [React 185 UI] Because of that, the knowledge sources do not provide a confirmed resolution path. Given what is documented, here’s what you can concretely do next: 1. Confirm it’s only the UI failing ◦ Check whether syncs are still running and whether you can see job history and logs. [Browsing logs] ◦ If jobs are running fine and only the UI crashes, it’s likely a frontend-only issue (as in the referenced GitHub issue). 2. Check logs for related backend errors ◦ From the Airbyte UI (if you can still access it on some pages), go to a connection’s Job History and open View logs for a recent job. [Browsing logs] ◦ If the UI is unusable, use your deployment’s logs (Docker / Kubernetes) to confirm whether the

airbyte-server

or webapp containers are throwing errors at the same time as the React 185 message. 3. Try basic UI-side workarounds The GitHub issue suggests this appears after the page is idle for some time; there is no documented fix, but you can: ◦ Hard-refresh the browser and/or try another browser. [UI crash e undefined] ◦ If you recently upgraded Airbyte, note the version you’re on and whether the error started after that upgrade. 4. If the problem persists, open an issue Since there is no documented fix in the knowledge sources, the next step is to report it upstream with: ◦ Airbyte version and edition (OSS / Enterprise) ◦ Deployment method (Docker, Kubernetes/Helm, etc.) ◦ Exact URL where the error appears (e.g., connection page) ◦ Whether it happens only after being idle, or also immediately on load ◦ Any correlated backend log errors (HTTP 500s, 404s, etc.) Similar UI issues have been escalated this way for investigation. [HTTP 500 UI issue; React 185 UI] Because the sources don’t document a concrete fix for React error 185, I can’t reliably tell you more than the steps above. If you share your Airbyte version and deployment method, I can help you shape a minimal, precise bug report based on the patterns in the linked issues. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.