NFPS / Private Native Stalker Client - Authentication Failed

IPTV Private Server (NFPS)
After disabling PVR Stalker NFPS and before enabling PVR Stalker cleint, you would need to do an IPTV Reset (with Kodi shut down), since PVR Stalker NFPS used its own set of internally generated credentials. When you enable PVR Stalker client w/o doing an IPTV Reset, the server sees a different set of credentials and will not allow authorization -- and thus you receive an authorization failure.
 
Thanks for the reply...

I already tried this a few times, I even went as far as to uninstall, turn of unplug device, wait about 2 hours and re-install kodi, setup up native stalker client and authentication failed.

Really don't know whats going on.
 
You must do the IPTV Reset. Even if you uninstall Kodi, the IPTV Reset has to be conducted before PVR Stalker client is enabled.

If worse comes to worst, change the credentials and see how that affects the situation. Make sure you are using the long form of the URL in the configuration dialog. (See the long form URL and other instruction within the tutorial below.)

http://iptvtalk.net/showthread.php?16461-PVR-Stalker-(Kodi-Built-in)-Set-up-tutorial
 
Thanks again for the reply ilan...

I did all you mentioned and went through thread slowly line by line, reset over and over, I changed credentials also, waited before retrying and native stalker client still is saying authentication failed.

Any ideas?
 
At the moment, I'm not sure. If everything is set up correctly, there shouldn't be an issue. All it takes, however, is one item to be incorrectly configured and there can be authentication issues. (Kodi needs to be shut down when you do the IPTV Reset.)
 
Post your kodi pvr.stalker configuration setup info.(blank out donation and last 6 digits of mac#).
you can also go to System settings/System/Logging and turn on "Enable debug logging".
Start kodi and run until you get the error. Shutdown kodi and go to your "userdata" directory.
There will be a text file named kodi.log. Open it and near the bottom 3/4 down, you will find a couple of lines with "ERROR..."
This will explain the problem.
If you cant figure the log out, post it for us to analyze.

And dont forget to go back and turn off debug logging.
/kens