Polisy/5.5.5 , Today suddenly when I attempt login to AC using the http link in IoX Finder, my user/password will not authenticate (I tried admin/admin and that was not working either). This happened every time I tried over the course of about 15 minutes. When I tried the https link in IoX Finder, authentication worked correctly.

Given all the other churn going on with ZMatter, and eisy, I thought I would mention this in a form post, in the hope it helps someone else. I'm not going to open a ticket at this point, as there are so many other more pressing issues at the moment.

I just tried mine and all I have in my finder here at work is http which I added manually and works.

Try removing it and re-adding https manually and see what happens.

 

 

 

For me, the IoX finder finds my eisy on my network automatically using https on port 8443. 

2 hours ago, wmcneil said:

Polisy/5.5.5 , Today suddenly when I attempt login to AC using the http link in IoX Finder, my user/password will not authenticate

I've seen this happen several times, especially after rebooting. Http takes a while to work, but https works right away.

It might even be related to some of the errors in my error log related to Home Assistant.

Edited February 7, 20232 yr by stevesreed

1 hour ago, stevesreed said:

I've seen this happen several times, especially after rebooting. Http takes a while to work, but https works right away.

It might even be related to some of the errors in my error log related to Home Assistant.

I had done a reboot not too long before I was trying to authenticate, so that could be a strong hint.

On 2/7/2023 at 1:09 PM, stevesreed said:

I've seen this happen several times, especially after rebooting. Http takes a while to work, but https works right away.

It might even be related to some of the errors in my error log related to Home Assistant.

Not sure how that is even possible really. Both ports HTTP (80) and HTTPS (443) run from the main HTTP Server. You literally can't have SSL without a non-SSL server entity for a working web server. Any sever that enforces HTTPS is actually using .htaccess and 301 Redirects to the HTTPS version either by page headers or DNS Redirect.

 So why the secure site loads before the non-secure site is mind boggling to me.


TRI0N