I have a dedicated server build that opens an EOS session and runs this code:
The idea is, the session is created, the server preps the level, and the client searches for the level and joins it. But the client can’t connect. And heres what I tried:
- Adding -multihome parameter
- Adding/removing -port parameter
- Changing port from 7777 to 25565
- Opening both ports to UDP/TCP
- Adding both ports to the firewall, allow access all, UDP.
- Using public and local ip (only local ip works)
- Utilizing the server build rather than editor build
- Utilizing an entirely different computer to emulate a client/server environment (on same network AND different network)
- Swapping to use an Express.js server on the ports used (works perfectly fine and YouGetSignal.com can find the Express.js on the open port, but not the server build on the same port
- Skipping EOS session altogether and utilizing JUST the open cmd and client build
- Changing from Open Level bp node to Execute Console Command
Let me know if there is anything I haven’t tried. This is a screenshot of the server when its opening the level and preparing it to listen.
The client screenshot is what you expect; sent packets but no response. Strangely enough, When I use localhost:7777 or localhost:25565, I can connect to the server. But only IF the server is being run on the same machine