Can't Connect Via Apex.Local
 

I can connect to Apex and control things via Fusion, both app on iPhone and "direct" online, so this tells me that my Apex is "talking" to the Internet though my router/modem. But I can't connect more directly via Apex.local. Any thoughts re why that would be the case?

I did cycle power on router and Box (firewall) the other day, and had unplugged all Verizon devices in the house to prevent kids from accessing internet/TV (rough day......), so devices have needed to reconnect to internet. I've also cycled power to Apex, and as noted above it's "talking" to the router.

Obviously, I can do what I need to do with the device, but just wondering what would be preventing more direct connection via Apex.local.

I had this happen before. Take out AC Plug from router then wait 10 minutes and plug back in router. Go To Router Screen and see if your apex is being recognized after that.

Go into Apex Fusion and click on the expand icon. Click the network icon and take note of the IP Address listed. In your web browser type http://<ip address> replacing the <..> with the ip address in Fusion. You router is not performing correct name resolution but the Apex is online.

took me right in, even without including http:// before the ip address.

Any idea why router won't resolve? It worked before. I wonder if it has anything to do with the Bitdefender Box I have installed, though it did work with that present previously.......

In any event, I set a bookmark to the page after accessing it via the ip address.

local name resolution is quirky. Th router has a builtin DNS but sometimes name registration fails or gets old. You can reboot both the router and the APEX and it would likely fix itself.

Name resolution of .local host names does not use the router or DNS. It uses other protocols.

There are two likely reasons that http://ip-address works but http://apex.local does not work:

1. You are using an Android device. Android does not have built-in support for resolving .local hostnames.

2. The Apex’s name has been changed from the default of “apex”. If so, you must use the Apex’s actual name. For example, if your Apex has been renamed to Reef120, then you need to use http://reef120.local

Nope. Neither 1 nor 2 is true.

Further wrinkle: I can connect using Apex Local on Safari on iPhone, i.e., talking to the router wirelessly, but not via the desktop pc (wither Firefox of IE)...... sigh! Yes, I can access via the ip address, as noted above, but the engineer in my likes to figure out why something isn't working quite the way it's supposed to

Is the apex set to static or DHCP?
Is the 3rd octet in the apex IP consistent with the 3rd octet in local LAN IP scheme?
3rd octet being XXX in ie: 192.168.xxx.1

Apex IP address is XXX.YY.1.ZZZ

I don't know how to determine the local LAN IP. Per router settings, IP address for the Ethernet/coax connection is XX.YYY.223.ZZ; is THAT the local LAN IP?

apex is set for DHCP

WWW facing or your computers facing IP?

.223 can be class A, B or C so I don’t know

But if your local area network (LAN) is in an xxx.xxx.223.xxx scheme and your 3rd octet on your apex is anything but .223, you won’t be able to connect locally without more advanced routing and/or LAN segments