-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
[BUG] version 8.2.93 fails to connect to any ubiquiti devices #97
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
this seems like something you would seek support from ubiquiti on, we just package their application in a container, we have nothing to do with development of their software. also there is no since 8.2.93 is quite old, i suggest 1) do not update right away, ubiquiti are known for releasing bad software and pulling it, check changelogs and other user's experiences first 2) when you do upgrade, bear in mind we support the container, not the software within the container. will go ahead and close this due to the age of the version |
This issue is locked due to inactivity |
Is there an existing issue for this?
Current Behavior
I have an existing setup and have been using various docker versions of the unifi controller and now network application. As soon as I upgraded to 8.2.93, none of my previously adopted devices [3 APs and 1 PoE switch] were shown in web interface.
I manually force downgraded back to v8.2.93-ls52 and all of my devices were again showing as adopted.
Expected Behavior
No response
Steps To Reproduce
Simply upgrading the docker to 8.2.93 caused the issue. I made no other configuration changes.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: