Some providers refuse streams that come from servers in data centres, but accept the member's home connection. For those playlists, AromaOtt Player uses direct play: your device loads the lists and the streams itself, from your own connection. The Android app does this from version 2.2.2, and the web player offers what your browser allows.
How do I know the provider refuses our server?
The player says it in one sentence instead of retrying forever, for example:
- Your provider refused the stream from our server (511). Direct play is off for this playlist: ask whoever manages your account to turn it on.
- Your provider refused the stream on this device (403). The line may have expired or be locked to another device or address.
- Your line is already in use on another device (connection limit).
- Your provider is not answering right now.
The number is the answer the provider gave.
Which lines play on my device?
The operator decides per line. By default:
- Your own playlists and the line your provider set up for you play on your device.
- Shared servers play through our server, unless the operator sets them to play on devices.
A line can also be set explicitly to on the member's device or through the server.
How does it work in the Android app?
From version 2.2.2, for a line that plays on your device:
- The app receives the line's address and login over your signed-in connection and keeps them in its private storage.
- It loads the Live TV, Movies and Series lists itself, one at a time.
- It plays streams straight from the provider, from your connection.
The provider sees your IP address, as it would for any player at home. If the provider refuses your device too, the line itself is the problem: it may have expired or be locked to another address.
Older app versions cannot open plain http addresses on the device and play these lines through our server, which some providers refuse. Update the app.
What about the web player?
A secure page like aromaott.com cannot load plain http video, and most providers use http. So in a browser:
- Safari and browsers with built-in HLS offer Open in the HTTP player, a plain http page of the player (not encrypted) where the browser reaches the provider itself. Or choose Play through our server.
- Chrome, Edge, Brave and Firefox on a computer can use the optional AromaOtt Web Helper extension.
- Other browsers play through our server with a notice. If the provider refuses our server, use the AromaOtt app.
If a line is https, the browser can often play it on the device directly.
Do you use proxies to get around refusals?
No. Streams either come from your own device or from our server, openly. No third-party or residential proxy is ever used to hide our server.
What if the player says direct play is off?
That line is set to play through our server. Only the operator can change it. Tell whoever manages your account which playlist it is; they can test the line from our server and switch it to play on your device.
Is direct play less private?
It is different. With direct play, your device talks to the provider, so the provider sees your IP address and the player's name. Through our server, the provider sees our server's address instead. For direct play, the line's login reaches your device, only over your signed-in connection, and is never shown in Diagnostics. The privacy page explains this.
What else helps with refused or busy lines?
- Close the player on other devices using the same line.
- In Settings → Player, try the other Live stream format.
- Check Settings → About → Diagnostics: it shows whether each play went through the device or our server, and the provider's answer.