Having followed advice/recommendations I set up a CloudFront CDN for our AWS S3 bucket on our Discourse a few days ago.
I added the S3 CDN URL in our control panel, then duly then issued a rebake command on 200,000+ posts.
Didn’t think much of it at that point, it was off and working it’s magic for the next 12 hours or so.
We have many, many videos embedded in our Discourse. We are a drone/uav community and people are posting and sharing their pictures and videos all day long. Tens of thousands of YouTube videos are on our Discourse posts.
Hindsight…? After adding a CDN URL, I probably only needed to rebake posts matching a
*.jpg pattern or similar
Anyway, what’s happened?
YouTube have blocked the IP address of our server
We can no longer onebox any YouTube links, our community is met with:
429 Too Many Requests
(a simple curl / wget on the server itself also returns the same thing)
We obviously got blocked at some point during the rebake as half of the existing posts that did have working videos, don’t anymore
I’m assuming this block is permanent but as you’ll know, it’s impossible to find anyone at YouTube to contact and beg forgiveness.
On the off chance it’s permanent, a question for @Iceman please. Can you share the details of how you obtained a second IP address at Digital Ocean, and the changes you made to route “out” on that IP but leave incoming traffic on the existing IP?
And a question for everyone, does anybody know if this block is likely to be just temporary? And/or is there anything I can do in order to fix my now very broken YouTube posts?
For a heavily media-driven community, this is quite disastrous for us.