React Router crash on login with Chrome/Chromium based browsers - tRPC file operation error

[mikexkllr]

Title

React Router crash on login with Chrome/Chromium browsers - tRPC file operation error

Does not occur in Firefox or Safari

Description

When logging into Umbrel OS using Google Chrome or any Chromium-based browser, the application crashes immediately after successful authentication. The error appears to be related to a tRPC client subscription failure on the files:operation-progress event bus, which triggers cascading React Router render errors.

Steps to Reproduce

1. Access Umbrel instance in Google Chrome or Chromium-based browser (e.g., Edge, Brave, Vivaldi)
2. Login with valid credentials
3. Application crashes and displays blank/error state

Expected Behavior

After successful login, the user should be able to navigate the Umbrel dashboard without errors.

Actual Behavior

Multiple React Router render errors occur within seconds of login, preventing access to the dashboard.

Environment

• Browser: Google Chrome / Chromium-based browsers
• OS: Umbrel OS
• Access: umbrel.local
• Status: Reproducible immediately after login

Error Details

Initial Error:

eventBus.listen(files:operation-progress) subscription error
TRPCClientError

Cascading Errors:
Multiple React Router render errors triggered at timestamps:

• 18:57:15 GMT
• 18:57:22 GMT
• 18:57:30 GMT
• 18:57:37 GMT
• 18:57:44 GMT
• 18:57:51 GMT

Component Stack: Errors originate from the Io component with failures propagating through React Router and Suspense boundaries.

umbrel logs error chrome.json

[nmfretz]

Hey @mikexkllr thanks for reporting. I can't seem to recreate this. The subscription error you're seeing (eventBus.listen(files:operation-progress)) is logged but shouldn't cause the crash.

Can you please let me know the following:

1. what version of umbrelOS are you on
2. what specific browser and browser version are you accessing umbrel.local from
3. if you use the browser where you have issues, but open an incognito window does it still error or does it work? Potentially there is something funny happening with stale state or a browser extension.

[mikexkllr]

Hey @nmfretz ,

Thanks for reaching out. I appreciate you looking into this.
Here are my system details:

Browser: Google Chrome 143.0.7499.170 (Official Build, arm64)
OS: macOS 26.1 (25B78)
Client Device: M4
umbrelOS: Version 1.5 (Intel N100, 16GB RAM)

I've tried troubleshooting on my end—including testing in incognito mode—but the issue persists on my Mac. Interestingly, when I tested the same workflow on Chrome for Android, it worked without problems. On iOS it also worked with Chrome but I guess it's using WebKit instead of the real Chrome engine.

I really do appreciate umbrelOS. I'm daily driving it for several different tasks as an alternative to cloud solutions, and you've built something genuinely solid here.