ProHD No Video using HTTPS

[PsychoPhreak]

Unfortunately your 2 posts do not at all relate to this thread. Viewing HTTP streams have never been an issue with any firmware, the issue is when trying to access the camera stream using HTTPS, on the default port of 443.

[AuroraHorizon]

Suggested workaround for users with "advanced" functionality.

If you have the ability to establish a L2TP VPN with IPsec (encrypted VPN over public networks) to the site where remote HTTPS viewing of a camera feed is desired I have good news and tidings of joy in this wondrous holiday season.

I recently ordered a camera and experienced the same trouble described here. I found this thread with an internet search and realized that there was no "resolution" provided. This solution has been tested and confirmed to provide remote access of the camera live feed function via HTTPS.

With this solution you can access the camera, login and view the stream with HTTPS (encrypted) through an encrypted VPN connection. I like the sound of layered encryption

It may be that some of the equipment supplied by an ISP, or a router that you have purchased, has this capability as well. Check with your router documentation, or supplier, for details and related information.

Steps:
1.) Configure a L2TP VPN with IPsec on the devices involved, the device on the "edge" of the LAN and the remote device(s).

2.) Establish the VPN, connecting from anywhere through the internet, to the site where remote viewing is desired.

3.) Access the camera(s) with HTTPS for login and live stream.
(https://[LAN IP Address]:[designated port] if other than default)

4.) Get the "sit-rep" and move on with your day.

L2TP with IPsec is often utilized to enable access to company network resources while working from home.

This method would be preferable to DDNS with port forwarding, or any other option requiring a "persistent hole" into the LAN from the WAN.

Cheers!

[PsychoPhreak]

I see there's a new firmware this morning, loading it up now and crossing fingers!

Changelog indicates Security improvement so we'll see...

UPDATE: nope, same issue when trying at either 720 or 1080 resolution. HTTP still works just fine

[jjreynolds]

This is odd. You can access the live video locally via https:443, but not over the Internet when you port forward 443 in your router. As far as the camera knows, somebody is connecting to it , whether locally or across 10 gateways in China, it doesn't make any difference. SSL requires more CPU and memory resources in the camera, and the throughput would be lower and more random over the Internet. Anyone try lowering the video resolution? Apparently streaming SSL encapsulated video over slower, random behaving media like the Internet is choking the video service in the camera. What does Amcrest say?

[PsychoPhreak]

As I mentioned above, I've tried multiple resolutions, all the way down to VGA, changing frame rate, bit rate, everything, it always gives the same error. Not a bandwidth issue as I've got much bigger upstream bandwidth available than the camera is using.

This used to not be an issue with the firmware version I think 2 ago, yes it's very weird indeed. As I mentioned, support said this will be fixed in a future firmware release.

[jjreynolds]

If remote SSL video streaming worked with older firmware and this problem has not been resolved for over a year, then my guess is that the newer firmware added features that took away memory from the SSL and/or video streaming buffers that are only needed on remote connections. I'm not sure why remote or local would make any difference, but obviously it does. So in order to get this to work Amcrest will have to either
1) Optimize the code or fix the bug they introduced with the new code. which isn't happening
2) Remove some of the new features to free up memory which probably won't happen either.
3) Update the hardware to support more memory which isn't going to do anyone with old hardware any good, like us.

I've had the 841 camera now for a couple of days and only use it for email alarms and live streaming locally and remotely using the third party software OWLR for multi cameras.The camera's configuration is too complicated, some of the shit doesn't work the way you would expect -- if it works at all -- and the documentation is outdated and not clear. Other than that it works OK once you figure out the anomalies. I checked the Amcrest website and can't find older firmware, you can only download the latest revision. I hope you kept a copy of that older firmware that worked

[PsychoPhreak]

I'm now on my 4th(?) support person? After a few canned responses this time, I now got this reply. I don't think Amcrest considers this an important issue anymore unfortunately, and I refuse to access my personal camera through a cloud service, so FYI to all:

"If you wants to use HTTPS for security, then you can use amcrestview.com.
The camera video will not come through HTTPS port through port forwarding currently.
Please feel free to reach me for any other questions.
Thanks & Have a great day.


Regards,
Christine"

[PsychoPhreak]

I hope you kept a copy of that older firmware that worked

I actually did, but the latest firmware from 3/22 actually fixes all issues, great work Amcrest devs!

[PsychoPhreak]

Another new one finally! Won't upgrade until I'm wired at home based on the upgrade PDF they listed, but they say they fixed expired cert issue and a few other things, fingers are crossed!

Update: Latest firmware fixed all my issues (including one's outside of this post!) and changed up the interface a bit in the settings in ways I think are good! Much better https support! I found it odd *many* more of my settings remained during a "Restore to Default Settings" reset after the upgrade than I expected (IP & Port configuration, Usernames & Passwords...) but this was actually welcomed. I imagine a hard reset using the button on the camera would wipe this as well.

The only issue I've found is using the Web View software, the input to click on "Advanced" and then to Proceed to the site is off by an inch or so. If you tab to the options and enter with your keyboard you can get around this, but other than that one connection issue, I say cheers to Amcrest for a job well done, it might have taken 6 months, but the support is actually there!

[sz1]

New firmware doesn't work for me. SSL works from within the LAN but not from outside. It allows login but I get the "no resources" error.

I also tried nginx https to http pass. With the old firmware it allowed login (but no video). Now it says login failed...

This webcam is useless if you can't have a secure connection.
nginx works well with other webcams. Did anyone have success with Amcrest?