- Unifi Port 8080 Is Used By Other Programs Startup Failed Attempts
- 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 Version
Unifi Port 8080 Is Used By Other Programs Startup Failed Attempts
Red Squirrel
[H]F Junkie
Unifi Port 8080 Is Used By Other Programs Startup Failed To Be
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.
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.
Unifi Port 8080 Is Used By Other Programs Startup Failed Interview
![Unifi port 8080 is used by other programs startup failed to be Unifi port 8080 is used by other programs startup failed to be](https://www.kuhnline.com/wp/wp-content/uploads/2012/10/unifi-blog1.png)
Unifi Port 8080 Is Used By Other Programs Startup Failed Version
For example if port 8081 was in use you would modify the line “unifi.shutdown.port=8081” to something like “unifi.shutdown.port=8089” assuming port 8089 was not already in use. When done, leave the server some time to start all the necessary programs (2-5 min depending on your server). I will be using a freshly installed Ubuntu 14.04. I also use the nginx proxy manager. The golfing machine book download. (port 80 + 443 are open in my router to reach it) For unifi i also opened these ports: 3478,8080,8880,8843,6789,10001 I configured my domain in the nginx proxy manager unifi.domain.com with a forward to my ubuntu server with port 8443.