Identify the actual application
Follow the official project repository or the website it links to, then use its release downloads. Record the operating system, package and installed version. Avoid a site claiming to sell a premium or activated IPTVnator build merely because it uses the project’s name. The publisher specifically distinguishes its application from those offers.
Choose between desktop and a web/PWA deployment before following feature instructions. A desktop package and a webpage can look similar while using different media engines and permissions. The installer filename is useful for support, but does not establish an authenticated IPTV Australia compatibility test.
Match the source you received
The documented project supports remote or local M3U/M3U8 lists, XMLTV guide information and dedicated Xtream and Stalker/Ministra source paths. Enter information into the matching source form. A portal address is not automatically interchangeable with an M3U URL, and XMLTV is guide data rather than the programme video itself.
Give the source a recognisable local label without embedding your password in that label. Import one source first and check whether categories, channel names and a programme can be opened. If a list loads but no item plays, preserve that distinction instead of repeatedly deleting the account.
Check the selected playback path
The current README describes several built-in engines and desktop external-player options, with some options marked experimental. Begin with the default documented path for your release. An engine advertised in the desktop app should not be assumed available in a hosted web installation.
Guide loading, catalogue parsing and media playback are separate operations. Check them in that order so a missing guide does not become a needless reinstall and a browser codec limitation is not mistaken for a bad password. The most useful support report names the exact engine and the first stage that failed.
Treat extras as separate requirements
Catch-up, recording, downloads and metadata features depend on the source, application edition and relevant permissions. Their presence in an interface does not prove that your account grants them. Confirm those requirements before using them and keep private playlists and backups out of public issue reports.