Good deal. I have been in IT for over 20 years and have never heard of this. Ive never experienced it in my career. If you ever need any help with the project let me know. I have extensive knowledge of AWS and programming in general. I would be happy to help.
Hello, checking to see who has this working through the NVR? I can easily get this working from the camera direct but if the camera is plugged direct into the nvr using the internal network I am unable to view the stream. I can get it to work from vlc. I use the ip of the nvr and tried what the rtsp port is and also the virtual host port of 65002. (rtsp://10.0.0.121:10554/Streaming/Channels/102) I have tried changing the rtsp ports as well and nothing. I am tiring to view this from fire stick or alexa and nothing. I am also using simple passwords to eliminate any issues and i have the gateway running, thinking it may have something to do with the internal address and routing but that does not explain why i can get it working from vlc. any help would be appreciated.
Thanks for all the details. I’m still sorting it all out in my head, but do have a couple of notes.
When using the Monocle Gateway with a camera that is tagged with any of these: @tunnel, @proxy or @proxy-tcp the RTSP stream is initiated from the Alexa device directly to the Monocle Gateway. Not directly to the camera or in your case the Docker Unifi Video server. (So it would be the Monocle Gateway that actually communicates RTSP to the Unifi server.)
I see now that you are generating your own LetsEncrypt certificate and that is allowing you to terminate it on your Apache server. That makes sense now. Just a note, if you already have your own domain name and SSL certificate, you should be able to override the DNS hostname that Monocle Gateway uses. See the Monocle Gateway Configuration topic here. There is no magic here, you just need a publicly resolvable DNS host entry that points to an IP address where the Monocle Gateway is listening (or via Apache proxy in your case.)
I was under the impression that the RTSP protocol was not able to be proxied via an Apache or NGINX server. But I guess I got that wrong somewhere. Maybe the TCP only streams are OK, not sure it would work with UDP streams. I’ll have to play with this setup again when I have some time. The SSL termination could be difficult for some people, but for advanced users this could be a nice alternative.
You probably don’t need to worry about the proxy handling any web sockets, at least not at this time – that may change in the future as we plan on adding a Monocle Gateway Web GUI with access to logs, etc. Today only outbound secure web sockets are used to communicate with the Monocle servers over the Internet.
Good news that you have fixed the DNS resolver issue. My configuration here is using tags: @fakefmtp, @tunnel
Another issue I have had is that I have been running out of user streams…if that makes sense. I thought it was related to using ONVIF. I am using onvif jpg, rtsp, onvif. The test is using VLC. Sometimes I get an error stating no more streams allowed. This also was seen sometimes with the Alexa. I have had to remove the Zoneminder and Blue Iris streams to solved the issues.
For anyone else having the same Proxy Error starting on Windows Servers, i found that 443 was also being used by IIS. Stopping and disabling the “World Wide Web Publishing Service” service freed the port and allowed monocle gateway to run. Appreciate this may not be an option for everyone.
Also, some routers will allow you to simply override a DNS host to a fixed address of your choosing. This could also be an option for you if your router allows that. You would just use the hostname 2b49b758-a6fd-4a36-a6ac-29b674ff1ce5.mproxy.io and have it pointed to the gateway’s IP address (192.168.0.110). So instead of the router actually resolving the address from a public DNS record, it just returns the overridden IP locally.
@dathomas85 could you clarify what you did, I have traefik running and trying to get the monocle gateway going as well but I thought both need access to port 443 externally. What ports did you forward?
As far as I know I’m the only reported working success story on the Echo Show 10 Gen 3.
I never experienced it not working so it’s hard to say if its a camera compatibility issue or if some Amazon firmware/system update occurred that fixed the original issue.
So at this point, all I can suggest is that you try and it see … with the caveat that you may end up having to return it if it does not work for you.