JasonFPV1

I'm self hosting a server with a port besides 19132 open on my router, so 19132 is closed. I have someone else with phantom running elsewhere with a successful connection...

> Hi @JasonFPV1 sounds like you need to specificy the port when you launch phantom. Your connection command should look something like. > > `./phantom -server example.com:25500` Thanks for the...

> Ah... Windows. Have you checked your firewall settings? You may need to put the phantom executable in a more permanent location, say in a folder in program files or...

> Yeah so... Windows firewall is annoying but entirely essential so please don't disable it. I find most issues I have with Windows Firewall are caused by it incorrectly detecting...

> Hey @JasonFPV1, just to confirm: > > * your server is hosted on your network > * your friend is running phantom on a Windows PC on their own...

> > So I need to open port/firewall 19132 on my friends pc, then use the standard phantom command (no other flags like bind_port) with my ip and non-19132 port?...

Alright, I created inbound and outbound rules to open port 19132 (UDP) on my friends pc, but it didn't solve the issue. The phantom command I'm using is just phantom-windows.exe...

> Hi @JasonFPV1, So highlighting some lines from the output here. > > `Binding ping server to port 19132` This one's fine because you've opened that port. And this enables...

Still having this issue in the latest stable release, any solution at all yet? I had them working fine before I updated core/os today...