I don’t actually understand and listed quite a few possibilities so at this point, any idea welcomed.

  • utopiah@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 hours ago

    Different networks entirely. AFAICT no IP is hardcoded, only domain names which are the same.

    But… please feel free to check the URL, it seems to work.

    My hypothesis is that the player in the browser, maybe due to WebWorks, had cached the IP of the content. So I was getting the UI/API from the new IP but the content itself (namely video files) from the old IP which might have created some CORS/CSP issues and that the player itself blocked it. (updating the post on the forum with that idea in case others get in a similar situation)