Reply
New Member
Posts: 2
Registered: ‎03-02-2017

Re: Cannot log in to Cloud Key WebUI

I cannot get this to work. I SSH into the cloudkey and it asks for "Login as:" I've tried every combination:

 

user-ubnt

pass-ubnt

user-root

pass-ubnt

 

I get "Access Denied" every single time, so I can't even try to fix this. Any help would be much appreciated. 

New Member
Posts: 9
Registered: ‎11-22-2016
Kudos: 4
Solutions: 1

Re: Cannot log in to Cloud Key WebUI

I had the same problem just after the update to 0.6.  I had updated the firmware as I've done before, and after that I couldn't log in to manage the CK... but I could log in to the controller portion.  After noticing this thread I was able to finally get in using "root" and "ubnt".  I was then able to reset my username and password for it.

 

However, at some point prior to finding that login info and getting everything working, I had also decided to tell it I wanted to reset it.  Well, that command queued up (I guess because of the permissions issue it didn't apply, because it definitely didn't reset after I issued the command) and once I reset the user/pass back to my original, it then reset my CK Man Tongue  Thankfully I had saved a backup just prior - but still this was quite the messed up situation.

 

I hope this gets resolved and fixed in a future update.  My set up is just for home use, but if this was for an enterprise config, I'd be very frustrated!

New Member
Posts: 2
Registered: ‎03-02-2017

Re: Cannot log in to Cloud Key WebUI

In my situation this is a test bed for our future sites and its not looking good. We were excited about 2 weeks ago and now this.. this couldn't have been the most idiotic move on ubiquities part. Most companies use this for remote sites. 

Member
Posts: 139
Registered: ‎12-06-2016
Kudos: 4
Solutions: 2

Re: Cannot log in to Cloud Key WebUI

Fortunately i came across this thread while post a new topic. This is still an unresolved issue in 0.61 and requires manual intervention.

 

 

Regular Member
Posts: 453
Registered: ‎01-08-2015
Kudos: 45
Solutions: 2

Re: Cannot log in to Cloud Key WebUI

Yes, I am stll having the same issue here also.....

 

Man Sad

Member
Posts: 139
Registered: ‎12-06-2016
Kudos: 4
Solutions: 2

Re: Cannot log in to Cloud Key WebUI

The fix does resolve the issue @doc2485 have you implemented it?
Regular Member
Posts: 453
Registered: ‎01-08-2015
Kudos: 45
Solutions: 2

Re: Cannot log in to Cloud Key WebUI

Yes I did do both of those commands on SSH... still does not connect via the cloud.

 

Man Sad

Capture99.JPG
Member
Posts: 139
Registered: ‎12-06-2016
Kudos: 4
Solutions: 2

Re: Cannot log in to Cloud Key WebUI

Seems your error maybe different to the on discussed in this thread. Have you generated the report?

Are you able to still SSH into your cloud key and are all your devices still reporting to your cloud key controller? No corruptions on your CK/SD card?

Member
Posts: 139
Registered: ‎12-06-2016
Kudos: 4
Solutions: 2

Re: Cannot log in to Cloud Key WebUI

I recall strange errors in older versions of the controller.
Regular Member
Posts: 453
Registered: ‎01-08-2015
Kudos: 45
Solutions: 2

Re: Cannot log in to Cloud Key WebUI

Yes I can SSH in fine and use the dashboard cloud to remote in on the ip address....but not using the "launch using cloud" button....

 

Man Sad

 

 

New Member
Posts: 5
Registered: ‎11-13-2016

Re: Cannot log in to Cloud Key WebUI

Hm, very unfortunate and that's damaging all the good reputation of Ubiquity and, to be honest, can't recommend it anymore as I see, many users seem to have the same issue and nobody at Ubiquity seems to find a solution.

 

To me, this problem happens after updating to Firmware 0.6.1. After that, I was no longer able to login to the WebUI of the Cloud Key or use the unify controller anymore. When trying to login to either of those, I get a timeout error in the browser.

 

Here is what I found with a particial solution:

 

- Not sure if the ssh / user-right thing was necessary. I did it but it didin't solve the issue

- Fortunately I am still able to ssh into cloudkey

- I checked the log files and found (as expected) timeout errors in /ver/log/nginx/nginx.log

 

