Also one badge on one location is working.
It is a lock badge that originally needed some extra configuration to make it work. I don’t recall what I did.
Accessing the server directly on my local network the badges are working.
So this is clearly an issue of proxy access but I haven’t changed any proxy configuration only updated the browser.
For what it is worth.
I have just tested chrome .117 on win 10 win 11 also server2019 (1909) using both a default reverse proxy of the nginx version on Linux build also hosting a linux build of openHAB (debian 12) openHAB version 4.2.2 using recommended openHAB config and also IIS reverse proxy with previously documented configurations and with and without certs and the locations tab and badges are all displaying fine for me.
So, this would appear to be localized to your configuration.
And as a fyi all my windows boxes are fully patched to current release patch levels as well.
That is not a surprise. Looking at the browser output you posted, something is interfering with API connections.
Another thing you can try is to go to the UI sessions list (click on User profile in the bottom left) and delete all the old sessions to see if starting a new session can create a stable link to the API.
clearing cache and deleting sessions did not help.
just to review same browser directly to the OH server works fine. My proxy is separate machine from my OH server.
accessing through the proxy blocks the badges/ item values
so my conclusion is the new chrome version has trouble in the proxy environment
My proxy server is also separate from the server openHAB runs on and I can not repro your issue using chrome or edge.
So my conclusion is the issue is local to you.
My mistake, I missed the the sseConnected false at the top of your posted log. It’s not the API in general that is the issue, it’s the event stream… But, if that is true, then this is a second report because we saw this just a few days ago as well:
@BoxSon did you find a solution to the problem? If not, you and @brianlay should compare systems to see if we can identify the common factor.
If this was a browser version issue with the use of a reverse proxy we would expect this to impact all folks using the reverse proxy configuration that is recommended.
I normally see any of these kind of issues pretty quickly as I have various test beds and configurations that press the reverse proxy to its limits.
So, for me at least I still struggle with the global statement this is a browser version issue.
And I am no big fan of chrome or edge browser btw.
I really think you should reconsider the subect of your post as it is misleading considering you now state this is a managed browser issue and search engines picking this up may lead openHAB users down a trouble shooting path that is not valid
maybe updating the broswer just happened at the same time as your issue appeared.
We have some antivirus system on our company laptops which is blocking those sse events. Maybe yours in combination with a proxy causes those issues? Just a humble guess. Do you have the same issue with e.g. edge or another browser if you configure proxy settings?
Just tried Edge on my work machine and also does not work when using the proxy. Works fine accessing the OH server directly. So same behavior on both Chrome and Edge
I never use Edge so I can’t confirm whether it ever worked through the proxy and when it might have stopped.
I should mention that Edge is also managed by my company