Error 153 on Youtube Videos
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2025 08:45 AM
Everything has been working perfectly fine for months now. But this week, on all of the YouTube videos on our intranet pages, there's an error code 153. I haven't been able to find information on what the issue is.
We used the Rich Content editor with the Video block and entered YouTube information on all the videos on topic pages. We have not changed any settings on our YouTube, and our IT department has let me know we have not made any updates to policies that would affect YouTube or ServiceNow. The only videos working are the ones that we have in the Video Carousel widget. I updated all of the videos the other day, and it randomly started working for an hour or so, but then it went back to having issues.
Has anyone else experienced this? Any ideas for fixes that still allow us to have a video within the Rich Content widget?
- 17,301 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
I have the same experience.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago - last edited 2 weeks ago
PRBs are only visible if you have a case and the PRB is attached to it. The current PRB for this scenario is PRB1957001, and the article is shared; it is visible once you log in to support.servicenow.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
We put in a case with HI so that we could monitor PRB1956661, but were told that it was being referenced incorrectly and that the actual record is PRB1957001, but the solution is the same - change the f32c629253120010d64cddeeff7b1291 system property from "default" to "origin when cross origin".
We've tested this in a Yokohama subprod and experienced the issue first in our Prod instance on Xanadu.
What I'm not seeing is guidance from ServiceNow on what security or other implications there could be, other than that "default" is best and "origin-when-cross-origin" is just "good" security. I'll admit that though I've read the KB linked above and I understand that there are different system property values that do different things, I don't really understand what I'm reading.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
Thanks! it works!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Our clients only had YouTube links on their KBAs.
So, we did this hacky workaround, that comes with some limitations... Not advisable if the KBA is often changing.
Use this filter to find KBAs with YouTube links:
textLIKE<iframe^textLIKEsrc="https://www.youtube.com^sys_class_name!=kb_knowledge_block^workflow_stateINdraft,review,scheduled_publish,published,pending_retirement,retired
For Each KBA, run the following in background script:
var gr = new GlideRecord("kb_knowledge");
gr.get("KBA SYS ID here");
gr.text = `The HTML here updated with referrerpolicy="strict-origin-when-cross-origin"`;
gr.setWorkflow(false); // Optional
gr.update();
Insert your KBA Sys ID and insert your HTML to the code. Add the below to all iframes with YouTube links:
referrerpolicy="strict-origin-when-cross-origin"
The limitations are:
- Any new KBA will need to be manually fix
- If the KBA is checked out, and re-published, then it needs to be manually fix