Hi!
I’m trying to share my Nucleus server.
I created a dynamic DNS and opened the following ports:
-8080
-3333
-3001
-3009
-3180
-1666
-3100
I can easily access the server on my local machine and on other machines in my local connection.
But every time someone tries to connect to <my_ddns>:8080 from outside of my local connection, an endless loading screen appears and nothing else happens:
@Jeff_Costello , @zintugabriele
If after making sure the ports are open as per the doc link above. If you still have an issue can you capture the chrome network logs? Both the network (HAR) and console logs. These will help us understand the issue.
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)
The problem is nothing that you did wrong. At the moment the Workstation Nucleus infrastructure will only allow for local area servers to use the collaboration services. This issue specifically has to do with the authentication logic. The muxing of private and public IPs.
I have raised this issue internally. (OM-2981).
At this time i do not have a workaround for using workstation based nucleus between clients outside of a local area.
Thanks for the information.
Isn’t there a way to bypass the authentication? That’s probably a stupid question, but I guess it’s worth a try.
Also, any idea when it will be possible to share a server outside of a LAN?