Is the Nx Cloud up? Visit our Status Page for the current health and performance of the Nx Cloud.

Status Page

Problem retrieving video streams via the relay

Comments

3 comments

  • Ichiro
    • Network Optix team

    Hi Benjamin,

    It has no problem that IP address changes all the time, as that is CDN and the nature of Nx Cloud Relay works. It will have several access points (usually 3 relays) that will take care of the site. So IP address changing is not considered an issue.

    In your case, it is more like something about the webRTC connections or others.
    To help us properly diagnose this, could you provide the following:

    1. A screen recording showing the issue as it happens
    2. Wireshark packet/Browser Developer Tool logging captures showing what the request  was sent and when the server responded to.
    3. Server debug-level logs

    With this information, we can take a closer look at what might be happening on your end. 

    We'd suggest following our standard troubleshooting procedure and sharing the information above when you're able. (If you want to proceed and share the site access as well) 

    Thanks.

     

     

    0
  • Benjamin

    Hi,

    Thank you for your reply.

    Attached the browser traces (anonymized) showing the request sent and the response from your server. => LOG (removed the link after download)

    For your information, our application is developed using Angular and the @networkoptix/webrtc-stream-manager-v2 library.

    Note that we found no trace of this in the client debug logs during this connection attempt.

    Thanks,

    0
  • Ichiro
    • Network Optix team

    Hi Benjamin,

    Thanks for your information, but this log may not help much on this.

    What we would really want to see might be the server debugging log, which really contains the period that you were pulling the video.

    In your case, it is more like something about the webRTC connections or others.
    To help us properly diagnose this, could you provide the following:

    1. A screen recording showing the issue as it happens (reuqired)
    2. Wireshark packet/Browser Developer Tool logging captures showing what the request  was sent and when the server responded to.
    3. Server debug-level logs (mandatory)

    With this information, we can take a closer look at what might be happening on your end. 

    0

Please sign in to leave a comment.