PeteAsking

Members
  • Posts

    674
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by PeteAsking

  1. 7 hours ago, pmeledeo said:

    I am actually having this same problem with 8.1.113. First time using this and everything during setup was just fine. Restored backup just fine. But my USG and my U6-Lite are stuck in an "Adopting" and "Offline" loop. Anyone else run into this with 8.1.113 or any suggestions? I've restarted the docker and power-cycled the devices. I didn't change anything during the docker setup. Followed the instructions.

    Is the inform ip in the settings set correctly still? (inform host override)

  2. 12 minutes ago, MammothJerk said:

    I'm trying to figure out why my container doesn't see the network traffic for the unraid server it is running on (192.168.1.111)

     

    image.png.5ecaa501d5d61620e64897ab5e94b44d.png

     

    i did not change anything in the docker template, running "11notes/unifi:8.1.113-unraid"

    I believe i set up the container without changing any settings other than disabling automatic updates.

    Not sure but there probably isnt much I can do to fix it. The software works however unifi code with all the bugs they insert into it and its a closed box.

    • Thanks 1
  3. 4 hours ago, CrippleZero said:

    My apologies for necro-ing this post, but I had been following along and got it working; however, I am migrating from a backup and I am getting an error message that the backup is from a newer version that can't be used.

     

    I guess, I'm wondering, how often is the app/docker updated?  I would like to move off of my actual VM and move it to unRAID.

    Are you using the latest tag? It was made available just a few days ago. 

  4. 46 minutes ago, veeco said:

     

    EDIT: I'll follow up on UI forums, looks like someone else spotted it as well:

    https://community.ui.com/releases/UniFi-Network-Application-8-0-24/43b24781-aea8-48dc-85b2-3fca42f758c9#comment/87c8b4cc-3b0e-4927-a271-fc61aedaff24

     

    Looking in the container, I found the files at:

    `/usr/lib/unifi/webapps/ROOT/app-unifi/react/fonts/`

     

    I see that js i properly loading, for example:

    `https://192.168.3.152:8443/manage/react/js/5869.2f02b1d33b809f53b77e.js`

     

    But the path to the fonts is missing the `manage/react` prefix:

    `https://192.168.3.152:8443/fonts/UI_Sans_v8_Regular.eb36d6ff9c768a1639ca397b4dd84137.woff2`

     

    It looks like a Unifi problem with the wrong paths, unless there is some configuration option. You can see the inline style loading the wrong path:

     

    unifi_style.png

    Thanks. Will just let unifi resolve it then. 

  5. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
    |.|.|.|.|.|.|o|o|o|o|o|o|O|O|O|O|O|O|0|0|0|0|0|0|0|0|0|0|O|O|O|O|O|O|o|o|o|o|o|o||.|.|.|.|.|.|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
        
    ██████╗░███████╗██████╗░░█████╗░██████╗░███╗░░██╗
    ██╔══██╗██╔════╝██╔══██╗██╔══██╗██╔══██╗████╗░██║
    ██████╔╝█████╗░░██████╦╝██║░░██║██████╔╝██╔██╗██║
    ██╔══██╗██╔══╝░░██╔══██╗██║░░██║██╔══██╗██║╚████║
    ██║░░██║███████╗██████╦╝╚█████╔╝██║░░██║██║░╚███║
    ╚═╝░░╚═╝╚══════╝╚═════╝░░╚════╝░╚═╝░░╚═╝╚═╝░░╚══╝


                ░█████╗░██████╗░███████╗░██╗░░░░░░░██╗
                ██╔══██╗██╔══██╗██╔════╝░██║░░██╗░░██║
                ██║░░╚═╝██████╔╝█████╗░░░╚██╗████╗██╔╝
                ██║░░██╗██╔══██╗██╔══╝░░░░████╔═████║░
                ╚█████╔╝██║░░██║███████╗░░╚██╔╝░╚██╔╝░
                ░╚════╝░╚═╝░░╚═╝╚══════╝░░░╚═╝░░░╚═╝░░

    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
    |.|.|.|.|.|.|o|o|o|o|o|o|O|O|O|O|O|O|0|0|0|0|0|0|0|0|0|0|O|O|O|O|O|O|o|o|o|o|o|o||.|.|.|.|.|.|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
                                🅟🅡🅞🅤🅓🅛🅨 🅟🅡🅔🅢🅔🅝🅣🅢

     

    Docker tag: 8.1.113-unraid

     

    NEW: Current recommended Home User tag: 11notes/unifi:8.1.113-unraid

     

    NEW: Current Company/Corporate recommended tag: 11notes/unifi:8.1.113-unraid

     

    Current Critical Infrastructure (no downtime) tag: 11notes/unifi:7.5.187-unraid

    • Thanks 2
    • Upvote 1
  6. 54 minutes ago, rorton said:

    cheers, I thought I'd give it a go, its installed no problem, but got this message in the output:

     

    WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.

     

     

    This message is normal, unraid does not support SWAP by default. It is an unraid limitation.

  7. 8 hours ago, NeuroDoc said:

    Ok, this seemed to work now.  I was also able to restart my other containers, and it's still working.

     

    My only concern is that I had to set this container up on the bridge network.  For the old UniFi controller, I set it up under br0 and assigned it a unique IP.  I did this to maintain the AP adoption during software updates.  Going back to the bridge network now, I'm concerned that I will have to go through the adopt process each time the software updates...

    It sounds like one of the other dockers is using that port and if it starts first gets it. You will likely continue to have sporadic problems until you identify the conflicting docker. 
     

    So far users found plex and jellyfin dockers both try to steal that port but there may be others. 

  8. 4 minutes ago, NeuroDoc said:

    First, thanks for creating this!

     

    Second, I'm having problems getting the app to run.  I'm using 11notes/unifi:8.0.26-unraid, and everything seems to start-up correctly (no warnings during docker build).  However, I'm unable to get the UI to load.  Looking at the log, the only error is:

     

    WARN Unable to load properties from '/usr/lib/unifi/data/system.properties' - /usr/lib/unifi/data/system.properties (No such file or directory)". 

     

    However, when I go into the console, the directory and file are there.

     

    Any suggestions?

    Are you able to put the address in the url bar manually eg: https://<ipyouset>:8443 ?

  9. 15 minutes ago, yverde said:

    Ah I misunderstood, I thought it was unsupported until they release it here https://hub.docker.com/r/11notes/unifi/tags

    But it is actually completely skipped I see.

     

    Thanks for the clarification!

    It was discussed and understood that some critical feature might be required for someone in a new version and we cant prevent someone using a new version altogether if it is absolutely critical for their operations they do so, but at the same time we can only really support images that we vetted to actually work properly since this is the solution that covers 99% of people and ensures minimal breakage. 

  10. 38 minutes ago, yverde said:

    Hi,

    I'm trying to restore a backup from the official desktop controller app.

    When I use this container instead my AP shows as adopting then goes to Offline then back to adopting, but never succeed.

     

    image.png.e836f5f973f5c304cc22646cfd237f03.png

     

    image.png.89074a274dbafa949dcc3b3c07febc98.png

     

    The AP is not offline though as all my devices are not connected to it. 

    I'm using the new version 8.0.28

     

    Should I be able to restore from a backup made in the official controller?

     

    Thanks!

     

    Yes you should be able to. 
     

    However, as noted:

     

    “8.0.28-unraid (Version skipped, did not pass testing).”

     

    As you are using an unsupported tag, any issues are up to you to resolve. We do not support tags that are unsanctioned and you are told to skip. You can use whatever tag you want, but if it falls outside what is sanctioned then its on you to resolve any problems. 

  11. 4 minutes ago, Elmojo said:

    Yes, I know, thanks.  I'm trying to determine if I can get away with using this docker and self-hosting, or if I need to just through all the hoops required to get the physical UDM playing nice with my pfsense box.  So far, I'm not having much success either way. :/

    Actually, that doesn't quite seem to be the case.  I have only 1 U6 Pro AP adopted, and I now have all the icon categories along the far left available, and under settings, I have WiFi, Networks, and System.

     

    However, the wifi isn't really working.  My phone says it "can't connect", but the Unifi dashboard is reporting that my phone is indeed connected with a "good (70%) experience", which is really worrying, since the AP is sitting about 8 feet away from my phone.  If this is the type of "experience" I can look forward to with Unifi devices, they may not be for me.

     

    I realize I'm likely doing something (or many things) wrong, but this all just seems far more difficult than it should be.  Running the Unifi controller software behind one of the world's most popular router/firewall software should be a well-documented process.  It baffles me that I'm having such a hard time finding clear, step-by-step tutorials for how to make it happen.

    Sorry for the rant, it's been a rather frustrating couple days... :(

    The docker controller just setup up the devices with the settings you type in. If the phone or whatever cant get internet then its not a controller issue (if the settings are correct) more a networking issue with how your firewall/switches and so on are configured. 

  12. 8 minutes ago, Elmojo said:

    The Unifi Controller webUI.  I'm logged in, but it's mostly unavailable.  It's telling me that I don't have internet, or access to any of the network or WiFi screens, because nothing is connected.  I understand the WiFi part, since I have no APs connected yet.  The rest I don't understand.  How do I connect this controller (docker) to my network, is basically what I'm asking.  See the screenshots.

    unifi1.JPG

    unifi2.JPG

    They become unlocked as you adopt devices. You wont have access to the gateway features as you are using pfsense and you cant adopt a usg with a self hosted container. 
     

    if you adopt a switch, you can edit network settings. If you adopt a wifi ap you can modify wifi settings and so on. Otherwise its greyed out. 

  13. 1 minute ago, Elmojo said:

    Gotcha!  Yep, pfsense is handling DHCP duties.  I assigned an IP outside the range and applied.

    Now, when I start the docker and launch the webUI, I get a blank screen with "about:blank#blocked" in the address bar.

    EDIT: The logs are totally blank, but the console appears to be running.

    You have to type the address manually into your address bar you cant use the launch button in this setup. 
     

    So if you set ip to 192.168.1.20 then you must manually type in your browser https://192.168.1.20:8443

  14. 1 minute ago, Elmojo said:

    Oh boy, you just leapt right over my skill barrier... lol

    Okay, let me see if I follow... I changed back the ports to the defaults.  I changed the network type to custom: br0.

    Now, under 'fixed IP address', what would I put?  Just make one up, or does it need to be one that already falls within (or outside) my existing subnet?  This stuff is a little beyond my comfort zone, but I'm learning. :)

    On your firewall or whatever you must have dhcp setup?

    So lets assume the dhcp is something like 192.168.1.50 - 192.168.1.200. This means you have some addresses spare for static assignment outside the dhcp range eg: 192.168.1.20 in this example. 
     

    Check nothing is using an ip you want to use outside the dhcp range and use one of your choice. 

  15. 5 minutes ago, Elmojo said:

    Hi all,

    Okay, so I'm totally lost here...

    I'm trying to get this up and running from scratch, not restoring from any sort of prior Unifi system.  The initial instructions on page 1 all seem to relate to migrating from a previous install.

    I can install and run the docker, and I can even log into the WebUI, but it tells me I have no access to a gateway, so most everything it grayed-out.

    I suspect it may be because I have 2 ports that I was forced to change (I know!); ports 8080 and 6789 are used by other dockers on my system, and can't be removed.  Is this a dealbreaker?  I edited them in the Unifi template, which I know was noted as a very bad idea.  Is there any hope for me? lol

    Assuming that this isn't the cause of all my woes, what's my next step?  How do I connect to a "gateway"?

     

    I'm using a pfsense box as my router/firewall, and it's an external machine, not hosted in unraid.  I'm sure that matters.

    I watched a video by Lawrence systems about setting up Unifi with pfsense, and that's actually what got me thinking about self-hosting the controller software, as he didn't seem to like the UDM Pro very much.  I have one here, but I'll probably just sell it if I can get this working.  However, Tom was talking about having to have 2 networks for the UDM Pro to work correctly, is that also the case when using this docker?  As you can tell, I'm rather confuzzled... ;)

    unifi requires these ports so instead of changing the ports, set them back and try changing your network to a custom one like br0 and setting a manual static IP. I haven’t actually tested this but maybe you can tell us if that works for you. Then you wont get a port conflict. 

  16. 5 minutes ago, yverde said:

     

    yes that totally worked for me so far thx!

     

    Other question, my backup was made on v8.0.28 but the latest docker is on 8.0.26 as I understand?

    Will it eventually be updated to 8.0.28 so I can restore my backup or am I better restart from scratch?

     

    Thanks!

    You will have to wait for the next version to come out in a couple weeks. The .28 version was not accepted for deployment. 

    • Like 1
  17. 55 minutes ago, yverde said:

     

    I found one that was using port 1900 but was not showing in the port mapping of the docker page.
    Turning this off didn't work at first, but then I turned everything off one by one and it ended up working when I also turned off Jellyfin. Now I'm not sure if Jellyfin is really related because it is in host mode, not using port 1900 and now both are runing at the same time. 

    anyways, turning off some dockers did end up making it work!

    Thanks!

     

    EDIT: Somehow it really looks related to jellyfin, I am onle able to start it if jellyfin is not running, but once it's started I can start jellyfin after without any issues.

    Sounds related. Maybe ask on the jellyfin support thread.