When i set wireless access point Unify Ubiquiti, i found this problem with output problem, you can look picture : Vso downloader 3 key generator.

• Unifi Port 8080 Is Used By Other Programs Startup Failed To Be
• Unifi Port 8080 Is Used By Other Programs Startup Failed Interview
• Unifi Port 8080 Is Used By Other Programs Startup Failed Attempts

How to solved this problem ? you can try a litle solution with edit port, follow this step.

At one point it was also going to 'failed'. I went on it and did 'syswrapper.sh restore-default'. How do I go about making this work again? I'm guessing I probably have to manually update the firmware? Also just to confirm, from the AP I can telnet into port 8443 and 8080 of the controller, so I know the tcp connectivity is ok. How to fix Unifi Controller error port 8080 used by other programsHow to Repair Unifi Controller error port 8080 used by other programs. Mac OS x 10.8.3, running a Java’s web application on Tomcat, port 8080. Users from same network are able to access my web server via port 80, but failed on port 8080. Is there a firewall setting blocked the incoming connection via port 8080. The simplest solution is turn off your Firewall.

1. Right click from shortcut unify controller and then properties, after that open file location. Find file with name file system.properties under directory data. How to download a song from youtube.

2. Open that file with text editor, you can look output when open this file

3. Change default port 8080 to port 8083, and remove hastag code like this

4. After that you can try restart your computer and try start unify contoller.

5. Finish

Baca Juga !!

Package Details: unifi 6.0.41-1

Package Actions

• View PKGBUILD / View Changes

Dependencies (3)

• fontconfig(fontconfig-srb, fontconfig-infinality-ultimate, fontconfig-infinality, fontconfig-git, fontconfig-ubuntu, fontconfig-infinality-remix)
• mongodb(mongodb34-bin, mongodb-bin-3.6, mongodb-3.4, mongodb-bin-3.2, mongodb-3.6-bin, mongodb-bin-4.0, mongodb-bin, mongodb-shell-bin)
• java-runtime-headless=8 (jdk5, tuxjdk, jre7-openjdk-headless-infinality, java-8-openjdk-shenandoah, jre8-openjdk-headless-infinality, jdk9, jre9, jdk-devel, jre10, jdk8-arm64, jdk6, jdk12-openj9-bin, zulu-12-bin, jre6, jre12, jdk8-openjdk-dcevm, server-jre, jdk8-arm, jdk13-openj9-bin, jdk9-openj9-bin, jdk10, jdk11-openjdk-dcevm, jre8-openjdk-jetbrains-headless, jre8-openjdk-shenandoah-headless, jdk10-openj9-bin, jdk14-openj9-bin, sapmachine-jdk-bin, jdk7, jre7, jdk8-j9-bin, jre14, java-openjdk-bin, jre, jdk-openj9-bin, jdk-arm, jdk-adoptopenjdk, jdk11-adoptopenjdk, liberica-jdk-full-bin, jdk8-jetbrains, amazon-corretto-11, liberica-jdk-8-full-bin, liberica-jdk-11-bin, liberica-jdk-11-full-bin, liberica-jdk-11-lite-bin, liberica-jre-11-bin, liberica-jre-11-full-bin, liberica-jre-8-full-bin, amazon-corretto-8, jdk8, jre11, jdk7r1-j9-bin, jdk7-j9-bin, zulu-15-bin, zulu-14-bin, zulu-13-bin, jre8, jdk-jetbrains, jre8-adoptopenjdk-headless, jre11-jetbrains-headless-imfix, jre-jetbrains, zulu-embedded-jdk11, jdk-bcl, jre-bcl, jdk8-openj9-bin, jdk11-openj9-bin, zulu-11-bin, zulu-8-bin, amazon-corretto-15, jre-openj9-headless, java-openjdk-ea-bin, java-openjdk-loom-ea-bin, jre-openjdk-headless, jre11-openjdk-headless, jre7-openjdk-headless, jre8-openjdk-headless)

