Remote access not working with latest version?

[Olbrit]

Anyone else have this? Remote access was working fine, I did an upgrade to the latest SH version and now remote access just times out (Windows desktop IE, Chrome and Firefox). The port is unchanged, it says server running, etc. Do I need to downgrade?

[millenios]

I'm also having this issue since the upgrade to 5

[ryan]

It is likely that any adjustments/exceptions in firewall software you may have performed in the past will need to be re-added for Sighthound 5.0. As it is now 64 bit rather than 32 it will both appear to many security applications as a completely new program and it also exists at a different location on disk, C:\Program Files\ rather than C:\Program Files (x86)\

[Olbrit]

I went into Windows firewall and added some more .exe exclusions from the Program Files/sighthound folder in addition to the ones that Sighthound 64bit had already added. That worked. I can now use the remote view option. Thank you.

[sivart321]

I am having the same issue and didn't have luck with the firewall settings. Any help?

[HAMMERDARRELL]

I had the same issue and solved it. After upgrading to version 5.0 and discovering my phone app wouldn't work, I wasn't sure if the issue was due to a port problem on my router or a Windows firewall setting. I narrowed it down to the firewall by turning it off briefly and verified that the mobile app/remote access worked once again.

Keep in mind, all of this worked perfectly for years prior to the 5.0 upgrade. The root of the problem is that this upgrade is really a different program altogher, as it's a 64-bit application...not 32-bit like days of old. Your existing firewall rules no longer apply, but it's not obvious because you can still see the Sighthound entries in your firewall exception list.

Hopefully this solution works for others in the same situation...

- Open Windows 10 Control Panel
- Open Windows Firewall
- Select "Allow an app or feature through Windows Firewall"
- Click "Change Settings"
- Scroll down the list of Allowed apps and features and Remove anything related to Sighthound (should be 3 or 4 entries with "Sighthound" in the name). These are entries you probably installed long ago and no longer apply.
- Click "Allow another app.." and navigate to "C:\Program Files\Sighthound Video\".
- Allow 4 new apps for the 64-bit 5.0 version of Sighthound...these are Sighthound Agent.exe, Sighthound Video.exe, Sighthound Web.exe, Sighthound XNAT.exe.
- Make sure you place the checkbox in "Private" and "Public" for each of these new 4 apps.

That should do it!

[ryan]

We aren't aware of any remote access problems at the moment, so the first thing to do would troubleshoot where the connection is being lost.

* Are you able to access from the same machine using the local or internal addresses? If so this indicates that remote access is up and running as expected.

* Are you able to access via the local address from another device on the same physical network as the computer hosting Sighthound Video? If not, it indicates that something on the machine hosting Sighthound Video, such as a firewall, is blocking incoming connections to the machine.

* If both of the above are working but accessing via the external IP from a machine outside the network can't connect it indicates that the router facing the public internet is not accepting connections, or that the port forwarding may not have been mapped correctly (the port set in SV changed, the host computer IP changed and was not tracked by MAC, ...)

[ryan]

Thanks for that detailed firewall post HAMMERDARRELL

[sivart321]

Thanks for that detailed firewall post HAMMERDARRELL

Same. That worked. I think I missed one of the 4 apps when adding the firewall exceptions.

[ranger6]

My Windows 10 firewall is OFF, so thats not whats going on for me.

After updating to 5.01, I could not pull down clips / alerts with iPhone, they timed out. Was able to get to the machine via PC at the IP:PORT and get the clip to load.

I ended up restarting SH, and then it worked fine on my iPhone, so not sure what to make of it. My SH server is remote, and sometimes there can be higher latency getting to it, maybe that was it, strange that killing / restarting the SH app worked, but it did.