WebSocket Failing/"Try Connecting via TCP" Message

[Rodney-hubs]

Related to Discussion 3033.

After configuring CDN settings, importing a custom scene, and restarting the Droplet on Digital Ocean, the scenes fail to load and the "Unable to connect to this room, please try again later. You can try connecting via TCP..." message is shown.

Steps to reproduce (I believe the import steps are 12-18):

1. Create Hubs Cloud Droplet from Marketplace

• Basic/Shared CPU
• 2GB/50GB SSD/1vCPU
• NY1 Datacenter
• No VPC
• Authentication with SSH Key

1. Connect to instance via PuTTY using SSH Key
2. Configure Hubs instance

• Domain uses a subdomain that's within Digital Ocean
• Shortlink is within Digital Ocean
• Use startup script to create managed database on Digital Ocean (1GB/1vCPU/10GB Storage)
• SMTP configuration is through Mailgun
• Use startup script to update DNS records within project
• Enable 2FA

1. Sign in with admin account
2. Import a single avatar and set to default (Graduation Robot)
3. Import a single scene and set to default (Wide Open Space)
4. Create and enter room with default scene
5. Exit window (don't close room)
6. Restart Droplet with 'sudo shutdown -r now'
7. Once Droplet is restarted, sign in with admin account
8. Create and enter room (worked as expected)
9. Configure CDN (verified CDN is working)
10. Import custom scene (I can PM the custom scene link from hubs.mozilla.com if needed)
11. Create and enter room with default scene
12. Change scene to be custom imported scene and name the room
13. Exit the room and rejoin (Worked as expected)
14. Restart the Droplet with sudo shutdown -r now
15. Scene doesn't load and user is presented with Unable to connect to this room, please try again later.

I have recreated this three times and am happy to provide any additional information or assistance if possible.

┆Issue is synchronized with this Jira Task

[GBR-422777]

Did you find a solution to this?