And a wget from the server, if it helps?
1 like
Strange, no?
That the wget takes you to the consent page, but the oneboxāing doesnāt? 
EDIT/UPDATE:
Iām not a python developer, but does this help?
2 likes
I noticed that the āembedā URLs for YouTube videos donāt (currently!) redirect to the consent page. Iāve created a couple of PRs so that weāll attempt to fetch embed URLs and parse the JSON contained within the response body.
Itās not the most elegant solution, but it might be a reasonable way forward for now.
13 likes
Thatās great news, appreciate you taking the time to look in to this for us all 
2 likes
A possible fix for this has been merged in. Can those affected please update if possible, and let us know if the problem with Oneboxing videos has been resolved?
11 likes
This is 100% a YouTube issue, not a Discourse issue.
@techAPJ went over and above to solve a similar issue with Instagram oneboxes last year, again when it was an Instagram issue and not a Discourse issue.
@jamie.wilson and anyone else who worked on this YouTube issue over the last week or so, I canāt thank you enough.
The level of support you all provide when itās not even your problem is simply second to none.
I thank you all for your time and dedication 
6 likes
I can update our Discourse tomorrow morning. Will report back.
2 likes
Itās looking good on my staging server - Iāll upgrade the production site this morning and will update my report.
Edit: our YouTube embeds are working properly again 
Thanks for your help @jamie.wilson!
6 likes
Also confirmed!
I can even click āRebuild HTMLā on previously failed ones and the video appears in under a second 
Great job @jamie.wilson - Thank you 
4 likes
Have you tried embedding via the youtube-nocookie.com domain?
Embed videos and playlists - YouTube Help ā āTurn on privacy enhanced modeā
3 likes
Can also confirm this works, server is in Germany. Thanks a lot! 
1 like
Any chance this could be merged into the stable branch as well to be included in its next release?
When a stable release is cut (next one happens next month) all commits will be included!
3 likes
Sorry, perhaps Iām not using the right terms here. I didnāt mean version 2.7, but what is likely to become 2.6.5.
Our policy is to only backport critical security fixes to old stable releases, so Iām afraid you will have to move to our standard release channel or wait for next stable.
Unless @jamie.wilson says itās a clean backport, but at this point in the release cycle it may be too risky.
2 likes
Fair enough ā thatās a reasonable policy and I respect that.
Just though asking anyway as this is a quite annoying thing to live with for some weeks for those who opted for this channel for the stability.
1 like
Thatās the thing right? The stable channel is not our default release channel, and not what we ship to our many paying customers for a reason.
Because while it provides a āstableā source code for the product, the internet it interacts with is much more dynamic, and we go for great lengths to quickly adapt Discourse to the changing environment in the internet, be it changing behaviors on the browsers who are updated every other week, in the thousands of sites we onebox, etc.
7 likes
Itās stable, but itās actually less well tested, because many fewer people use it. If this issue had come up 10 months before the next stable release, it likely wouldnāt be back ported. In the English sense of the word stable youāre better off with tests passed.
I run Ubuntu only in long term release versions. I donāt recommend stable (or even beta) with discourse.
1 like
This topic was automatically closed after 16 hours. New replies are no longer allowed.