10-07-2014 11:31 AM
unfortunately it doesn't work even BETA is activated ..
Three are only two Apps:
mFi controller and
UniFi controller ... no MongoDB.
And - if I click on UniFi controller than an error message asks to install MangoDB 2.0.0 first :-(
10-07-2014 11:43 AM - edited 10-07-2014 11:44 AM
The DS214+ does not have an x86 CPU, it has a dual-core ARM-based CPU; I'm not sure you'll be able to run Java JRE on that CPU and will be unable to install MongoDB.
But I have been successful running UniFi and mFi on both an DS1512+ and DS713+, versions 3.2.1 and 4.
10-07-2014 11:57 AM
That's a pitty indeed... you should have bought the 214play... then you were good.
You could always run controllerless, and only start the controller when you want to make changes (unless you're in the need for a guest portal, then you need a controller).
10-07-2014 12:00 PM
I posted in the Synology thread awhile back about this issue, but since that thread hasn't seen much traffic I'll post here as well.
I'm using a DS1813+ running DSM 5.0-4493 Update 7 | Java Version 1.7.0_67 | MongoDB 2.4.8 | mFi Controller 2.0.24
Things work well with MongoDB 2.4.8, but if I try to use MongoDB 2.6.4 I cannot adopt any devices. Anyone else having this issue?
10-08-2014 01:41 PM
Could anybody try to download and install this http://synology.acmenet.ru/packages/MongoDB-arm-2.6.4-beta-1.spk package on Synology with ARM CPU? Like DS214+. Not x86 or x64!!!
Install, then ssh to your Synology and just try to run this commands:
MongoDB shell version: 2.6.4
connecting to: test
2014-10-09T00:37:00.325+0400 warning: Failed to connect to 127.0.0.1:27017, reason: errno:111 Connection refused
2014-10-09T00:37:00.327+0400 Error: couldn't connect to server 127.0.0.1:27017 (127.0.0.1), connection attempt failed at src/mongo/shell/mongo.js:146
exception: connect failed
NAS:~# /volume1/@appstore/MongoDB/bin/mongo --version
MongoDB shell version: 2.6.4
NAS:~# /volume1/@appstore/MongoDB/bin/mongod --version
db version v2.6.4
2014-10-09T00:37:17.273+0400 git version: 3a830be0eb92d772aa855ebb711ac91d658ee910
If everything will be ok, I'll publish this MongoDB release in repository.
10-08-2014 05:02 PM
to install the .spk file - no problem, sucessfully.
to run the file mango/d failed ...
via ssh from my MacBook Pro - not possible with my user data ... user = OK, password not accepted - why ever ..
via web console (via DSM) - error message ::
10-08-2014 05:23 PM
in the dsm5 now i was able to instsll the 4.2.0-beta out of respository, unfortunately it is not possible to start this service ... it seems the latest beta is not compatible ..
10-15-2014 01:11 AM - edited 10-15-2014 01:12 AM
Same here on a DS414. Installed Mongo succesfully but the Unifi Service does not want to start.
Wakko, thanks for the effort so far Getting a bit closer to running it on my Synology
11-03-2014 05:27 PM
I offer you a new version of Ubiquiti Controllers for Synology:
1. UniFi Wireless Controller (former UniFi Controller version 3.xx, for those who use the controller only to access points).
2. UniFi Controller (new UniFi Controller version 4.xx, for those who use the controller to the access points and other equipment from the UniFi Switching & Routing equipment).
3. mFi Controller (controller form mPower and mPort devices).
The main difference of the new packages:
1. Now before installing the controller does not need to be installed separately MongoDB.
2. After the upgrade DSM on Synology - no need to reinstall MongoDB.
3. Each controller contains MongoDB server version 2.2.7, which recommends by Ubiquiti.
4. During installation, you can now set the controller ports for the web-interface of the controller, as well as you can change the system ports, to prevent conflicts with other packages (eg service SABnzbd, which also uses port 8443).
5. The script for starting the controller has been rewritten, now, in the event of an error on startup, error text will be displayed on the screen.
6. All three packages can coexist on a single Synology, important not to cross the ports.
7. And finally, during the installation of new packages (as well as during migration UniFi Controller <==> UniFi Wireless Controller), you can import the previous database and logs.
Previous versions of the controllers (depending on the package with MongoDB) is now considered deprecated and will be removed from the repository. The package itself MongoDB will as before be present in the repository, but later it will be split into branches 2.2, 2.4 and 2.6.
PS. There is a great desire to make a version of controllers for Synology devices with ARM-based CPU, but unfortunately, the equipment for the tests is absent yet. See details on the web-page http://synology.acmenet.ru/
PPS. Any comments and bug reports can be sent to me at the address email@example.com
11-05-2014 04:46 AM
One thing: i've converted to The New packages in my DS713+ (both mfi and unifi 4.2.0) and All works great eccepì for The 4.2 that reverted back to 3.2.5 all unifi firmwares. Can you design some kind of way to choose live and beta channels? Unless ubiquiti will unify 3.x.x and 4.x.x we will have to stick to 3.x.x FOR betas and 4.x.x for live.
Thanks in advance.
Mauro from Italy.
Mauro from Italy
11-05-2014 04:55 AM
It's exactly what I currently do. Wait for a few hours please.
Will be four different packages:
UniFi Wireless Controller (release): 3.2.5
UniFi Wireless Controller (beta): 3.2.7-beta
UniFi Controller (release): 4.2.0
UniFi Controller (release + firmware from 3.2.7-beta): 4.2.0-beta
11-05-2014 05:31 AM
Waiting for your news
P.s. When you'll work in ARM version please Ensure compatibility with cheapest synology NAS (1 bay and J versions).
Mauro from Italy
11-11-2014 07:12 AM
I have updated to 4.2.0-141104.
The MongiDB version is: 2.6.5-141104
Java Version: 1.7.0_71
After the installation I tried to fire up the software.
I get the following error:
Port 8443 not availabe
Error. java is dead
Synology DS1010+ / Proc. Intel Atom
Any idea for that?
11-11-2014 07:17 AM - edited 11-11-2014 07:18 AM
This message mean that port 8443 is used by another application (SANnzbd, or previous deprecated version of UniFi Controller).
Try to choose another port when you installing your UniFi Controller.
11-11-2014 07:49 AM
I have replaced the port to 8445.
The install process went fine.
But the webpage with this port doesn't work.
Here is the Protokoll:
ERROR stun - Unable to start the STUN Server on 0.0.0.0:3478