Hello,
I have been using a QUSBCAM2 camera with Surveillance Station on a TS453be with no problem. I updated to QTS 5.2.2 from QTS 5.1.x and it seems to have broken so that while QUSBCAM can see the video I cannot mount it in Surveillance station.
Assuming SS was now broken, and knowing QNAP wants us to move to QVR Elite I moved there. That version of QUSB CAM can also see the video no problem but the app can not make a link to the camera.
Any ideas? Does 5.2 no longer support USB cameras?
One potential clue is when I search for cameras I now get two entries that if finds for the same camera, one at my normal IP address and one at another one that makes no sense. Neither work however.
Using Port 8080 and RTSP 554, which I have always used and is the default. Maybe these are wrong? It fails to “test” and says searching or connecting forever.
Hi @AnalogEngineer , thank you for using our QVR series products.
I have confirmed that QUSBcam works normally on my QVR Elite with QTS 5.2.2. (Please ignore that 100Mbps bitrate…)
Using Port 8080 and RTSP 554, which I have always used and is the default.
Please try using web Port 80 instead of system Port 8080 and try again.
If it still doesn’t work, please go to QNAP’s customer service web page to apply a ticket and let us use Helpdesk to remotely connect to help you check the situation.
thank you for confirming. I am still unable, using port 80 or 8080 to connect. The video is fine in QUSBCam but not in QVR Elite.
I noticed you are not logged in HTTPS but :8080, which does not work for me. Further your screen shows HTTPS Port 443, where mine does not allow me to enter anything there. Could this be the issue>?
Hi @AnalogEngineer I really didn’t notice that there is no way to set the HTTPS Port of USBcam in QVR Elite 2.6.
After cross comparison, the key seems to be the Web Port rather than the HTTPS Port.
Could you try using Web Port 8080 instead of 80 on your QVR Elite for USBcam?
Hello,
I had originally tried 8080, which did not work, then tried 80 on your suggestion, which also did not work.
Perhaps this is a clue. Why do I see the same entry twice? There is only one camera.
In addition everyting worked fine before updating from 5.1.x to 5.2.x
In my environment I only see one set of IP locations for the USBcam.
I thought about using IP 127.0.0.1, but it seems like standard IP will work fine too.
It seems that need you to go to customer service to open a ticket that the development team can use Helpdesk to remotely confirm the problem.
@HaruLin
I’ve found a temporary work around so posting for others but also have a question. I suspect there is a bug that needs to be fixed in the app.
If I uncheck “force redirect HTTP to HTTPS”, then click test and wait for the camera to mount it works fine. I am then able to re-enable Force HTTPS and it will continue to work. However if I make any setting changes I must again disable this while making changes. This seems to be some sort of bug somewhere. For now this work aorund works.
In addition I noticed your first screen shots there is a HTTPS port space, but not in my version or your later version. Is there a way to enable this option? I wonder if that would correct this problem by using the secure port instead?
