How to set up pvr.stalker.NFPS and have a Full EPG

Status
Not open for further replies.
#181
Thank you. I did all of those things (on the page you referenced). Doesn't help. When it was free, I successfully set up Stalker PVR with the above same steps (minus the username and password) without any problems

Btw, above I initially forgot to mention that the timezone is set to "America/New_York", in case that matters. I updated the original post above to contain that information, too.

It's worth noting that I also tried my Donated account credentials on a laptop with Kodi v15.x and Stalker PVR v0.8.1. Same issue.

Here are the kodi.log entries at the moment of the problem ....


Code: 
... [ SNIP ] ...
10:24:15 T:140591249745664   DEBUG: AddOnLog: Stalker Client: LoadProfile: timeslot=113.326624
10:24:15 T:140591249745664   ERROR: AddOnLog: Stalker Client: LoadProfile: status=1 | msg=table | block_msg=
10:24:15 T:140591249745664   DEBUG: CAddonCallbacksAddon - QueueNotification - Stalker Client - Error Message : 'Unable to load channels.'
[B][COLOR=#a52a2a]10:24:15 T:140591249745664   ERROR: PVR - GetChannels - addon 'Stalker Middleware:http://11.iptvRocket.tv' returned an error: server error
10:24:15 T:140591249745664   ERROR: PVR - GetChannels - cannot get channels from client '34400': server error[/COLOR][/B]
10:24:15 T:140591249745664   ERROR: PVRChannelGroup - Load - failed to update channels
10:24:15 T:140591249745664   ERROR: PVRChannelGroupInternal - Load - failed to load channels
  ... [ SNIP ] ...



Ideas anyone? Thank you!
 
Last edited:
#182
-- KODI version: 16.0 Alpha-1 (from GitHub; complied yesterday). I've compiled from GitHub this many times.
-- PVR Client: Stalker PVR v0.9.3 (complied yesterday).
Click to expand...

Alphas can't be supported here, as that version of PVR stalker. The reason being is that Alphas are experimental, but if you are able to get it going on your own, you can mention it, but always caveat with that its probably not going to work. Also, the password is not required, as of yet, and the timezone is not working, and probably best kept to default.
 
#183
Hello @Dara

Thank you.

Related to your comment above (#184), I went ahead and deleted the "settings.xml" file (this is Fedora/Linux by the way), and re-configured it through the U.I., but this time leaving the default timezone of "Europe/Kiev"; and I omitted the Password, too, even though the welcome-email indicates to use the same 12-digit number for both Username and Password. But I omitted it here, per your above comment.

I should also mention that I did the "Clear caches" steps (I almost always do as a matter of habit now); as well as tried Enabling/Disabling Parental control and clearing the cache (a step that you mention in your other read-only instructional thread).

Still cannot connect. And it's still the same error (above) indicated in the log file.

Does that log entry have any specific meaning, or seen before?

Finally, the only thing left to try, per your comment above, is to reboot my multi-boot laptop to Windows 8.1, and try a non-Alpha version of Kodi and Stalker PVR (no compiling -- just whatever is released). I will be doing that now.
 
#184
Just remember that PVR Stalker and IPTV Stalker are completely different. There is no "Clear cache" for the PVR Stalker available through "TV" or "Live TV" and parental control means nothing there as well for the configuration issues...at least on the released versions. You can do the various "clear caches" available in Kodi elsewhere, but all that does is clear the video buffer or in the case of IPTV Stalker, a channel cache.
 
#185
Yes, I Roger all that.

I'm only using the "PVR Stalker" client by dvbken. As far as "Clear cache" goes, the two "clears" I'm referring to are under the TV Tab. Occasionally clearing those (in the past) worked to get things going (i.e. to successfully load channels via PVR Stalker). But, yes, there are no clear cache options in the PVR Stalker client itself.

Anyway, my update here (as promised above) is concerned with trying my Donation account credentials on Windows 8.1, with PVR Stalker v0.8.3 and Kodi v15.0 Git 20150721 (which I simply downloaded from the Kodi downloads page).

Sadly, the same issue persists.

Here are the Kodi log entries (on Windows 8.1) at the point of the issue:
Code: 
... [ SNIP ] ...
12:08:09 T:4752   ERROR: AddOnLog: Stalker Client: SData::LoadProfile: status=1 | msg= | block_msg=        
[COLOR=#ff8c00]12:08:09 T:4752   ERROR: PVR - PVR::CPVRClient::GetChannels - addon 'Stalker Middleware:[/COLOR][URL="http://11.iptvRocket.tv"][COLOR=#0000cd]http://11.iptvRocket.tv[/COLOR][/URL][COLOR=#ff8c00]' returned an error: server error
12:08:09 T:4752   ERROR: PVR - PVR::CPVRClients::GetChannels - cannot get channels from client '769': server error[/COLOR]
12:08:09 T:4752   ERROR: PVRChannelGroup - PVR::CPVRChannelGroup::Load - failed to update channels
12:08:09 T:4752   ERROR: PVRChannelGroupInternal - PVR::CPVRChannelGroupInternal::Load - failed to load channels
12:08:09 T:4752   ERROR: PVR - PVR::CPVRChannelGroups::Load - failed to load channels
12:08:09 T:4752   ERROR: PVRManager - PVR::CPVRManager::Process - failed to load PVR data, retrying
... [ SNIP ] ...

I tried it with and without the password field filled in. The only real difference -- that I can see -- between the Windows 8.1 log entries and the Fedora/Linux log entries (pasted previously above), is the client number (769 versus 34400).

So I've now methodically tried everything as instructed to the letter; on multiple OSs; on multiple versions of Kodi and PVR Stalker client. The issue persists.

Is this possibly a provisioning issue?
 
#186
Since the MAC is made up, try to register a different one and see what happens with that. Also, it could be an issue with your local ISP, I'm not sure why but someone with a VPN was able to get it going with that on.
 
#187
Hi again @Dara:

Thanks again for the replies.

Yeah, I did also try establishing VPN sessions first, too, just in case the ISP was up to something. I tried that a few times, with a few different destination locations. Sadly, that doesn't appear to be it (i.e. doing that didn't fix it).

A question (or two) regarding the MAC address. You're correct that I made it up per my comment #181 ...
-- Does not the provisioning tool behind the order page have a check for possible MAC conflicts?
Maybe you don't know, but just asking in case you do. :)

-- Also, I emailed the Contact-Us page about this issue. What, if not that, is the support/escalation procedure for problems like this?

I will try a different MAC now (I have to figure out how to do that). I'm not hopeful, but I'll report back my findings.

Thanks!
 
#188
The only way to verify your mac is unique to your donation is to try to input it into another donation, preferably expired. That will tell you that it has been assigned. Unfortunately, the MAC checker seems to verify wrong macs and linked macs as valid. So, the core problem if you had exhausted options could be 'provisioning', given the number of people doing this in the last week.

It may take some time for your e-mail to be answered by papaio. You should only trust the mods or supermods with donation information, but that's the next step after you've done it all.
 
#189
dara said:
The only way to verify your mac is unique to your donation is to try to input it into another donation, preferably expired. That will tell you that it has been assigned. Unfortunately, the MAC checker seems to verify wrong macs and linked macs as valid. So, the core problem if you had exhausted options could be 'provisioning', given the number of people doing this in the last week.

It may take some time for your e-mail to be answered by papaio. You should only trust the mods or supermods with donation information, but that's the next step after you've done it all.
Click to expand...

Thank you Dara.

I just searched my Donation and looked at my "Rocket", and there is definitely something inconsistent because the welcome-email says that the IPTV Portal URL is http://11.iptvRocket.tv (eleven); but on my Rocket Donation page (where you can change your MAC address), it indicates that it is http://1.iptvRocket.tv (one). Hmmm.

So I tried the latter, but that doesn't work either (with or without a VPN established). The Kodi log errors now are the same as before, except that the named IPTV Portal URL is http://1.iptvRocket.tv (which is expected).

I haven't changed anything yet (i.e. haven't the MAC), but thought I'd just quickly indicate that oddity here (before I did); in case you had a comment about this anomaly/new development. :) Thanks!
 
#190
The donation check page has the old 1.iptvrocket.tv for me as well, so you aren't the only one. I noted that the first day that 11. came available. For PVR Stalker, it doesn't matter as both address resolve to the same place, but it definitely is an issue with boxes and the STB Emu. To avoid confusion, I tell everyone to use the 11. address for all except IPTV Stalker.
 
#191
dara said:
The donation check page has the old 1.iptvrocket.tv for me as well, so you aren't the only one. I noted that the first day that 11. came available. For PVR Stalker, it doesn't matter as both address resolve to the same place, but it definitely is an issue with boxes and the STB Emu. To avoid confusion, I tell everyone to use the 11. address for all except IPTV Stalker.
Click to expand...


Gotcha regarding the above. Thanks.

Next, when I clicked on the Change MAC address button, the following warning came up. Notice another oddity ... The prefix is now 00:1A:78 (not 00:1A:79). Maybe they ran out of MAC addresses and needed to change the 3rd. octet?

Code: 
[COLOR=#ff0000]WARNING: If you are using an STB emulator for IPTV then you should use a MAC Address under the following range 00:1A:78:XX:XX:XX (replace XX by hexadecimal digits), or your MAC Address may be modified without any previous notice.[/COLOR]

I still haven't updated the MAC just yet.
 
#192
78 doesn't work yet. It's another thing that is confusing people. The 78 is intended to keep the emulators and Kodi add-ons from interfering with boxes that can't change their MACs.
 
#193
dara said:
78 doesn't work yet. It's another thing that is confusing people. The 78 is intended to keep the emulators and Kodi add-ons from interfering with boxes that can't change their MACs.
Click to expand...

LOL. :) So this is definitely a provisioning (slash moving target) issue.

I changed the MAC Address so that it uses the same last-three octets as before, but now with the '00:1A:78' prefix. FYI: For good measure, I also went back to 11.iptvRocket.tv (even though, as you mentioned, nslookup(1) for both are the same... for now).

Well that finally did work. The channels loaded. \o/

BUT: Do we think I should change it again to something beginning with "00:1A:79" or -- as the change button suggested/warned -- perhaps "00:1A:78" now works, and can be used? I'd hate to not leave well enough alone. I've been struggling with this since last night. I'll change it if I have to, of course. :)

Thanks again.
 
#194
You know, I've been thinking the same thing about 78. I initially linked my donation with a 78 before the system went paid, but changed it to 79 just before. I've not had problems with my MAC ever. Try changing it to use the 79 to see if it works.
 
#195
longodongo said:
I think your reply is inappropriate and unwarranted,anything having to do with this service and obstruction of it is on topic. Simple as that.
Click to expand...

it is warranted because this thread is for those that need help with Mac Addy and connecting that way , as they paid for.
It's not about posting 'walk arounds' and etc..
Please do not hyjack !
 
#197
dara said:
You know, I've been thinking the same thing about 78. I initially linked my donation with a 78 before the system went paid, but changed it to 79 just before. I've not had problems with my MAC ever. Try changing it to use the 79 to see if it works.
Click to expand...

@Dara, What I'll do is let it ride for a week or so and report back my experience/findings (i.e. with '.78'). We'll all be better off with that extra intel. :)

