Hi Thomas;
I’ve been looking into this and even when trying to open the URL in the embed iframe directly I get the same error, so that begs the question; does this problem also occur when LYTE is not active?
frank
Thread Starter
towpni
(@towpni)
I see … But does this problem also occur when LYTE is not active?
Thread Starter
towpni
(@towpni)
The new YT policy affects all embedded vids – with or without YT LYTE.
What exactly do you mean by “… when LYTE is not active”?
Your plugin uses shortcode. When I deactivate it, all vids are completely gone, only some remeining code remembers visitors that something went wrong …
What can explain to my client? Will you offer a plugin update to manage the 153 error?
Kind regards
Thomas
problem is that I am at this point not certain where the problem is to be honest. I have seen LYTE working on multiple site the last days/ weeks, including my own blog (e.g. https://blog.futtta.be/2025/11/05/radiohead-2025-jukebox/), so this is not necessarily a generic issue with LYTE?
to advance troubleshooting, I would have to know if the problem also arises with a normal youtube-embed or a WordPress oEmbedded YT.
As LYTE acts on shortcodes but also on YT-iframes (in the HTML) and on a YT-URL on a new line, so can you try changing the shortcode into e.g. https://youtu.be/s-sMWH85E5g (so just that on one line) to see if that does or does not work?
Thread Starter
towpni
(@towpni)
Breaking news, it’s a hosting issue. I migrated the complete website to a staging site (different hoster) and voilà – videos (with your plugin activated) are looking good, no error 153.
wow, how … weird. any difference in the HTTP response header tags that could explain this?
Thread Starter
towpni
(@towpni)
After deleting “Security Headers”, sun was shining again.
I was also able to fix the error. Thanks to this blog entry, I looked for the following entry in the header of my theme:
<meta name="referrer" content="no-referrer">
After deleting it, everything worked again.
