Latest post Wed, Feb 19 2020 4:01 PM by Vadym. 6 replies.
Page 1 of 1 (7 items)
Sort Posts: Previous Next
  • Mon, Feb 17 2020 4:16 PM

    • matev
    • Not Ranked
    • Joined on Tue, Aug 2 2016
    • Posts 16
    • Points 190

    Cloud UX dev Proxy Tool can't connect to Media Player (CORS issue)

    Hi All,

     

    after Chrome update to v80 the cloudux-starter-kit 's proxy tool for UI app development is not working correctly. The application which is served by the proxy tool is visible and accessible from the Cloud UX App Bar, but the Cloud UX Media Player is not able to load any media. It is just trying to connect to the video server without success.

     

    I tried different versions of the cloudux-starter-kit but the symptoms are the same.

     

    cloudux-starter-kit@2.0.0 prints error into the dev console -> Access to XMLHttpRequest at 'https://cloudux-a.local.sk/api/xlb/nodes/less/?service=xmd' from origin 'https://127.0.0.1:8080' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: Redirect is not allowed for a preflight request.

     

    while cloudux-starter-kit@2.0.9 prints -> GET https://cloudux-a.local.sk:8080/api/xlb/nodes/less/?service=xmd net::ERR_CONNECTION_REFUSED

     

    To be totally correct this problem did not came with chrome v80, it was in earlier versions also. But since v80 I can not launch chrome with flag --disabled-web-security what did the trick in the past...

     

     

    Environment:

    Cloud UX 2019.9.6

    PAM 2019.6

    Dev machine -> macOS 10.15.3 but tried on Windows machines also

     

    Do you have any idea how to solve this issue?

  • Mon, Feb 17 2020 4:51 PM In reply to

    • sharnois
    • Not Ranked
    • Joined on Fri, Dec 7 2012
    • Posts 7
    • Points 75
    • Avid Developer Moderator
      Avid Employee

    Re: Cloud UX dev Proxy Tool can't connect to Media Player (CORS issue)

    Have you check this message? I think the same solution would apply here.

     

    http://community.avid.com/forums/p/198816/890789.aspx#890789

  • Mon, Feb 17 2020 5:55 PM In reply to

    • matev
    • Not Ranked
    • Joined on Tue, Aug 2 2016
    • Posts 16
    • Points 190

    Re: Cloud UX dev Proxy Tool can't connect to Media Player (CORS issue)

    Hello,

     

    probably it's not the same issue. Cloud UX does not use flash like the old Central UX did. Or? :)  

    And in chrome's dev console there is an error regarding CORS while the player is initialising. And the CORS error makes sense  while working with the developer proxy tool, beacuse from http://localhost:8080 it is trying to establish the xmd connection with the real server which is http://cloudux. So other origin...

     

    Am I wrong? Or do you have any other idea?

  • Tue, Feb 18 2020 8:37 PM In reply to

    • Vadym
    • Top 500 Contributor
    • Joined on Thu, Apr 17 2014
    • Posts 231
    • Points 2,775
    • Avid Developer Moderator
      Avid Employee

    Re: Cloud UX dev Proxy Tool can't connect to Media Player (CORS issue)

    Hi Mate,

     

    Please use the latest starter kit 2.0.10. Everything works in my case

  • Tue, Feb 18 2020 9:08 PM In reply to

    • matev
    • Not Ranked
    • Joined on Tue, Aug 2 2016
    • Posts 16
    • Points 190

    Re: Cloud UX dev Proxy Tool can't connect to Media Player (CORS issue)

    Hi Vadym,

     

    I tried that version also but the situation is the same :(

     

    Any other idea? Is not possible to enable CORS headers on the server, is it?

  • Wed, Feb 19 2020 10:24 AM In reply to

    • matev
    • Not Ranked
    • Joined on Tue, Aug 2 2016
    • Posts 16
    • Points 190

    Re: Cloud UX dev Proxy Tool can't connect to Media Player (CORS issue)

    Hi Vadym,

     

    maybe I have found the "solution". If I remove the cloudux FQDN from the cloudux/admin -> workflow settings -> playback -> hostname, then while using the dev proxy-tool the xmd is beeing requested from the 127.0.0.1:8080 url, while if the player hostname FQDN is set in the settings, then the xmd is requested from the real server FQDN:8080 wich is not valid.

     

    I think we had some playback issues if the player hostname setting was not set in the admin app so we filled it with the FQDN. In which cases is necessary to fill that setting?

     

    Thanks

  • Wed, Feb 19 2020 4:01 PM In reply to

    • Vadym
    • Top 500 Contributor
    • Joined on Thu, Apr 17 2014
    • Posts 231
    • Points 2,775
    • Avid Developer Moderator
      Avid Employee

    Re: Cloud UX dev Proxy Tool can't connect to Media Player (CORS issue)

    Hi Mate,

    Great to hear you have found the issue. That field should be left empty for the most cases and is used only for some very special workflows.

    Thanks

Page 1 of 1 (7 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller