Troubleshooting
Fix common RVE Cloud Rendering problems.
Cloud Rendering is not available
Confirm that RVE enabled beta access, the plan is active, and your API key is active. Check that the server environment contains the key after deployment.
A media file could not be accessed
Confirm that every media item has an HTTPS URL. A render worker cannot read a blob: URL. If you use signed URLs, make sure they remain valid for the full render.
The render starts but media playback fails
Open the media URL from a private browser window. Check the response content type, CORS rules, redirects, and URL expiry. The URL must return the media file to the render worker.
The editor still shows browser rendering
Confirm that you pass an enabled renderer to the RVE SDK through customRenderer. If the custom renderer is absent or disabled, the editor can use browser rendering.
The output opens in the current page
Download the output through your application instead of assigning the output URL to window.location. Fetch the file, create an object URL, and click an anchor with the download attribute.
You still need help
Send the render identifier and the visible error message to RVE support. Do not send your API key.