UniFi Protect: Unable to authenticate with UniFi OS 4 about core

[CajuCLC]

Again, THIS ISSUE HAS NOTHING TO DO WITH SSL. IT HAS TO DO WITH UNIFI SO 4.0.

If you have another issue, GO MAKE ANOTHER ISSUE. This one is NOT GOING TO BE REOPENED. No matter how much you complain. UniFi OS 4.0 is NOT SUPPORTED by this integration yet.

And while we are on the topic of your "fix" your whole fucking issue is probably because you checked the Verify SSL checkbox when you did not have one. But guess what? I do not have any way to know that because you are trying to stow away on an unrelated issue instead of making your own issue with your own logs and diagnostics.

The error is the same either on 3.2 or 4.0. I didn't check anything, I know how to read. I am not your typical person that is just using HASS and comes here often to ask for help.
You are really the type of person who gives the open source community a bad reputation. If you don't want to deal with people, then don't respond.
I am not asking to reopen any issue. I simply posted here trying to help others that might have the same issue.

What I find absurd is how HASS allows you to be a contributor when you like to curse at people, be rude, just because you wrote an integration that is being used by HASS.
Do better.

[CajuCLC]

Stop talking about SSL. This issue has nothing to do with with SSL. It is because the cookie changed in 4.x making existing sessions incompatible. If you literally have any other issue with logging in, it is off topic.

You are an extremely rude person. If you don't like the community, don't write code for the community.
I have always seen how you respond to people and I have been just observing how you are so rude to people seeking help.

Either way, I was replying to other folks comments, not to you. If you have a problem with it, I don't care. Go be rude to someone else.

[AngellusMortis]

Again, THIS ISSUE HAS NOTHING TO DO WITH SSL. IT HAS TO DO WITH UNIFI SO 4.0.

If you have another issue, GO MAKE ANOTHER ISSUE. This one is NOT GOING TO BE REOPENED. No matter how much you complain. UniFi OS 4.0 is NOT SUPPORTED by this integration yet.

And while we are on the topic of your "fix" your whole fucking issue is probably because you checked the Verify SSL checkbox when you did not have one. But guess what? I do not have any way to know that because you are trying to stow away on an unrelated issue instead of making your own issue with your own logs and diagnostics.

[darkpixel]

LOL--ok. Just ignore it. In a week or so it'll be a production version.

[darkpixel]

Maybe someone should modify the bug template to mention that so people don't waste their time reporting bugs in the wrong place.

I'm using early access to help test not only Ubiquiti's software and provide feedback, but to also help test with things like Home Assistant integration.

[AngellusMortis]

It does not matter who you were talking to. You are contributing nothing to this conversation except confusing people. No one else has mention SSL issues. The issue is that upgrading to UniFi OS 4.0.3 can cause auth to stop working. The cause is because the session cookie was renamed.

You have already stated that the issue occurs on 3.2.x for you and upgrading to 4.0.x does not fix it. That further enforces your issue is 100% not related. Stop trying to introduce a completely unrelated issue onto this one and learn how issue tracking works.

[fxstein]

I have the same problem for the past 2 days on Protect 3.0.26 on UniFi OS v3.2.17 both on the Official Release Channel

[CajuCLC]

It does not matter who you were talking to. You are contributing nothing to this conversation except confusing people. No one else has mention SSL issues. The issue is that upgrading to UniFi OS 4.0.3 can cause auth to stop working. The cause is because the session cookie was renamed.

You have already stated that the issue occurs on 3.2.x for you and upgrading to 4.0.x does not fix it. That further enforces your issue is 100% not related. Stop trying to introduce a completely unrelated issue onto this one and learn how issue tracking works.

I mentioned how I fixed it. It is STILL failing on OS 3.2, I just tested again. Someone else just commented that it's also failing for them.
For ME the fix was to use a valid SSL.

I also decided to run HASS and UniFi OS in a separate environment and it also failed to auth. Once I created a self signed certificate and made sure HASS trusted that certificate, then it worked.

Again, this is how I fixed it. If it's different for anyone else, then it's different for them.
For ME that was the fix.

[AngellusMortis]

@home-assistant close

[AngellusMortis]

Github is not the place for feature requests, nor do I have any control over the issue reporting workflow. If you do not like it, go complain on Discord or the community forums.

It is not my fault you failed to read the docs and the issue reporting workflows for Home Assistant has poor UX.

[CajuCLC]

For me it is failing with OS 3.2, which is not EA. Changing to a SSL domain with a valid SSL worked fine.

[CajuCLC]

Do you have a dot (.) in the username by any chance? I've ran into the same issues with my Unifi Protect integration after updating to 4.0.3 Unifi OS. It seems the integration fails when the username of the account includes a dot. After changing the username to one without a dot, it worked again.

When I tested yesterday I was still on OS 3.2. I upgraded to OS 4.0.3 this morning and using a domain with a valid SSL still works.

[AngellusMortis]

Stop talking about SSL. This issue has nothing to do with with SSL. It is because the cookie changed in 4.x making existing sessions incompatible. If you literally have any other issue with logging in, it is off topic.

