Fresh AWS 1.1.6 stack couldn't import content

[sarurururu]

Description
A fresh Hubs cloud stack (both personal and enterprise versions) set up using the 1.1.6 AWS template with #6049 S3 bucket issue workaround cannot import content (stuck at rotating blue circle)

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Content>Import Content'
2. Specify a .pack/ URL, then Click on 'PREVIEW IMPORT'
3. See error

Expected behavior
Showing a preview of the avatar or scene to be imported

Screenshots

Hardware

• Device: [Desktop]
• OS: [Windows 11]
• Browser: [Firefox/ Chrome/ Edge]

Additional context
The same happens after updating the stack using the stock AWS 1.1.6 template (without workarounds). Using the AP-NE-1 (Tokyo) server.

[msub2]

Also observed this when attempting to set up Hubs Cloud AWS for the first time today. Attempting to import an avatar pack yields two failed network requests:

• A 404 to https://<cors-proxy>.<internal domain>/<request URL>, which if followed shows a GitHub pages 404 error page
• A 403 to https://<cors-proxy>.<internal domain>/null/api/v1/avatars/undefined

[tietoafinlandoy]

Same here, jamming to the "import content" as described above on fresh default template setup on Ireland server using MacBook Pro M1 (not that it would matter here).

On browser console errors: Uncaught (in promise) SyntaxError: Unexpected token '<', "<?xml vers"... is not valid JSON

[tietoafinlandoy]

@keianhzo with my limited knowledge and skills - this seems to be preventing finalising the deployment-setup as we cannot get past the obligatory setup of avatar and scene. Any links to follow to find a detour?

[nurse-the-code]

This bug also appears to be present in hubs-compose.