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

    Trouble with the gateway - no connection

    Support
    1
    3
    135
    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.
    • O
      olaf.zilles last edited by

      Hi!
      I have the gateway installed and have it running - I think ;-) But it shows some errors when starting

      When I call Alexa to show a camera, I can see it in the terminal. But I see only the first part with “initalize RTSP-Streanm”, the camera name, label, URL and so on. After that there comes no Socket connected or something like that as in all the threads I have already listened!

      Any hint for me?

      (Cameras work without the gateway on an Echo Show 1. Gen.)
      Here is the log:

      Last login: Sat Sep 26 15:17:37 on ttys000
      Mac-mini:~ bergmann-zilles$ sudo ./monocle-gateway
      Password:
      sudo: ./monocle-gateway: command not found
      Mac-mini:~ bergmann-zilles$ cd monocle-gateway
      Mac-mini:monocle-gateway bergmann-zilles$ sudo ./monocle-gateway


      •         __  __  ___  _  _  ___   ___ _    ___              *
        
      •        |  \/  |/ _ \| \| |/ _ \ / __| |  | __|             *
        
      •        | |\/| | (_) | .` | (_) | (__| |__| _|              *
        
      •        |_|  |_|\___/|_|\_|\___/ \___|____|___|             *
        
      •                                                            *
        


      MONOCLE RUNTIME ENVIRONMENT

      VERSION = 0.0.4
      OS/ARCH = darwin/x64
      PROCESS = monocle-gateway (PID=9424)
      TIMESTAMP = 2020-09-26T13:59:31.055Z


      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=9425)
      [RTSP Server Listening] 0.0.0.0:8554 (PROXY)
      [RTSP Server Started]
      2020-09-26T13:59:31.121Z [ERROR] [PROXY SERVER ERROR] Error: listen EADDRINUSE 0.0.0.0:8555
      [ ‘[PROXY SERVER ERROR]’,
      { Error: listen EADDRINUSE 0.0.0.0:8555
      at Object._errnoException (util.js:1031:13)
      at _exceptionWithHostPort (util.js:1052:20)
      at Server.setupListenHandle [as _listen2] (net.js:1367:14)
      at listenInCluster (net.js:1408:12)
      at doListen (net.js:1523:7)
      at _combinedTickCallback (internal/process/next_tick.js:141:11)
      at process._tickCallback (internal/process/next_tick.js:180:9)
      at Function.Module.runMain (pkg/prelude/bootstrap.js:1299:13)
      at startup (bootstrap_node.js:227:16)
      at bootstrap_node.js:649:3
      errno: ‘EADDRINUSE’,
      code: ‘EADDRINUSE’,
      syscall: ‘listen’,
      address: ‘0.0.0.0’,
      port: 8555 } ]
      2020-09-26T13:59:31.130Z [ERROR] [RTSP Server Error] listen EADDRINUSE 0.0.0.0:8555
      [ ‘[RTSP Server Error]’, ‘listen EADDRINUSE 0.0.0.0:8555’ ]
      2020-09-26T13:59:31.130Z [ERROR] [PROXY SERVER ERROR] Error: listen EADDRINUSE 0.0.0.0:443
      [ ‘[PROXY SERVER ERROR]’,
      { Error: listen EADDRINUSE 0.0.0.0:443
      at Object._errnoException (util.js:1031:13)
      at _exceptionWithHostPort (util.js:1052:20)
      at Server.setupListenHandle [as _listen2] (net.js:1367:14)
      at listenInCluster (net.js:1408:12)
      at doListen (net.js:1523:7)
      at _combinedTickCallback (internal/process/next_tick.js:141:11)
      at process._tickCallback (internal/process/next_tick.js:180:9)
      at Function.Module.runMain (pkg/prelude/bootstrap.js:1299:13)
      at startup (bootstrap_node.js:227:16)
      at bootstrap_node.js:649:3
      errno: ‘EADDRINUSE’,
      code: ‘EADDRINUSE’,
      syscall: ‘listen’,
      address: ‘0.0.0.0’,
      port: 443 } ]
      2020-09-26T13:59:31.139Z [ERROR] [RTSP Server Error] listen EADDRINUSE 0.0.0.0:443
      [ ‘[RTSP Server Error]’, ‘listen EADDRINUSE 0.0.0.0:443’ ]
      [RTSP Proxy Stopped] CODE=1; SIGNAL=null
      [Monocle Connected]
      [RTSP Server Registered]


      MONOCLE RTSP SERVICE - INITIALIZED

      FQDN = 5b98792d-6d1d-4777-9fdf-1b19face9fd1.mproxy.io
      HOST = 192.168.178.150
      PORT = 443


      INITIALIZE RTSP STREAM: Dach Wintergarten

      • NAME : Dach Wintergarten
      • LABEL : PRIMARY
      • URL : rtsp://192.168.178.5:554/Streaming/Channels/301
      • UUID : STREAM:bf5a4c0d-19a9-40c0-b761-ac3adb2ae448
      • SESS : 5bd010de-fc3e-4c2f-a8c1-bd6105ce7ad9
      • MODIF : Sat Sep 26 2020 15:59:59 GMT+0200 (CEST)
      • TAGS : @tunnel


      INITIALIZE RTSP STREAM: Dach Wintergarten

      • NAME : Dach Wintergarten
      • LABEL : PRIMARY
      • URL : rtsp://192.168.178.5:554/Streaming/Channels/301
      • UUID : STREAM:bf5a4c0d-19a9-40c0-b761-ac3adb2ae448
      • SESS : 586e000c-d43e-4b65-9108-1f6f4237843e
      • MODIF : Sat Sep 26 2020 15:59:59 GMT+0200 (CEST)
      • TAGS : @tunnel


      INITIALIZE RTSP STREAM: Dach Wintergarten

      • NAME : Dach Wintergarten
      • LABEL : PRIMARY
      • URL : rtsp://192.168.178.5:554/Streaming/Channels/301
      • UUID : STREAM:bf5a4c0d-19a9-40c0-b761-ac3adb2ae448
      • SESS : ca99f88a-af17-4a1f-861b-3a0753d9ff11
      • MODIF : Sat Sep 26 2020 15:59:59 GMT+0200 (CEST)
      • TAGS : @tunnel

      ===

      O 1 Reply Last reply Reply Quote 0
      • O
        olaf.zilles @olaf.zilles last edited by

        @olaf-zilles
        Just wanted to add:

        • Fritzbox with binding exception - ping works, …mproxy.io is resolved and I see the IP of the mac where the gateway is running on!
        • port not blocked by other services
        • all devices are on the same subnet
        1 Reply Last reply Reply Quote 0
        • O
          olaf.zilles last edited by

          Nobody an idea which helps me out of my problem?

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Privacy Policy  |  Terms & Conditions

          © 2018 shadeBlue, LLC.