mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-10 23:55:15 -05:00
[GH-ISSUE #8104] Network problem behind reverse proxy #85740
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 @N4S4 on GitHub (Dec 26, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8104
Hello, thank you for the amazing repo.
I am having an issue since the 0.51 update,
If I access open-webui from local ip everything works as expected. While if i access it from remote behind reverse proxy and start a chat gives me "network problem" error. I can see the model is loaded and start inference but the answer is always the error.
Could someone help me?
Thank you
@galvanoid commented on GitHub (Dec 26, 2024):
Same issue here.
Thx.
UPDATE:
Fix it in my Synology reverse proxy:
@oldskewlcool commented on GitHub (Dec 26, 2024):
Also confirm this issue. Occurred in v0.5.0 and also still occurring on V0.5.1.
Using reverse proxy with custom header for auth (WEBUI_AUTH_TRUSTED_EMAIL_HEADER=X-User-Email) to avoid local network users needing to log in and nginx for the reverse proxy.
Install via docker and the combined openwebui / ollama image.
Occurs regardless of model used resulting in the installation being non-functional for querying models.
No issues prior to the upgrade to 0.5.0
Additional details that may be helpful:
Network debug show NS_ERROR_WEBSOCKET_CONNECT when trying to GET ws://192.168.1.110/ws/socket.io/?EIO=4&transport=websocket
The connection to ws://192.168.1.110/ws/socket.io/?EIO=4&transport=websocket was interrupted while the page was loading.
@hasron commented on GitHub (Dec 26, 2024):
I solve the problem using information provided here:
https://github.com/open-webui/open-webui/issues/8074#issuecomment-2562061337
@N4S4 commented on GitHub (Dec 26, 2024):
this fix my issue too, I'll be clsing the issue as is a reverse proxy setup to be modified
@N4S4 commented on GitHub (Dec 26, 2024):
thank you for the support