Unifi controller not adapting ap's and switches. Status Server Reject.

[gasemans]

I have installed the unifi controller app from the default store and from the truechart store.

I am able to setup and import my settings.
but when i try to adapt any of the devices or use the mgrate from the old controller then it will not work.

the devices are offline.
sometimes i see the icon going orange like it is adopting.
but it never comes online in any of the portals.

When i check the status on for this example my 8 port poe switch i see the status as rejected.
No info in the logs of the controller.

Model: US-8-60W
Version: 6.5.59.14777
MAC Address: fc:ec:da:4c:ff:2d
IP Address: 192.168.178.29
Hostname: US-8-60W
Uptime: 1515 seconds
NTP: Synchronized

Status: Server Reject (http://192.168.178.94:8080/inform)

I can ping the controller.
when i open http://192.168.178.94:8080 in my webbrowser i am being redirected to the dashboard on https (8443)

when i do curl -I http://192.168.178.94:8080/inform
I see

HTTP/1.1 400
Transfer-Encoding: chunked
Date: Sat, 23 Sep 2023 21:42:37 GMT
Connection: close


So it seems like the inform part is not working...

I have setup an addon on my Home assistant for now.
But i like to have everything in my dockers on the truenas server.

Any one with a solution for this?

A quick test with my HA addon and the connection.

When i check the info directly on the same switch now it is connected with the controller on HA.

US-8-60W-US.6.5.59# info

Model: US-8-60W
Version: 6.5.59.14777
MAC Address: fc:ec:da:4c:ff:2d
IP Address: 192.168.178.29
Hostname: US-8-60W
Uptime: 667 seconds
NTP: Synchronized

Status: Connected (http://192.168.178.49:8080/inform)



When i do a curl on the inform adres i get the same result.
US-8-60W-US.6.5.59# curl -I http://192.168.178.49:8080/inform
HTTP/1.1 400
Transfer-Encoding: chunked
Date: Sat, 23 Sep 2023 22:00:19 GMT
Connection: close

 

[Sasquatch]

did you find the solution?
myunifi app from truecharts don't see AP. AP is brand new and appears in UNIFI controller for windows

 

[sretalla]

Are you running a bridge? not running that way may cause issues with broadcast, which I expect is part of the problem. (link to how to set that up... must stop all apps and VMs first... https://www.truenas.com/docs/scale/scaletutorials/virtualization/accessingnasfromvm/)

A second one (and easier to check) is the need to have the Network controller set properly with the "Inform Host".

(Stolen from the Home Assistant Add-on instructions):

1. Go to the settings (gears icon in the bottom left) -> System -> Advanced.
2. Toggle Override Inform Host.
3. Change the Host for Inform to match the IP or hostname of the device running TrueNAS.

 

[Sasquatch]

Are you running a bridge? not running that way may cause issues with broadcast, which I expect is part of the problem. (link to how to set that up... must stop all apps and VMs first... https://www.truenas.com/docs/scale/scaletutorials/virtualization/accessingnasfromvm/)

A second one (and easier to check) is the need to have the Network controller set properly with the "Inform Host".

(Stolen from the Home Assistant Add-on instructions):

1. Go to the settings (gears icon in the bottom left) -> System -> Advanced.
2. Toggle Override Inform Host.
3. Change the Host for Inform to match the IP or hostname of the device running TrueNAS.

I am running bridge,
Changing that option did nothing,
Logging to AP over SSH and issuing set-inform http://192.168.xx.xx:8080/inform did nothing.
I suspect that UNiFi controller sitting at kubernetes IP address and showing it in gui may be the culprit, VM Ubuntu 22.04 works straight off the bat with no messing about, but it gets it's own IP address in same subnet as AP.

 

[sretalla]

I suspect that UNiFi controller sitting at kubernetes IP address and showing it in gui may be the culprit,

That's exactly what the override inform address is there for... can you see that the port is listening on the TrueNAS host? in that case, the override pointing at the IP should do it.

 

[Sasquatch]

That's exactly what the override inform address is there for... can you see that the port is listening on the TrueNAS host? in that case, the override pointing at the IP should do it.

TCP: 8080, 8843,8443,6789
UDP:1001,3478
I'll contact truecharts support IF I decide to keep UNiFi as signal rang in initial testing is...lacking. 40m2 and half of I get 20Mbps link despite signal is excellent/good...max right next to u6+ is 300Mbps

 

[sretalla]

You might find that you need to reset/restart the device/AP adoption after enabling that option to get the loop going in the right direction...

Controller broadcasts (including the right IP address to come back on).

Device picks up the broadcast and asks for config, then reboots and connects to the override IP.

If that doesn't happen right, it can be left in a reboot loop looking for the wrong IP (probably the Kubernetes internal IP of the controller container).

 

[Sasquatch]

Removed(reset to factory defaults) AP and restarted controller app, still no joy. And UNiFi android app sees only VM controller as available console. When I shut that down it say no consoles found....

 

[sretalla]

Did you also set Network discovery to enabled right above that override IP option?

 

[Sasquatch]

Did you also set Network discovery to enabled right above that override IP option?

Yes...

 

[sretalla]

OK, well, I've only had success with the controller running as a docker add-on for home assistant (at the in-laws' place) where that setting was required and worked once set.

I'm out of ideas about what is wrong with your setup and/or the TrueCharts app.