OK, So i have now tried http://ip.of.server:8103/inform and it comes through to the unifi controller on the remote server but instead of adopting as it should it shows inform error. when doing SSH - "info" on AP i can see that it says "Server Reject (http://ip.of.server:8103/inform)". So i think i now have the correct port but its not getting through fully!? would anybody be able to help with this?
Oh boy. Had the same inform trouble as other people, and now SSH'ing trouble on the old AP's (IP's had changed, sic.)
But ... yes, http://unifi.domain:8080/inform worked, even though, like @hawkinnz had, it's not clear if/how the address works/worked, or if modifying the default 8103 -> 8080 in portainer made a difference.
There is a brief STUN error, but that would be PortGuard associated, and it worked around it eventually.
(Mostly because I didn't really want to reboot my home DSL gateway to troubleshoot my home network ... because that would be hilarious to figure out when not at home.)
Anyway, got the POE switch and USG gateway adopted over, and the AP's individiually vis SSH.
For reference, logging in with admin and the SSH password set up in the controller, 'mca-cli' then paste in 'set-inform http://unifi.domain.com:8080/inform' and
'info' should show the new status as Unknown (11) or Server Rejected (), or Connected ()
Sorted it! I had to forget the device on my current controller (resetting the device) and forget it on the new controller. I then manually informed the new controller and then it was able to adopt! network back up and running and controlled by the remote server
Will also add, I had some trouble with Unifi post-migrate, with the AP's not being able to send stats via STUN on UDP 3478, using CloudFlare proxying by default, since Cloudflare is Proxying some of the HTTP/HTTPS ports for the subdomain...
but not UDP and not STUN proxying. (In the future, there may be a STUN over TCP relay feature, but it's not supported.)
I’m struggling to understand how to have Cloudflare DNS enabled and still allow UDP 3478 through to my endpoint as it appears that Cloudflare is blocking it. Is it classed as a non-standard port/service and therefore will not work on Cloudflare or is there a workaround? Broken: Multiple...
it's not a Docker problem, but a CloudFlare problem ... which solves so many of those early debugging problems where it wouldn't work right away. So, If only I had this problem earlier, it makes so much more sense due to http/https proxying for different ports, sigh.