Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Home Assistant Operating System 11.4 (from 11.3) breaks Authentication #88

Closed
domenicdistefano opened this issue Jan 12, 2024 · 6 comments

Comments

@domenicdistefano
Copy link

Previously I had to turn off authentication for the integration to work (had been working for several months). Now after upgrading the OS to 11.4 authentication is broken completely which also makes any existing / associated entities disappear.

I am running on a VM so luckily made a snapshot before the upgrade and after rolling back everything is back to working - for now....

@Idan37S
Copy link

Idan37S commented Jan 14, 2024

Happened to me as well,
Waiting for a fix hopefully.

@meichthys
Copy link
Owner

meichthys commented Jan 14, 2024

I'll need some logs or more information since it is working fine for me on os 11.4

Also make sure you've followed the same setup instructions:

NOTE: If you have issues connecting, try creating an uptimekuma API key and using that with NO username for the credentials. If you are still having issues,make sure you can successfully connect to http(s)://your_uptimekuma.url/metrics

@Idan37S
Copy link

Idan37S commented Jan 14, 2024

I disabled the authentication in Uptime Kuma and it now works.
Note: even though it says "Host\Url" in the configuration of the package, "192.168.10.3" didn't work and "http://192.168.10.3" did work.

@meichthys
Copy link
Owner

I've seen a few reports like this. My general digestion is to use a valid ssl certificate using something like ngixproxymanager.

@meichthys
Copy link
Owner

Could be related to: #84

@domenicdistefano
Copy link
Author

Someone fixed something in the last couple of days because I just re-ran the update on the rolled back VM and now post-update everything still works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants