I'm facing a very weird issue.
When I connect to the NVR on my local network, video streams as expected.
However when I do it via amcrestddns remotely, video gets stuck buffering and never plays.
"Amcrest View Pro" app however does work as expected.
Attached the screenshots.
Remote access video stream just keeps on buffering
Remote access video stream just keeps on buffering
- Attachments
-
- remote.png (254.99 KiB) Viewed 675 times
-
- local.png (1.49 MiB) Viewed 675 times
Re: Remote access video stream just keeps on buffering
Hello and Welcome to the Forum
So I am not sure how you have ASP setup but I am guessing your talking about accessing the cameras on ASP over a P2P connection or are you saying that when you connect with ASP to your amcrestddns address your able to access the cameras?
I know that I am able to access my cameras by remote over ASP on a P2P connection.. When setting up ASP it ask how are you trying to connect to the camera IP or SN?
Now if it has nothing to do with ASP and amcrestddns as the same type of connection then maybe you will want to call the number at the top of the webpage and ask for Support staff and see if maybe there was an issue with the Server from what I have known anyway there was some type of Server Move and maybe there was something that was missed on the DDNS part of the amcrest record..
Outside of that I am not sure as I don't use the Amcrestddns service..
So I am not sure how you have ASP setup but I am guessing your talking about accessing the cameras on ASP over a P2P connection or are you saying that when you connect with ASP to your amcrestddns address your able to access the cameras?
I know that I am able to access my cameras by remote over ASP on a P2P connection.. When setting up ASP it ask how are you trying to connect to the camera IP or SN?
Now if it has nothing to do with ASP and amcrestddns as the same type of connection then maybe you will want to call the number at the top of the webpage and ask for Support staff and see if maybe there was an issue with the Server from what I have known anyway there was some type of Server Move and maybe there was something that was missed on the DDNS part of the amcrest record..
Outside of that I am not sure as I don't use the Amcrestddns service..
Be Safe.