freswa commented on 2019-10-30 11:50

We are on Stable with this Package. Please flag out-of-date only if the Version provided with this package does not match the version under 'Stable' in this link: https://help.ubnt.com/hc/en-us/articles/360008240754#1

Scimmia commented on 2020-11-20 03:45

Max-P,a few notes on your backup and restore instructions.

You need mongodb-tools.You have /usr/lib a few times when you mean /var/lib.

Max-P commented on 2020-11-19 21:17

For those that have issues starting Unifi after updating MongoDB: you may need to rebuild/repair the database for it to work again. Something with the WiredTiger database backend versions. I'm currently running on mongodb-bin-4.4.1-1 with no problems and Unifi controller is working perfectly.

sudo -u unifi -g unifi mongod --repair --dbpath /var/lib/unifi/data/db

Alternatively, you can do a backup and restore on a fresh DB:

1. Restore an older version of MongoDB that was previously working
2. Start mongod manually: sudo -u unifi -g unifi /usr/bin/mongod --dbpath /usr/lib/unifi/data/db --port 27117 --unixSocketPrefix /usr/lib/unifi/run --bind_ip 127.0.0.1
3. Dump the database: mongodump --port 27117 -o backup-unifi-controller
4. Stop mongod (Ctrl+C in the terminal running it)
5. Upgrade mongodb
6. Make a backup of /usr/lib/unifi/data/db and delete its contents (make sure the folder exists and has the correct permissions)
7. Start mongod again
8. Restore the backup: mongorestore --port 27117 backup-unifi-controller
9. Stop mongod and start unifi normally

ZAKhan commented on 2020-11-19 12:37

Scimmia commented on 2020-11-18 21:11

eagebhart, if you actually read the output you posted, you'd see that it has nothing to do with this package.

eagebhart commented on 2020-11-18 18:45

This is not building for me. I've done an pacman -Syu, and updated my keys.pacman-key --refresh errors with a General error, could not be retrieved on the same key.

Here is the snippet of the error. I have not tried working around it yet.

:: (1/3) Parsing SRCINFO: libcurl-openssl-1.0:: (2/3) Parsing SRCINFO: mongodb-bin:: (3/3) Parsing SRCINFO: unifi-beta

:: PGP keys need importing: -> 27EDEAF22F3ABCEB50DB9A125CC908FDB71E12C2, required by: libcurl-openssl-1.0> Import? [Y/n] :: Importing keys with gpg.gpg: keyserver receive failed: General errorproblem importing keys

Or this:

sudo pacman-key --refresh-keys ──#(Wed,Nov18)─┘gpg: refreshing 121 keys from hkps://hkps.pool.sks-keyservers.netgpg: keyserver refresh failed: General error> ERROR: A specified local key could not be updated from a keyserver.

Scimmia commented on 2020-11-17 23:02

Wwe smackdown vs raw 2006 iso download. squatched, mongodb-bin provides mongodb, so the dep already works with both.

squatched commented on 2020-11-17 20:00

ZAKhan, it should be available on https://localhost:8443

If you're getting 'Unable to connect' and the unifi.service systemd unit is running, perhaps you have something like iptables blocking access on the lo interface?

squatched commented on 2020-11-17 19:53

Any chance you would be willing change the mongodb dependency to mongodb-bin? Just did a test-run and it all appears to be working just fine and not having to build MongoDB from source is such a MASSIVE boost to install/build times on my little laptop that I run the Unifi controller from. It's certainly not optimized to be a fast compiler but it's great as a Unifi controller.

Unifi Port 8080 Is Used By Other Programs Startup Failed To Be

ZAKhan commented on 2020-11-01 01:14

Unifi Port 8080 Is Used By Other Programs Startup Failed Interview

ZAKhan commented on 2020-10-22 15:36

Same issue as before . service is running but web page does not open

Unifi Port 8080 Is Used By Other Programs Startup Failed Attempts

'Unable to connect'