A player can offer several ways to connect, but the correct choice is the one supplied for your account. A playlist URL, a server login and a device-linked portal are different workflows. This page explains the distinction so you can avoid a common first-setup mistake.
Recognise the format
A playlist usually arrives as a complete address to import. A server login normally separates the server address, username and password. A portal workflow may require a particular device identifier to be associated with access. Ask support which option to choose if the message and the screen do not match.
Copy without reshaping the details
Preserve the full URL, including punctuation and any query parameters. Do not add or remove a port, protocol or path based on another tutorial. For separate credentials, enter each value into its own field. Avoid extra spaces from copying an entire line of a chat message.
Protect the configuration
A playlist address can contain credentials even when it looks like an ordinary web link. Keep it private and do not paste it into public URL testers. Before replacing a working account, save the original details securely. If you accidentally expose them, ask support about rotating access.
Your checklist
- Identify the supplied account format.
- Choose the matching player login mode.
- Preserve URL punctuation and field boundaries.
- Treat full playlists as private account information.
Can I convert every portal into a playlist myself?
Not necessarily. Ask support which formats are available for the account and device rather than constructing addresses by guesswork.