Ritmjunk

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by Ritmjunk

  1. Quote

     

    The US8-60W is standard PoE (af). The product specifications limit PoE delivery to 15.4W per port.

    The U6-LR is a PoE+ (at) device. The product specifications have a max operating power consumption at 16.5W.

     

     

    I have an US8-60W POE, my controller is at version 7.3.83 and working fine!

    There are indeed some system logs: ## AP is connected to a PoE port incapable of providing enough power for the AP to operate at full capacity. Please connect it to a PoE+ port or adapter##

     

    7.37 W on the poe port (US8-60W) that powers my U6-LR. For me there are no problems at all, even no power loss or capacity loss.

     

    My equipment:

    2 x  US8-60W POE

    1 x  U6-LR

    1 x UAP-AC-LR

     

    To summarize, the equipment did not stop working. Just a message in the system log. Maybe in high density environments it can cause problems...

     

  2. 17 hours ago, klogg said:

     

     

    Same. Looking at the logs I saw:
     

    Invalid maximum heap size: -Xmx2048MM
    Error: Could not create the Java Virtual Machine.
    Error: A fatal exception has occurred. Program will exit.

     

    Notice the doubled up "MM" at the end of the heap size. Changing my environment variable to not specify "M" let it fire right up again.

     

    environment
        - MEM_LIMIT=2048M

    needs to become

    environment
        - MEM_LIMIT=2048

     

    Had the same issue, this solution works for me also.  

    Thank you for the information!

    • Thanks 1
  3. 2 hours ago, mfarrar said:

    Is it possible to pull a later version? Upgraded to the 7.2.93. Nothing but problems. Wifi clients wont connect. Restarting switch and APs cause them to not adopt after restarting.

     

    Not sure this will help, but you can give it a try:

     

    ensure your controller computer has a DNS resolvable hostname on your network(s) (you can ping it by name from your Unifi devices) then go into Settings on you controller, go to the controller section and ensure that your host name or IP address for your controller are entered intot he Controller Hostname/IP field, then check the Override inform host with Controller Hostname/IP like so:

     

    (use your own IP Adrress)

     

    Unifi.thumb.png.5e60a1139c5f582299a580a45b5ca1ec.png

  4. 13 hours ago, unraid-user said:

    Hello.  I have a little issue where my new Unifi Switch isn't being picked up by my controller.

    Controller is the version mentioned above that seems to work for a few others.

    When I'm in the controller on the devices tab, I can see my switch and it just sits there forever saying adopting in the status column.  Been like that for weeks.  I'm new to the unify family.  I've read around that the switch maybe needs pointing to where the controller lives?

     

    My network is basically that switch connected to my netgear router which is then connected to my modem (in modem only mode).

    I have two UniFi AP's connected to the switch and everything network access works fine.  I can get internet. I can ftp across to my server that's sat on the same network from me laptop etc.

     

    Any help appreciated as right now I'm using that switch like any other switch and not getting any benefit from it stats wise or able to configure anything on it.

     

    Hi,

    Been there, done that 🙂

     

    Two possible solutions that worked for me:

    - reset switch

    - ensure your controller computer has a DNS resolvable hostname on your network(s) (you can ping it by name from your Unifi devices) then go into Settings on you controller, go to the controller section and ensure that your host name or IP address for your controller are entered intot he Controller Hostname/IP field, then check the Override inform host with Controller Hostname/IP like so:

     

     

    b8282b56-d454-4d6f-96ac-5fef69a48807.png

    • Thanks 1
  5. 13 hours ago, Ritmjunk said:

    Hi Peteasking,

    Thank you for your reply, sorry for not providing much information.

    It's just that I never had an issue to log into the unifi controller, it started a couple of days ago after the latest update I guess.

     

    System information: Unraid 6.9.2

    Docker Unifi controller in bridge with standard settings, latest

    Domain name: unifi.mdeneve.be 

    nginxproxymanager (others domains, for example nextcloud, are running) 

     

    I'll include the log files from server and mongodb....there are some errors....

     

    Steps that I already did:

    - restarting the container

    - reinstalled docker unifi controller

    - I already took a backup when it wasn't working, restore appdata is not an option

     

    Thank you in advance for having a look. Appreciate the work you guys do.

     

    Ritmjunk

     

     

    mongod.log 1.38 MB · 0 downloads server.log 4.27 MB · 0 downloads

     

    I found the solution myself. I think the mongodb was totally screwed up....from what I understand from the logs.

    - tried to repair the database without luck

     

    Steps to the solution:

    - stopped the container

    - copied unify-controller folder from appdata (there's a folder with configuration backups from the unifi controller, xxxx.unf)

    - removed the container

    - delete unifi controller folder in appdata

    - reinstalled unifi-controller docker

    - access the web gui from unifi and restored from the backup file xxxx.unf

    - access to the controller with no issues

     

    Should anyone run into this issue, this solution worked for me.

     

    Ritmjunk 

     

  6. 36 minutes ago, PeteAsking said:

    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

    Hi Peteasking,

    Thank you for your reply, sorry for not providing much information.

    It's just that I never had an issue to log into the unifi controller, it started a couple of days ago after the latest update I guess.

     

    System information: Unraid 6.9.2

    Docker Unifi controller in bridge with standard settings, latest

    Domain name: unifi.mdeneve.be 

    nginxproxymanager (others domains, for example nextcloud, are running) 

     

    I'll include the log files from server and mongodb....there are some errors....

     

    Steps that I already did:

    - restarting the container

    - reinstalled docker unifi controller

    - I already took a backup when it wasn't working, restore appdata is not an option

     

    Thank you in advance for having a look. Appreciate the work you guys do.

     

    Ritmjunk

     

     

    mongod.log server.log

  7. On 12/21/2019 at 10:09 PM, Marbles_00 said:

    I figured it out.  Found a great youtube video on step by step procedures for setting up duckdns.org, setting up additional configurations in Unraid, and finally setting up the Letsencrypt docker properly.

     

    Video can be found here (for anyone else):

     

    Big thank you to Mr. Spaceinvader One.

     

    Hi Marbles,

    Im new to Unraid and also followed Spaceinvader guide. All went wel using my own domain name.

    Except for Home Assistant.......What exactly do you put in the home assistant configuration file? I'm familiar wit HA because it's running on a Raspberry PI, but like to set it up on Unraid.

    Thank you in advance,

    Michael