Is anyone else seeing the web interface drop? I can ping the unit, it is passing data etc, and generally working well. If I port scan I see port 80 is not open. If I power cycle the units (both exhibit this issue) they work and show port 80 open. After a few minutes they are closed again. Is this normal? I have tried them on static 192.168.1.x/24 addresses and also with DHCP from my router. Same with both.
top of page
To see this working, head to your live site.
12 Comments
bottom of page
Hello everyone! The significance of website design cannot be overstated when it comes to advancing any business. Additionally, a resource like royal flush images can prove highly beneficial. It offers a wealth of intriguing and practical resources for crafting an appealing web design.
Funny how goCoax can't seem to read and respond to these on-going posts.
Same issue on my UDM (not -Pro). My master goCoax MOcA 2.5 WF-803M adapter (w/current firmware version 1.06) is on a static local IP but cannot see it in my UDM Clients list nor access via Web browser (locally, via direct IP address). Otherwise, all seems to be OK with the MOcA connections/node. Pointers/advice welcome, pleeeeez?
It may have to do with the firmware of the MoCA chip. Right now, MaxLinear seems to be the only supplier of MoCA 2.5 chips. As far as I know, a majority of MoCA adapters on market uses the same MoCA chip.
I am on a Linksys Velop mesh currently before the swap to DM Pro and it has done it from the first day. As you say the performance is great. I am thinking about buying another brand to see if it does this also. If not then I only have three deployed, I can think about getting rid of them and moving to something else that works better.
Bad that they didn't follow up.
On the DM Pro, the unit drops off as a client consistently. It's pingable but annoying. Bigger problem is that in a professional enviornment where's there's multiple 'admins', not having a visible client is particularly problematic and quickly becoming a deal-breaker. Not being able to administer via the browser is really bad. Doesn't matter how good the product is if you can't support it. Hopefully somebody is watching...it's not a UBNT problem.
I never got a resolution. I am in the process of switching over to a unifi DM pro and was hoping that would clear the issue up. It is only a nuisance, the adaptors works fine and if I needed to change something I can alway re-power them and log in. They do show up on a nescanner. Once I get the network swapped to DM Pro I will report back here. Good to know it is not just me.
I'm curious as to what happened here. My unit dissapears from my Ubiquiti client list and is not accesable by browser. I can only see it in a lan scan. I have given the unit a static address. The unit functions flawlessly otherwise and performance is outstanding..
Configure port forwarding on your router. Instructions vary depends on your router and ISP.
what would I need to do to set that up?
Hello Gregory,
Could you setup a remote check for us?