I am a new user and thus far have been unable to successfully try any courses. I can load the webpage and the instructions, and get to click through all the 14 little pop ups. After that, no amount of waiting will get the rest of the terminal, simulation, and then the notebook also loses connection.
I looked at other issues, and it seems to apply to all courses I have tried, and I am on a stable, wired connection.
If this has anything to do with the “non-default” port comments (I am behind a firewall), IT requests more precise information so that we can implement a fix.
What browser are you using?
Do you have the same issue in ROSDevelopementStudio?
Have you tried a Tunneling VPN like TunnelBear of ExpressVPN?
Could you look for the ports that you have open by your firewall?
Post the output here
@duckfrost, thank you for your response.
Browser is firefox.
I do experience a similar issue in ROSDevelopmentStudio:
Due to policy, I am not allowed to access the Tunneling VPN.
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:29754 0.0.0.0:* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 ::1:631 :::* LISTEN
udp 0 0 127.0.0.53:53 0.0.0.0:*
udp 0 0 0.0.0.0:68 0.0.0.0:*
udp 0 0 0.0.0.0:631 0.0.0.0:*
udp 0 0 0.0.0.0:5353 0.0.0.0:*
udp 0 0 0.0.0.0:39505 0.0.0.0:*
udp6 0 0 :::35754 :::*
udp6 0 0 :::5353 :::*
I see…Hmmm… I’m not the expert in Ports , but it seems some of the most important are NOT open , like the 80 for example. Actually you have very few ports open there I’m affraid. Let me ask around if someone has any solution.
the services on both platforms run in different non-default ports, but we have
nginx that proxies all services to a common
https (port 443) port.
Given that all firewalls allow ports
80, then I think your firewall is blocking
WebSocket Connections. We use
WebSockets extensively. Could you check that with your IT team?
I think they are allowing
https:// protocols, but now allowing
wss://, which are used for
Thanks for the information. I’ll check in and let you know.
@ralves It turns out it was the websocket connection. Thank you for all your help.
Great to hear that @elizabeth.wills