THis is odd but by no means an urgent issue. Two machines both using wired ethernet on same LAN, both using Chrome browser. Mac works fine with eisy.local and numerical ip address. On PC eisy.local login fails --gets to password screen then redirects to eisy.clocal:3000 and eisy refuses to connect (according to chrome). Can log in on PC using ip address but on the system upgrade screen only three packages are listed-- eisy-ui, IoX, and UDX. This is with staging repo-- 1.4.3_1, 6.1.2_10, 5.0.0_7, PG3x 3.4.26, and mosquitto 2.0.18 . Rebooting eisy and restarting Chrome did not affect this behavior.

CORRECTION -- The part about the PC only displaying 3 packages is only partially correct. If I zoom out using the Chrome scren % tool, both the pc and the mac show seven packages. I had thought earlier there was a mechanism for scrolling but there isn't currently, or at least not that I can find. So the only difference between the PC and the MAC is that the PC can't access via eisy.local. the page needs a scroll bar for the packages or a format that shows all at once.

the eisy.local access problem seems likely to be solved by clearing a cache in chrome or by creating an equivalence in c:\Windowas\System32\drivers\etc\Hosts -- but it's not really something that needs fixing.

Edited October 13Oct 13 by stillwater

23 hours ago, stillwater said:

redirects to eisy.clocal:3000 and eisy refuses to connect (according to chrome).

Was this a typo - eisy.clocal:3000?

yes sorry eisy.local:3000 etc. 3000 was the port for PG3 when eisy (or polisy?) was first introduced so I am guessing there is something in the PC or Chrome cache that was doing this even though eisy was connecting and inviting login. eisy was accessible using the ip address. Some combination of clearing the chrome cache and setting up an alias in the Hosts file fixed the problem (I googled to find out how). I suspect that this was always an issue with my PC rather than with eisy.

On 10/14/2026 at 1:07 PM, stillwater said:

yes sorry eisy.local:3000 etc. 3000 was the port for PG3 when eisy (or polisy?) was first introduced so I am guessing there is something in the PC or Chrome

My Eisy still hosts PG3 on port 3000. I think UD eventually wants everyone to migrate their PG3 to the EisyUI, which I have already done.

EisyUI Plugins is still Beta and not fully developed so I find I have to go back to PG3 on port 3000 from time to time to check purchases. store etc.

Also my brother couldn't log into Eisy one day very randomly on his Mac. I figured out how to clear the cache for him and that fixed the problem. So there are some weird caching issues.