#Headless client and player client disconnect from server after loading map - cannot start raid

16 messages · Page 1 of 1 (latest)

weary gazelleBOT
#
Olivier has submitted a ticket

Versions: SPT - 4.0.13 Fika - 2.2.6
Networking: port forwarding
Description: I followed the docker fika-server/fika-headless guide to the letter. No other mods installed. My client can get into the stash/menus but when I try to load a raid I get stuck at "Preparing the game".

In fika-server container logs I see both the headless and player clients disconnect followed by what looks like the headless client terminating(?) itself and eventually reconnecting.

Project Fika ·
#

Thread started by: @silver panther

weary gazelleBOT
#

@silver panther please attach any applicable log files and mod lists while waiting for help!
You can find your log file at %AppData%\..\LocalLow\Battlestate Games\EscapeFromTarkov\Player.log

If you do not attach any logs, we will close the ticket without warning.

silver panther
weary gazelleBOT
#
Client Log Information
**Specifications**

GPU: NVIDIA GeForce RTX 4080 (ID=0x2704)
VRAM: 16050 MB
Driver: 32.0.15.8157
Drive: SSD
SwapDrive: SSD

**Install Type**

Fika-Installer

**Cached local IPs**

0.0.0.0, ::, 192.168.1.126

**Mods (total: 6)**

Configuration Manager 18.4
SPT.Custom 4.0.13
SPT.Singleplayer 4.0.13
SPT.Core 4.0.13
SPT.Debugging 4.0.13
Fika.Core 2.2.6

**Errors (total: 1)**

[Error : Fika.Core] [ShowFikaMessage]: You are trying to show error screen from non-main thread!

**Exceptions (total: 0)**

None

Project Fika ·
silver panther
weary gazelleBOT
#

@silver panther, that file extension is not allowed! finger_wave
Allowed extensions: .png, .jpg, .jpeg, .webp, .gif, .mp4, .mov, .webm, .mp3, .wav, .json, .jsonc, .json5, .yaml, .yml, .txt, .log, .cfg, .mkv, .bmp, .ts

silver panther
#

This is what I'm referring to with the clients disconnecting and headless client restarting(?) itself

📎 docker_log.txt
prime moth
#

fika-headless | [Warning:Fika.Headless] No connections after 2 minutes, terminating

silver panther
#

How is that the case if I'm on the loading screen? Am I misunderstanding?

tiny hornet
# 
[Info   : Fika.Core] [JoinMatch]: Attempting to connect to host session...
[Info   :Fika.PingingClient] Stopped pinging x.x.x.x:25565
[Info   :Fika.PingingClient] Received candidate: x.x.x.x:25565
[Info   :Fika.PingingClient] Picked candidate x.x.x.x:25565, using LocalPort: 56445
[Info   :Fika.PingingClient] Stopped FikaPingingClient
[Debug  :ModulePatch] TarkovApplication_LocalGamePreparer_Patch:Prefix
[Info   :NetManagerUtils] FikaClient has created!
[Info   :NetManagerUtils] Creating CoopHandler...

[Info   :Fika.Client] [CLIENT] We disconnected because ConnectionFailed```

something about the connection is failing. if the x.x.x.x is your public IP and you are on the same network as the headless client then perhaps NAT Loopback is not working properly.

check your router settings. also look for something like DDOS/DOS Protection and turn it off if you find anything like that
#

you could alternatively pivot and use network_mode: host in both your fika-server and fika-headless docker services in your docker-compose.yml. you'd also have to change SERVER_URL in your headless client service if you choose to do that.

network_mode: host will make it so the headless client has visibility to the LAN IP of the host OS, which would mean you can connect to the headless client directly through the LAN IP. you'd get a candidate for the LAN IP in place of the 172.18.0.3 from the log snippet above (which is a docker internal IP)

#

best to understand security considerations of host network type before just blindly doing that

silver panther
#

router doesn't support NAT loopback.... network_mode: host will suffice until I can add another router
was able to connect and do a test raid thanks!