probleme de lecteur video en direct qui ne ce charge pas sur chrome, mais audio ok

Bonjour, 

j'ai un raccourcis vers une chaine direct que j'utilise depuis plusieus mois (annees?) qui me permet de lancer une chaine sur mon PC dans CHrome avec un click sur un bouton de mon StreamDeck.

depuis cette semaine, quand j'utilise ce lien, la page ce charge, mais le lecteur video ne ce charge pas. j'ai un ecran chrome tout noir, pas de controles de player, rien. par contre j'entends le son... c'est handicapant, je ne veuxc pas faire 50 cliques pour charger une chaine dans mon browser chrome.

le lien est de ce type https://www.canalplus.com/live/tab/direct/infos?channel=553 mais maintenant dans la console je vois des problemes dont l'analyse est ci dessous:

1) Bad configuration: missing/undefined platform

This is the most important line:

You must provide a valid platform parameter ... Provided: 'undefined'
Possible values: 'live' | 'hapi' | 'multi' | 'directfile'

Immediately after, you get:

Uncaught (in promise) Error: Something went wrong, due to a bad configuration options.

Interpretation: the app is trying to initialize a video “player” (your stack shows OnePlayer.ts / OnePlayerContainer.tsx) but the configuration object is missing platform, or the code that sets it is not running (or runs too late). The player init rejects a Promise, which is why you see “Uncaught (in promise)”.

Typical causes:

• A required query param / route param isn’t present (e.g., URL missing ?platform=live or similar).

• Env/config not injected correctly for the web build.

• A feature flag / remote config fetch fails and leaves platform undefined.

• An SSR/isomorphic mismatch where server defaults differ from browser.

User impact: the player will fail to load reliably (or at all).

2) DOM element missing during player mount/unmount

You also have:

Uncaught TypeError: Cannot read properties of null (reading 'setAttribute')
in setContainerStyleAndId / resetContainerStyleAndId

Interpretation: code assumes a container element exists, but it’s null when the code runs. This commonly happens when:

• The player is being destroyed while an async init still completes (race condition).

• React unmounted the component, but a requestAnimationFrame callback still runs.

• The element ID changed or the ref wasn’t set when init ran.

User impact: can cause additional crashes, flicker, or repeated re-render loops.

These two issues often amplify each other: the bad config causes init to fail, the failure triggers teardown/cleanup, and the cleanup runs against an already-unmounted DOM.