So I believe this is the most straight forward method. `8443` and `8080` are both on the allowed ports for Cloudflare, but without a tunnel that would require opening the ports and pointing the subdomain at your public IP address (something I pondered with Duck DNS before deciding to try this first). If someone has another, perhaps cleaner solution, I'm all ears. But it's the same concept.Įnd result is I now have: :8443 and :8080 both going to the same internal IP. He uses it for a totally different internal application. So maybe it is possible using a different method.īut the solution I found after rewatching DB Tech ( I recall seeing multiple Cloudflare tunnel tutorials on channels I watch recently, but this one was the first I rediscovered) was to simply create a second subdomain with `:8080` and things seem to be working. I recall trying to manually set up tunnels with the command line last year and failing. So when you try to go to ` :8080/inform` you just get a redirect and attempt to access the machine on `8443`. However the subdomain you set up in Zero Trust usually includes the port when filling out the "setup wizard." There's no way to add other ports to the same subdomain in the interface. It's not too difficult to set up a tunnel allowing access to the machine where your Unifi controller is located internally. I found this post while dealing with what I believe is the same issue. Contact your ISP for assistance.To give some clarity to the first two responses and hopefully provide a solution. If the UniFi Network Application (often running on a Cloud Key) is running behind a remote gateway, but the gateway has a private IP address (it is double NAT'd), this will not work.If the UniFi Network Application (often running on a Cloud Key) is running behind a remote gateway and the gateway has a public IP address, then you must Port Forward TCP 8080 from the gateway to the IP address associated with the Cloud Key.If you are using Official UniFi Hosting or your UniFi Console has a public IP address, ensure your local firewall/gateway allows your unadopted UniFi device to communicate with it over TCP Port 8080.If the UniFi application and unadopted device are on separate VLANs behind the same local gateway, ensure inter-VLAN routing is enabled and TCP Port 8080 is not blocked on the firewall.This must be addressed differently depending on the location of your UniFi Network Application: If you are experiencing difficulty, then your UniFi device and UniFi Network application likely cannot communicate over TCP Port 8080. Fully Qualified Domain Name (FQDN): Troubleshooting.There are two methods of specifying the machine running the Network Application: You'll need to configure your DNS server to resolve unifi to your remote UniFi Network Application. Note: If you are using Official UniFi Hosting, you can visit your UniFi Network dashboard and click Copy Inform URL to paste into the command above.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |