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

More servers login issue #139

Open
JiriVanek opened this issue May 20, 2019 · 3 comments
Open

More servers login issue #139

JiriVanek opened this issue May 20, 2019 · 3 comments

Comments

@JiriVanek
Copy link
Collaborator

With the new version of WinGIN, when one of the configured servers is unavailable, the application displays error (erŕor 503 Service Unavailable) and shutdown during app startup. even though other servers are up and running

@achilleas-k
Copy link
Member

Before we close this issue, a small question about #140.

Currently if the public GIN server isn't available (for some reason) but a local instance is, it will still fail to start, right? I'm thinking maybe we can just show warnings for unavailable configured servers, regardless of which kind they are. A potential scenario is a lab environment with a local instance but no access to public GIN (or public GIN is down for maintenance).

@JiriVanek
Copy link
Collaborator Author

Yes, the Gnode Gin server is mandatory. Also the offline use of wingin is impossible. I am not sure how to handle state when in cofiguration are several servers but some of them are offline. Maybe i will just check online status of default server and if default server is offline or unavailable I will show user the form with option to switch default server. Could that be solution?

@achilleas-k
Copy link
Member

Yeah, I like that idea.

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

2 participants