beanmeister

@JorgeB Diagnostics attached. diagnostics-20221117-0907.zip

@JorgeB Added the recommended command to my /boot/config/go and rebooted. It did not work. Looked like the local console is blanked out as part of the boot process because I see output scrolling and then the entire console goes blank when the server finished booting. Should I insert the command before or after this line in the /boot/config/go? /usr/local/sbin/emhttp & I had it after.

I will give that a try and will reboot when I get around to upgrading to 6.11.3. Thank you for the suggestion.

I lose the screen after a few minutes after boot. If I have it up at boot, then I do get the IPMI console and can see the local console output. It appears like unRAID goes into a screen saver mode where the local console disappears because IPMI will report a "No Signal" if I start a KVM console.

I used to be able to login via the console via IPMI. Now I just get a blank screen or IPMI reports no signal. Is there a setting I need to enable to get this feature back? I am currently on 6.11.2. I like the console login via IPMI because I can open multiple sessions (Shit+function keys ?) to run multiple preclear sessions. I can use Putty, but then I would need to keep my computer running if I don't want to lose the preclear sessions. I haven't had the need to add or format new disks for years, but now I am planning to deal with the eventual deprecating of reiserfs by replacing my 2TB disks with larger disks.

Thanks for the tip. I had 5 orphaned images.

Successfully upgraded Unifi Controller from 5.14.23-ls76 to 7.1.66 by changing the repository field to linuxserver/unifi-controller:7.1.66. All six sites with Unifi AP AC Pro and Lite devices are now running firmware 6.0.15 (upgraded from 4.0.54) prior to upgrading the controller software to 7.1.66. Looks like everything is running smoothly, let's hope things remain stable. If so, I should be set for another 3 years🤞 Not a big fan of the screen real estate waste of the new GUI. I prefer the more condense view so I can display more columns without having to scroll horizontally. Another peeve is now it is harder to determine which site I am looking at since the site name is no longer displayed. Thanks for all the help.

Thank you! I see multiple tags for 7.1.66. Am I correct to assume that the tags without the -ls### would check for updates? So if I just want to stay on a specific version, I would use linuxserver/unifi-controller:7.1.66-ls157 instead of linuxserver/unifi-controller:7.1.66?

Where can I find a list of available Repositories? I want to make sure I type it in correctly. Currently using linuxserver/unifi-controller:5.14.23-ls76. Would like to move to 7.1.66.

May I ask what firmware were your devices running when you upgraded the controller to 7.1.66?

Updated putty to Release .77 and now the server is accepting the SSH key to bypass having to login again.

Restored the content of the /config/ssl/certs folder from the flash backup prior to installing 6.10.3 and Https certificate now works. Have to look into why my SSH key is not being accepted. Looks like the 6.10.3 upgrade automatically overwrites the certificate file. Not cool at all.

Updated from 6.9.2 to 6.10.3 via the GUI. After downloading the newer version, I clicked on reboot in the GUI as prompted and the server froze with a kernel panic. I had to reboot via IPMI and the server booted up under 6.10.3 and started a parity check, even though a parity check had just been run at the beginning of the month. Now my SSL key and HTTPS certificate is not working. Other than the SSL key and HTTPS certificate, everything seems to be running.

After updating to 6.10.3 from 6.9.2., my SSL and https connection is now broken. I am getting an invalid certificate and my SSH key is not being accepted. I self-signed my own certificate using my pfSense. I have a feeling the update overwrote the appropriate files for SSH and HTTPS. Unfortunately, it has been a few years since I set up the SSH keys and HTTPS certificates so I don't know which files I should be looking at.

Would anyone know why this Unifi controller (V5.14.23) docker container would be trying to access something at the stretchoid.com domain? I noticed a log entry in my firewall that this container is trying to access this domain.

Woo hoo! Upgraded from 6.8.3 to 6.9.1 without any noticeable issues for now. There go my 357 days of uptime It was really touch and go there waiting for bzroot to load. It seems to get longer with every upgrade.

I do have Chromecasts and Google speakers on my network. Was the firmware prior to 4.3.24.11355 (4.3.21.11325) stable?

Thanks @Hoopster. @PeteAsking, I was able to successfully update to Controller 5.14.23 without any issues by first upgrading to 5.10.24. The database was upgraded by 5.10.24 prior to upgrading to 5.14.23. All my APs (1 local, 5 remote) showed up without issues. @Hoopster, Would you happen to know what would be a rock solid firmware for the APs to match Controller 5.14.23?

I'm on LTS (5.6) and would like to go to 5.14. This is a very long thread, can you point to or summarize the interim steps needed? I will go back and look for the actual posts, but this would serve as a cross reference to make sure I got everything correct. Thanks. Update: So to go from LTS (5.6) I would change the Repository as follows: Upgrade from LTS (5.6) to 5.10.24-ls21 Currently: linuxserver/unifi-controller:LTS Change to: linuxserver/unifi-controller:5.10.24-ls21 Then upgrade from 5.10.24-ls21 to 5.14.23-ls26 change Repository field to linuxserver/unifi-controller:5.14.23-ls76 Does that sound right?

I just updated this docker container by reinstalling it. I am running the LTS version. However, when reinstalling the container, my firewall intercepted the container trying to reach zg-0312c-421.stretchoid.com Anyone know what this is?

If all you have is the AP, then all you had to do was configure the two WiFi Networks and assign one a VLAN ID. The Network settings in the UniFi controller does nothing if you do not use UBNT gateway products.

I am running pfSense and I used the UniFi Controller SW to tag my guest WiFi with a different VLAN tag from my main WIFI. My pfSense handles all the networking services for each WiFi network. I do have a smart switch between the AP and pfSense, so my AP is not plugged directly into my pfSense.

Yeah, I did not see any release notes to see what were the changes. Also, do you have to delete the container? Can't one just click on the apply update link under the Docker tab?

I am currently running with the LTS tag (Unifi Controller 5.6.42. I noticed in unRAID that the docker container has an update available. Is there a place where I can read what the update contains?

I am having the same issues after updating to 6.8.2 from 6.8.1. I had the same issue updating to 6.8.1, but it cleared up after I did a hard reboot. Now I am stuck with it using the 169.x.x.x IP. I can only access the server via IPMI console.