• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Error getaddrinfo EAI_AGAIN api.monoclecam.com:443

    Support
    2
    2
    190
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      chema pra last edited by

      i can´t see my dahua cameras in echo show 5.

      I have review all troubleshouting tips and all it´s correct but i received this message when i confirm monocle service with monocle-gateway --tail

      It´s a rpi 4b
      <<TAIL>> LOG FOR THE [MONOCLE-GATEWAY] SERVICE
      – Logs begin at Mon 2021-01-18 08:17:01 CET. –
      ene 18 08:17:09 raspberrypi monocle-gateway[488]: ******************************************************************
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: -------------------------------------------------
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: MONOCLE RUNTIME ENVIRONMENT
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: -------------------------------------------------
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: VERSION = 0.0.4
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: OS/ARCH = linux/arm
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: PROCESS = monocle-gateway (PID=488)
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: TIMESTAMP = 2021-01-18T07:17:10.774Z
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: -------------------------------------------------
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: MONOCLE GATEWAY SERVICE (Version: 0.0.4)
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: -------------------------------------------------
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: [Monocle Starting]
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: [Monocle Connecting]
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: [Monocle Started]
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: [RTSP Server Starting]
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: [RTSP Server Listening] 0.0.0.0:8555 (RTSP)
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: [RTSP Server Listening] 0.0.0.0:443 (RTSP-TLS)
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: [RTSP Proxy Started] (PID=707)
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: [RTSP Server Listening] 0.0.0.0:8554 (PROXY)
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: [RTSP Server Started]
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: 2021-01-18T07:17:10.902Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: [ ‘[Monocle Error]’,
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: ‘getaddrinfo EAI_AGAIN api.monoclecam.com:443’ ]
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: [Monocle Disconnected]
      ene 18 08:17:10 raspberrypi monocle-gateway[488]: [Monocle Reconnecting] … in 5 seconds (attempt #1)
      ene 18 08:17:15 raspberrypi monocle-gateway[488]: [Monocle Connecting]
      ene 18 08:17:15 raspberrypi monocle-gateway[488]: 2021-01-18T07:17:15.925Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443
      ene 18 08:17:15 raspberrypi monocle-gateway[488]: [ ‘[Monocle Error]’,
      ene 18 08:17:15 raspberrypi monocle-gateway[488]: ‘getaddrinfo EAI_AGAIN api.monoclecam.com:443’ ]
      ene 18 08:17:15 raspberrypi monocle-gateway[488]: [Monocle Disconnected]
      ene 18 08:17:15 raspberrypi monocle-gateway[488]: [Monocle Reconnecting] … in 14 seconds (attempt #2)
      ene 18 08:17:29 raspberrypi monocle-gateway[488]: [Monocle Connecting]
      ene 18 08:17:30 raspberrypi monocle-gateway[488]: [Monocle Connected]
      ene 18 08:17:30 raspberrypi monocle-gateway[488]: [RTSP Server Registered]
      ene 18 08:17:30 raspberrypi monocle-gateway[488]: -------------------------------------------------
      ene 18 08:17:30 raspberrypi monocle-gateway[488]: MONOCLE RTSP SERVICE - INITIALIZED
      ene 18 08:17:30 raspberrypi monocle-gateway[488]: -------------------------------------------------
      ene 18 08:17:30 raspberrypi monocle-gateway[488]: FQDN = 20b9e527-afda-4446-8cda-af4ea88faf5a.mproxy.io
      ene 18 08:17:30 raspberrypi monocle-gateway[488]: HOST = 192.168.1.20
      ene 18 08:17:30 raspberrypi monocle-gateway[488]: PORT = 443
      ene 18 08:17:30 raspberrypi monocle-gateway[488]: -------------------------------------------------
      ene 18 08:25:48 raspberrypi monocle-gateway[488]: 2021-01-18T07:25:48.153Z [ERROR] [Monocle Error] Closing connection due to PING response timeout; last PING response received was at: [2021-1-18 08:17:30]
      ene 18 08:25:48 raspberrypi monocle-gateway[488]: [ ‘[Monocle Error]’,
      ene 18 08:25:48 raspberrypi monocle-gateway[488]: ‘Closing connection due to PING response timeout; last PING response received was at: [2021-1-18
      08:17:30]’ ]
      ene 18 08:25:48 raspberrypi monocle-gateway[488]: [Monocle Disconnected]
      ene 18 08:25:48 raspberrypi monocle-gateway[488]: [Monocle Reconnecting] … in 5 seconds (attempt #1)
      ene 18 08:25:53 raspberrypi monocle-gateway[488]: [Monocle Connecting]
      ene 18 08:25:53 raspberrypi monocle-gateway[488]: [Monocle Connected]
      ene 18 08:25:53 raspberrypi monocle-gateway[488]: [RTSP Server Registered]
      ene 18 08:25:53 raspberrypi monocle-gateway[488]: -------------------------------------------------
      ene 18 08:25:53 raspberrypi monocle-gateway[488]: MONOCLE RTSP SERVICE - INITIALIZED
      ene 18 08:25:53 raspberrypi monocle-gateway[488]: -------------------------------------------------
      ene 18 08:25:53 raspberrypi monocle-gateway[488]: FQDN = 20b9e527-afda-4446-8cda-af4ea88faf5a.mproxy.io
      ene 18 08:25:53 raspberrypi monocle-gateway[488]: HOST = 192.168.1.20
      ene 18 08:25:53 raspberrypi monocle-gateway[488]: PORT = 443
      ene 18 08:25:53 raspberrypi monocle-gateway[488]: -------------------------------------------------
      ene 18 08:53:48 raspberrypi monocle-gateway[488]: [RTSP Server Stopping]
      ene 18 08:53:48 raspberrypi systemd[1]: Stopping Monocle Gateway Service…
      ene 18 08:53:48 raspberrypi monocle-gateway[488]: [RTSP Server Stopped]
      ene 18 08:53:48 raspberrypi monocle-gateway[488]: [Monocle Stopping]
      ene 18 08:53:48 raspberrypi monocle-gateway[488]: [Monocle Stopped]
      ene 18 08:53:48 raspberrypi monocle-gateway[488]: [RTSP Proxy Stopped] CODE=0; SIGNAL=SIGTERM
      ene 18 08:53:48 raspberrypi systemd[1]: monocle-gateway.service: Succeeded.
      ene 18 08:53:48 raspberrypi systemd[1]: Stopped Monocle Gateway Service.
      ene 18 08:53:48 raspberrypi systemd[1]: Started Monocle Gateway Service.

      1 Reply Last reply Reply Quote 0
      • S
        steinauf last edited by

        I had this issue too, though I was running the gateway in a container with macvlan networking. it creates a new IP address to use, and I had forgotten to forward ports to that IP. I attempted to forward TCP 443 that port, but being a macvlan it was on a different subnet and my Orbi wouldn’t allow that.

        no matter, I just switched back to host networking for now (which already had port 443 forwarded) and it works

        -------------------------------------------------
        MONOCLE GATEWAY SERVICE         (Version: 0.0.4)
        -------------------------------------------------
        [Monocle Starting]
        [Monocle Connecting]
        [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=16)
        [RTSP Server Listening] 0.0.0.0:8554 (PROXY)
        [RTSP Server Started]
        [Monocle Connected]
        [RTSP Server Registered]
        -------------------------------------------------
        MONOCLE RTSP SERVICE - INITIALIZED
        -------------------------------------------------
        FQDN = redacted.mproxy.io
        HOST = 192.168.1.99
        PORT = 443
        -------------------------------------------------
        
        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Privacy Policy  |  Terms & Conditions

        © 2018 shadeBlue, LLC.