localhost vs remote connection
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Hi-
I'm having an odd issue when I try to connect to a remote node.js server running websockets. When I run it locally, unity can connect to it perfectly. However, when I run it remotely, it fails to connect. I thought it was a problem with the settings on the remote server, but when I run another app (written in OpenFrameworks) on the same computer as the Unity client, it can connect to it just fine.
Any idea what it could be? Thanks!
-jesse
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
The report names Unity as the client and a remote Node.js WebSocket server, but identifies no repository file, test, entry point, or error output. Start by reproducing the local and remote connection paths and locating the connection failure; done would require a reproducible, actionable defect with a specified code or test change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, node.js, unity
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100