#Stuck at Waiting for (#) Players when anyone but the person who hosted the server.

27 messages · Page 1 of 1 (latest)

junior mirage
#

FIKA Version: MPT Release 0.9.8875.33465
Explain Problem: The server is hosted on a dedicated server. When anyone but the person who set up the dedicated server tries to host, we get stuck on "Waiting for (#) Players" until it asks to force start where none of us will load in together.

Any help is appreciated, I have followed the steps within allowing port 6969 as TCP, and for port 25565 UDP within my firewall, EFT has access also.

Attempted to follow a "FORCE IP" method within another persons suggestion having the same issue with no luck, unlike them.

forest wharf
#

This could be a issue with the router/ISP which for some reason, doesn't allow game hosting and port forwarding even though you have the option in the router config (in my case). Weird suggestion but maybe try setting up ZeroTier VPN (since you mentioned dedicated server so i assume on Linux) or Radmin if the dedicated server is hosted on Windows and hosting from there.

junior mirage
forest wharf
#

No problem! Make sure to apply Force IP stuff since you're trying to use VPNs now. So just copy the IP the VPN software gave to your machine in the network and paste in in Force IP and Force Bind IP.

glass loom
forest wharf
#

no, only for their respective machines

#

that's only for hosting i'm pretty sure but if it doesn't work, set it to host

junior mirage
#

Should I have UDnP Enabled in f12 setting in Tarkov?

#

I got this error when I tried hosting with it enabled

unique apex
#

~~Jumping into this as having the same issue.

'Dedicated' server. AKA, 3rd PC that isn't trying to play Tarkov at the same time.

Server and one of the clients are on the same LAN, 2nd client is on a different network.

If a single player tries to start a raid, it works fine.

If a player tries to host a multi-person raid, it just gets stuck on "Waiting for 'X' Players.

I've turned off the Windows firewall on both clients.
And turned off the Windows firewall on the Server.

I've port forwarded both 6969 TCP and 25565 UDP to my server IP.

One thing I have noticed, is the below from the output on the server console when a multi-person raid is hosted. Though, unsure if this is related.

TypeError: Cannot read properties of undefined (reading 'players')
    at MPTMatchService.removePlayerFromMatch (S:\Tarkov-SP\user\mods\mpt-server\src\services\MPTMatchService.ts:323:34)
    at MPTRaidController.handleRaidLeave (S:\Tarkov-SP\user\mods\mpt-server\src\controllers\MPTRaidController.ts:60:30)
    at MPTRaidCallbacks.handleRaidLeave (S:\Tarkov-SP\user\mods\mpt-server\src\callbacks\MPTRaidCallbacks.ts:33:32)
    at RouteAction.action (S:\Tarkov-SP\user\mods\mpt-server\src\routers\static\MPTRaidStaticRouter.ts:33:50)
    at MPTRaidStaticRouter.handleStatic (C:\snapshot\src\di\Router.ts:47:63)
    at HttpRouter.handleRoute (C:\snapshot\src\routers\HttpRouter.ts:79:62)
    at HttpRouter.getResponse (C:\snapshot\src\routers\HttpRouter.ts:44:30)
    at HttpRouter.getResponse (S:\Tarkov-SP\user\mods\mpt-server\src\overrides\routers\HttpRouter.ts:25:52)
    at AkiHttpListener.getResponse (C:\snapshot\src\servers\http\AkiHttpListener.ts:150:38)
    at IncomingMessage.<anonymous> (C:\snapshot\src\servers\http\AkiHttpListener.ts:75:43)
TypeError: Cannot read properties of undefined (reading 'players')
TypeError: Cannot read properties of undefined (reading 'players')
    at MPTMatchService.removePlayerFromMatch (S:\Tarkov-SP\user\mods\mpt-server\src\services\MPTMatchService.ts:323:34)
    at MPTRaidController.handleRaidLeave (S:\Tarkov-SP\user\mods\mpt-server\src\controllers\MPTRaidController.ts:60:30)
    at MPTRaidCallbacks.handleRaidLeave (S:\Tarkov-SP\user\mods\mpt-server\src\callbacks\MPTRaidCallbacks.ts:33:32)
    at RouteAction.action (S:\Tarkov-SP\user\mods\mpt-server\src\routers\static\MPTRaidStaticRouter.ts:33:50)
    at MPTRaidStaticRouter.handleStatic (C:\snapshot\src\di\Router.ts:47:63)
    at HttpRouter.handleRoute (C:\snapshot\src\routers\HttpRouter.ts:79:62)
    at HttpRouter.getResponse (C:\snapshot\src\routers\HttpRouter.ts:44:30)
    at HttpRouter.getResponse (S:\Tarkov-SP\user\mods\mpt-server\src\overrides\routers\HttpRouter.ts:25:52)
    at AkiHttpListener.getResponse (C:\snapshot\src\servers\http\AkiHttpListener.ts:150:38)
    at IncomingMessage.<anonymous> (C:\snapshot\src\servers\http\AkiHttpListener.ts:75:43)```


UPnP shouldnt be required due to the port forwarding. UPnP is basically a (less reliable) automatic port forwarding. If you've done it manually, it's not needed.~~

Port forwarded 25566 and in F12 set port to 25566, all good now.
junior mirage
unique apex
#

The UDP port, yeah

#

Only the person trying to host the raid has to port forward their PC, as well.

junior mirage
unique apex
#

Yes

junior mirage
#

Hm weird I tried doing what you did, still not connecting.

unique apex
#

So port forward dedi as your normally would.

Then for raid host PC, port forward 25566.
Then in F12, set 'UDP port' to 25566

#

I'd also allow port 25566 on your raid host PC firewall within windows

junior mirage
polar cliff
#

We got the same problem here, playing via Radmin. And my friend who is not the server host tries to host a raid, and we get waiting for (X) player 4 out of 5 times. Force binding IP for both player or only one player didnt work.

bleak escarp
harsh heart
#

same here

wispy depot
#

My fix was portforward normally with 25565 but ingame for both client and host F12, turn on UPnP and then set the UDP port to 25567, leave the force IP blank

short relic
#

Doesnt matter if youre hosting or conencting. You have to have these done on your local router that receives direct uplink to your ISP

unique apex