Not sure then, you’ve tried running this on another Windows machine? I will try and update the app though it sounds as if it may be something else that I’m not sure how to fix, I can’t replicate it.
Yeah just tried it on my Windows 11 laptop and having the same issue - I was prompted to allow both public and private networks, which I did, and it still refuses to do anything at the login screen, other than detecting the Home Assistant address. The Submit button is greyed out. Same issue I’m having on my Windows 10 desktop. And it doesn’t work if I replace the domain with the local IP either.
Fair enough, I’m not sure really without digging into it myself on your system! I’ve read that some people have had connectivity issues when running on an RPi and their version of Etcher bugged out on them.
I’ve published a new release, see if that helps anything at all. The parameter for the greyed out submit button is a begins with "http" verification, so if you’re using the raw URL i.e. homeassistant.local:8123 then prefixing with the http may work - I’m sure you probably were. That’s the most obvious thing code-wise that I can see that would relate to it. The app is basically just a little web browser page so I can’t see many reasons why it wouldn’t connect if the URL is correct.
OK thanks - and what if the prefix is https?
Still not working with the new release, unfortunately.
Was worth a try! If the prefix is https that’s fine too, it’s what I use.
I’m afraid I don’t really know how to help you, if it works for myself and the others using it there must be something particular about your specific HA installation that it doesn’t like. I don’t really have any way to test your issue, I’ve tried it on HTTP via port, HTTPS with self-signed cert and HTTPS with valid cert, they all work. If you want to post a screenshot of what you see that might be useful, but it sounds fairly basic.
I would try setting up a brand new HA install from scratch (on a test device) and seeing if you can connect to that, it’s the only thing I can suggest. EDIT: You can try modifying the instance directly if you go to %appdata%/homeassistant-desktop and modify config.json like below, replacing the instance:
{
"autoUpdate": false,
"automaticSwitching": true,
"detachedMode": false,
"disableHover": true,
"stayOnTop": true,
"fullScreen": false,
"shortcutEnabled": true,
"shortcutFullscreenEnabled": false,
"allInstances": [
"https://yourinstance.local"
],
"windowSize": [
1278,
930
],
"currentInstance": 0,
"windowPosition": [
1283,
534
],
"windowSizeDetached": [
1274,
880
]
}
If that still doesn’t work with HTTPS or HTTP then I believe the issue is your HA instance itself.
Hmm, yeah, unfortunately modifying the config doesn’t work either - it still shows the same screen when the program starts up. Here’s what it looks like (excluding the button that shows my public domain at top):
OK, I’m now thinking, have you tried http like I’ve mentioned? I just assumed you had and we could rule out a certificate error, but have you only been trying https?
Same behavior - the Submit button is just always greyed out for some reason. Also I don’t think I can reach my instance via http.
Is it a self-signed cert?
Yes, I use Let’s Encrypt and Cloudflared. Using the native IP will give a cert error that can be bypassed in a browser but that sometimes doesn’t play nice with programs if they don’t let you ignore the cert error.
Hello again, a few things.
You say your cert is self-signed but that you use Let’s Encrypt - is it not signed by their authority? If you have a fully signed cert, you should be fine, you just need the requisite DNS. Tell your local DNS server (or local hosts file) that https://yourinstance.com is on 192.168.1.20 (or whatever your instance IP is). Serve your signed certificate on that internal address and it should be fine.
The nominal requirements here will be:
- Trusted certificate signed by Let’s Encrypt
- Certificate is presented to user on both internal and external IPs - using Nginx reverse Proxy is easiest
- Verify you can access https://yourinstance.com/auth/providers - this part is important as that’s what the app looks for to verify and enable the submit button
OR
If you are using a truly self-signed certificate (signed by your personal internal certificate authority), installing your Certificate Authority cert to your local Windows Certificate Store may help. Install it to Trusted Root CA > Certs (Local Computer) > Trusted Root CA which should pick up system-wide. You can also just install the singular self-signed cert if you don’t have a CA, believe it should also work.
I’m using a Cloudflare tunnel, and hadn’t thought of this earlier, but I can access the tunnel without secure html, so when I put in that URL it does actually work. It just won’t log in via the other methods that work for me in-browser. Appreciate all the help with this.
1 Like
Ah cool, I’m glad to hear it! If you fancy trying out a secure connection, the above things I’ve described should work for you.
Personally I have:
mydomain[.]com > resolves to home firewall >> NAT/forward << Nginx proxy > HASSIO instance
As long as the proxy serves your signed certificate (you can set and forget using one of the proxy companions or just certbot natively, up to you) on all interfaces then you’re good to go internal and external.
Just here to say thank you to former and current maintainers for this amazing app and for keeping it alive!
I did try to run appimage-latest on mint, but unsuccessfully. Anyone who have some knowledge about that can help me, will be great.