Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: give an error when the websocket uri is not accessible #2545

Open
macau23 opened this issue Nov 15, 2024 · 0 comments
Open

Feature: give an error when the websocket uri is not accessible #2545

macau23 opened this issue Nov 15, 2024 · 0 comments
Labels

Comments

@macau23
Copy link

macau23 commented Nov 15, 2024

Related to

Web-Frontend (what users interact with)

Impact

better user experience

Missing Feature

If the reverse proxy is misconfigured and /ws/ is not working (e.g. missing port 3000), an error in the gui would be nice.
Currently semaphore appears to be working but does not because of lack of feedback (but actually is working if you refresh)

Implementation

Show an error in the gui

Design

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant