The app offers a login with a server address plus username and password, and a playlist option that takes one long URL. The API-style login is easier to type on a remote and usually brings a program guide and on-demand sections in properly. The playlist option is one field but a very long one, and it tends to present everything as a flat live list. Both connect to the same line, so this is a convenience decision rather than a quality one. If your service issues both, start with the API login. If sign-in fails there, the playlist URL is a useful second test, because a working URL alongside a failing login points straight at a typed field.

The name field is a label for you and can be anything. The username and password are case sensitive and are the two fields most often mistyped, because a remote keyboard may capitalize the first character. The server field wants the protocol, the host and the port exactly as issued, with no trailing slash and no space at the end. A missing port is the single most common cause of an otherwise correct login being rejected. Enter each field, then move back through them and read them once before submitting. Thirty seconds of proofreading saves the reinstall cycle people usually try next.

1. 1Name: any label you like
2. 2Username and password: case sensitive, watch auto-capitalization
3. 3Server: protocol, host and port, no trailing slash

The messages are terse but they do distinguish causes. An invalid credentials response means the server answered and rejected the details, so the address is right and a typed field or the account state is wrong. A connection or timeout error means the server was never reached, which points at the host, the port or the network. A successful login with an empty channel list means the account authenticated but the line has nothing assigned or the plan lapsed. Treat those as three different problems. Reinstalling the app addresses none of them, which is why it is the wrong first move even though it is the most common one.

Because plans carry a set number of simultaneous connections, from one to five. If someone starts a stream while your allowance is full, one session is refused, and the app usually reports a playback failure rather than explaining the cause. That looks like a fault and is actually a limit. Two habits help: close the app properly rather than leaving a stream running in the background, and size the plan to the number of screens that genuinely watch at the same moment. Installs are unlimited, so having the app on five devices is fine even on a single-connection plan, provided only one plays at a time.

Hide the categories you never open first. The app holds the visible list in memory, and it becomes unstable above roughly 18,000 visible channels, so trimming a 54,000-plus catalog is a stability step and not a cosmetic one. Then set the buffer to the lowest option available and point the network at a public DNS resolver. Those two settings resolve more stutter than any other pair. What they cannot touch is oversold capacity on a provider's servers, which no device setting reaches. That is the reason to ask any service what uptime it commits to. IP4KTV runs 99.99%, about 53 minutes a year.