mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-15 21:03:58 -05:00
UI not loading - Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'goto') #349
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @GanizaniSitara on GitHub (Feb 24, 2024).
Bug Report
Description
Bug Summary:
UI not loading staying with blank white screen.
Steps to Reproduce:
Install on Win10 standalone - Python 3.10.13, Node 18.16+
Expected Behavior:
Open WebUI starts.
Actual Behavior:
Blank screen. Error in Browser console
Uncaught (in promies) TypeError: Cannot read properties of undefined (reading 'goto')Environment
Reproduction Details
Confirmation:
Logs and Screenshots
Browser Console Logs:

Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
Manual installation. I have two machines one personal and one on corporate network. Identical configuration (Python versions, Node versions, Node package versions). Ollama validated running and reachable on both.
Personal one works, corporate has the issue described here. Corporate has limited internet connectivity. However transformers have been installed, tested.
Additional Information
Appears to be a SvelteKit promise issue as describe here
https://stackoverflow.com/questions/72186150/why-do-i-get-error-uncaught-in-promise-typeerror-firstnamef-is-null
and here
https://svelte.dev/repl/2b95425c5aec4389bd484cf40a3fd1e5?version=3.48.0
We're failing on the second "await K("/auth")line here, I've never run uvicorn with non-minified debug, would be happy for a pointer to try and learn more.
304's in console I don't see on the personal machine (all 200's there), but possibly unrelated(?).
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
@tjbck commented on GitHub (Feb 26, 2024):
Unable to reproduce at all with node v20, if anyone manages to reliably reproduce the issue please let us know!
@GanizaniSitara commented on GitHub (Feb 26, 2024):
Thank you, testing now repeated with v21.6.2, same result, will keep digging. Likely to be something to do with our corporate machine configuration, though am struggling to think what ...