WebsocketServiceManager.InternalTryGetServiceHost|A Websocket service with specified path isn't found:path :/
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
if you meet this problem ,Just make your websocketservice path shorter,like this:
wssv = new WebSocketServer(System.Net.IPAddress.Parse(ip), port);
wssv.AddWebSocketService<SocketParam>("/MonitorManager");
change it to :
wssv = new WebSocketServer(System.Net.IPAddress.Parse(ip), port);
wssv.AddWebSocketService<SocketParam>("/monitor");
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported lookup failure using WebSocketServer and AddWebSocketService with the /MonitorManager and /monitor paths shown in the issue. Investigate why the specified service path is not found; done when valid service paths resolve consistently without requiring an unexplained shorter name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100