PeteAsking

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.