An HTTP redirect directs a client toward another URL. Players differ in how they handle redirects, authentication and media requests. A redirected endpoint can work in a browser yet fail in a particular app without proving the account is invalid.
Use the provider's current address
Enter the endpoint supplied for your account rather than copying a browser's temporary final media link. A website redirect and a player API redirect can serve different purposes. Keep those addresses distinct.
Watch authentication boundaries
Moving between origins can change how credentials or headers are handled. Do not manually paste passwords into a redirected address to make it work. Report the redirect-related symptom through a private support channel.
Avoid stale bookmarks
A migration may leave old links that no longer serve the expected API. Ask for the supported replacement if the provider changed infrastructure. Do not guess a new hostname from a similarly branded service.
