# Escape from Tarkov (SPT-Fika) Troubleshooting (/docs/escape-from-tarkov/troubleshooting)



Most SPT-Fika issues fall into a few buckets. Find your symptom below.

A Mod Isn't Loading [#a-mod-isnt-loading]

The mod is for SPT 3.x but your server is SPT 4.0 [#the-mod-is-for-spt-3x-but-your-server-is-spt-40]

**Symptom:** You installed a mod, but its features never appear. The **Console** shows a line like:

```
No Assemblies found in path: /home/container/SPT/user/mods/<ModName>
ModLoader: loading: 1 server mods
```

**Cause:** SPT **4.0** changed how server mods work. A 4.0 server loads compiled **.NET assemblies** (`.dll` files) from `user/mods/<mod>/`. Older **3.x** mods are TypeScript/Node and contain no `.dll`, so a 4.0 server reports "no assemblies" and silently skips them.

**Fix:** Install the **SPT 4.0-compatible** build of the mod. On the mod's page, confirm it lists **SPT 4.0** support before installing. A 3.x-only mod will never run on a 4.0 server, no matter where you place it.

The mod is in the wrong folder [#the-mod-is-in-the-wrong-folder]

**Symptom:** The mod doesn't load and there's no error about it at all.

**Fix:** Server mods go in `user/mods/`, each in **its own folder**. Some mods also ship a **client-side** part that each player installs in their own `BepInEx/plugins` folder — the server copy alone won't enable it. Check the mod's page for client requirements.

You didn't restart after installing [#you-didnt-restart-after-installing]

**Fix:** Mods are loaded at startup. **Stop and start** (or restart) the server after adding or removing a mod, then check the **Console** for load messages or errors.

Players Get Kicked on the Mod Check / Client Mods Out of Sync [#players-get-kicked-on-the-mod-check--client-mods-out-of-sync]

**Symptom:** A player can't join because their installed client mods don't match the server's.

**Fix:** Open the **SPT Mods** tab in the panel and use **Enable Client Mod Sync**. This installs a sync mod on the server so that, when players connect, their client mod set is checked and kept aligned with the server automatically — no hand-matching of files. Players still install their own EFT/BepInEx client, but the mod list is kept in step for them.

The Server Won't Start [#the-server-wont-start]

**Symptom:** The server stops right after starting, or never reaches "server started."

**Fix, in order:**

1. **Read the Console.** SPT prints the exact mod or config that failed. The last lines before it stops are the clue.
2. **Suspect a recently added mod.** If it started failing right after you installed something, remove that mod's folder from `user/mods/` and try again.
3. **Check your config edits.** A malformed value in a `.jsonc`/`.json` config (a missing comma or bracket) can stop the server. Undo your last config change.
4. **As a last resort, reinstall.** For heavily-modded setups that won't recover, back up `user/profiles/` first, then use [Reset Server](/docs/escape-from-tarkov/reset-server) for a clean reinstall and re-add mods one at a time.

> 💡 **Tip:** Back up `user/profiles/` before any reinstall — that's where all player progress lives.

Can't Join a Friend's Raid ("Unable to Connect") [#cant-join-a-friends-raid-unable-to-connect]

You can log in and see each other, but joining a raid fails. This is a **client-side NAT/Fika setting**, not a server fault. Follow the full step-by-step in **[How to Play Co-op with Friends](/docs/escape-from-tarkov/play-with-friends)** — in short: clear **Force IP**, enable **Use NAT Punching**, disable **UPnP**, remove any manual port forwards, and fully restart every player's game.

Headless Client Problems [#headless-client-problems]

A **headless client** is a second EFT game client a player runs on their **own machine** to host raids — it doesn't run on the game server.

* **Create one from the panel:** open the **Fika Admin** tab → **Headless Clients** → **New profile**, then load that profile ID into the headless EFT client. See [Manage Your Server](/docs/escape-from-tarkov/manage-your-server).
* **A headless client is unstable or crashing:** headless clients are sensitive to mods. Test with a minimal mod set, and make sure the headless client's mods match the server.

Performance / Desync [#performance--desync]

**Symptom:** Stutter, rubber-banding, or AI desync during raids.

**Cause:** SPT raids are largely **single-threaded**. Raw core count matters less than **single-thread performance**.

**Fix:** Keep your mod count reasonable (AI-heavy mods are the biggest cost), and if you consistently host large co-op raids, a plan on faster single-thread hardware will help most. Note that in Fika co-op the **raid host's** machine also carries load for that session.

Still Stuck? [#still-stuck]

Open a ticket from the [XGamingServer panel](https://panel.xgamingserver.com) or ask in our [Discord](https://discord.xgamingserver.com/). To help us help you fast, include:

* The **Console** output from a fresh start-up.
* The exact **SPT and Fika versions** shown in the console.
* Whether **all** players are affected or just one.

That tells us immediately whether it's a version mismatch, a mod, a port/NAT issue, or a single client's setup.