PeteAsking

Members
  • Posts

    672
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by PeteAsking

  1. As upgrading functions as expected I am moving the project from aplha ---> beta
  2. The latest version has been pushed to the repository and the first post updated with instructions to upgrade. @bmartino1 @wgstarks
  3. Webui button wont work in that mode for various reasons beyond my control.
  4. I tested this and was able to get brx networks to work. For some reason the docker displays no IPs like you saw on your screenshot from Saturday 18th/11 - however you can connect to the web interface no problem and so long as an inform URL is set with the correct IP then it works. I dont see any issue my side with this setup. 100% you should get the web login when using brx networking, this is tested and working for me so please troubleshoot why that did not work for you (must be something your side). P
  5. Something is wrong with your docker networking because that is not normal. did you actually type in an ip address? Because that setup wont work and is above the container so its something you must fix in unraid.
  6. Interesting. I will try test custom:br0 this weekend if thats not creating a functional docker for you.
  7. You should configure the container to use the same IP as before or they wont adopt I dont believe, or you might have to unplug them and reboot them. Its a unifi thing.
  8. I agree this appears like something is already using this port but if what you are saying is accurate and nothing is because everything else is stopped then its an issue one layer up with unraid itself and not something I can address. I cant say why unraid would claim the ports in use if that is in fact untrue.
  9. Pretty much what @JonathanMsaid. I realise this is not well known, but the linuxserver.io one is being deprecated in its current form and this is being developed as a replacement that is similar to how that one worked. To continue with linuxserver.io going forward will require 2 dockers to be configured and maintained and communication between them at all times which is very different to the current single docker solution they provide.
  10. That would not be supported as the images are build in different ways, it would be only from one unraid version to the next.
  11. Unclear what you mean 'by each revision'. To upgrade to a later tag you just change the tag and the database auto upgrades. The restore option is if you are moving from another container.
  12. The restore is designed to work this way for some reason by unifi. So it doesn’t break, it just works like that. If that’s incorrect then unifi would have to fix how it works.
  13. Interesting. This docker is designed to avoid at all costs using root in any way whatsoever so most likely enabling this (privileged) option is breaking things. The image is built under the assumption root will not be used, its possible enabling this is causing the issues you are seeing and everything should function without that option.
  14. @bmartino1It is not clear to me why you have ‘privilege = true’ in your setup. This is not default in the setup.
  15. Still meed more testers guys. Please consider testing this if you are able.
  16. Its not being discontinued like the linuxserver.io one
  17. No worries just need more testers then to progress forward.
  18. Thank you for the feedback. Let me know regards github if desired.
  19. @wgstarksdo you have a github? I can add you as a contributor.
  20. Im confused by your comment. What is raspi4? Like raspberry pi? Unclear how to interpret your message.
  21. If this works for you then we will need to wait for more testers to check the deployment is easy enough to follow.
  22. To start from scratch and check directory perms are working as intended: Make a backup in running docker Stop docker Use gui to remove docker and check "also remove image" SSH: rm -r unifi-controller-reborn/ rm /boot/config/plugins/dockerMan/templates-user/my-unifi-controller-reborn.xml Everything is now clear, install as normal and use backup file. Follow instructions on page 1 (updated them). check directory perms using ls -l should be : drwxr-xr-x 1 nobody users P @wgstarks