"API Error" / "Please wait" for Unifi Controller widget

[bverkron]

Note: I have already tried re-creating the container as per the note in the doc

I have setup a read-only user with the follow settings and even expanded the permissions to try and rule out a permissions issue.

This is the homepage config

- unifi_console:
    url: https://192.168.1.101:8443/
    username: homepage_read_only
    password: 3hkjaxxxxx5kja
    site: Home # optional

The homepage container logs don't show any errors, only the following. I have stopped the stack in Portainer and restarted it which I believe recreates the container (when stopped it does not show the homepage container in the list of containers). I have also tried manually re-creating the container a few times.

Listening on port 3000

The main widget stil returns API error

When I try to use the service widget it returns

API Error: The string did not match the expected pattern.

Curl shows the following. Not sure if it's because of the 302 http response code?

/app # curl -i -v -k https://192.168.1.101:8443/
*   Trying 192.168.1.101:8443...
* Connected to 192.168.1.101 (192.168.1.101) port 8443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / RSASSA-PSS
* ALPN: server did not agree on a protocol. Uses default.
* Server certificate:
*  subject: CN=unifi
*  start date: Jul 16 23:17:11 2023 GMT
*  expire date: Jul 13 23:17:11 2033 GMT
*  issuer: CN=unifi
*  SSL certificate verify result: self-signed certificate (18), continuing anyway.
*   Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption
* using HTTP/1.x
> GET / HTTP/1.1
> Host: 192.168.1.101:8443
> User-Agent: curl/8.5.0
> Accept: */*
> 
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
< HTTP/1.1 302 
HTTP/1.1 302 
< Location: /manage
Location: /manage
< Content-Length: 0
Content-Length: 0
< Date: Thu, 04 Jan 2024 01:27:23 GMT
Date: Thu, 04 Jan 2024 01:27:23 GMT

Happy to try other curl commands against the API if someone can give some tips on how to construct the API call the same way as homepage does it. I dug briefly but could not quickly or easily find the request details in the source code.

I'm on the latest version of the unifi-controller image from linuxserver.io here: https://hub.docker.com/r/linuxserver/unifi-controller I noticed that this image had been deprecated in favour of Unifi's newly named Unifi Network Application but this existing image was updated two days ago despite saying it's deprecated so not sure what's going on there. Should this widget work with this unifi controller image or does it require the newer Unifi Network Application?

[shamoon]

I haven’t tried it lately but I built the widget against the lsio image

How about the rest of these:
#612 (comment)

[shamoon]

I just tested it against lsio latest

Ps. the commands from the link above are a little different for you, they're for UDM but the controller uses a different port (443) and urls dont include '/proxy/network'

[bverkron]

... but I built the widget against the lsio image

To confirm do you mean the unifi-controller image or the newer unifi-network-application that replaces it?

Ps. the commands from the link above are a little different for you, they're for UDM but the controller uses a different port (443) and urls dont include '/proxy/network'

Not sure I'm clear on what the correct port / url is to use for the unifi-controller image I'm running. 8443 seems to be just the web interface since I get HTML back (see below). Can't tell if you're saying I should or shouldn't use 443. I tried exposing it anyway and got Connection refused so doesn't seem like the unifi-controller I'm using listens on that port.

$ curl -L --insecure -X POST --data-binary '{ "username": "homepage_read_only", "password": "**********", "remember": true }' -c cookies.txt --header 'Content-Type: application/json' https://192.168.1.101:8443/
<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"><title>UniFi Network</title><meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no" unifi-prevent-focus-zoom><meta name="apple-itunes-app" content="app-id=1057750338"><base href="/manage/"><link rel="apple-touch-icon-precomposed" href="angular/g1d599cf54/images/favicons/favicon-192.png?v=2"><meta name="msapplication-TileColor" content="#0193d7"><meta name="msapplication-TileImage" content="angular/g1d599cf54/images/favicons/favicon-192.png?v=2"><link rel="apple-touch-icon-precomposed" sizes="192x192" href="angular/g1d599cf54/images/favicons/favicon-192.png?v=2"><link rel="apple-touch-icon-precomposed" href="angular/g1d599cf54/images/favicons/favicon-64.png?v=2" sizes="64x64"><link rel="icon" href="angular/g1d599cf54/images/favicons/favicon-32.png?v=2" sizes="32x32"><link rel="icon" href="angular/g1d599cf54/images/favicons/favicon-16.png?v=2" sizes="16x16"><script src="angular/g1d599cf54/js/index.js" defer></script></head><body id="unifi-network-app-container"></body></html>

---

Edit: Found part of the problem. I had the trailing slash at the end of the url in the homepage config and that was probably breaking the url for the API call.

url: https://192.168.1.101:8443/
should be
url: https://192.168.1.101:8443

That fixed it for the service widget but not the main widget at the top of the page. It now says "Please wait" but never comes back with anything.

Still nothing in the logs. Interesting that there was nothing in the logs earlier either when it was the hard error before.

[shamoon]

Yea, the trailing slash is the first item under troubleshooting: https://gethomepage.dev/latest/more/troubleshooting/#service-widget-errors

I'd guess re-creating the container (not just restarting) should fix things, the service and info widget literally use the same code.

[bverkron]

I had started reading the troubleshooting doc but think I only got to the end of the general section and then started digging into logs and then looking at specific posts related to the Unifi widgets and never made it back to the rest of the troubleshooting page. Doh.

I've force re-created the container several times after removing the slash and still can't get past "Please wait".

• Selected the container in the list in Portainer
• Clicked Remove, confirmed
• Container no longer appeared in the list
• Verified via docker ps -a the container was gone
• Restarted the the stack to re-create the container

I even checked an option during the manual container removal "remove non-persistant volumes" and still no change.

I won't pursue the issue any further as I can just use the service level widget. Maybe eventually once I upgrade to the newer Unifi Network Application I'll try again. Maybe it's something quirky with my environment of composes file or something.

Thanks for the quick turn around. Sorry for wasting your time. I try to be as diligent as possible as per my original post but I'm still a stupid human at the end of the day that can miss things. 😜

[shamoon]

No worries man, all we ask is that people try on their own as you did, nothing wrong with still needing help after that!

[bverkron]

A-ha! It was site: Home causing the Please wait. For some reason it's not picking up that site. I may have 'Home' set in the wrong place on the Unifi side. Once I commented out that line it worked. The service widget worked because during my troubleshooting I never added the site property to the service widget.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.