#Friend cant join game

19 messages · Page 1 of 1 (latest)

raven hull
#

• FIKA Version: Fika.Release.0.9.8995.14684
• SPT version: 3.9.5
• VPN
• Explain Problem: We have spt server on a docker container on a raspberry PI, @person1 has the pi at his home, @person2 and @person3 can connect to the game using the PI. If @person2 and @person3 try to host a game no one can join, if @person1 host we can join. This same setup was working on 3.8.3, after updating to 3.9.5 it stopped.

We all are on the same network on Radmin, we used the Fika firewall fixer and have the ports open on the router or are using UPnP

Compared both configuration (3.8.3 and 3.9.5) and are the same

jaunty otter
#

everyone needs to force and bind their own vpn ip in the f12 > fika.core menu

raven hull
#

even if they are not hosting?

#

already tried that and had the same result

round nova
# raven hull already tried that and had the same result

either re-run fika firewall fixer or go in to windows firewall advanced settings and delete any entry related to EscapeFromTarkov.exe, then restart the client and try to host a raid again. it should pop up asking to allow incoming connections, make sure both Private and Public networks are checked and click allow.

raven hull
#

same result, I'll keep researching to see if i can find a solution

vestal knot
#

The actual SPT server in this scenario is irrelevant. The error you are getting is 100% from the UDP port 25565 not being able to communicate.
The backendIp should also be your VPN IP, not 0.0.0.0

#

Change that + send a screenshot of your VPN interface and your F12 settings for IPs

raven hull
#

if there is multiple people that can host, which ip should go on backendIP? the pi is not on the VPN network

vestal knot
#

Only one person should host the backend (SPTserver)

#

That machines Ip should be used

abstract magnet
#

Got the same problem

#

Cant fix it

vapid locust
#

Im having same issue as well

abstract magnet
#

I removed the EscapeFromTarkov.exe from my firewall settings and it fixed it

#

Try to do that

#

@vapid locust

#

The host and wheover is joining too

vapid locust
#

ok i will try that