Like someone mentioned there seems to be a weird logging issue.

I have backed up my config from my UDM pro, installed the Docker image but then after restoring the backup I can no longer log in.

"Invalid username and pass". I am using the exact local user and pass that my UDM Pro is using

I deleted and recreated the container few times.

Not sure what the issue is.

Can anyone point me to what am I doing wrong?

 

Thank you

Edited March 12, 20233 yr by rainfactor

UniFi Network Application 7.3.83 has received multiple patches over the last 3 months and should be considered the "best" latest version for anyone who does not require a legacy version such as 5.14.23-ls76 or 6.5.x for older hardware.

 

So if you are on tag 7.2.95 you could upgrade to this 7.3.83 tag safely I imagine.

 

 

Current situation:

Legacy systems: 5.14.23-ls76 or 6.5.55 versions seem fine. (AKA "old old old stable" or "old old stable").

Wifi6/New Deployments: 7.2.95 or 7.3.83 tags are fine. (AKA "old stable" or "stable").

 

Do not use tag: "latest" unless you are an alpha tester who fixes their own problems.

 

Posting this info because of the upcoming next release (7.4.x) AKA "alpha"

 

Kind regards
Pete

1 hour ago, PeteAsking said:

Posting this info because of the upcoming next release (7.4.x) AKA "alpha"

Pinned (recommended)

 

Should I unpin the 30 Nov 2022 now?

5 hours ago, JonathanM said:

Pinned (recommended)

 

Should I unpin the 30 Nov 2022 now?

Yes thank you, that would make sense. 

11 hours ago, PeteAsking said:

UniFi Network Application 7.3.83 has received multiple patches over the last 3 months and should be considered the "best" latest version for anyone who does not require a legacy version such as 5.14.23-ls76 or 6.5.x for older hardware.

I've been on this for a week or 2, mostly because patch notes said it was supposed to help some L3 switch issues I was seeing (which did improve).
Have had no issues so far

Is it safe to go directly from 5.14.23 to 7.3.83?

I went from 5.14.23 to 7.1.68 a while back and only had to make some adjustments to the AP Groups, so I can confirm that worked in my situation.

 

I've upgraded to 7.3.83 since then.

 

Hope that helps.

Edited May 13, 20233 yr by a_n_d_y

34 minutes ago, a_n_d_y said:

I went from 5.14.23 to 7.1.68 a while back and only had to make some adjustments to the AP Groups, so I can confirm that worked in my situation.

 

I've upgraded to 7.3.83 since then.

 

Hope that helps.

It should be safe but some old devices could stop working if you have any in your environment. There have been many posts about various old devices in this thread and how they have issues. You should review that unless all your devices are on the newer side. 

8 hours ago, a_n_d_y said:

I went from 5.14.23 to 7.1.68 a while back and only had to make some adjustments to the AP Groups, so I can confirm that worked in my situation.

 

I've upgraded to 7.3.83 since then.

 

Hope that helps.

Can you post yr equipment if old and ‘unsupported’ that works.

7.4.156 was released to official 14 hours ago. I have an upgrade to this version scheduled for 13/06/2023 (13 days time - will post an update 48h later) if anyone is wanting to wait along for the test at this time where I will check the forums for issues and then update if it seems all clear.

 

Otherwise if you choose to update then you are on your own and just tell us what happened.

 

Kind regards

Pete

Edited June 1, 20233 yr by PeteAsking

I made the jump from 7.1.68 to 7.3.83. Only issue I had was an error when starting the container... it complained about invalid memory heap size. I had to set the MEM_LIMIT and MEM_STARTUP back to default and it worked again.

Im not able to recommend 7.4.156 for business use. I already had some issues, nothing deal breaking but mostly vlan issues that the upgrade seemed to alter settings around and I had some trouble setting back. Also seems like how its done has changed slightly. I would expect some issues in more complex environments, and mine is quite simple just a handful of vlans that run through an opnsense firewall.

 

I would guess for business you should review the new features and see if there is anything you have to have, and then plan correctly if you update. If you dont need anything then 7.3.83 is still very capable and the last good version without issues.

 

For home users you can go ahead and update to 7.4.156 most likely but take a backup of the docker first so you can just stop it and paste back the old copy if something goes wrong. Its hard to put an exact finger on it but this version seems either a little rushed or has a lot of changes. I imagine the version after this one will be better if they just do bugfixes (this is a guess I have no actual idea).

 

