⚔️ Conan Exiles Enhanced
Dedicated Server

Configuration Generator
Build a complete Docker Compose .env without editing every setting by hand
← Back to Quick Start
Don't know the game? Check out the official Conan Exiles Enhanced website or find it on Steam
✅ Compatible with Conan Exiles Enhanced. Legacy Conan Exiles names may remain in Steam app IDs, image names, repository URLs, and internal ConanSandbox paths because they are upstream identifiers.

Quick Start

🍷 Wine — Existing Deployments

Backward-compatible path for existing Wine servers. The :latest channel remains Wine to prevent automatic cutovers.

Updating an existing docker-compose.yml deployment never switches it to Native. New installations should use docker-compose.native.yml.
🐧 Native Linux — Recommended New-Server Quick Start
Fresh Native deployment. Do not point Native at Wine volumes. Existing servers must verify a backup and run the migration plan while Wine is still running; apply owns the stop and creates new Native volumes while keeping the original Wine volumes unchanged.
mkdir conan-native && cd conan-native
curl -O https://raw.githubusercontent.com/balnaimi/conan-exiles-server/main/docker-compose.native.yml
curl -o .env https://raw.githubusercontent.com/balnaimi/conan-exiles-server/main/.env.minimal
nano .env
docker compose -f docker-compose.native.yml up -d
Native images: rolling :native or versioned :2.9.1-native. RCON is internal-only by default. Fresh named volumes are initialized for the non-root UID/GID 1000:1000; custom bind mounts must be writable by that identity. Check docker compose -f docker-compose.native.yml ps for A2S health; use the bundled rcon.py listplayers client explicitly when you need an RCON diagnostic.
Native SteamCMD updates game binaries in place. A failed update stops startup but is not transactionally rolled back; retry after correcting disk/network issues, optionally with NATIVE_VALIDATE_SERVER=true.
🍷 Update an Existing Wine Deployment
Run from an existing Wine project directory. This preserves the Wine runtime and its current volumes.
cd /path/to/existing-wine-server
docker compose pull
docker compose up -d
:latest stays Wine for backward compatibility. These commands do not migrate the deployment to Native.
🍷 Edit an Existing Wine Deployment
Back up and edit the current Wine deployment's configuration without replacing its Compose file or volumes.
cd /path/to/existing-wine-server
cp .env .env.backup
nano .env
docker compose up -d
Use Config Generator for a New Native Server
Use the visual config generator (⚙️ Config Generator tab), save the generated output as .env beside docker-compose.native.yml, then start Native.
mkdir conan-native && cd conan-native
curl -O https://raw.githubusercontent.com/balnaimi/conan-exiles-server/main/docker-compose.native.yml
# Save the generated config as .env in this folder
docker compose -f docker-compose.native.yml up -d

Network Ports

Port Protocol Description
7777 UDP Game port
7778 UDP Game port (required for correct ping in server list)
27015 UDP Steam query
25575 TCP RCON (if enabled)
Make sure these ports are open in your firewall.

Connecting to Your Server

How to connect:
Use Direct Connect in Conan Exiles Enhanced → Enter your server IP and port 7777 (IP only, no hostname)
⚠️ Important: Conan Exiles Enhanced does not support hostnames — you must use an IP address.
CG-NAT / Tunnels: If your server is behind CG-NAT, a tunnel, a VPS port forward, or a host with multiple network interfaces, set MULTIHOME to the public or forwarded IP address that players should use. The container will also use that value for MULTIHOMEHTTP so server-browser registration comes from the same IP. Leave both empty for normal hosting.
⏱️ First Run and Updates: SteamCMD downloads and verifies the Enhanced server, while major game updates may download several gigabytes and require temporary disk space. Startup time depends on storage, memory, CPU, and cache state—verify the readiness markers instead of relying on container uptime alone.

💻 System Requirements

