Reply
New Member
Posts: 44
Registered: ‎11-22-2017
Kudos: 9

UNMS Container IP Issues - No access to GUI post install

As the name states the IP on the containers is set to 0.0.0.0<port>, as shown below.  Is this the expected behavior?  Why would it not be set to one of the two IPs assigned to the existing interfaces?  I am not able to access the interface after the install and I am initially thinking this is my issue.  Thoughts?

 

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7135f8fea119 ubnt/unms-nginx:0.13.1 "/entrypoint.sh ngin…" 35 minutes ago Up 35 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp unms-nginx
a240c63cbdfe ubnt/unms-netflow:0.13.1 "yarn start" 35 minutes ago Up 35 minutes 0.0.0.0:2055->2055/udp unms-netflow
fb9bb1309e61 ubnt/unms:0.13.1 "/usr/bin/dumb-init …" 35 minutes ago Up 35 minutes unms
63b24791c893 redis:3.2.8-alpine "docker-entrypoint.s…" 35 minutes ago Up 35 minutes unms-redis
35bbf957b8f9 rabbitmq:3.7.4-alpine "docker-entrypoint.s…" 35 minutes ago Up 35 minutes unms-rabbitmq
3fd23f61331a postgres:9.6.1-alpine "/docker-entrypoint.…" 35 minutes ago Up 35 minutes unms-postgres
f438a265a69d ubnt/unms-fluentd:0.13.1 "/entrypoint.sh /bin…" 35 minutes ago Up 35 minutes 5140/tcp, 127.0.0.1:24224->24224/tcp unms-fluentd

Ubiquiti Employee
Posts: 3,006
Registered: ‎09-08-2017
Kudos: 1151
Solutions: 211

Re: UNMS Container IP Issues - No access to GUI post install

@gh0stwr1terX Hello Justin. The '0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp' is intended. It is a mapping to the localhost. All your containers are running so everything seems to be all right. Can you please describe with more details what does it mean 'No access to GUI'? Do you get a blank screen or some error? Also if you send me your UNMS support info I will be able to tell you more. You will need to download the files manually from '/home/unms/data/logs'. Please, send the files to my email radek.skrivan(at)ubnt.com and include URL of this thread in the message.

UBNT_Alternate_Logo.png
UNMS Support - If you want to report an issue please use this guide.

Check out our ever-evolving Help Center for answers to many common questions!

New Member
Posts: 44
Registered: ‎11-22-2017
Kudos: 9

Re: UNMS Container IP Issues - No access to GUI post install

[ Edited ]

Thanks for replying so fast @UBNT-Radek. I ended up canning the installation altogether after rethinking my long term management strategy. I manage multiple Unifi sites from a single Unifi Controller I host in the Cloud. I was hoping to tinker with UNMS for one ER-8 device that is at one of my sites. My overall thought process after I started building the UNMS server was 'do I really need a whole new server for one device'? lol My thoughts right now are that I will just continue to manage it as a standalone device and eventually replace it with a USG Pro so I can keep that single pane of glass management solution.

On that note, after checking out the UNMS roadmap page, is there any chance that the Unifi Controller will be replaced by UNMS, allowing UNMS to do the same things for the Unifi product line as the Controller does today? My thought here is as my client base grows I don't want to have to have to different 'management' servers if I end up using two different product lines from UBNT. It would make things a ton easier to use one of these over the other, and then integrate which ever one wins into UCRM for client billing and management automation.

Ubiquiti Employee
Posts: 3,006
Registered: ‎09-08-2017
Kudos: 1151
Solutions: 211

Re: UNMS Container IP Issues - No access to GUI post install

@gh0stwr1terX  Hello Justin. There are no plans to replace the UniFi controller with UNMS. There will be an option to quickly switch form UNMS to UniFi controller in case a UniFi network is present in the topology, though. 

UBNT_Alternate_Logo.png
UNMS Support - If you want to report an issue please use this guide.

Check out our ever-evolving Help Center for answers to many common questions!

Reply