Interesting find.......DNS options
-
AS per a few of my previous threads, I have been using Monocle since launch and after a few initial teething issues I managed to get all of my UCM247 IP cameras working perfectly with the Monocle Gateway running on a spare rPi3 and playing to my Echo Show 5 and 8.
Worked well for ages (had a small blip but reinstalling the gateway fixed things) and was always happy with it. Did manage to get it working on Synology as well briefly but then it stopped working and in truth, I have no idea why. So I gave up on the Synology Docker install (for now anyway) and went back to the RPI BUT initially, it wasn’t working.
Checked lots of my settings and through a lot of trial and error, it appeared to be my choice of DNS that was causing the issue. I have used Googles DNS servers for a while now 8888 and 8844 but I thought I would try an alternative (went with Cloudflare) and all of a sudden cameras were once again working.
Of course, this could have been a coincidence so I switched it back to the Google DNS’s overnight (when cameras instantly stopped working) and then this afternoon I have switched them back to Cloudflare and now they are working well again so I’m very happy to report that for now at least it seemed to be ‘something’ to do with the Google DNS I was using.
Next, I’m going to try to re-setup my Synology Docker install to see if that works again…happy to give it one more try but worst-case scenario, the RPI isn’t used for anything else now as I’ve managed to move everything over to Dockers on the NAS so it wants to be used for something.
Ill report back after trying the NAS again…fingers crossed
-
@Jouster-74 back to report that on the new DNS servers, the Synology Docker gateway still isn’t working
below is a grab of the logs in case anyone can see any issues…looks like a port issue to me with 443 mentioned a lot…but I thought the MACVLAN was meant to take care of that so in truth, I am very confused, especially as it has worked fine when I first tried setting it up a while ago
[Monocle Started]
[RTSP Server Starting]
[RTSP Server Listening] 0.0.0.0:8555 (RTSP)
[RTSP Server Listening] 0.0.0.0:443 (RTSP-TLS)
[RTSP Proxy Started] (PID=14)
[RTSP Server Listening] 0.0.0.0:8554 (PROXY)
[RTSP Server Started]
2020-09-27T14:13:10.695Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443
[ ‘[Monocle Error]’,
‘getaddrinfo EAI_AGAIN api.monoclecam.com:443’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 5 seconds (attempt #1)
[Monocle Connecting]
2020-09-27T14:13:20.710Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443
[ ‘[Monocle Error]’,
‘getaddrinfo EAI_AGAIN api.monoclecam.com:443’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 12 seconds (attempt #2)
[Monocle Connecting]
2020-09-27T14:13:37.727Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443
[ ‘[Monocle Error]’,
‘getaddrinfo EAI_AGAIN api.monoclecam.com:443’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 19 seconds (attempt #3)
[Monocle Connecting]
2020-09-27T14:14:01.748Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443
[ ‘[Monocle Error]’,
‘getaddrinfo EAI_AGAIN api.monoclecam.com:443’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 21 seconds (attempt #4)
[Monocle Connecting]
2020-09-27T14:14:27.766Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443
[ ‘[Monocle Error]’,
‘getaddrinfo EAI_AGAIN api.monoclecam.com:443’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 28 seconds (attempt #5)
[Monocle Connecting]
2020-09-27T14:15:00.778Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443
[ ‘[Monocle Error]’,
‘getaddrinfo EAI_AGAIN api.monoclecam.com:443’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 34 seconds (attempt #6)
[Monocle Connecting]
2020-09-27T14:15:39.813Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443
[ ‘[Monocle Error]’,
‘getaddrinfo EAI_AGAIN api.monoclecam.com:443’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 36 seconds (attempt #7)
[Monocle Connecting]
2020-09-27T14:16:20.828Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443
[ ‘[Monocle Error]’,
‘getaddrinfo EAI_AGAIN api.monoclecam.com:443’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 43 seconds (attempt #8)
-
so the choice of DNS that either your ISP uses by default, or the one that you pick if you do set one manually, appears to have an impact, at least via my current ISP (for which everything else has worked). Googles servers (8888 and 8844) both cause the gateway to NOT work…and no video to be displayed…I leave the system to settle after the change for uptown 24 hours but it never works…then i change to another DNS option (cloudflare in the first instance 1111 or 1001 and then it just works s it should.
Now I don’t know the ins and outs of how or why this would make a difference but it is certainly worth looking at for those that are having connective issues of any sort.
I should really try the Synology Docker version again but I’m not sure I can be bothered as know this is now working as it should
-
Hello,
I have the same error. Perhaps the problem is that I use my Synology as DNS Server ? Did you solve this problem ?
Thanks -
@hakkai94 said in Interesting find.......DNS options:
Hello,
I have the same error. Perhaps the problem is that I use my Synology as DNS Server ? Did you solve this problem ?
ThanksI solved this problem by forcing DNS servers in my docker-compose.yml file :
version: '2' services: monocle-gateway: container_name: monocle-gateway hostname: monocle-gateway image: monoclecam/monocle-gateway restart: always volumes: - /volume1/monocle:/etc/monocle dns: - 1.1.1.1 - 1.0.0.1 networks: monocle-gateway-network: ipv4_address: 192.168.1.114 networks: monocle-gateway-network: driver: macvlan driver_opts: parent: ovs_eth0 ipam: config: - subnet: 192.168.1.0/24 gateway: 192.168.1.1