-
Notifications
You must be signed in to change notification settings - Fork 3
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
Error determining UniFi unique ID #7
Comments
Hi @cblt2l, The line that's output from is 112 in |
I pulled latest from git and got this. I don't see anything obvious that would be causing the problem. Any ideas?
|
You have your site as |
I tried "default" as well as "DEFAULT" with the same result. The actual site name is "Default" in the settings. |
At this point my guess is that there's a change in the 7.5.x controller version that breaks this utility. I'm still on 7.4.x. Once I upgrade to 7.5.x, I'll check to see if it's a version issue, and will circle back. |
@cblt2l I've upgraded my network controller to 7.5.x and tested; it doesn't appear to be an issue with the controller version. There's conditional logic in the utility based upon whether or not the network controller is running on a UniFi Dream Machine Pro device - that's what I suspect next is the issue. Perhaps the UniFi folks have changed some functionality for the controller when it isn't running on a UDM Pro. What version of Go do you have installed? |
This is the version I used to build. (Debian 12.1)
|
@cblt2l I've tried building and executing via Can you post the entire contents of all files with logged HTTP calls (sensitive information redacted) and not just the most recent one? I this same error crops up, it should result in two logged files - the first one may have more information I need. |
I've now tested against network controller |
@rfpludwick When I run the compiled binary it only generates 1 log file in the local directory with a timestamp in the filename (ex. "2023-10-19_19-15-48_-0400.log") I will try updating the controller via docker and see if that changes anything. |
I think I see an issue with the HTTP logging system. I'm going to make some adjustments there and when I publish the changes, I'll let you know for retesting. |
@cblt2l I've added logic to the logging to make sure that same-second HTTP calls don't get clobbered. If you update the repo and try again, you should hopefully have correct logs this time. |
Apologies for the delay. I pulled the latest from git and rebuilt the go binary. There was 1 log file generated named "01-2023-12-17_14-26-17_-0500.log". The contents are below. I have also updated my unifi controller to 8.0.7 and still see the same behavior as before. Thanks.
|
@cblt2l I'm a bit stumped here as to what the issue is. I took a brief look at the Docker image you're using and that's the only explanation I've got - it's that there's something awry in the UniFi Network Controller in that image. They say to migrate to a new version of the image anyhow. Here's a log from the login auth on my UniFi Network Controller, which is the running on UniFi hardware:
I'm not completely sure if the auth flows for UniFi Network Controller are different when they're not running on UniFi hardware, or even specific hardware. Can you give it a try on the newer version of the LinuxServer.io image? |
I'm running the Linuxserver.io Unifi controller container in docker on a Synology. The controller version is 7.5.174.
I cloned & built the latest from this repo, filled in the config file and when I try to run I get the following:
My config file looks like this:
Any idea what could be wrong? I figured there would be more output from the -verbose flag.
The text was updated successfully, but these errors were encountered: