Unifi Port 8080 Is Used By Other Programs Startup Failed Due



  1. Unifi Controller Error Port 8080 Is Used By Other Programs

Unifi controller startup failed windows, Jul 03, 2020 Fix: Unifi Controller Startup Failed If the issue is with your Computer or a Laptop you should try using Restoro which can scan the repositories and replace corrupt and missing files. This works in most cases, where the issue is originated due to a system corruption. ERROR launcher - Port 8080 is used by other programs. Change the ports used by UniFi Network Controller, as seen in this article: UniFi - Changing Default Ports for Controller and UAPs. Java Incompatibility. Issue: Currently, Java 9 is not supported for the UniFi Network Controller. Please use Java 8. Can't start UniFi Controller - port 8080 used by other programs Okay, so this is kind of a messed up one. I googled this issue and in most sources I've read it seems that java is using port 8080 and the most straight forward solution is to end task the java process tree. In my case, port 8080 is used by PID 4, which is system. Unifi Port 8080 Is Used By Other Programs Startup Failed Due. 8080 Is Used By Other Programs Startup Failed; Unifi Port 8080 Is Used By Other Programs. Router Security Checklist. If you are using a router that supports WPS, then check to see if it can be turned off. There are two aspects to this. When the security issues with WPS first came.

ProgramsStartup

Red Squirrel

[H]F Junkie
Unifi controller error port 8080 is used by other programs

Unifi Controller Error Port 8080 Is Used By Other Programs

I used to have a Windows VM for the controller software which was kinda a pain and during network changes I just got rid of it with intention of looking into what it would take to run it in Linux. So today I did just that and found a tutorial and download link for a Linux version of the software. I got it working and can login to it and everything. It's version 3.2.10.
I have a single AP, with potential plans to add another as I have 2 spares. They are version 1.2.3.360 which I'm guessing is probably too old. When I try to adopt the AP, it just eventually goes to 'Disconnected'. 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. I can also telnet to port 22 of the AP from the controller host.
Some interesting stuff going on in the logs (on the AP itself). I tried to force the inform url to change, but it's like if it's resolving it wrong.

rohan.loc is 10.1.1.5 but at one point it's trying to go to http://unifi:8080/inform but then it tries to go to http://10.1.1.14:8080/infom. I can't recall what .14 is but think that's the old server. I did a cleanup in my DNS a while back so the reverse for it no longer works, otherwise I could know for sure.
I also tried setting to port 8080, as I think that's actually the proper port for the inform protocol. This is going beyond what any documentation really talks about so kind of grasping at straws.
Oh and to clarify the hostname resolves OK on ap. I just got home from night shift expecting my WiFi to be down but its still working so I think the restore command did not fully restore to factory. I'll play with it more after sleep but open to suggestions.