Open David-Lor opened 1 year ago
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). I add auth. providers, I restart but still the same.
When I check the auth providers I get:
[{"name":"Home Assistant Local","id":null,"type":"homeassistant"}]
Thanks in advance for any help !
Chrisbati
My YAML config:
`# Loads default set of integrations. Do not remove. default_config:
homeassistant: auth_providers:
'# Load frontend themes from the themes folder frontend: themes: !include_dir_merge_named themes
http: ssl_certificate: /ssl/fullchain.pem ssl_key: /ssl/privkey.pem
automation: !include automations.yaml script: !include scripts.yaml scene: !include scenes.yaml
media_player:
Hi All, i have identified issue, this URL login does not work with SSL_certificate/SSL_key if you remove it will work again. I do not want to use open text, but would love to use this app, is there any workaround to make SSL works ?
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 (https://github.com/iprodanovbg/homeassistant-desktop/issues/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?