Finally figured this out. I was binding the HTTP ports to a specific IP address, because 80 & 443 were in use by another site on the same server. Binding the 29810-29814 ports to a specific IP never...

@d0ugmac1 Upgrading back to 1.0.6 also fails in the same way.

Not sure if related, but during the upgrade I get this error in server.log with the MAC of the AP: WARN [manage-work-group-12] [] c.t.s.o.m.d.p.t.h.a(191): send set request to OmadacId(...)...

These are the ports being mapped into the controller container: 0.0.0.0:29810 29810/tcp 0.0.0.0:29810 29810/udp 0.0.0.0:29811 29811/tcp 0.0.0.0:29811 29811/udp 0.0.0.0:29812 29812/tcp 0.0.0.0:29812...

@shberge I double-checked and forwarded port 8043 into the Docker container (443 already was), and that also didn't help.

@d0ugmac1 There's only one AP. That same AP previously upgraded to 1.1.0 sucessfully, and there have been no changes since other than upgrading to the newest controller version. It looks like the...