Up to you if you update, but I personally would leave this as a home update only and thats what I intend to do myself. Certainly at the very lease do not update without a full backup that you know you can roll back to. If you upgrade and all is fine then it should be no issue once you get past that so I expect success upgrades to cause little to no problem after the updates done. If you are unlucky might be a bit of fiddling needing after to get things back to normal.

 

Good luck

Can I run this container on a VLAN or does it have to be ran as bridge?

On 8/17/2021 at 3:30 PM, PeteAsking said:

Just to reiterate. If you run tag: latest you will 100% have an issue at some point. Just use the tag of the latest version (by specifying the number) if you want the latest version. You are then in control as to when you move to the next version. No surprises and if people are complaining you can wait it out.

How do you check / change the tag you're using without uninstalling / reinstalling from CA?  Or is that the recommended method?

11 minutes ago, JimmyOdcu said:

How do you check / change the tag you're using without uninstalling / reinstalling from CA?  Or is that the recommended method?

You can check what tag you are using by going to the docker tab and clicking on the name of the docker. The tag will be shown on the repository field.

 

 

If you change the tag the associated version will install when you click “apply”.

7.4.162 is more stable than 7.4.156. Please go directly to this version if you are not on .156.

 

Situation:

 

Legacy systems: 5.14.23-ls76 or 6.5.55 versions seem fine. (AKA "old old old old stable" or "old old old stable"). (Old in wall APs or other legacy APs need this?)

 

Wifi6/New Deployments: 7.2.95 or 7.3.83 tags are fine. (AKA "old old stable" or "old stable").

(Newer APs wont adopt if not at least this?)

 

Current (Production/Business should be fine. Hopefully): 7.4.162 ("stable")

(Dont use this if your company builds rockets or does heart surgeries. You dont need it.)

 

Future version (Only recommended for home or if your business requires a new feature missing from an old version): n/a at this time.

(Using future versions is risky.)

 

Kind regards

P

Edited July 13, 20232 yr by PeteAsking

I have a UAP-AP-LITE and UAP-AP-LR - both version 2.

I also have a USG router.

They dont make it easy to find out where I can upgrade too.

Can anyone on similar hardware let me know what is safe to use.

3 hours ago, vw-kombi said:

I have a UAP-AP-LITE and UAP-AP-LR - both version 2.

I also have a USG router.

They dont make it easy to find out where I can upgrade too.

Can anyone on similar hardware let me know what is safe to use.

I think you are supposed to be on 5.14.23-ls76. Hopefully someone else can confirm. 
 

i thought if you had a usg router you didnt use this docker though. Could be wrong as I dont own one. 

Edited July 14, 20232 yr by PeteAsking

Hhmm.  Been using this docker forever.  Upgraded loads of times with no issues until the last time late last year when I found out about all this support stuff.  I’m on 7.3.76…… been on it for a while.  Only thing I really want ant is cos I have to flip to the old interface to ‘forget’ dhcp reservations so ip addresses can be reused.

Hi. My server did a check on containers for updates, and my Unifi controller container says "not available"

 

Is this an easy fix?

 

It fixed itself. 

Edited July 21, 20232 yr by urbanracer34
resolved for now

On 7/13/2023 at 10:16 PM, PeteAsking said:

i thought if you had a usg router you didnt use this docker though

With the USG, the controller needs to run somewhere (like this docker container) as it is not built in..  The Dream Router has the controller built in and cannot be controlled by an external controller.

On 7/14/2023 at 10:24 AM, vw-kombi said:

I have a UAP-AP-LITE and UAP-AP-LR - both version 2.

I also have a USG router.

They dont make it easy to find out where I can upgrade too.

Can anyone on similar hardware let me know what is safe to use.

Just posting that yesterday I went up to 7.3.83 tag.  No issue in the upgrade and I messged around with a few settings and all is working fine.  Each update on the AP's throws an error about an uplink cant be removed or something like that - I dont have any uplinks so now sure what it is meaning.  Everything is working to date........

Is it possible within this docker container to run early access versions like 7.5.169?

 

I have an open ticket about the topolgy of my network because it shows my switch is uplinked from an AP, which it is clearly not.

 

They have suggested to run the early access version, so just asking if its possible, if not, all good

 

Cheers

6 hours ago, bdydrp said:

Is it possible within this docker container to run early access versions like 7.5.169?

Probably not, here are the versions available.

https://hub.docker.com/r/linuxserver/unifi-controller/tags

15 hours ago, JonathanM said:

Probably not, here are the versions available.

https://hub.docker.com/r/linuxserver/unifi-controller/tags

Thanks

Thought i would ask anyway

Cheers