Mixed content occurs when a secure HTTPS page requests resources over an insecure connection. Browsers may block or upgrade such requests according to their rules. A working address in another application does not prove it will be allowed inside a secure web player.
Recognise the security boundary
The page and the media can come from different origins. If the interface loads but the media request is blocked, changing the account password may not address the problem. The service needs a delivery configuration compatible with the browser’s security model.
Avoid disabling browser security
Do not weaken global protections to make an undocumented media address work. Ask the service for its supported secure web-player route. Manually changing HTTP to HTTPS is also not a guaranteed fix because the media server must actually support it.
Report the right evidence
A normal user can report the browser name, page address without private tokens and visible error. Technical support may inspect the browser console for the blocked resource category. Keep any full media URLs private because they can contain account access information. The correct repair belongs in the supported delivery configuration, not in a guessed password or picture setting.