Pixelblaze Discovery Issue: Chrome vs. Safari Behavior

Troubleshooting
1

I’m having an issue with the Pixelblaze Discovery service that behaves differently depending on the browser.

Using Chrome:
Pixelblaze Discovery works and shows the Pixelblaze devices on my network, including their IP addresses. However, when I click on a device to access it, Chrome returns the following error:

This site can’t be reached
http://192.168.68.103/ is unreachable.
ERR_ADDRESS_UNREACHABLE

Using Safari:
Pixelblaze Discovery does not detect any devices and displays:

“No Pixelblaze controllers have registered yet.”

However, if I manually enter the IP address that was shown in Chrome’s Pixelblaze Discovery page, Safari connects to the Pixelblaze successfully.

So, in summary:

  • Chrome can discover the Pixelblaze, but cannot connect to it.

  • Safari cannot discover the Pixelblaze, but can connect to it manually using the IP address.

Has anyone encountered this issue or have any suggestions for what might be causing it?

Ideally, I would like Pixelblaze Discovery and device access to work normally in either browser. I’ve been trying to troubleshoot this on my own for several months without finding a solution.

Any help would be appreciated.

2

This can happen if you ever deny chrome access to local networks, even on accident. There’s some kind of bug with some versions where you can’t even fix it properly in system settings → privacy and security → local network. Chrome shows up multiple times. There was some way to nuke all of that for an app, then it re-prompts you. I forget exactly! But it is a weird interaction with macOS permissions system. Not PB specific but has hit me before!