The issue sees to be the unifi service.

 

If I do

 

service unifi stop

service nginx restart

 

I can now again access the WebUI and access and configure the Cloudkey.

 

However, as expected as the service was stopped, I can't manage my devices using the Controller.

 

A reboot doesn't help and brings back the previous situation.

 

The box sais, I am using Version 5.4.11 of the controller software and 0.6.1 of the cloudkey firmware.

 

I might be able to run a separate controller software on a PC but that's not what I want and why I purchased CloudKey.

 

I will further investigate and let you know once I make some more progress.

 

New Member
Posts: 5
Registered: ‎11-13-2016

Re: Cannot log in to Cloud Key WebUI

Update:

 

when monitoring the server log by

 

tail -f /srv/unifi/logs/server.log

and starting the unifi service by

service unifi start

 

I see the folloging log:



[2017-04-07 10:31:15,334] <launcher> INFO  system - ======================================================================
[2017-04-07 10:31:15,342] <launcher> INFO  system - UniFi 5.4.11 (build atag_5.4.11_9184 - release) is started
[2017-04-07 10:31:15,343] <launcher> INFO  system - ======================================================================
[2017-04-07 10:31:15,368] <launcher> INFO  system - BASE dir:/usr/lib/unifi
[2017-04-07 10:31:15,417] <launcher> INFO  system - Current System IP: 192.168.1.5
[2017-04-07 10:31:15,419] <launcher> INFO  system - Hostname: UniFi-CloudKey
[2017-04-07 10:31:15,615] <launcher> INFO  system - UniFi Cloudkey, UUID = 0222ae2a-e5d2-5d87-9b5d-593332315969
[2017-04-07 10:31:15,618] <launcher> INFO  system - Setting LED status to INITIALIZING
[2017-04-07 10:31:16,525] <launcher> INFO  db     - waiting for db connection...
[2017-04-07 10:31:17,027] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117
[2017-04-07 10:31:18,976] <db-server> ERROR system - [exec] error, rc=100
[2017-04-07 10:31:18,977] <db-server> INFO  db     - DbServer stopped
[2017-04-07 10:31:23,273] <db-server> ERROR system - [exec] error, rc=100

 

...

 

So it seems, the mongodb connection is the issue.

 

However, the log file  /var/log/mongodb/mongodb.log  doens't log anything while starting the unifi service but I noticed the following line:

 

Fri Apr  7 10:32:55.523 [initandlisten] waiting for connections on port 27017

 

so mongodb is listening to port 27017 and not 27117 as in the server.log file. So I changed the port in /etc/mongodb.conf to 27117. Now, I get indeed logs in the mongodb log file but this is now, what's happening after starting the unifi service:

 

Fri Apr  7 10:41:31.602 [initandlisten] MongoDB starting : pid=10620 port=27117 dbpath=/var/lib/mongodb 32-bit host=UniFi-CloudKey
Fri Apr  7 10:41:31.602 [initandlisten]
Fri Apr  7 10:41:31.602 [initandlisten] ** NOTE: This is a 32 bit MongoDB binary.
Fri Apr  7 10:41:31.602 [initandlisten] **       32 bit builds are limited to less than 2GB of data (or less with --journal).
Fri Apr  7 10:41:31.603 [initandlisten] **       See http://dochub.mongodb.org/core/32bit
Fri Apr  7 10:41:31.603 [initandlisten]
Fri Apr  7 10:41:31.603 [initandlisten] db version v2.4.10
Fri Apr  7 10:41:31.603 [initandlisten] git version: nogitversion
Fri Apr  7 10:41:31.603 [initandlisten] build info: Linux hartmann 3.16.0-0.bpo.4-armmp-lpae #1 SMP Debian 3.16.7-ckt4-3~bpo70+1 (2015-02-12) armv7l BOOST_LIB_VERSION=1_55
Fri Apr  7 10:41:31.604 [initandlisten] allocator: system
Fri Apr  7 10:41:31.604 [initandlisten] options: { bind_ip: "127.0.0.1", config: "/etc/mongodb.conf", dbpath: "/var/lib/mongodb", journal: "true", logappend: "true", logpath: "/var/log/mongodb/mongodb.log", port: 27117 }
Fri Apr  7 10:41:31.620 [initandlisten] journal dir=/var/lib/mongodb/journal
Fri Apr  7 10:41:31.621 [initandlisten] recover : no journal files present, no recovery needed
Fri Apr  7 10:41:31.687 [initandlisten] waiting for connections on port 27117
Fri Apr  7 10:41:31.688 [websvr] admin web console waiting for connections on port 28117


