all is clearly explained here:
keep in mind, there is heavy difference between supported version and “really stable” version. Stay away from RC.
28 patches for new 6th version from September. Never happened in Unifi controller history.
Still in 5th
Have you tried it? While I tested it it worked fine via rp. Not sure if there was a websocks or not. Still, it won’t hurt to try.yes. I’ve seen another reference regarding Plex, and it said for that to go to customer header and add websocket.
I tried that and the error was gone. Does this sound like the appropriate fix to do?
Have you tried it? While I tested it it worked fine via rp. Not sure if there was a websocks or not. Still, it won’t hurt to try.
Your are certainly right. I'm not very familiar with IP ROUTING so I need to dig a bit to see if there is something I can do. Anyway, Thanks for your help
sudo docker network create -d macvlan --gateway=192.168.0.1 --subnet=192.168.0.0/24 --ip-range=192.168.0.100/32 -o parent=bond0 --aux-address 'host=192.168.0.101' UniFi-Network Please not this part is not persistent and needs to be done after each reboot (I need to write a script and add is to DSM scheduler) sudo ip link add UniFi-Bridge link bond0 type macvlan mode bridge sudo ip addr add 192.168.0.101/32 dev UniFi-Bridge sudo ip link set UniFi-Bridge up sudo ip route add 192.168.0.100/32 dev UniFi-Bridge
#! /bin/sh # Update network configuration to add a route to unifi container # Create a virtual network interface to allow IP routing to UniFi container # Not persistant, has to be done after server boot-up ip link add UniFi-Bridge link bond0 type macvlan mode bridge ip addr add your_container_static_ip/32 dev UniFi-Bridge ip link set UniFi-Bridge up ip route add your_bridged_IP/32 dev UniFi-Bridge
not sure what are you thinking for
Destination: Protocol : https hostname : 192.168.0.100 port : 8443 (not 443)