Unifi Port 8080 Is Used By Other Programs Startup Failed Due

Red Squirrel

[H]F Junkie
Unifi Port 8080 Is Used By Other Programs Startup Failed Due

I use a Unifi appliance for my home, been running it for over a year but now there is a issue, before I rebuild it anyone know how to fix this: Suppose to show IP and interface name, I can ping it. Controller - An instance of the UniFi controller software; wirelessClient - Any wireless client connected to a UniFi wireless network # Discovery. If you need the SSL port to be free as well, use the Change Apache SSL Port option and change it to something other than 443. Click the Start Apache button and you should get a green light for a successful connection. We did look at AMPPS but it has a few problems when you change the port manually to something other that 80.

Unifi Port 8080 Is Used By Other Programs Startup Failed Due Coronavirus

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.