On pages translated by GTranslate, such as /fr/ or /en/, some images, scripts, or other assets return 404 errors. The same assets load on your default language pages.
Why this happens. The GTranslate proxy rewrites some absolute asset links inside inline page scripts so they carry the language prefix, for example /fr/wp-content/. The web server has no route for those prefixed paths, so they return 404.
How to fix it. The fix is a server rule that strips the language prefix for wp-content, wp-includes, and wp-admin paths. The rule leaves regular pages and the REST API untouched. On HCS-hosted sites, contact support to enable this rule. On self-hosted sites, pass this description to your host so they can configure it.
After the rule is in place, clear your site’s page cache. A CDN may take a few minutes to stop serving the old 404 response.