Thanks for your report. We think we’ve found the problem and should have an update out later today.
Thread Starter
aprtv
(@aprtv)
Great news!! Thank you as always Rob. You’re plug-in otherwise is the best thing to happen on WordPress. I appreciate the quick response and action.
When you have finished updating and testing, please let me know if the fix worked or not.
Hi Rob, I am having the exact same issue. I checked today August 12 11:50am pst and the issue is not fixed.
Thread Starter
aprtv
(@aprtv)
Unfortunately both of my sites that utilize the plug in are still experiencing the issue as of 8/12.
Just a quick update. We haven’t been able to get any information from Roku as to what exactly is the problem. They have said the feeds are not structured properly, however, we haven’t made any major updates to the REST API for Roku DP and have been unable to replicate it on our test servers using WP Engine and DreamHost (both of which work fine).
We even went as far to import the JSON feed from a few users and had it load in Direct Publisher with no errors.
One thing you may want to try is if your host is using “mod_security” in PHP, have your host disable it and try to ingest the feed again. It has worked on some users servers, but it depends on if your host is willing to make the change or not.
We will update you again when we have some answers from Roku beyond the basic response we are getting.
Because Roku has been extremely unhelpful, we spent the weekend testing things out and trying to find a solution.
@aprtv We took an exact copy of your JSON feed from your server and moved it to our testing server. The feed validates perfectly and Roku is able to ingest the feed without the 406 error.
Screenshot:
https://rtestplatform1.wpengine.com/test-feed/aprtv-test-feed-img.jpg
Link to the test feed:
https://rtestplatform1.wpengine.com/test-feed/aprtv.json
This proves to us that the issue is between Roku Direct Publisher and your hosting company. Unfortunately, until they give us a real answer (beyond the default one they gave you) we are unable to diagnose the issue.
We will keep working on this until we have an answer from Roku.
It looks like Roku did change something, but we are not sure what it was. However, if your host is using “mod_security” in PHP, it will need to be disabled in order to fix the issue.
Please note that many “shared” hosting plans will not disable mod_security, so you may have to upgrade to a VPS or find another host that doesn’t require mod_security to be enabled.
Thread Starter
aprtv
(@aprtv)
According to my host…even with disabling mod_security in PHP they are saying the problem is the following:
[*] Rule ID: 900095
[*] Times Hit: 67
[*] URLS Affected: /wp-json/tv/roku/
[*] Description: Bad UA :: Fake Mozilla Agent
Yes, it appears Direct Publisher has changed its User Agent. You’ll need your host to allow an exception for the updated UA.