Fri Apr  7 10:42:24.674 [initandlisten] connection accepted from 127.0.0.1:60462 #1 (1 connection now open)
Fri Apr  7 10:42:24.675 [initandlisten] connection accepted from 127.0.0.1:60463 #2 (2 connections now open)
Fri Apr  7 10:42:24.952 [initandlisten] connection accepted from 127.0.0.1:60465 #3 (3 connections now open)
Fri Apr  7 10:42:24.956 [initandlisten] connection accepted from 127.0.0.1:60466 #4 (4 connections now open)
Fri Apr  7 10:42:24.963 [conn3] terminating, shutdown command received
Fri Apr  7 10:42:24.963 dbexit: shutdown called
Fri Apr  7 10:42:24.964 [conn3] shutdown: going to close listening sockets...
Fri Apr  7 10:42:24.964 [conn3] closing listening socket: 9
Fri Apr  7 10:42:24.964 [conn3] closing listening socket: 10
Fri Apr  7 10:42:24.964 [conn3] closing listening socket: 11
Fri Apr  7 10:42:24.964 [conn3] removing socket file: /tmp/mongodb-27117.sock
Fri Apr  7 10:42:24.964 [conn3] shutdown: going to flush diaglog...
Fri Apr  7 10:42:24.964 [conn3] shutdown: going to close sockets...
Fri Apr  7 10:42:24.965 [conn3] shutdown: waiting for fs preallocator...
Fri Apr  7 10:42:24.965 [conn3] shutdown: lock for final commit...
Fri Apr  7 10:42:24.965 [conn3] shutdown: final commit...
Fri Apr  7 10:42:24.966 [conn3] shutdown: closing all files...
Fri Apr  7 10:42:24.966 [conn3] closeAllFiles() finished
Fri Apr  7 10:42:24.966 [conn3] journalCleanup...
Fri Apr  7 10:42:24.967 [conn3] removeJournalFiles
Fri Apr  7 10:42:24.969 [conn2] end connection 127.0.0.1:60463 (3 connections now open)
Fri Apr  7 10:42:24.969 [conn1] end connection 127.0.0.1:60462 (3 connections now open)
Fri Apr  7 10:42:24.986 [conn3] shutdown: removing fs lock...
Fri Apr  7 10:42:24.986 dbexit: really exiting now

 

so mongodb is dead now and the unifi service reports again a db error.

 

so that's not the solution but it's pretty clear that the problem has to do with the mongodb database connection. Maybe somebody has a clue after reading this - hopefully !

 

 

 

 

Member
Posts: 139
Registered: ‎12-06-2016
Kudos: 4
Solutions: 2

Re: Cannot log in to Cloud Key WebUI

Maybe not helpful but are you able to do a restore from your last backup?
New Member
Posts: 5
Registered: ‎11-13-2016

Re: Cannot log in to Cloud Key WebUI

[ Edited ]

Unfortunately not for two reasons:

 

1) In order to be able to restore, I will have to run the unifi controller software, which is, what is currently not working

 

2.) So I will have to do a clean installation of the CloudKey and as I didn't do a backup right before the update (sigh) I am not sure what's missing when restoring.

 

