benloh
commented
3 years ago In GitLab by @daveseah on Apr 26, 2021, 10:29
My first guess is that that our code is grabbing the internal LAN address when for this use case we actually need the external address. This requires some kind of external reflector server, but I do see an external-ip package that is set up to do this.
THIS IS LOW PRIORITY!
Vanderbilt is trying to set up a Mac and Ubuntu server running in their lab for students to access remotely from off-campus.
While we have been able to set up a Digital Ocean server as well as a server on Ben's laptop, the set up at Vanderbilt does not work.
The Error
The server is running at 216.171.61.109, with ports properly opened, but when you hit the site, the console reports:
WebSocket connection to 'ws://192.168.1.145:2930' failed: Error in connection establishment: net::ERR_CONNECTION_TIMED_OUTThe request seems to come from
client-urnet.js:191.Expected Behavior
The connection to port 2930 appears to use 192.168.1.145 instead of 216.171.61.109.
Other requests do appear to properly go through 216.171.61.109.
The current workaround is to use the Digital Ocean server, so this is not high priority. But flagging this in case we need to revise how IP addresses are designated throughout the system.
The discussion thread is here: https://inquirium.slack.com/archives/C01J8G6FRK2/p1609352914021100