Nightingale Can't Connect to Dedicated Server? Every Fix

Most failed joins to a Nightingale dedicated server come down to five things: the address typed as ip:port in one box instead of the separate IP and port boxes on the IP/LAN screen, a wrong or missing connection password, a server that has not updated to the game's latest build, a server and players on different Steam branches, or UDP port 7777 not reaching the server. Check them in that order. The very first join to a new server is also slow by design, because the game uploads your character and realms, so give it time before calling it a timeout.

How the join screen expects the address

The path from Inflexion's own guide is: Play, pick a character, Join a Game, then choose how to connect. There are two options, Steam and IP/LAN. For a dedicated server you rent or run yourself, use IP/LAN.

Pasting ip:port into the address box is the most common mistake, and the game will not split it for you. Since the July 2025 update, the Continue button stays greyed out until an address is entered, so a dead button means the IP box is empty or not accepted.

The newer Join Code option (February 2026) is for games hosted from a player's PC: the host picks Join Code and shares it from the Social tab. It does not replace IP/LAN for a dedicated server.

Wrong password

By default a Nightingale server has no connection password, and Inflexion recommends setting one. It can be set in two places, and the command line wins:

So if you changed the password in the ini and friends still get rejected, something is passing the old one on the command line. On hosted servers the control panel usually builds the command line, which is why the panel's password is the one that counts there. Also make sure players type the connection password. AdminPassword is a separate value for kicking and banning once inside, covered in Nightingale admin password, kick, ban and cheats.

Server and game on different builds

A dedicated server only accepts clients on the same build. When Inflexion patches the game, Steam updates players automatically, but the server stays on the old build until someone updates it. That is exactly what players reported the day the February 2026 update shipped: "New update won't allow connection to dedicated server".

Update the server (Steam app 3796810):

steamcmd +login anonymous +force_install_dir C:\NightingaleServer +app_update 3796810 +quit

Run that after every game patch and restart. On Linux use your install path and start ./NWXServer.sh afterwards. If you installed the server through the Steam client (Library > Tools > Nightingale Dedicated Server), Steam updates it, but only while Steam is running, and the server still needs a restart to load the new files.

Players on the old Epic or legacy version

Epic and Steam both list an older pre Realms Rebuilt version (0.3.2) next to the current one. That old build cannot join today's servers. If one friend cannot connect while everyone else can, ask which version they launched.

Beta branch mismatch

The dedicated server app has a public-test-realm branch next to the default one, which Steam describes as a "Test branch for upcoming releases". Inflexion runs those test builds as its Public Test Realm (PTR), and access for players is arranged through the official Discord. A server on a test build refuses players on the normal game, and the other way round. Before using it, check on SteamDB or in Discord that the test branch is actually newer than the default one; between test phases it can sit on an old build. To run one, install the server with the branch:

steamcmd +login anonymous +force_install_dir C:\NightingaleServer +app_update 3796810 -beta public-test-realm +quit

and have every player on the same test build, or keep everyone, server included, on the default branch. When a test phase ends, move the server back to the default branch at the same time as the players. Our guide to installing a beta branch on a dedicated server shows how to switch both ways.

Connection timeouts

The port is not reaching the server

Nightingale listens on UDP 7777 by default and uses no other port for players. If you changed it, check the start line: Inflexion's guide warns that -port=<num> needs the = "or Unreal will ignore the setting", leaving the server on 7777 while your players and firewall use the other number. The allowed range is 1024 to 65535.

For a server at home:

1. Allow UDP 7777 inbound in the firewall on the server machine.
2. Forward UDP 7777 on the router to the server's local IP (from ipconfig, the IPv4 address).
3. Give friends your public IP, not the local one.

Inflexion's play with friends post walks through the same steps. If a machine has several network cards, -multihome=<IP> makes the server listen on the right one. If forwarding is set and nothing gets through, your connection may be behind CGNAT; see how to tell if you are behind CGNAT.

You are on the same network as the server

Players inside the same house should use the server's local IP (for example 192.168.1.50). Many routers cannot loop a connection out to the public IP and back in, so the public address fails from inside while working perfectly for friends elsewhere.

The server is still loading

A server that has just started is not ready for players straight away. Inflexion's optional status endpoint shows this clearly: start the server with -statusPort=8080 and http://localhost:8080/status returns "status":"loading" with a 503 until it is ready, then "status":"ready" with a 200. Wait for ready before joining.

The first join to a new server takes longer

On a server that has never had a player, the first character to connect also uploads their realms, and Inflexion's FAQ warns that this makes the first connection slower than usual, but only happens once. Let that first join finish before anyone else connects. Who goes first also decides which realms the server keeps, explained in how to move a Nightingale realm to a dedicated server.

The server is full

Six players is the supported cap. Extra players are refused unless the start line raises MaxPlayers with -ini:Game:[/Script/Engine.GameSession]:MaxPlayers=<num>, which Inflexion calls unsupported past six.

Quick checklist

The low effort route

A Nightingale server from GamezServers has its own address and open port, so there is nothing to forward. The connection password, admin password, difficulty and max players are panel fields passed on the start line, auto update pulls the new build on restart, and the panel shows the exact IP and port to put in the two boxes. For the setup basics, see how to host a Nightingale server.

FAQ

How do I connect to a Nightingale dedicated server?

Select Play, pick a character, choose Join a Game, set the connection to IP/LAN, type the IP and port in their separate boxes and enter the password.

What port does a Nightingale server use?

UDP 7777 by default, set with -port= on the server's start line. No other port is needed for players.

Why can I not join my Nightingale server after an update?

The server is still on the old build. Update app 3796810 with SteamCMD and restart it.

Can Epic players join a Nightingale dedicated server?

Yes, through IP/LAN with the server's address and port, as long as they launch the current version, not the legacy 0.3.2 build.