EyezOn Forum

I have Foscam FI8910W and using iPhone with Envisalink to monitor alarm system and view camera. I bought this Foscam model because it was noted as being compatible with Eyyz-On. So far I am able to view the camera with Eyez-On but none of the controls work. Using other apps or via web browser I am able to control the camera.

Anyone have any ideas? Am I simply overlooking something?

Thanks,

Alan

You have a "mixed content" issue. Chrome and Firefox don't like the fact that the streaming images don't use SSL while the rest of the page uses SSL. It is a huge issue with many IoT platforms and browser developers need to understand this.

Have a look at this link

http://arstechnica.com/information-tech ... -blocking/

I have a Foscam FI9821P and I am also not able to use PTZ. Watching the Camera with Wireshark I see nothing in HTTPS mode attempted to the camera. Using an obsolete browser version with the Eyez-on portal, I am able to make PTZ work and see cmd=ptzMoveLeft and cmd=PtzStopRun commands being sent to the camera on Wireshark. Using a modern browser with the Eyezon portal these commands are not sent to my camera.

This appears to be a compatibility problem between current generation web browsers and the Eyez-On portal. Even if it is a "mixed-content" issue, I wouldn't expect Eyez-on just to throw their hands up and quit.

Is Eyezon planning to fix this issue?

As I said before, this is NOT an issue with the portal, it is the fact that IP cameras do not use SSL and browsers these days block "active-mixed-content". Active-Mixed-Content are the commands sent to the camera within an SSL session to our server.

The only option would be to make the Eyezon portal non SSL which will not ever happen for blatantly obvious reasons.

Until the browser vendors provide an easier solution, you need to disable mixed-content blocking in your browser to access the Foscam controls.

Before anyone says "Hey, there is no problem using the Foscam App", please note that their app communicates completely unencrypted with the camera and hence has no "Mixed Content".

Why couldn't the camera data stream be unencrypted from the customer camera to Eyez-on and be encrypted using the Eyez-on SSL cert from the Eyez-on portal to the customer? Everything to the customer would be SSL encrypted with no active-mixed-content issue for the browser to complain about.

I understand and agree with not wanting to remove SSL at the Eyez-on portal, but I am not yet convinced this isn't solvable at your end with some software development effort and proxying the camera data though your portal. The camera data rate is pretty slow as the frame rate is pretty low so I wouldn't think this wold burden your servers.

Waiting for the browser vendors will likely result in no solution to this most annoying problem. I still don't see why Eyez-on can't fix this.

It is not addressable within the framework of a free service. If you wish to setup a reverse proxy within your home go ahead, but we cannot provide this service to our customers at no cost as we would have to build out the infrastructure to proxy thousands of video streams simultaneously. This is not going to happen.

This issue is closed. Just do what everyone else does and turn off mixed-content blocking and you can control your camera again.