I saw that error while working on the embed in our new blog. The easy thing to do is to just remove this header right?