Remote Access stuck on starting

[billdickens]

I'm attempting to setup remote access, however when clicking Apply on the option window the status briefly says "Updating..." then stays forever on "Starting...".
What am I doing wrong? I'm running Windows 10 at the latest patch level and the latest Sighthound Pro release.
I have turned off windows firewall to eliminate that as a problem. I have setup port forwarding on my router for port 8848 (although I can't even access port 8848 on the sighthound server from the local network so the problem appears to be on my Sighthound server and not the router.) I have tried selecting and deselecting the "Open this port in my router" checkbox.
What username/password should I be specifying? A local username and password? Or some arbitrary made-up username and password? I've tried both; same result.

image001.png (17.85 KiB) Viewed 1825 times

[Devin]

Hello billdickens,

I'm sorry to hear you're experiencing this issue. Please submit a bug report by going to Help > Report a Problem so we can take a look at your logs. Include a link to this forum post when submitting the bug report so we know it is you.

Regards,

-Devin

[billdickens]

Thanks Devin. I've submitted a bug report.

[billdickens]

Following up on this.
The new release (3.0.2) fixed the problem; the remote service now starts. Thanks for the quick response and fix.
I forwarded port 8848 on my router and followed the advice on configuring Windows Firewall in the following forum post and remote access is now working from my iPhone. This is a very useful service.
https://www.sighthound.com/forums/topic12288

[sfbaycpa]

I had a hdd fail and reinstalled Sighthound with version 4.0 build 16721 running on Mac Sierra. Now I am receiving the same error message where the "server access" in the remore access setup is stuck on "starting". Sent in a log report. It worked fine when the OS was El Capitan.

[Devin]

Hello All,

We are aware of a bug in 4.0 which affects a small number of users on Mac OS's. We've already identified the cause and have a build with the fix in testing. This issue can be resolved by reverting to 3.0.2, but if you'd prefer to download the test build with the fix, please email us at [email protected] referencing this post and we'll send a link. We hope to release a build with the fix as soon as it's undergone adequate testing and additional fixes if needed.

Regards,

-Devin