Enhanced / UE5 guidance: Conan Exiles Enhanced requires substantially more memory and storage than the previous UE4 dedicated server. Older Conan Exiles hardware recommendations are not reliable sizing guidance for the current Enhanced server running through Wine.
Server Profile CPU RAM Disk
Test / very small 4 fast x86-64 cores 12 GB practical start 20 GB practical start
Small private server (up to 10 players) 4+ fast x86-64 cores 16 GB recommended 25–35 GB recommended
Growing or modded server 6+ fast x86-64 cores 24 GB or more 70 GB comfortable; 100 GB heavy

These are project planning recommendations, not official Funcom requirements or hard limits. Actual usage depends on the runtime, map, database, buildings, players, mods, backups, and game updates.

Measured RAM guidance: RAM sizing uses total host/VPS allocation. 12 GB is a practical starting allocation for a small vanilla server. In measured no-player tests under a hard 10 GiB container cap with no extra swap budget, Wine peaked at 9.19 GiB and Native peaked at 8.69 GiB; both remained A2S-ready through 20-minute observation windows without cgroup pressure or OOM events, and Native completed multiple save cycles. 16 GB is recommended for typical use, not a hard minimum. The test host remained at 16 GiB, so the 10 GiB cap tested the game budget under pressure but did not reproduce whole-system pressure on a 12 GB VPS. The measured worlds were small and unmodded; players, larger worlds, and mods can require more memory.

CPU Compatibility

Epic documents SSE4.2 as the general UE5 x64 minimum CPU specification. An individual game build may choose a higher minimum. AVX and AVX2 are important Conan Exiles Enhanced compatibility diagnostics, but Funcom has not officially confirmed AVX2 as a hard requirement.
for flag in sse4_2 avx avx2; do
  grep -qw "$flag" /proc/cpuinfo \
    && echo "$flag=yes" \
    || echo "$flag=no"
done
lscpu
VPS / QEMU: The flags visible inside the guest are what the server can use. Select a current virtual CPU model or host-passthrough when available. A host change that exposes several flags can confirm a CPU compatibility problem, but it does not isolate AVX2 alone.

Verified Runtime Observation

A clean, unmodded server using Steam build 24383534 and Wine Staging 11.10 repeatedly entered an OOM restart loop on an 8 GB host. With 16 GB, the same server reached InProgress, responded to Source/A2S queries on UDP 27015, and stabilized at approximately 9.1 GB idle memory.
🐧 Native Linux observation: On the same 16 GiB test CT and Steam build 24383534, the native Shipping binary reached A2S/RCON readiness and stabilized near 8.70 GiB unmodded. Enhanced-tagged StayBloody and Better Thralls mounted in order at roughly 8.42–8.57 GiB. The guest exposed SSE4.2, AVX, and AVX2. UE5's general x64 baseline is SSE4.2; these tests do not prove AVX2 alone is a Conan requirement.
8 GB RAM should be considered insufficient for the current Enhanced server. The measured 12 GB practical-start profile is intended for small vanilla workloads with limited headroom; choose 16 GB or more as the workload grows.
Storage guidance:
  • Storage sizing assumes one runtime—Wine or Native, not both. 20 GB is a practical starting allocation for one runtime.
  • 25–35 GB is recommended for updates, world growth, and a simple backup. 35–40 GB is a comfortable allocation, not a minimum.
  • The measured clean Wine-to-Native coexistence used about 14 GB on the host; 25 GB is a practical migration floor for that scenario, while 35 GB is recommended for safer migration headroom.
  • 70 GB is comfortable, not required, for mods, multiple backups, long-term growth, or repeated maintenance. 100 GB is a safer recommendation for heavily modded servers or long backup retention.
  • Table values are total disk allocations in decimal GB; Native preflight reports currently free binary GiB after existing host and Docker usage.
Network:
  • Stable internet with at least 10 Mbps upload recommended
  • Lower upload speeds may cause rubber-banding and lag
  • Each connected player uses roughly 30-60 KB/s of bandwidth
Good to know:
  • Wine adds CPU and memory overhead compared with native Windows
  • Game logic benefits heavily from fast single-core performance
  • RAM usage grows as players build and explore — monitor with docker stats
  • Mods may substantially increase startup time, memory use, and storage
  • No physical GPU required — the dedicated server is headless