I just created a support ticket. They already responded but with standard suggestions so I asked them to read my support ticket (what they obviously didn't do) and rethink their answer.

 

Meanwhile, I am pretty sure that one of the configuration files have been overwritten during the update process as one (the unifi file) uses port 27117 and the mogodb file uses 27017 which won't work.

 

I have just installed the older firmware 0.6.0 again which hasn't made any difference.

 

I was using the CloudKey out of the box a few months ago. I just started it, installed all available updates via the user interface then I configured it and was happy until today.

 

I never ssh'ed into the box before so it's definitely their false.

 

Very unfortunate.

 

 

 

Member
Posts: 139
Registered: ‎12-06-2016
Kudos: 4
Solutions: 2

Re: Cannot log in to Cloud Key WebUI

I recall reading on here another post which referred to the same port errors you mention and I can't put my finger on it as I'm on the mobile, but when I had an issue which was stopping unify running I was doing a general search on mongodb errors which me required to delete two files in the ace folder (don't quote me one that) local.ns0 or something like that as they had. It's been zeroed. This may lead to nowhere and I don't want to give you false hope if Ive gone off on a tangent from the original problem.
New Member
Posts: 5
Registered: ‎11-13-2016

Re: Cannot log in to Cloud Key WebUI

[ Edited ]

Thanks. I already did that. I also did a db.repairDatabase() on both the ace and ace.start databases which all repoted back a good database. But thanks for the hints.

 

I will keep you updated.

 

New Member
Posts: 5
Registered: ‎11-13-2016

Re: Cannot log in to Cloud Key WebUI

I am finally back up and running - after 11 hours !

 

Support responded but only with standard questions and they didn't even read my mail - disappointing.

 

What I finally did was a complete CloudKey factory reset but even then, I immediately had the same issue as before after finishing the first configuration on the web ui.

 

What has finally helped was a manual install of the 0.6.0 firmware via ssh and the following command:

 

ubnt-systool fwupdate https://dl.ubnt.com/unifi/cloudkey/firmware/UCK/UCK.mtk7623.v0.6.0.9b60a01.170208.1122.bin

 

Then, I did another firmware reset (a firmware reset seem to keep the current firmware version to my surprise).

 

After that, I was able to start the CloudKey Web UI as well as the Controller Web UI.

 

The Controller Web UI told me that I have to update the Firmware to 0.6.1 and so I did (expecting the worst). But this time, all went well. Version 0.6.1 is now up an running fine.

 

Last time I was using the CloutKey Web UI to download and install this 0.6.1 update. Maybe that has been the root cause of my messed up day.

 

Fortunately, I had autobackup switched on so I had a configuration backup on the sd-card of the CloudKey (EVERYBODY SWITCH THIS ON!)

 

However, to use this backup, I had to unplug the sd-card, mount it on my linux PC to be able to select the unf backup file on the controller web ui for restoring (maybe there is an easier way, don't know).

 

(This step also showd me that the sd-card only contains the backup files. I was under the impresseion - and even read it somewhere here - that the card also contains other files such as the database etc.)

 

After this FINALLY all is now back to normal.

 

I have just ordered another CloudKey as future fallback device. I don't want to have this again.

 

I am pretty sure that this was a bug in the update process or the update files. That was really the first time I had a problem with the Ubiquiti products. So far, everything went well. I hope that my good impressions of the hard and software is no wrong assumption. I can't imagine what would have happened when I would have to re-configure everything from the beginning. Or if such an issue would have happened to the USG in my network.

 

Anyway, a lost day but all is good now.

 

 

 

New Member
Posts: 6
Registered: ‎04-10-2017
Kudos: 5

Re: Cannot log in to Cloud Key WebUI

I found I could log in using "root" and the password I had set.

Emerging Member
Posts: 43
Registered: ‎01-20-2017
Kudos: 1
Solutions: 2

Re: Cannot log in to Cloud Key WebUI


@UBNT-APieper wrote:

For anyone who's encountering difficulties logging in on WebUI in both cases we have worked with the resolution has been the same. The issue appears to be arising from incorrect SUID account privileges on the UCK system. This can be confirmed by sshing into the CloudKey and running the following command:

ls -l /usr/bin/sudo

 

This should return output similar or identical to the following if the same root cause: 

-rwxr-xr-x 1 root root 106820 Jan 10 2016 /usr/bin/sudo

 

To resolve this and ensure that any suid issues are not causing the issue, run the following command: 

chmod u+s /usr/bin/sudo 

 

Re-test logging in to the WebUI and confirm the issue is resolved. 

 

We are still investigating the root cause of why this issue was encountered by some. 

 

@jba256 Can I get you to run this on your Cloud Keys? Can you confirm this resolves it? 

 


Used this to resolve probelm today. Thank you!

Regular Member
Posts: 453
Registered: ‎01-08-2015
Kudos: 45
Solutions: 2

Re: Cannot log in to Cloud Key WebUI

I did this 2 weeks ago...no luck on my side.... same issues here going on each few days...

 

Man Sad

Reply