It seems there may have been a recent change on Vimeo’s side affecting background videos in Bricks.
When using a Vimeo video as a background video in Bricks, the generated embed URL returns a 403 error in the console:
Failed to load resource: the server responded with a status of 403 ()
For example, I simply enter this Vimeo URL in Bricks: https://vimeo.com/1143488454
Bricks automatically generates the following embed URL: https://player.vimeo.com/video/1143488454?autoplay=1&controls=0&loop=1&background=1&app_id=122963
After testing, I found that the issue comes from the automatically added parameter: background=1
With background=1 → 403 error
Without background=1 → video works correctly
So it looks like Vimeo may now block or restrict this parameter in some cases, which breaks Vimeo background videos in Bricks.
I contacted Vimeo support in parallel, and here is their response.
“What you’re seeing is normal: Vimeo’s background player mode (background=1) is a paid feature. On Free/Basic plans, it triggers an embed error (often shown as a 403 error or “cannot be played with the current embed configuration”).
You have two options:
Upgrade your plan to one that includes background embeds (Standard, Advanced, or Enterprise). Once upgraded, existing embeds using background=1 will automatically work.
Update your embed code to remove background=1 and use a standard player configuration instead. To recreate a similar “background” appearance on all plans, use: ?autoplay=1&muted=1&loop=1&controls=0&title=0&byline=0&portrait=0
(and add playsinline=1 on iOS).
The visual effect is similar, but not identical to true background mode.
Note: if this used to work before, it was due to a bug that incorrectly allowed background=1 on Free/Basic accounts, and that bug has now been fixed.”
Do you have any solution to continue using a free Vimeo account as a background video player?
I’ve updated to the latest Bricks version (2.3.6) but Vimeo background videos still generate URLs with background=1, causing a 403 error.
You previously mentioned that a future version would allow disabling the background parameter. Has this feature already been released? If so, where can I find it?
This will be available in version 2.4 because it is more than just a simple bug fix;, we have also added new options to accommodate different use cases.
Please feel free to test it once it is released and let us know your thoughts.
Came across this thread searching for an answer to this problem. I can believe that it is not a simple fix, so thanks for taking the time to include it in version 2.4. Is there an estimate on when this update will come? Thanks in advance!