Unifi widget doesn't work with new 2FA requirement

[ryanrichardson3]

Description

Everything is set up correctly, and it was working perfectly before. There is a new Unifi update that suggests to enable 2FA before a certain date.

homepage version

latest

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

I already understand the issue and I don't believe there is a way to fix it at the moment. I was going to open an issue, but it said to create a community post first. I would appreciate anybody's advice if you have ideas.

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

Based on the information provided, it seems that the recent Unifi update which suggests enabling 2FA (Two-Factor Authentication) may have affected the functionality of the Unifi widget on your homepage installation. Since you've mentioned that everything was set up correctly and was working before the update, it's possible that the update has introduced changes that are not yet compatible with the current version of the homepage Unifi widget.

Here are a few steps you can take to troubleshoot the issue:

1. Check for Updates: Ensure that you are running the latest version of the homepage software, as updates may include fixes for compatibility issues with Unifi updates.

2. Review Recent Changes: Look for any release notes or documentation from Unifi regarding the update to see if there are any breaking changes or new requirements for API integrations.

3. Disable 2FA Temporarily: If possible, temporarily disable 2FA on your Unifi account to see if that restores functionality. This can help determine if 2FA is the cause of the issue.

4. Check the Homepage Community: Since you were advised to create a community post, check the homepage community forums or discussions to see if others are experiencing the same issue and if any solutions have been proposed.

5. Open a Community Post: If you haven't already, create a post in the homepage community detailing your issue, the steps you've taken to troubleshoot, and any relevant logs or error messages. This can help gather input from other users who might have encountered the same problem.

6. Contact Support: If the issue persists and you cannot find a solution within the community, consider reaching out to the homepage support team for assistance.

Remember to provide as much detail as possible when seeking help, including the specific version of Unifi OS you are using, the homepage version, and any error messages or logs that can help diagnose the problem.

If you have any additional information or specific error messages that you can share, please provide them so that I can offer more targeted advice.

This comment was generated by Glime.

[shamoon]

There is a new Unifi update that suggests to enable 2FA before a certain date.

What do you mean by this, as in it will be required for all accounts?

[craw0967]

OP hasn't replied, but yes, they're enforcing MFA for all accounts (local accounts might be excluded?) effective July 22, 2024. I was looking for a possible solution to this as well.

I'm not sure there's a good way around this either. I haven't spent a lot of time looking, but I'm not seeing alternative authentication methods, such as generating an app specific token, etc.

[ryanrichardson3]

Yes, they are pushing for everyone to get it. I disabled it for now but eventually we will be forced to use it.

[craw0967]

After some more reading, it appears that the MFA requirement will only impact Cloud accounts.

We should be able to retain API access for the widget by converting the account used to a local account and by ensuring that the widget config points to the local UniFi controller’s IP address. Alternatively, and the option I’m going to test out later, is to create a second admin account that is local only and use that one.

I found this link with some basic details - https://artofwifi.net/blog/important-update-for-all-unifi-api-users-switch-to-local-admin-accounts-before-july-2024

[ryanrichardson3]

Wow this is great! Hopefully everyone looking for the solution is able to see this article. Thanks for your help.

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.