Can't Connect Remote, 404

[crackulator]

Knewc 2.7.4, NextPVR v5 server, remote, two different clients. One is Linux, one is Kindle/Android.

Was working but the last couple days it just won't connect. Log file shows a 404.  Knewc Web Client doesn't work either, also says it can't connect.

Haven't changed anything (that I know of) since it was working. Restarted service, rebooted client, no change. Re-entered credentials several times. Also tried using real IP address instead of virtual static IP, no change.

Both clients can hit and play from the server just fine from web browsers.

Log enclosed. Any ideas?

[crackulator]

May not be knewc or remote that is at issue... just tried on local network with NextPVR Android client, no success there either.

Not sure what changed, only thing I can think of is Ubuntu doing its incessant updates...

[mvallevand]

Uploading logs takes 3 steps you likely missed one.

Martin

[crackulator]

Indeed, sorry

[crackulator]

I don't think it's a knewc issue. Suddenly, it seems, none of my clients can connect to my v5 server. But browser client works everywhere.

[mvallevand]

Have you got the remote api enabled for v5?

If it is local to upload your nextpvr logs.

Martin

[crackulator]

Yes, remote API is enabled.

Attached are the kodi/knewc and server logs. This attempt was local on my home network, one Ubuntu computer to another. From what I can tell the symptoms are the same.

[crackulator]

It appears to be the pincode. I rebooted and reset that again, for at least the third time, and now it seems to work.

Of course any rational person will suspect that I can't keep track of my pincode, but I can assure you that is not the case. I didn't touch anything before it started failing, and reset it to the same thing again several times in diagnosis, even restarted the server after setting it, and it's not an easy number to mistake. Something is wrong with those forms, man.

[BrettB]

It appears to be the pincode. I rebooted and reset that again, for at least the third time, and now it seems to work.

Of course any rational person will suspect that I can't keep track of my pincode, but I can assure you that is not the case. I didn't touch anything before it started failing, and reset it to the same thing again several times in diagnosis, even restarted the server after setting it, and it's not an easy number to mistake. Something is wrong with those forms, man.

I suspect that you have a browser or browser extension which is autofilling the PIN field. And in V5, when a settings field is changed (even by an autofill), NextPVR automatically (and silently) changes the setting in the config.xml file. At least a couple of people have had similar issues with their Schedules Direct credentials getting mysteriously changed, too. Those fields marked as "password type" (where the actual value is masked) are the most problematic because they tend to trigger the autofill more and because the user doesn't see any visual change to the field value. In the latest version, sub made some changes to the SD settings to try to discourage browsers from autofilling. He probably needs to do the same thing with the PIN field.

[mvallevand]

Yes I think that is it too, especially since you are using Firefox. Sub did attempt a change for the PIN autocomplete logic in the last release, but it still fails for me.

Typically to clean up I have to go to the FF settings and remove the two entries that show for the NextPVR IP.

Martin