Remote access vs Internal access

[dwRCjCCil]

I have port forwarding enabled and have no problem accessing the camera (Foscam) thru the Android app on my phone using my external IP and the specified port, when on cellular data, but when connected to my home network wi-fi, but after starting the camera just stays at 'loading' and the camera never loads in the app. If I disable wifi on my phone, the app (Android running on Nexus 6P) loads and is accessible. If instead of the external IP /port, I substitute the internal IP + (same) port of the computer running the Sighthound software , it functions normally. Is there any setting change I can make to eliminate this problem?
Thanks for your thoughts and suggestions.

[zxcslo]

Your router doesn't support or is not configured for loopback (I think is the right term).
Not all routers support access to your local network over the internet/wan from your local network (home).

[dwRCjCCil]

Thank you for the suggestion. I've not run into this with other applications with port forwarding enabled. I'm kind of stuck with my router, as it's a Uverse gateway and provides both TV and Internet. Without buying another router to do pass through, guess I've got what I've got. I will look into it, but don't recall seeing that in the router configuration.

[dwRCjCCil]

I looked into my router's (NVG589) capabilities on the ATT forum and you are correct that it does not have loopback capabilities.

[markn62]

I port forward Sighthound along with many other services. I use PfSense, a commercial router, with the Pure NAT feature and Reflections enabled. They all work fine as does Sighthound's video streams (CAMERAS). In CLIPS the thumbnails load but choosing any of them fails after about 30 seconds of spinning to show a play icon with an "X" through it. Even if I VPN into my LAN where the cameras exist it behaves the same since I'm still routing through AT&T cellular. Once home on WiFi, using either VPN and non-VPN, the clips play fine. Seems AT&T is the common denominator. Any suggestions how to remote into the clips via AT&T?

[markn62]

Turns out AT&T was filtering OpenVpn port. I reassigned to a non-standard port and all works well. For those using port forward for remote access but have no access on local wifi here is another way to do it. Use dynu.net or other dns host to translate your router's Wan ip to a host name. Then in your router, if it's capable, do a custom dsnmasq to point the host name to the SH server's private IP. In this way your client app will have access to SH both remotely (cellular) and on your local WiFi.