My channel has been up and running for over a year. It auto ingested at 4:21PM today and everything ingested fine. It went to auto ingest again at 5:43PM and everything failed. It is saying “required video url is unreachable” for all of my videos, and also errors saying no valid items were found in the feed. I am hosting with Vimeo Pro but my JSON is created on Wordpress. All my links/video types are HLS. Is anyone else having this problem and does anyone know what is causing it or how I fix it? The videos work fine for me when I go to the video links in my JSON feed and I did not change anything between the time it was working and the time it went down. Thanks for any help.
Same issue for me. Vimeo videos, json hosted on my site.
Feed URL: https://bibletalk.tv/cache/roku.json
Also receiving the same. I’ve tried switching my Feed URL from my WP Smart TV generated URL, to my Vimeo Business account showcase feed URL, and lastly, directly to the .json file hosted on my server. I’m still getting the same result:
Any updates on this issue would be greatly appreciated.
Will do.
I sent a support request first thing this morning. Hopefully it can be resolved.
Thanks for posting this. I was just on mine a day or two ago & all was fine. Another channel seems to work, although oddly in the developer portal that one has the errors - missing url warning, but the videos still play. Likely a 6 hour cache issue.
I send an email as well, will post back if I hear anything. Hopefully we hear something before the weekend.
I’ll say, it’s getting tougher & tougher each time. I speak for alot of us when I say I mostly am in it for the challenge & intrinsic motivation anymore (“Doing It”), rather than any real money. The constant bugs, uninformed blackouts, errors due to backend platform updates, they just always seem so ill timed. I hope it isn’t an issue between Vimeo & Roku (I doubt it as Vimeo seems to offer json feeds for Roku DP), as I’m not sure I can re-upload to a new host & re-code everything. Just overwhelming to redo but we’ll see. Hopefully just a glitch that’s fixed easy peasy.
@HalGatewood Your Json feed file has some problems.
- Your release date does not reflect the Json spec (YYYY-MM-DD).
- You’ve incorrectly formatted the Credit object. It’s actually an array.
Good catches! Thanks!!
Sorry, forgot to post my feed url… it is http://www.votvnetwork.club/wp-json/tv/roku/
Wish I could use it, but I’m in a Mac.
I just noticed that the only videos that are still showing on my channel are pointing to Amazon AWS. The ones pointing to Vimeo are all down (HLS or MP4).
When testing through the Stream/RAF Tester Tool, they work fine.
I heard back from partner success, you all likely did as well. Just posting for anyone who didn’t or just checking in, seems they’ve become notified by us and are looking into it.
"We’ve had some other reports of Vimeo feeds with channel issues.
We are working with our engineering team and I will update this thread as soon as I have more information."
Roku is looking into it, but the issues is most likely with Vimeo. I changed my media URL to my JWPlayer account and Roku successfully ingested the video. I’ve logged a ticket with them as well.
I’m not really looking forward to switching everything back over to another host, but I will if I have to…or self-host.
I am having the same issue with a Vimeo feed that was working fine and now is down. Sent in a ticket. If you get a response, please post! Thx!
I haven’t received anything more from Roku, but received the following message from Vimeo:
"Thanks for following up and sorry to hear you’re having trouble. I’m passing your message along to one of our Developer API technical specialists.
You’ll receive another note from us as soon as possible. Thank you for your patience!"
I think I am struggling with the same issue. I just moved my videos to Vimeo. Early today they were working. Now they are not. Here is how I have the videos in json. Is this right? Thanks for any help.
{
“id”: “50099”,
“title”: “Tennessee Commit Elijah Howard”,
“shortDescription”: “Elijah talks about why he chose Tennessee. Who he talks with the most on the Vols staff.”,
“thumbnail”: “https://drsec.s3.us-east-2.amazonaws.com/eh.jpg”,
“genres”: [“news”, “special”],
“releaseDate”: “2020-03-20”,
“content”: {
“dateAdded”: “2020-03-20T14:14:54.431Z”,
“captions”: ,
“duration”: 536,
“videos”: [{
“url”: “https://vod-progressive.akamaized.net/exp=1584934522~acl=%2A%2F1704192155.mp4%2A~hmac=0c4993f56e361e67479978c009663106c88ea955aa627472cc2345a9e022a342/vimeo-prod-skyfire-std-us/01/4911/15/399557131/1704192155.mp4”,
“quality”: “HD”,
“videoType”: “MP4”
}]
}
},
@RedRoad Assuming your example is a Short Form Video (based on the duration), and, according to the Roku Json spec, you’re missing at least one required object: ‘longDescription’.
Has anyone had any luck?
I’m trying to publish a new channel that hosts their videos on Vimeo and they are not working either. I have other channels that are already published using the same JSON file using Vimeo hosted videos and it is working fine.
My theory is that Vimeo is doing a redirect on the URL and that is causing Roku feed checked to think that the video doesn’t exist when it actually is there. I wished the validation wasn’t so strict.
Somebody please help with this… stuck in the water and cannot publish channels.
@avodahsoftware I am same boat. I got this back from them
'Thank you for getting back in touch! I’m really sorry for the delay in getting back to you! We’re experiencing a high demand for support at the moment.
I’m really sorry for the confusion caused here.
The direct video links that we provide are not meant to expire. However, these links will redirect to expiring direct video links when accessed by a browser. For security purposes, a unique token is appended to the end of the redirect URL. Each time you click on the original direct video link, a new direct video link should be shown, with a new token.
When sharing direct links, we always recommend double-checking that the link begins with https://player.vimeo.com/external/ as opposed to https://fpdl.vimeocdn.com/ or https://gcs-vimeo.akamaized.net. When pasting a direct link into another application, you’ll want to make sure that the original direct link stays in tact. If the fpdl.vimeocdn or gcs-vimeo.akamized.net link is shared and opened in a browser after the active time has elapsed, an error message will appear. The player.vimeo/external URL will automatically transfer viewers to an active link and will never expire.
I hope this information helps! Please let me know if you have any other questions, I will be happy to help.
Sincerely,
Rachel M.
Community Support Associate
