PeteAsking

Yes it will

Could have. Its just a wizard, I just closed mine. It has no use for anyone who has already setup their server so dont worry about closing it. Better to setup how you want your server specific to you anyway rather than some general setup that might work 90% of the time for most people.

Try in the edge browser on a windows machine.

Do you get some sort of error when you import the backup?

Yes. Unifi are sending cease and desist anyway now so its not tenable to continue in any way.

Im not aware of deleting anything. Maybe the post above explains something.

I suggest moving to the VM version and no longer using this docker version as Unifi no longer support it. Unfortunately a solution cant be safely and reliably made when unifi actively work against it.

My personal opinion is Unifi have made it pretty clear they only want their project run on a vm with their sanctioned method so if you deviate from that your doing so at your own risk. Its the unifi way or dont complain basically.

Seems like unifi have fully decided to kill off the network application so in the short term there is no way to upgrade anymore unfortunately.

You could open an issue on Github, Im not 100% sure myself. GitHubIssues · 11notes/docker-unifirun Unifi Controller rootless. Contribute to 11notes/docker-unifi development by creating an account on GitHub.

Is everything working at this stage or not working?

@oakley4404 what happened?

Do not remove /mnt/user/system/docker/docker-xfs.img Remove only: /mnt/cache/appdata/unifi-controller-reborn (and any other unifi-controller-reborn directories you might have created unless you need to back them up somewhere). /boot/config/plugins/dockerMan/templates-user/my-unifi-controller-reborn.xml also any other "my-unifi-controller-reborn.xml" related files in above templates-user directory. Test without any changes to the docker template and all other dockers stopped first before altering networking settings.

@oakley4404 Im not clear why its not working for you. Are you sure you are on the same network and can ping the container ip you gave it?

Yes post the log file also please copy and paste the entire text from the extra parameters line as its truncated in the screenshot.

Go into the unifi docker and change from basic view to advanced view and paste the extra parameters line here. Someone else had an issue there before maybe its the same for you.

And this is a fresh install? Its not working if you browse https://10.0.0.249:8443 ?

If you click on the unifi docker the tag will look something like: 11notes/unifi:10.1.85-unraid

Still the tag you are using like I asked.

The logs you provided show no viability into docker or related settings so have no use. Can you tell me what tag you are using?

It wont be soon, problem is to figure out how to make it secure as unifi dont themselves, so any solution 6+ months away probably.

Doesnt make sense because in your docker run ‘11notes/unifi:10.0-unraid-amd64' is different to what is specified in the xml template so its not pulling the template correctly. What cpu do you have

No worries. You should open a bug regarding unraid port locking. Im not sure what causes it but I have seen other people have it before on plex dockers and similar.

Reboot unraid I guess. Unraid issue, complain to unraid devs, I cannot prevent a port becoming locked. You have to get rid of this error: docker: Error response from daemon: driver failed programming external connectivity on endpoint unifi-controller-reborn (0d11e26333500a88b486606d2a5d74e83bb5cf93f5597734a8aadf6549d73b7d): failed to bind port 0.0.0.0:1900/udp: Error starting userland proxy: listen udp4 0.0.0.0:1900: bind: address already in use.

This is an unraid issue. I cannot fix it. Stop all dockers and start only this unifi one. If it starts then you have a port conflict. There is nothing I can do about that.