META File not loaded

[Arko7777]

Hi All,

maybe some of you can help. I searched already a lot that's why I try my best here.

Our hubs stops here and is never ever connected again. Where is the issue? What to change? Anything inside the CORS?

-) and here also the "network" log i got out of it. It seems that the Meta file is not loaded.

Thanks in advance!

[robinkwilson]

Quick questions:

1. Do you have a custom client?
2. Did you update any Server Settings in the Admin Panel?

In the AWS Console > EC2 (double check your region!), can you "Terminate" your instance to restart the servers?

Thanks!

[Arko7777]

Hi,
thanks for your feedback first!! :)

1. No custom clients
2. No server settings from admin panel

I have terminated the EC2 instance. I will check the Meta File again in 2 days.

Is there anything else what could cause the issue?
Thanks!

[Arko7777]

In the meantime still getting this wss//:80 and https://80 issues.

My researched showed, that https is not able to run on port:80. May that be the "security" issue while on some private networks the meta data is not loaded?

[robinkwilson]

You're correct (however, we do encrypt the traffic usign port 80, but networks still don't like it since it's anti-pattern).

We have some open issues for customizing the ports that are used to bypass the firewall restrictions: Hubs-Foundation/hubs-cloud#90

We're actively working on this, please stay tuned!

[Arko7777]

Thanks @robin-k-wilson

Can I do it right now manually to make the hubs work?