Error determining UniFi unique ID

cblt2l commented 10 months ago

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:

user@mypc ~/P/unifi-phantom-clients-cleanup (main)> ./unifi-phantom-clients-cleanup -verbose
Executing for host https://192.168.50.5:8443
Error determining UniFi unique ID

My config file looks like this:

---
version: "0.2"
httpLogDirectory: ""
sites:
  - host: "https://192.168.50.5:8443"
    site: "Default"
    username: "username"
    password: "password"
    udmp: false
    validateCertificate: false

Any idea what could be wrong? I figured there would be more output from the -verbose flag.

rfpludwick commented 10 months ago

Hi @cblt2l,

The line that's output from is 112 in main.go. I just pushed a new commit to main to log that HTTP call if the unique ID cannot be found. Please update the repo and run with httpLogDirectory in your config YAML set to a writeable directory on your host. After running, that directly should have HTTP call logs in it, including the log for that particular unique ID call if it fails. Hopefully that response body should have a clue in it. If you want additional help once you have that response body, feel free to post it here in this issue with sensitive information like usernames, etc. redacted.

cblt2l commented 10 months ago

I pulled latest from git and got this. I don't see anything obvious that would be causing the problem. Any ideas?

Request

&{Method:POST URL:https://192.168.50.5:8443/api/login Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Content-Type:[application/json]] Body:{Reader:} GetBody:0x65ffa0 ContentLength:53 TransferEncoding:[] Close:false Host:192.168.50.5:8443 Form:map[] PostForm:map[] MultipartForm:<nil> Trailer:map[] RemoteAddr: RequestURI: TLS:<nil> Cancel:<nil> Response:<nil> ctx:0xc0001a65b8}

Request Body

Response

&{Status:200  StatusCode:200 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Access-Control-Allow-Credentials:[true] Access-Control-Expose-Headers:[Access-Control-Allow-Origin,Access-Control-Allow-Credentials] Content-Length:[30] Content-Type:[application/json;charset=UTF-8] Date:[Tue, 26 Sep 2023 21:04:01 GMT] Set-Cookie:[unifises=02x0Qj1dRoeG4HHwyyFvt4l5dEDdD7rh; Path=/; Secure; HttpOnly csrf_token=**REDACTED**; Path=/; Secure] Vary:[Origin] X-Frame-Options:[DENY]] Body:{Reader:} ContentLength:30 TransferEncoding:[] Close:false Uncompressed:false Trailer:map[] Request:0xc00021c000 TLS:0xc0001ee370}

Response Body

TLS

&{Version:771 HandshakeComplete:true DidResume:false CipherSuite:49199 NegotiatedProtocol: NegotiatedProtocolIsMutual:true ServerName: PeerCertificates:[0xc0001fc580] VerifiedChains:[] SignedCertificateTimestamps:[] OCSPResponse:[] TLSUnique:[**REDACTED**] ekm:0x616c00}

rfpludwick commented 10 months ago

You have your site as "Default" in caps - have you tried lowercasing that?

cblt2l commented 10 months ago

I tried "default" as well as "DEFAULT" with the same result. The actual site name is "Default" in the settings.

rfpludwick commented 10 months ago

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.