PeteAsking

Members
  • Posts

    407
  • Joined

  • Last visited

Everything posted by PeteAsking

  1. Thats great. Thats 5 unraid users verified on linuxserver/unifi-controller:version-6.4.54 without any issues then, who took the time to post.
  2. No when you set a tag it stays safely on that version until YOU are ready to update. This is a far far far preferrable option than using a tag like "latest" which means one day you will wake up and find nothing is working and all your AP's are offline and you have no clue whats broken. Currently for both of you I would recommend the linuxserver/unifi-controller:version-6.4.54 tag. This is verified to be working safe by at least 3 of us on this thread (Im sure more people are using it but they tend not to post or provide feedback unless things brake even though we ask they post if everything went well so others know), and has few complaints on the unifi forums. For enterprise, there is an older version in the 5 series (5.14.23-ls76) we still recommend that is very safe and unbreakable but for home use this 6 series version is fine and brings you up to date to use the unifi 6 equipment. Eventually everyone will have to upgrade so the more home type people we can push along onto these newer versions (and provide feedback) the better for the people who are in the unfortunate position of being in an enterprise environment with larger numbers of AP's and other unifi stuff that need to be shielded from anything bad happening. @fc0712 you may want to upgrade first to 5.14.23-ls76 and ensure everything is perfect before moving to the 6 series as you are a little way behind. Obviously it goes without saying that you would make a copy (and write down the version) of the docker before upgrading so you can just copy and past back the version you had. I mean if I do have to say that then we are all in trouble. P
  3. Set your tag to linuxserver/unifi-controller:version-6.2.25 and try again after updating to this specific version. P
  4. Awesome thats great. So whats your front page like now that you can have the ids stats @jademonkee? Does it actually show information etc?
  5. Huh I have thanksgiving and everyone seems to fix their problems in this thread without me. Guess I should do that more often. Regards to @jademonkee - not suggesting you dont know what you are doing but when you enable DPI what speeds do you get (and can you confirm QOS(smartqueues) is off, IDS/IPS is off and hardware offload is enabled)? Because other people get good speeds even with only dpi on. Just asking.
  6. I mean we are pretty helpful on this thread I feel, but you do actually have to take the time to inform us of a little more about the setup and whats going on. We might know more about the unifi software than you do but we are also totally ignorant about your specific setup or settings so unless you tell us we cant really do much. I mean you dont even tell us if you stopped and started the docker again or anything so we are totally blind as to what step/stage you are at along with anything that might be different to the rest of us. P
  7. Ok sounds good to me. 5.14.23-ls76 is still in my opinion the absolute best version and only issue with it is the wifi6 devices that have come out from unifi that require a later version than the 5.14 series one. Literally that version is unbreakable in my opinion. That said, if you dont configure or change settings much or mind the new GUI (although occasional settings can still only be changed in the classic interface still) the last couple of versions have been ok, and currently this linuxserver/unifi-controller:version-6.4.54 seems acceptable. Its similar to the linuxserver/unifi-controller:version-6.2.26 version but contains more bugfixes so if you were using 6.2.26 before then likely 6.4.54 will be an improvement for you. I would also say it could be a very long wait for a version like 5.14.23 again, so unless you are in an enterprise setting and dont intend to replace any kit for a couple years then you may as well at some point try out the 6 series. Its getting better slowly which is great because a while back upgrading seemed to be a nightmare undertaking where you could end up with no working kit post upgrade. I did like the widgets etc that the previous version had but I am finding that I have learned to live without them on the 6 series anyway and tend to log into the controller a lot less and just use my phone if I want to see a specific client so maybe its a good thing to not be tempted to "improve" (AKA fiddle) around in the controller so often I dont know. Maybe others will find the same sort of thing Im not sure.
  8. Seems fine also after a day. Nothing unexpected happened.
  9. Try the 2GB docker option spoken about in the thread multiple times.
  10. Dont worry I found it in this odd location using find on the server. tail /var/lib/docker/btrfs/subvolumes/30d8b0a1507f7fd6d77979e44a078334ce582acb7cdd0e796a24b8160317d998/var/log/pihole.log
  11. Is there a way to make this docker write to the pihole.log file /and/or where is this file pihole.log?
  12. Can we use zram with unraid at all?
  13. 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 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.
  14. I saw this message a few days ago and didnt know how to respond so just waited to see if anyone else would. Im guessing nobody will. You see the issue is that you have provided too little information for anyone to actually help you. While we might know more that you do collectively and easily be able to solve a problem like this on our own, you invariably know more about your current setup and the steps you have taken to get to this point. We are totally reliant on you to actually give us information. If you fail to do this, then helping you is impossible. For all we know you have a complex setup with VLANS etc. But right now we are totally in the dark. So can you actually write up a detailed scenario and problem, with steps you took to resolve so far so we can check we agree with what you have done up until this point? Pete
  15. Yes exactly I always tag because running latest is just too risky. Currently my tag reads in full as: linuxserver/unifi-controller:version-6.2.26 I dont see a benefit to not tagging a version. You get any fixes to it and are not surprised one day by a bad upgrade. And if the version turns out to be a good stable one then you can just sit on it for a while. Its honestly required sysadmin for the unifi docker at this point
  16. I think the version is totally upgradable from 5.14 without an issue. I see people on the forums who have done it without any issue at all even though I havent done it myself. Obviously with docker its very easy to just take a copy of the docker files and put it back if anything goes wrong anyway so would recommend just stopping it, copying down the docker files, then upgrading. It does take longer to start up when doing the upgrade as it is updating some files and the database so maybe you have to just give it 5 minutes or so to complete the first time you move to the newer version. And obviously the cosmetic changes are still there which some people dont like but main issue is if you have wifi6 devices (or intend to buy them), you cant escape upgrading. When all is said and done, 5.14 was a really amazing and stable version with a nice interface so the best one can ever hope is to equal it in a future version. Its going to be a while to we see that same level again so just temper your expectations a little if you upgrade (ie the new interface isnt as nice and wotnot but at the same time its certainly usable in a production environment from what I can tell).
  17. I have had no issues and its working as expected.
  18. Its received multiple fixed (this version) and people seem happy on the forums. A small subset of users are having issues with vlans and a memory leak but nobody can work out what causes the people affected to have the issue. I see the docker image is regularly updated (last update 1 day ago) for this version so this particular one seems to be the one they are working the most on and have released no new version for over 2 months now. Will do. So far Im having no issues whatsoever.
  19. I have updated to version-6.2.26 today just fyi.
  20. repository is set to linuxserver/unifi-controller:version-6.2.25 on my docker.
  21. No problems, all seems to be working. As you cant provision the new devices without upgrading it seems like its just a matter of time until you will be forced to update anyway. Especially if you want that wifi 6 speeds the new equipment have. This seems like a pretty good version except for the fact you have to bounce back and forth between the classic and new interface to expose all options which is annoying. There was a video on youtube from that pfsense guy about the new version and these annoying quirks if you want to look that up but otherwise all good.
  22. I agree you should use qcow for snapshot support. Raw might appear to work but produce a dirty copy which cant be used so you might want to verify the backup actually works rather than it just saying 'success' and assuming its ok.
  23. There are alternative things you can to to harden this more such as locking the firewall rules down to the public IP the site connects from or if its a dynamic IP having the remote site establish a wireguard connection back to the primary site so that the inform URL can be an internal IP. If both those options are unavailable and the remote site has a dynamic ip another thing you can do is setup a dyndns service on the internet router there and then have a device on your primary network via a script write the ip of the remote site to a text file that can be imported as an alias to the firewall every 15 minutes or so so that if the IP changes the firewall rule is still locked down to an IP. This would ensure after 15 minutes that the AP's are allowed through to the firewall in case of an ip change.