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,304 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Few ways to get the HTML text from KBA is to Show XML, or Script Retrieve it, or SNUtil.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
RESOLVED:
With the assistance of NOW Support I changed the system_property
com.glide.security.referrerpolicyto the Value
origin-when-cross-originSee the Washington Docs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
We changed this system-property on one of our non-prod instances and the error-153 is no longer shown on embedded YouTube videos.
We have NOT made any changes to the individual knowledge articles.
Wat does changing this system-property value actually do and what is the resulting impact on our instance security?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I would review the NOW docs with your web / security team and base your config on the results.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
It seems this issue is not affecting our clients with Zurich instances.
Only Yokohama instances are affected. We have also confirmed this with our DEMO instances.
There's a solution to update the System Property "com.glide.security.referrerpolicy" to "origin-when-cross-origin" according to KBA: KB2614673 - Now Support Portal
However, ServiceNow Instance Hardening security recommendation is "Default", and adjusting that may lower the security score below what's agreed in contract.