Support

Velora Player for iPhone, iPad and Apple TV

Before you write in: if a channel buffers, a film is missing or your login stopped working, that is almost always your IPTV provider rather than the app — and we have no access to your account or their server. Anything that looks like the app misbehaving, though, we very much want to hear about.

Getting started

Connect an Xtream Codes playlist

Open Velora and choose Xtream Codes on the welcome screen.
Enter the server address exactly as your provider gave it, including http:// or https:// and the port if there is one — for example http://example.com:8080.
Enter your username and password, and give the playlist a name you'll recognise.
Leave Download EPG on unless your provider's guide is enormous and you don't need it.
Tap connect. The first load pulls the whole catalogue, so give it a moment; later launches read the cache.

Connect an M3U playlist

Choose M3U playlist on the welcome screen.
Paste the full playlist URL — it should end in .m3u or .m3u8, or be a get.php link.
Optionally add an XMLTV guide URL. Plain and gzipped (.xml.gz) feeds both work.

Set up the Apple TV

Add the playlist on your iPhone first. With iCloud on, the Apple TV picks it up by itself and reads the password from iCloud Keychain — nothing to type on the remote. If it asks for the password anyway, that item hasn't reached the TV; enter it once in the single field and it's done. You can also add a playlist directly on the TV if you don't own an iPhone.

Troubleshooting

“Can't connect” when adding a playlist

Check the address for a missing http://, a wrong port, or a trailing slash or space.
Try the same URL in Safari on the same device. If Safari can't reach it either, the problem is the server or your network, not Velora.
Some providers block particular countries or require a VPN; some suspend accounts for connecting from two places at once.
If your subscription has expired, the panel will refuse the login — Velora reports that as an expiry rather than a typo.

A channel or film won't play

Try a different channel. If everything fails, it's the account or the server; if one fails, it's that stream.
Velora uses Apple's player where it can and switches to its bundled libVLC engine for Matroska, AVI and raw MPEG-TS. If one specific file misbehaves in a way others don't, tell us the container and codec if you know them.
Live streams stall when the provider's server is overloaded — usually at peak times, and usually nothing the app can fix.

The guide is empty or wrong

Guide data comes from your provider's XMLTV feed. If they don't publish one, or publish a thin one, there is nothing for the app to show.
Entries appear against the wrong channel when the provider's channel IDs don't match the IDs inside their own XMLTV file — a provider-side mismatch we can't correct from here.
Programme times are drawn from the feed's own timestamps. A feed that publishes the wrong timezone will look shifted.

The catalogue looks out of date

Velora caches your library so it opens instantly rather than re-downloading everything each launch. Pull to refresh, or remove and re-add the playlist, to force a full rebuild.

Nothing syncs to my other device

Both devices need to be signed in to the same Apple ID, with iCloud Drive and iCloud Keychain switched on.
Check that Velora is enabled under Settings › [your name] › iCloud.
Sync is not instant — Apple's key-value store batches changes. Give it a minute and reopen the app.
Not signed in to iCloud? Everything still works, just only on that device.

I forgot my provider password

We can't recover it — it's stored encrypted in your device Keychain and we never receive it. Ask your provider.

Still stuck?

Email support@veltroforge.com. To get a useful answer on the first reply, please include:

your device and OS version (e.g. iPhone 15 Pro, iOS 18.4 — or Apple TV 4K, tvOS 18.4);
the Velora version, from the app's settings;
playlist type — Xtream or M3U;
what you did, what you expected, and what happened instead;
a screenshot or screen recording, if there's anything to see.

Please don't send us your server address, username or password. We never need them, and we don't want them. If a problem genuinely can't be described without one, we'll say so.

We're a small team, so replies take a day or two — longer at weekends. Bug reports and feature requests are both welcome.

Also on this site

Privacy Policy — what the app stores, and why we hold none of it
Terms of Use
Frequently asked questions