[AngellusMortis]

@home-assistant rename "UniFi Protect: Unable to authenticate with UniFi OS 4"

[AngellusMortis]

@home-assistant rename UniFi Protect: Unable to authenticate with UniFi OS 4

[home-assistant]

Hey there @AngellusMortis, @bdraco, mind taking a look at this issue as it has been labeled with an integration (unifiprotect) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of unifiprotect can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign unifiprotect Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

unifiprotect documentation
unifiprotect source
_{^{(message by IssueLinks)}}

[CajuCLC]

I was able to get the debug, not much:

2024-05-08 13:39:06.698 DEBUG (MainThread) [pyunifiprotect.api] Successfully loaded session from config
2024-05-08 13:39:06.699 DEBUG (MainThread) [pyunifiprotect.api] Request url: https://192.168.0.95/proxy/protect/api/bootstrap
2024-05-08 13:39:06.725 DEBUG (MainThread) [homeassistant.components.unifiprotect.config_flow] Request failed: /proxy/protect/api/bootstrap - Status: 401 - Reason: {'code': 401, 'message': 'Unauthorized'}

If I try to load https://192.168.0.95/proxy/protect/api/bootstrap on my browser, it gives me a warning for the SSL (expected). On HASS I didn't select to verify SSL, but it seems like it is trying to. And trying to load with HTTP just redirects to HTTPS:

curl -I http://192.168.0.95/proxy/protect/api/bootstrap
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Wed, 08 May 2024 18:44:35 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Location: https://192.168.0.95/proxy/protect/api/bootstrap

I have a Kubernetes cluster where I have SSL enabled for my pods and one of the services I run there is one to setup domains and redirects traffic to the service. So I have a local domain with SSL enabled and that worked for me. Debug log below (removed sensitive data).

2024-05-08 13:42:16.691 DEBUG (MainThread) [pyunifiprotect.api] No existing session for XXXXX
2024-05-08 13:42:16.691 DEBUG (MainThread) [pyunifiprotect.api] Request url: https://nvr.MYDOMAIN.local/api/auth/login
2024-05-08 13:42:17.166 DEBUG (MainThread) [pyunifiprotect.api] 200 application/json <ClientResponse(https://nvr.MYDOMAIN.local/api/auth/login) [200 OK]>
XXXXX

2024-05-08 13:42:17.167 DEBUG (MainThread) [pyunifiprotect.api] Authenticated successfully!
2024-05-08 13:42:17.167 DEBUG (MainThread) [pyunifiprotect.api] Request url: https://nvr.MYDOMAIN.local/proxy/protect/api/bootstrap
2024-05-08 13:42:17.360 DEBUG (MainThread) [homeassistant.localponents.unifiprotect] Connect to UniFi Protect
2024-05-08 13:42:17.374 DEBUG (MainThread) [pyunifiprotect.api] No existing session for XXXXX
2024-05-08 13:42:17.374 DEBUG (MainThread) [pyunifiprotect.api] Request url: https://nvr.MYDOMAIN.local/api/auth/login
2024-05-08 13:42:17.713 DEBUG (MainThread) [pyunifiprotect.api] 200 application/json <ClientResponse(https://nvr.MYDOMAIN.local/api/auth/login) [200 OK]>
XXXXX

2024-05-08 13:42:17.713 DEBUG (MainThread) [pyunifiprotect.api] Authenticated successfully!
2024-05-08 13:42:17.714 DEBUG (MainThread) [pyunifiprotect.api] Request url: https://nvr.MYDOMAIN.local/proxy/protect/api/bootstrap
2024-05-08 13:42:17.846 DEBUG (MainThread) [pyunifiprotect.data.nvr] Reading release cache file: /config/.storage/unifiprotect/release_cache.json

[randybb]

Looks like this is related to the latest update. Unifi OS was just updated from v3.2.12 to v4.0.3 and HA is not able to authenticate anymore.

[AngellusMortis]

EA versions are not supported.

[AngellusMortis]

The docs are very clear. Home Assistant does not support Early Access versions of UniFi Protect or UniFi OS or Early Access anything from Ubiquiti. If you have issue with Early Access versions, you are supposed to report them upstream. Like someone else already has.

If you do not like those requirements, stop using Early Access.

[redfoxert]

Do you have a dot (.) in the username by any chance? I've ran into the same issues with my Unifi Protect integration after updating to 4.0.3 Unifi OS. It seems the integration fails when the username of the account includes a dot. After changing the username to one without a dot, it worked again.

[AngellusMortis]

@home-assistant rename UniFi Protect: Unable to authenticate with UniFi OS 4

[AngellusMortis]

If you are on 3.2.x then no, you are not having this problem. As mentioned, this one is because of 4.0.x. This issue is closed. Adding more comments will not reopen it or get you any support. If you are having a different authentication problem, make a new issue (and fill out the issue template correctly).

[johnypony3]

@AngellusMortis, I hope you don't speak like this in a professional setting.