• Posts

  • Joined

  • Last visited


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

mifronte's Achievements


Enthusiast (6/14)




Community Answers

  1. Would there be an issue if I rename the container name? I believe I will need it to match my current SSL certificate.
  2. Any thoughts on making a copy of the current linuxserver.io unifi appdata and then configuring the reborn container to the location of the appdata copy? Will the reborn unifi be able to use the copy of the linuxserver.io appdata so that no restore is required and hopefully I retain my SSL self signed certificate (I don't recall how I got it to work, but I am hoping to avoid having to do it again).
  3. Is there a recommended version of the controller that I would need to be at before switching from the linuxserver.io container to the reborn container? I am currently on 7.2.95.
  4. My current Unifi Controller (linuxserver.io) is running on Network Type: Custom: BR0.30 (VLAN 30). Will this pose a problem when I switch to the reborn container? Also, will the restore also restore the SSL certificate (self signed) that I had configured so my browser doesn't complain about the HTTPS?
  5. Still on 7.2.95 but just checking in after a little over year to see what's up. On first read here's is my two cents opinion: 1. One container solution is simpler and less moving parts to break. The unknown is an unestablished container developer? 2. Two containers solution sounds like it would be a nightmare for casual users (like me) to keep updated since there are now twice or more moving parts to worry about. However, the containers are maintained by established developers. Operating under the KISS mantra, I would prefer a one container solution. Let's put it this way, if I was brand new to Unifi and looking for a way to run it on unRAID as a docker container, I would most likely opt for the one container vs the two containers solution.
  6. Upgraded from 6.11.5 to 6.12.6 with no issues other than losing my 355 plus days of uptime.
  7. OK then. Look like there's some hope. Will have to do some more experimenting.
  8. @JorgeB What X7 motherboard are you using? My X7SBE has an add-on daughter card (AOC-SIM1U+) to provide IPMI functionality. I have a feeling the IPMI firmware (V1.64) is just too old to work with IPMIView. I also have a Supermicro A1SRi-2758F with built-in IMPMI functionality on the motherboard and IPMIView works fine. So I may be SOL with my unRAID server.
  9. Next time I have to reboot, I will see if I can enter the BIOS during boot before unRAID even loads. If my keyboard responds and I can navigate the BIOS, then at least I can eliminate IPMIView as the culprit.
  10. IPMIView 2.17 and 2.20. I will try to downgrade to IPMIView 2.14 (don't have 2.15) to see if that solves my issue. Edit: Nope, my keyboard input is not responding even with version 2.14. Could it be some configuration with the IPMIView software? I think it used to work until I upgraded unRAID and lost the local console screen, but never looked into it until now since I never had a need to access the local console for a long time.
  11. I get the login prompt, but I am unable to interact with the KVM console. No response from my keyboard. Don't know it this is related to unRAID or the IPMIView software.
  12. Thank you! That got me the local console login prompt via IPMI back. Not quite sure why I need to blacklist something that I do not have installed.
  13. @JorgeB Diagnostics attached. diagnostics-20221117-0907.zip
  14. @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.
  15. I will give that a try and will reboot when I get around to upgrading to 6.11.3. Thank you for the suggestion.