Most likely causes
- The server URL, username or password was mistyped, or a space slipped in at the start or end when the details were copied from a message.
- The wrong port is set. A line issued for port 80, 8080 or 8880 will not connect if a different port is entered, so the login is rejected before it reaches the channels.
- The address uses http where it should be https, or the other way around, so the app cannot reach the portal at all.
- The subscription line has expired or was paused, so the credentials are correct but no longer accepted.
- Too many connections are already in use on the line. This can happen when the same login is streaming on more devices than the plan allows, and a new sign-in is refused.
- The login was entered on the wrong screen, for example typed into the M3U URL box when the account is an Xtream Codes login with separate username and password fields.
Fixes, in the order to try them
Retype every value by hand from the original WhatsApp or email message rather than pasting. Watch for a space before or after the server URL, username or password, and for a lowercase l read as a 1 or an O read as a 0. A single wrong or extra character is the most common reason for this error.
Use the Xtream Codes login fields correctly. On the add-user screen choose Login with Xtream Codes API, then fill the three separate fields: the server URL (the http or https address with the port), the username and the password. Do not paste a full M3U link into the username box, and do not put the username into the server field.
Check the port on the server URL. The address usually ends in a colon and a number, such as :80, :8080 or :8880. If your details list a specific port, it must be included exactly. Leaving it off, or using the wrong one, is a frequent cause of login failed even when the username and password are right.
Confirm http versus https. If the address your provider gave you starts with http, enter http; if it starts with https, enter https. Switching one for the other stops the app reaching the portal, which reads as invalid credentials.
Confirm the line is active. If it started after a renewal date, the subscription may have lapsed. Some users report the exact same login working the day before and failing once the line expired. Message the AurexTV desk to confirm the line is live before assuming a typo.
Free up a connection. If the plan covers a set number of devices and they are all streaming, a new login can be refused. Close the app fully on the other devices, wait a minute, then try signing in again on the device you want to use.
Delete the profile and add it fresh. Remove the saved user in IPTV Smarters Pro, restart the app, and add the account again from scratch using the Xtream Codes option. A profile saved earlier with a small mistake will keep failing until it is re-entered cleanly.
Related guides and fixes
IPTV Smarters Pro setup guide
The full walkthrough for adding your AurexTV login in IPTV Smarters Pro the right way, field by field.
IPTV Smarters Pro not loading channels
Signed in but the list is empty? Refresh the playlist, clear the group filter and reload here.
Contact the AurexTV desk
Send a photo of the error and we will confirm your line is active and the details are right.
All IPTV Smarters Pro fixes
Every common IPTV Smarters Pro problem and its fix, gathered on one page.
IPTV questions answered
Cost, legality, devices and setup, in plain language.
Still stuck after the fixes above?
Send the AurexTV desk a photo of the screen on WhatsApp and someone will walk you through it. Real people, under 15 minutes.
Invalid credentials / login failed FAQ
Does invalid credentials mean my subscription stopped?
Not usually. It most often means one of the three login values does not match, the wrong port is set, or http and https are swapped. Retype the details exactly and check the port first. If everything matches and it still fails, ask the AurexTV desk to confirm the line is active.
Where exactly do I enter the server URL and port?
On the add-user screen pick Login with Xtream Codes API. The server URL field takes the full http or https address including the colon and port number, and the username and password go in their own fields below. Keeping the port on the server URL is what many people miss.
I copied the details but it still says login failed. Why?
Copying often drags in a hidden space at the start or end of a value, which the app treats as part of the URL or password. Deleting the profile and typing each value by hand, checking for stray spaces, resolves most of these cases.
Could too many devices cause a login failure?
Yes. If the plan allows a set number of simultaneous streams and they are all in use, a fresh sign-in can be refused. Close the app on the other devices, wait a moment, then try again. If you need more simultaneous streams, ask about a larger plan.