In this article, there are steps on how to resolve the "Managed by Other" status on the UniFi Cloud Access Portal (https://unifi.ubnt.com). Readers will have an understanding of the causes and resolution of this issue after reviewing this article.
NOTES & REQUIREMENTS: This article assumes that local access to the Cloud Key is available and that the admin following this troubleshooting guide can log in locally. Devices used in this article:
Table of Contents
The UniFi Cloud Key product line offers an easy and convenient means for managing a UniFi Network. The Cloud Key is intended to be used in places where remote access is required and it comes prepared for management over the UniFi Cloud dashboard: https://unifi.ubnt.com.
Once enabled, UniFi’s Cloud Service associates the UniFi administrator’s SSO login with the Cloud Key device. When a device appears "Managed by other" it typically indicates that the Cloud Key device has been configured for cloud use with a different SSO account.
In some less common cases, a user may encounter an issue where their Cloud Key appears as “Managed by Other” despite being associated to the correct account. This article will explain how to resolve these issues.
The most common cause for a Cloud Key to incorrectly appear as Managed by Other is either that the login used to log in to https://unifi.ubnt.com is not the same that was associated with the device, or that the device hasn’t been granted Cloud Access to the UniFi Controller. Verify that your SSO account is correct and that the right account is associated in the Controller's Settings > Admins section.
Cases where the Cloud Key appeared properly on this account previously, but is now appearing as “Managed by Other”, usually point to a conflict preventing the Cloud Key from being detected correctly by the cloud service. This is most often caused by Cloud Key migration, where a backup was restored on a different Cloud Key and both devices are attempting to authenticate to our cloud service with the same identifier.
1. Post-Migration Steps Needed
If this occurrence is happening after migration the device may appear to be changing IPs, going from online to offline, or presenting other similar symptoms. This indicates that the old Cloud Key has not been reset/taken offline. To resolve this, simply reset the Cloud Key or unplug it from the network to prevent conflict between the two Cloud Keys.
2. Disable and Re-Enable Cloud Access
After verifying that the SSO account is correct, that Cloud Access has been enabled and assigned to the proper account, and that the issues are unrelated to migration, this may indicate that the device is in a corrupt state with the Cloud Service.
To resolve this quickly, simply disable and re-enable Cloud Access by going to the UniFi Controller's Settings > Cloud Access, and clicking the button labeled Disable and Remove Cloud Access in the bottom right corner of the screen.
Once this is finished, the Cloud Access section of the controller should appear as so:
To re-enable, set Enable Cloud Access to ON. Log in with your SSO login and go to https://unifi.ubnt.com to confirm the issue is resolved.
Issue Still Not Resolved
1. Collecting Cloud Status Logs from Controller
If the issue is still not resolved, you may want to collect more information to help pinpoint the exact issue. To do this:
- Go to Settings > Services > Log Level, change Cloud Access to Debug, and click Apply.
- Attempt to disable and re-enable the Cloud Access again, once finished, grab the server.log file from the controller and look for error messages related to Cloud Access.
- An error that resembles the following may be logged:
<webapi-10> WARN sdn - failed to register controller to SDN: device.svc.ubnt.com
If you identify an error message and wish to report, please post on the Community or submit a support request with logs/error message noted.
2. Reset & Restore
At this point, you may opt to reset your Cloud Key and restore from a backup. This will resolve most residual errors related to a corrupt Cloud Key backup. Follow the steps in this article: