Amcrest WebUI-HTTPS setup

[rayleaf]

I have several IP2M-841 cameras that I am trying to set up for HTTPS and hope someone who has done this can assist me.

I assume that each camera which has a static IP address will require a separate created certificate and will require a separate/different HTTPS port and both the local IP address and https port will need to be portforwarded in the router for remote viewing.

In the setup process(and there is a video on the Amcrest website) once you press Create certificate a new window pops up ..IP or Domain with three options Local IP address or Public IP address(or WAN) or DDNS Domain URL.

I would like to use HTTPS for both local and remote viewing. If I select and input the local IP address for the particular camera in this pop up window and then follow the video steps and then afterwards port forward that local IP address with a new HTTPS port(not default https 443) in my router then I assume that I will be able to view this camera remotely if I remotely input in the Amcrest WebUI my PUBLIC IP ADDRESS: NEW HTTPS port in the URL. Assume this will work..

I do not understand why there is a the Public IP address option in the pop up window above and when you use this option.

Can someone who has done this please assist .

[Melvin]

Hello,

Please follow the below guide for https set up. The IP address can be public IP or a domain name (ddns) if you have set up port forwarding. The certificate will be registered against that address.

https://support.amcrest.com/hc/en-us/ar ... rest-WebUI

[rayleaf]

Melvin thanks for the quick response!!!

But I have already seen/reviewed the Amcrest website attached document that you included above and I am aware by watching the Amcrest youtube video & by also reviewing the Amcrest website document that the IP address can be public IP or a domain name(ddns) ....thus my posting with my above initial questions looking for clarity.

The Amcrest youtube video mentions one can use 3 options including the Local IP address ( or Public IP or DDNS domain) while Melvin you mention only 2 options( Public IP or DDNS) .

Melvin can you confirm that for the Certificate Creation step in the process inputting the Local IP address ( for each camera and repeating the process on every camera generating a new certificate for each camera ) would work per my 4th paragraph initial posting comments above....OR will this NOT work and I NEED to use the Public IP or a domain name(ddns) per your response to me.

Thank you for your support.

[Melvin]

Hello rayleaf ,

You can put any of the three (public,private or ddns). If you want to access the camera remotely wither public IP or DDNS should be used and certificate needs to be created for that.

[rayleaf]

Thanks Melvin!!! I have successfully set up one of my cameras on HTTPS protocol with remote access.

Noticed that this camera( now set up) has a certificate with validity period defaulted to 1 year. What happens after this 1 year period .... assume I would need to recreate another certificate again for this camera?

For the remaining cameras setups if I choose ie.3650 days validity period instead of the 365 day period will the process still work( and thus will not need to worry about redoing again this process after the 1 year period expiration)?

Appreciate your suggestions/support. Thank you!

[magraff]

So (only?) port 443 is for https? If you have (2) cameras, and are using (example) cam1.amcrestddns.com or cam2.amcrestddns.com... you need to do port forwarding... but how can you port forward the same port 443 to both cameras? Can you use a different port for https?