Problem connecting to websocket server on local network wit an external ip 192.168.0.xx

Open
#72 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, unity

Research direction

Start with Assets/Scripts/Clients/CortexClient.cs:56 and reproduce the TLS handshake using the LAN address instead of localhost in the Unity editor. Compare the failing Unity connection with the working wscat connection and inspect the NativeWebSocket package at WebSocket/WebSocket.cs:478. Done means the Unity editor and a compiled VR device can connect to the stated local websocket server over its LAN address.

Written by the indexing model from the issue text.

Description

PROBLEM

Im trying to connect to a websocket server hosted on my lan at wss://192.168.0.42:6868. It doesn't require authorization.

The websocket client fails the TLS handshake if i use an external ip like wss://192.168.0.xxx:6868 but it works fine if i use wss://localhost:6868

DETAILS

I can connect via the the TUI app wscat, but when I try to connect via the Unity editor I get the following error:

Connection Error! Please double check your URL and ensure the cortex API is runningURL: wss://192.168.0.42:6868 Error: Unable to connect to the remote server
UnityEngine.Debug:LogError (object)
CortexClient:<Start>b__13_1 (string) (at Assets/Scripts/Clients/CortexClient.cs:56)
NativeWebSocket.WebSocket/<Connect>d__27:MoveNext () (at Library/PackageCache/com.endel.nativewebsocket@c5101c0776/WebSocket/WebSocket.cs:478)
UnityEngine.UnitySynchronizationContext:ExecuteTasks () (at /Users/bokken/buildslave/unity/build/Runtime/Export/Scripting/UnitySynchronizationContext.cs:107)

Ideally I'd like to connect to the same local web socketserver over the local network on the Unity editor, and via a compiled device in VR.

Dominant language
C#
Stars
1.7k
Forks
206
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from endel/NativeWebSocket

All issues in endel/NativeWebSocket

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.