PeteAsking

This basically confirms that the ip changed since the docker/unraid has a different ip to the pc it was on before. You need to set the inform ip and do what bmartino said

Not sure what is wrong. Can you check no other dockers are running when you start it to rule out some sort of conflict and check you have enough disk space and so on. Also check your networking is logical. Seems like an error above the container.

Is the inform ip in the settings set correctly still? (inform host override)

Not sure but there probably isnt much I can do to fix it. The software works however unifi code with all the bugs they insert into it and its a closed box.

Thanks. I have fixed this error now.

Are you using the latest tag? It was made available just a few days ago.

Thanks. Will just let unifi resolve it then.

I can check but I doubt it is important

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- |.|.|.|.|.|.|o|o|o|o|o|o|O|O|O|O|O|O|0|0|0|0|0|0|0|0|0|0|O|O|O|O|O|O|o|o|o|o|o|o||.|.|.|.|.|.| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- ██████╗░███████╗██████╗░░█████╗░██████╗░███╗░░██╗ ██╔══██╗██╔════╝██╔══██╗██╔══██╗██╔══██╗████╗░██║ ██████╔╝█████╗░░██████╦╝██║░░██║██████╔╝██╔██╗██║ ██╔══██╗██╔══╝░░██╔══██╗██║░░██║██╔══██╗██║╚████║ ██║░░██║███████╗██████╦╝╚█████╔╝██║░░██║██║░╚███║ ╚═╝░░╚═╝╚══════╝╚═════╝░░╚════╝░╚═╝░░╚═╝╚═╝░░╚══╝ ░█████╗░██████╗░███████╗░██╗░░░░░░░██╗ ██╔══██╗██╔══██╗██╔════╝░██║░░██╗░░██║ ██║░░╚═╝██████╔╝█████╗░░░╚██╗████╗██╔╝ ██║░░██╗██╔══██╗██╔══╝░░░░████╔═████║░ ╚█████╔╝██║░░██║███████╗░░╚██╔╝░╚██╔╝░ ░╚════╝░╚═╝░░╚═╝╚══════╝░░░╚═╝░░░╚═╝░░ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- |.|.|.|.|.|.|o|o|o|o|o|o|O|O|O|O|O|O|0|0|0|0|0|0|0|0|0|0|O|O|O|O|O|O|o|o|o|o|o|o||.|.|.|.|.|.| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 🅟🅡🅞🅤🅓🅛🅨 🅟🅡🅔🅢🅔🅝🅣🅢 Docker tag: 8.1.113-unraid NEW: Current recommended Home User tag: 11notes/unifi:8.1.113-unraid NEW: Current Company/Corporate recommended tag: 11notes/unifi:8.1.113-unraid Current Critical Infrastructure (no downtime) tag: 11notes/unifi:7.5.187-unraid

This message is normal, unraid does not support SWAP by default. It is an unraid limitation.

Tag 8.1.113-unraid is currently being tested. Please do not use this tag unless you are prepared to be part of the testing process.

Most of the issues here are people having no clue what networking decisions they are making and how networking works which is unrelated to this docker.

It sounds like one of the other dockers is using that port and if it starts first gets it. You will likely continue to have sporadic problems until you identify the conflicting docker. So far users found plex and jellyfin dockers both try to steal that port but there may be others.

Strange. What if you stop all your dockers then just start this one? Maybe one of the other dockers has consumed that port.

Are you able to put the address in the url bar manually eg: https://<ipyouset>:8443 ?

I still have a disk in an array because unraid requires at lest 1 disk in an array to start, although I now use pools only for all my data. has this requirement been depreciated yet or do we still have to have 1 dummy disk in the unraid array even today?

It was discussed and understood that some critical feature might be required for someone in a new version and we cant prevent someone using a new version altogether if it is absolutely critical for their operations they do so, but at the same time we can only really support images that we vetted to actually work properly since this is the solution that covers 99% of people and ensures minimal breakage.

Yes you should be able to. However, as noted: “8.0.28-unraid (Version skipped, did not pass testing).” As you are using an unsupported tag, any issues are up to you to resolve. We do not support tags that are unsanctioned and you are told to skip. You can use whatever tag you want, but if it falls outside what is sanctioned then its on you to resolve any problems.

The docker controller just setup up the devices with the settings you type in. If the phone or whatever cant get internet then its not a controller issue (if the settings are correct) more a networking issue with how your firewall/switches and so on are configured.

If you own a unifi switch and adopt it then you can create vlans and wotnot under the network tab

They become unlocked as you adopt devices. You wont have access to the gateway features as you are using pfsense and you cant adopt a usg with a self hosted container. if you adopt a switch, you can edit network settings. If you adopt a wifi ap you can modify wifi settings and so on. Otherwise its greyed out.

Im unclear exactly the screens you refer to. Can you describe what is happening further or in more clarity?

You have to type the address manually into your address bar you cant use the launch button in this setup. So if you set ip to 192.168.1.20 then you must manually type in your browser https://192.168.1.20:8443

On your firewall or whatever you must have dhcp setup? So lets assume the dhcp is something like 192.168.1.50 - 192.168.1.200. This means you have some addresses spare for static assignment outside the dhcp range eg: 192.168.1.20 in this example. Check nothing is using an ip you want to use outside the dhcp range and use one of your choice.

unifi requires these ports so instead of changing the ports, set them back and try changing your network to a custom one like br0 and setting a manual static IP. I haven’t actually tested this but maybe you can tell us if that works for you. Then you wont get a port conflict.