- #Unifi port 8080 is used by other programs startup failed due plus
- #Unifi port 8080 is used by other programs startup failed due windows
The other is TCP 8080, this is known as the "inform port", this is the web service the Unifi devices use to actually communicate with the controller. "Now, for basic functionality there are only two ports up there that matter, TCP 8443 to login to the controller itself, so web access to this needs controlled that's your admin surface PROTECT IT! What do you mean by ".and feed it the IP address of the machine running the controller?"
![unifi port 8080 is used by other programs startup failed due unifi port 8080 is used by other programs startup failed due](https://www.partitionwizard.com/images/uploads/articles/2020/10/unifi-controller-startup-failed/unifi-controller-startup-failed-9.png)
So, I've set a static DNS entry (SCS.com) and the machine hosting the controller has always been static as well. Each correlates to their respective LAN ports on the Untangle box. All internal devices look to either 10.58.xxx.xx1 (if that's the LAN they're on), or 10.25.xxx.xx1. Each is on it's own port on the Untangle box. The primary LAN is 10.58.xxx.xxx, and the secondary LAN is 10.25.xxx.xxx. In theory it shouldn't matter, but my paranoia is acting up.Ĭlick to expand.First, thanks for this! Perhaps this can be moved to a private thread? I don't want to obfuscate this data any further, it degrades the value, but I don't really want that utterly public either. Not sure why I blanked out my public IP address up there, only to leave the 3CX public name, everyone here now has the means to see my public IP address if they are bored and can do a DNS lookup. You'll have to reset them to factory if you adopted them on another controller.Īnd don't ask me about USG's, I HATE USG's, I use Untangle. Once the above is complete, your LAN 2 devices will automatically locate the controller on LAN 1, assuming of course they are actually open and available for adoption. So, wherever you set the blocks up to prevent LAN 2 from talking to LAN 1, you need to make a pin hole for traffic destined to TCP 8080, and destination address of your Unifi controller. Now, for basic functionality there are only two ports up there that matter, TCP 8443 to login to the controller itself, so web access to this needs controlled that's your admin surface PROTECT IT! The Unifi Controller uses these ports by default: Yes, DNS resolution works over the tunnel too, but the IP address is faster to type than either of the DNS names attached to my desktop. Also handy for when I use OpenVPN to connect to my home office, I can easily RDP to an easy to remember IP address. 10.10.10.125 is my desktop's internal IP all the time now.
#Unifi port 8080 is used by other programs startup failed due plus
You can see both in my configuration here:Īnd again, you want to make sure that IP address is permanent on the device it belongs to, my controller runs on my desktop, so I just kicked over to the DHCP Server tab, and clicked the add static plus next to its reservation to make the static DHCP entry. So kick over to the DHCP Server tab and make a reservation real quick if the platform is DHCP assigned. Yes, that machine needs to have a static IP because of this. You want to create a Static DNS Entry, for the FQDN discovered above, and feed it the IP address of the machine running the controller.
![unifi port 8080 is used by other programs startup failed due unifi port 8080 is used by other programs startup failed due](https://1.bp.blogspot.com/-GYYiH8g3N7c/W4b_rYEW5LI/AAAAAAAAMLo/j5imY_oGOU8V1Z0oihut3cSNzw6P0sI5wCLcBGAs/s1600/Windows.jpg)
So now back in Untangle, config -> network -> DNS Server
#Unifi port 8080 is used by other programs startup failed due windows
If you have a windows station on the IP network in question, configured via DHCP, you can verify this there with ipconfig /all.ĭNS suffix in this case is critical, because all unifi devices will look for to find their controller. It's by default, but it can be almost anything.
![unifi port 8080 is used by other programs startup failed due unifi port 8080 is used by other programs startup failed due](http://mas.txt-nifty.com/3d/images/2009/09/13/2009091311.jpg)
This should be your DNS Suffix for the network. Make a note of the domain name configured at the top. Given the two above, the first thing you do is log into Untangle, config -> network -> Hostname. 2.) Untangle again by default is the DNS server for all local networks.
![unifi port 8080 is used by other programs startup failed due unifi port 8080 is used by other programs startup failed due](https://peyanski.com/wp-content/uploads/2021/03/HA-UniFi-configuraiton.jpg)
So I assume you know where your restrictions are. 1.) Untangle by default allows all internal networks to communicate with all other internal networks, there are no restrictions. So, for starters I'm assuming two things. Well, the good news is ignorance can be fixed!