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

Present meaningful message to user when backend is unreachable #1785

Open
grzanka opened this issue Oct 17, 2024 · 1 comment
Open

Present meaningful message to user when backend is unreachable #1785

grzanka opened this issue Oct 17, 2024 · 1 comment

Comments

@grzanka
Copy link
Contributor

grzanka commented Oct 17, 2024

I've tried to check what happens if frontend it working, but backend is dead and users tries to login via plgrid on yap-dev.
The message to the user is meaningless in that case. See movie below

Screencast.from.2024-10-17.15-42-12.webm
@grzanka grzanka changed the title Present meaningful message to user when backend is dead Present meaningful message to user when backend is unreachable Nov 15, 2024
@grzanka
Copy link
Contributor Author

grzanka commented Nov 15, 2024

Backend can be unreachable for couple of reasons: it can be dead or connection can be blocked by firewall.
We saw today second reason. User could reach https://yaptide.c3.plgrid.pl/ and use the UI, when logging via plgrid user got redirected to keycloak. Unfortunately later got a following error:
Zrzut ekranu 2024-11-15 181748

After some inspection we realized that user was using "Guest WiFi" network in IFJ PAN. In this network also an attempt to connect to https://yaptide.c3.plgrid.pl:8443/ (this endpoint returns hello world and doesn't require authentication) failed.

I suggest to add much clearer indication whether backend is reachable or not. If backend is not reachable it doesn't make sense to let the user through logging process.

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

No branches or pull requests

1 participant