Thanks for the reply! @vbrisebois @mirice
I’ve opened all the ports listed in the documentation.
Using a port check tool (Open Port Check Tool - Test Port Forwarding on Your Router), the ones that result open are
-3009
-8080
-3333
-3100
-3180
-8080
-3400
-3120
After a few tries, I’ve found out that it’s possible to recreate the same issue locally just by stopping either one of “Auth” or “Discovery Service” services, that’s why I suspect one or both of those services may be the cause.
The logs are attached to this message.
Chrome-console.log (3.0 KB) 79.49.210.192.har (10.3 MB)