Hi, I’m Tommy and I’m a developer support specialist at Vimeo – I recently replied to Steve above, and in all likelihood handled IP address whitelist requests from other users who have posted here in the past few weeks. I wanted to provide some information here so that developers and website owners encountering Vimeo errors related to IP blocks know what to expect and how to resolve their issue.
We have some blocked IP addresses on some cloud host providers. For security purposes we cannot publicly disclose which cloud hosting providers or which IP addresses on those providers are banned.
After making some changes on our backend last week, human users (such as clients using a VPN hosted by one of these cloud providers) should be able to solve a CAPTCHA challenge to gain Vimeo access and temporarily whitelist their IP address. Whitelisting IP addresses manually by contacting us at Vimeo should no longer be necessary, though we’re always happy to clarify and guide you in the right direction.
What seems to be happening on Discourse, and specifically when using the Onebox library, is that Onebox tries to get Vimeo video metadata in an unsupported way (based on what I’m seeing here). Officially, Vimeo doesn’t support the
og tags for widespread public consumption. Instead, we recommend using our oEmbed implementation to get that same metadata (embed code, thumbnail image, video url, etc.)
Using oEmbed or the full-fledged Vimeo API is generally not subject to the same IP block – using oEmbed or the Vimeo API are the only supported methods for servers to get and interact with data on Vimeo. Discourse will need to modify the Onebox library accordingly to use oEmbed instead.
The Vimeo oEmbed implementation is documented here: Working with oEmbed: Embedding Videos | Vimeo Developer