Monocle Gateway error - synology nas
-
Hi - hope you can help.
I have diligently followed the set-up to install on my synology ds218+ NAS.
Camera tests perfectly using RTSP stream in VLC, supports H.264 and I have set up Monocle Gateway using the detailed guidance (install docker etc)
When I look in the terminal I get a recurring error - not sure what I need to do to fix it - ive replicated below - anyone got any advice? thank you.
2019-12-15 18:51:41 stdout [Monocle Connecting] 2019-12-15 18:51:26 stderr 'getaddrinfo EAI_AGAIN api.monoclecam.com:443' ] 2019-12-15 18:51:26 stderr [ '[Monocle Error]', 2019-12-15 18:51:26 stdout [Monocle Reconnecting] ... in 15 seconds (attempt #3) 2019-12-15 18:51:26 stdout [Monocle Disconnected] 2019-12-15 18:51:26 stderr 2019-12-15T18:51:26.804Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443 2019-12-15 18:51:21 stdout [Monocle Connecting] 2019-12-15 18:51:11 stderr 'getaddrinfo EAI_AGAIN api.monoclecam.com:443' ] 2019-12-15 18:51:11 stderr [ '[Monocle Error]', 2019-12-15 18:51:11 stdout [Monocle Reconnecting] ... in 10 seconds (attempt #2) 2019-12-15 18:51:11 stdout [Monocle Disconnected] 2019-12-15 18:51:11 stderr 2019-12-15T18:51:11.789Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443 2019-12-15 18:51:06 stdout [Monocle Connecting] 2019-12-15 18:50:57 stdout [Monocle Reconnecting] ... in 9 seconds (attempt #1) 2019-12-15 18:50:57 stdout [Monocle Disconnected] 2019-12-15 18:50:57 stderr 'getaddrinfo EAI_AGAIN api.monoclecam.com:443' ] 2019-12-15 18:50:57 stderr [ '[Monocle Error]', 2019-12-15 18:50:57 stderr 2019-12-15T18:50:57.764Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443 2019-12-15 18:50:52 stdout [RTSP Server Started] 2019-12-15 18:50:52 stdout [RTSP Server Listening] 0.0.0.0:8554 (PROXY) 2019-12-15 18:50:52 stdout [RTSP Proxy Started] (PID=15) 2019-12-15 18:50:52 stdout [RTSP Server Listening] 0.0.0.0:443 (RTSP-TLS) 2019-12-15 18:50:52 stdout [RTSP Server Listening] 0.0.0.0:8555 (RTSP) 2019-12-15 18:50:52 stdout [RTSP Server Starting] 2019-12-15 18:50:52 stdout [Monocle Started] 2019-12-15 18:50:52 stdout [Monocle Connecting] 2019-12-15 18:50:52 stdout [Monocle Starting] 2019-12-15 18:50:52 stdout ------------------------------------------------- 2019-12-15 18:50:52 stdout MONOCLE GATEWAY SERVICE (Version: 0.0.4) 2019-12-15 18:50:52 stdout ------------------------------------------------- 2019-12-15 18:50:52 stdout 2019-12-15 18:50:52 stdout TIMESTAMP = 2019-12-15T18:50:52.729Z 2019-12-15 18:50:52 stdout PROCESS = monocle-gateway (PID=1) 2019-12-15 18:50:52 stdout OS/ARCH = linux/x64 2019-12-15 18:50:52 stdout VERSION = 0.0.4 2019-12-15 18:50:52 stdout ------------------------------------------------- 2019-12-15 18:50:52 stdout MONOCLE RUNTIME ENVIRONMENT 2019-12-15 18:50:52 stdout ------------------------------------------------- 2019-12-15 18:50:52 stdout 2019-12-15 18:50:52 stdout 2019-12-15 18:50:52 stdout ****************************************************************** 2019-12-15 18:50:52 stdout * * 2019-12-15 18:50:52 stdout * |_| |_|\___/|_|\_|\___/ \___|____|___| * 2019-12-15 18:50:52 stdout * | |\/| | (_) | .` | (_) | (__| |__| _| * 2019-12-15 18:50:52 stdout * | \/ |/ _ \| \| |/ _ \ / __| | | __| * 2019-12-15 18:50:52 stdout * __ __ ___ _ _ ___ ___ _ ___ * 2019-12-15 18:50:52 stdout ******************************************************************
-
It looks like the docker instance is not able to resolve the DNS hostname
api.monoclecam.com
. That would suggest something about the network info is not configured correctly or the docker instance does not have access to a DNS server to resolve the hostname?Thanks, Robert
-
Thank you for your reply - I’ll uninstall everything and start over
Greig -
@aitkeng
I had the same issue - in the end i used my synology nas as the gateway but direct to my camera’s ip addresses instead… can you ping the path of the camera via the gateway? -
It sounds like it might be the network configuration part of the docker instance that gets created. You will have to use network configuration settings that are compatible with your local area network and router. The example uses a 10.x.x.x address, but most people probably need a 192.168.1.x address scheme.
Can you post the network settings you used in your docker-compose file?
Thanks, Robert
-
Hi - thanks for the responses - i uninstalled everything from the synology NAS drive and tried to install on one of my PC’s that is permanently on.
Followed the (much simpler) instructions but when I ask alexa to connect it says “Hmmm the camera isn’t responding”.
Any pointer to what to adjust would be gratefully received.
Thank you in anticipation.
here is the data dump I get
INITIALIZE RTSP STREAM: Back Door
- NAME : Back Door
- LABEL : PRIMARY
- URL : rtsp://192.168.0.67:554/ch1/main/av_stream
- UUID : STREAM:1381e0f8-779e-44e3-88e7-9d3417dc738f
- SESS : e5f510c1-9ab6-4859-b77b-cdbbca59c676
- MODIF : Wed Dec 18 2019 21:47:38 GMT+0000 (GMT Standard Time)
- TAGS : @tunnel
2019-12-18T21:50:19.980Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP CLIENT SOCKET CONNECTED
2019-12-18T21:50:20.112Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP CLIENT ATTACHED TO STREAM: Back Door (STREAM:1381e0f8-779e-44e3-88e7-9d3417dc738f)
2019-12-18T21:50:20.117Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP ENDPOINT SOCKET CONNECTED {192.168.0.67:554}
2019-12-18T21:50:20.120Z [DEBUG] [192.168.0.63:54334 <BkNX1XOCS>] [CLIENT REQUEST] --> [DESCRIBE] rtsp://c120dfbd-dcf0-4e82-a200-5ad2502c1d9e.mproxy.io:443/STREAM:1381e0f8-779e-44e3-88e7-9d3417dc738f?session=e5f510c1-9ab6-4859-b77b-cdbbca59c676
2019-12-18T21:50:20.120Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [CLIENT REQUEST] --> [HEADERS] {
“accept”: “application/sdp”,
“user-agent”: “Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)”,
“cseq”: “1”
}
2019-12-18T21:50:20.121Z [DEBUG] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT REQUEST] --> [DESCRIBE] rtsp://192.168.0.67:554/ch1/main/av_stream
2019-12-18T21:50:20.123Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT REQUEST] --> [HEADERS] {
“accept”: “application/sdp”,
“user-agent”: “Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)”,
“cseq”: “1”
}
2019-12-18T21:50:20.127Z [DEBUG] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT RESPONSE] <-- [401 (Unauthorized)] <cseq=1> (session=undefined)
2019-12-18T21:50:20.128Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT RESPONSE] <-- [HEADERS] {
“cseq”: “1”,
“www-authenticate”: “Digest realm=“IP Camera(C6181)”, nonce=“d6e2fe894410953a2653ec2b70a17a8c”, stale=“FALSE”, Basic realm=“IP Camera(C6181)””,
“date”: “Wed, Dec 18 2019 21:50:20 GMT”
}
2019-12-18T21:50:20.130Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP ENDPOINT REQUIRES AUTHENTICATION: Digest realm=“IP Camera(C6181)”, nonce=“d6e2fe894410953a2653ec2b70a17a8c”, stale=“FALSE”, Basic realm=“IP Camera(C6181)”
2019-12-18T21:50:20.133Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP ENDPOINT ATTEMPTING AUTHENTICATION: DIGEST
2019-12-18T21:50:20.134Z [DEBUG] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT REQUEST] --> [DESCRIBE] rtsp://192.168.0.67:554/ch1/main/av_stream
2019-12-18T21:50:20.135Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT REQUEST] --> [HEADERS] {
“accept”: “application/sdp”,
“user-agent”: “Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)”,
“cseq”: “1”,
“authorization”: "Digest username=“admin”, realm=“IP Camera(C6181)”, nonce=“d6e2fe894410953a2653ec2b70a17a8c”, uri=“rtsp://192.168.0.67:554/ch1/main/av_stream”, response=“b219684613e374b05cf50a7bc40214f4"”
}
2019-12-18T21:50:20.173Z [DEBUG] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
2019-12-18T21:50:20.176Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT RESPONSE] <-- [HEADERS] {
“cseq”: “1”,
“content-type”: “application/sdp”,
“content-base”: “rtsp://192.168.0.67:554/ch1/main/av_stream/”,
“content-length”: “470”
}
2019-12-18T21:50:20.177Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT RESPONSE] <-- [BODY]
v=0
o=- 1576705820426873 1576705820426873 IN IP4 192.168.0.67
s=Media Presentation
e=NONE
b=AS:5050
t=0 0
a=control:rtsp://192.168.0.67:554/ch1/main/av_stream/
m=video 0 RTP/AVP 96
c=IN IP4 0.0.0.0
b=AS:5000
a=recvonly
a=x-dimensions:3840,2160
a=control:rtsp://192.168.0.67:554/ch1/main/av_stream/trackID=1
a=rtpmap:96 H265/90000
a=Media_header:MEDIAINFO=494D4B48010300000400050000000000000000000000000000000000000000000000000000000000;
a=appversion:1.02019-12-18T21:50:20.177Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP ENDPOINT AUTHENTICATION SUCCESSFUL: DIGEST
2019-12-18T21:50:20.181Z [DEBUG] [192.168.0.63:54334 <BkNX1XOCS>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
2019-12-18T21:50:20.182Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [CLIENT RESPONSE] <-- [HEADERS] {
“cseq”: “1”,
“content-type”: “application/sdp”,
“content-base”: “rtsp://192.168.0.67:554/ch1/main/av_stream/”,
“content-length”: “462”
}
2019-12-18T21:50:20.183Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [CLIENT RESPONSE] <-- [BODY]
v=0
o=- 1576705820426873 1576705820426873 IN IP4 192.168.0.67
s=Media Presentation
b=AS:5050
t=0 0
a=control:rtsp://192.168.0.67:554/ch1/main/av_stream/
m=video 0 RTP/AVP 96
c=IN IP4 0.0.0.0
b=AS:5000
a=rtpmap:96 H265/90000
a=control:rtsp://192.168.0.67:554/ch1/main/av_stream/trackID=1
a=recvonly
a=x-dimensions:3840,2160
a=Media_header:MEDIAINFO=494D4B48010300000400050000000000000000000000000000000000000000000000000000000000;
a=appversion:1.02019-12-18T21:50:20.184Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP CLIENT SOCKET CLOSED
2019-12-18T21:50:20.194Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP CLIENT DETACHED FROM STREAM: Back Door (STREAM:1381e0f8-779e-44e3-88e7-9d3417dc738f)
2019-12-18T21:50:20.196Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP ENDPOINT SOCKET CLOSED [192.168.0.63:54334 <BkNX1XOCS>]