First setup issue
-
Good morning, I am really excited to try out this service on my echo shows!
My current setup is the following:
monocle gateway running on linux server A: 192.168.1.67, port 443 is open
nginx reverse proxy running on linux server B: 192.168.20.10 with an host configured like this: monocle.mydomain.com -> https://192.168.1.67:443
I have changed the following properties in the monocle.properties:
rtsp.port=9555 (I have the port 8555 used by frigate on the same machine)
rtsp.proxy.port=9554 (same reason as above)
rtsp.register.fqdn=monocle.mydomain.com (I need this because the internet exposed 443 port is occupied, therefore I need to use a proxy)
rtsp.register.host=192.168.1.67And on my router I have created a local dns rule to point monocle.mydomain.com -> 192.168.1.67
This is the log trying to load a video feed on echo show
****************************************************************** * __ __ ___ _ _ ___ ___ _ ___ * * | \/ |/ _ \| \| |/ _ \ / __| | | __| * * | |\/| | (_) | .` | (_) | (__| |__| _| * * |_| |_|\___/|_|\_|\___/ \___|____|___| * * * ****************************************************************** ------------------------------------------------- MONOCLE RUNTIME ENVIRONMENT ------------------------------------------------- VERSION = 0.0.6 OS/ARCH = linux/x64 PROCESS = monocle-gateway (PID=1) TIMESTAMP = 2024-07-16T10:46:56.051Z ------------------------------------------------- MONOCLE GATEWAY SERVICE (Version: 0.0.6) ------------------------------------------------- [Monocle Starting] [Monocle Connecting] [Monocle Started] [RTSP Server Starting] [RTSP Server Listening] 0.0.0.0:9555 (RTSP) [RTSP Server Listening] 0.0.0.0:443 (RTSP-TLS) [RTSP Proxy Started] (PID=16) [RTSP Server Listening] 0.0.0.0:9554 (PROXY) [RTSP Server Started] [Monocle Connected] [RTSP Server Registered] ------------------------------------------------- MONOCLE RTSP SERVICE - INITIALIZED ------------------------------------------------- FQDN = monocle.mydomain.com HOST = 192.168.1.67 PORT = 443 ------------------------------------------------- ------------------------------------------------- INITIALIZE RTSP STREAM: Daniel ------------------------------------------------- - NAME : Daniel - CAMERA.MFG : Reolink - CAMERA.MODEL : E1 Poe - CAMERA.LABEL : PRIMARY - RTSP.URL : rtsp://192.168.1.167:554/h264Preview_01_sub - STREAM.ID : STREAM:cea0d8e6-45ac-436c-879b-99dc956b762f - SESSION.ID : 0bfef149-1f1a-4a9c-8b54-49b1f07fffb8 - LAST.MODIFIED : Tue Jul 16 2024 10:46:53 GMT+0000 (Coordinated Universal Time) - TAGS : @proxy-tcp ------------------------------------------------- ATTENTION -> Next you should see log statements showing your camera establishing an inbound connection to this gateway instance via: -> DNS URL: rtsp://monocle.mydomain.com:443/STREAM:cea0d8e6-45ac-436c-879b-99dc956b762f -> This DNS host address should resolve to: 192.168.1.67:443 on your network. NOTE: If you don't receive any inbound connection log statements, please see: https://monoclecam.com/monocle-gateway-troubleshooting 2024-07-16T10:47:01.237Z [INFO] [RTSP PROXY] REGISTERING STREAM [Daniel/PRIMARY]; (STREAM:cea0d8e6-45ac-436c-879b-99dc956b762f) 2024-07-16T10:47:01.245Z [DEBUG] <RTSP-PROXY> [REQUEST] --> [REGISTER] rtsp://192.168.1.167:554/h264Preview_01_sub 2024-07-16T10:47:01.245Z [TRACE] <RTSP-PROXY> [REQUEST] --> [HEADERS] { "cseq": "1", "transport": "reuse_connection=0;preferred_delivery_protocol=interleaved;proxy_url_suffix=STREAM:cea0d8e6-45ac-436c-879b-99dc956b762f;username=user;password=password" } 2024-07-16T10:47:01.247Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined) 2024-07-16T10:47:01.247Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] { "cseq": "1", "date": "Tue, Jul 16 2024 10:47:01 GMT" } -
To me looks like that the initial connection Alexa -> Gateway and afterwards Gateway -> camera works, but hangs right after, not sure how to proceed