I can also confirm that my Donation works with KODI v16.0-Alpha and Stalker.PVR client v0.9.3 (dvbken). So far so good anyway. Your mileage will vary here friends so, as @Dara pointed out, stick to non-Alpha versions of Kodi. I just happen to require downloading and compiling KODI & Friends from GitHub (e.g. Kodi; Platform; Kodi-platform; Pvr.stalker, etc.), because I run Fedora/Linux (not even Ubuntu), and nearly never boot into Windows 8.1 either. So I needed to do things from scratch and got accustomed to it, a while back. But, again, non-alpha versions are strongly recommended. :)

@Dara thank you for your guidance and insight today. It was tremendously helpful!
 
#198
No problem on you keeping 78. Like you said, if it works, why mess with it! I was thinking about trying it myself and thought better of it, but I'll make that a 'try this' for those that aren't connecting as a last resort.
 
#199
Hello, idid the setup according to the text instructions and it did work perfectly in kodi 14 and 15 but since yesterday i think it cant start it says an error happen to the stalker plug in. ? has anyone notice this issue, can you verify the server link.
is it htt //portal.iptv...... or the one in the pictures 1.iptvpriv........
because i have try both using the h tt p and without it and still wont load.
Thank you and good work stalker is the most stable iptv source i have
 
#200
The pics were old in the second post. I just updated the first one with a correct portal url. Look for the new tutorial at the top of the Kodi Tutorials section. It has the right portal url for all supported servers. (starts with http://11.)
 
Last edited:
Status
Not open for further replies.
Top Bottom
Back
Menu