-
Notifications
You must be signed in to change notification settings - Fork 50
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
Submit button when entering instance URL is not functional #26
Comments
Same problem here |
The problem in my case is, that I enabled login without password (allow_bypass_login: true) see here and therefore the login URL is not "/auth/providers" but "/auth/authorize". |
In version 1.4.11 the login with these settings works fine. |
Yeah that was the problem. I added the default auth provider and now also 1.5.3 is working for me: auth_providers: |
Hello, I have the same issue, "Submit" bouton is greyed out and I cannot click (on windows 10). When I check the auth providers I get:
Thanks in advance for any help ! Chrisbati My YAML config: `# Loads default set of integrations. Do not remove. homeassistant: '# Load frontend themes from the themes folder http: automation: !include automations.yaml media_player:
|
Hi All, |
I'm trying the app v1.5.3 running the AppImage from the Linux x86_64; my HomeAssistant instance is version 2023.3.1. Right-clicked the icon on the toolbar, clicked "Add another instance" or "Show window", and on the window where the HA instance URL is entered, the Submit button is greyed out, no matter which URL I enter (even the example one). Pressing Enter doesn't work.
Logs when executing the appimage from terminal:
EDIT: Found a similar issue (#19) but in my case the auth provider seems to be the correct one:
Maybe it has something to do with the selfsigned certificate I'm using? On the example picture above I've tried typing the example URL, but my HA instance is actually running in the address shown in the curl command above, served behind an nginx reverse proxy with selfsigned certs, not added to the OS. Seeing the #19 issue I'm now assuming the app tries to connect to the server while typing, and the Submit button is only enabled once the connection with the instance can be successfully established?
The text was updated successfully, but these errors were encountered: