How to Fix a Factorio Server Not Responding

When Factorio says it could not establish network communication, first prove that the server is running and reachable on the host, then verify matching game versions and mods, and only after that troubleshoot the network edge. Factorio multiplayer uses UDP only; the default port is UDP 34197. A LAN connection that works while Internet connections fail points to forwarding, firewall, address, container publishing, or ISP NAT rather than the save itself.

Godlike.Host offers hosted Factorio servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.

Start with the fastest diagnosis

Do not begin by changing several router settings at once. A Factorio server can fail at four different layers: the game process, the game and mod versions, the host’s local firewall, or the path between the Internet and the host. Testing in that order tells you which layer is actually broken.

#	Preview	Product	Price
1		CyberPowerPC Gamer Xtreme VR Gaming PC, Intel Core i5-13400F 2.5GHz, GeForce RTX 5060 8GB, 16GB...	$1,285.00	Buy on Amazon
2		ZER-LON Prebuilt Gaming PC Desktop, Core I7 up to 3.9 GHz, RX 550 4GB GDDR5	$469.99	Buy on Amazon
3		Mumba Mouse Grip for Nintendo Switch 2 Joy-Con, [2 Pack] Ergonomic Gamer Grip Holder with Super...	$24.29	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

1. Confirm that Factorio is running the intended save

Start a headless server explicitly

A dedicated server must be started with the server option and a save file. The command-line form is:

factorio --start-server SAVE

Replace SAVE with the path or filename of the save you intend to host. On Linux, Factorio provides a lightweight dedicated headless package. On Windows, the normal Factorio package can be run in server mode. Keep the server console open while testing: an immediate exit, a missing save, or an error before the listening message means the network is not yet the problem.

#1 Best Overall

Sale

CyberPowerPC Gamer Xtreme VR Gaming PC, Intel Core i5-13400F 2.5GHz, GeForce RTX 5060 8GB, 16GB DDR5, 1TB PCIe 4.0 SSD, WiFi Ready & Windows 11 Home (GXiVR8060A40)

• System: Intel Core i5-13400F 2.5GHz 10 Cores | Intel B760 Chipset | 16GB DDR5 | 1TB PCIe 4.0 NVMe SSD | Windows 11 Home
• Graphics: NVIDIA GeForce RTX 5060 8GB Graphics | 1x HDMI | 2x DisplayPort
• Connectivity: 1 x USB-C 3.2 | 2 x USB-A 3.2 | 6 x USB-A 2.0 | 1 x LAN | WiFi 6 | Bluetooth 5.3 | 7.1 Channel Audio
• Tempered Side Case Panel | Custom RGB Lighting | Keyboard and Mouse
• 1 Year Parts & Labor Warranty, Free Lifetime Tech Support

$1,285.00

Buy on Amazon

Test from the host before involving the router

Use a local client on the same computer with the loopback address, or use another device on the same LAN with the host’s private address. Factorio’s command-line reference also supports a direct connection test:

factorio --mp-connect ADDRESS[:PORT]

For a first test, use the host’s LAN address and the actual configured port. A successful local connection proves that Factorio loaded the save and is accepting traffic on the host. It does not prove that an Internet player can reach it.

Keep the private address stable

Port forwarding points to a private address such as the server computer’s LAN address. If the router later gives that computer a different address, the rule can silently point to the wrong device. Use a DHCP reservation or another method that keeps the server’s private address stable, then confirm the forwarding destination matches it.

2. Make versions and mods identical

The official multiplayer guidance is explicit: “All game instances need the installation of exactly the same game-versions and mods.” This includes the dedicated server and every connecting client. A server that is perfectly reachable can still reject a player when one installation is on a different game build or has a different mod set.

Check the game build

• Read the version shown by the server installation and by the client that is trying to join.
• Update or roll back every installation to one identical build; do not assume that a close-looking version number is sufficient.
• Restart the server after changing the installation so the process is definitely running the selected build.

Check the complete mod set

• Compare enabled mods, not only the number of mods. A different mod, disabled dependency, or different mod version is a mismatch.
• Apply the same changes to the server and all clients before testing connectivity again.
• If you are isolating a network problem, first make a clean, matching test setup rather than debugging forwarding with incompatible installations.

Resolve this compatibility layer before changing router settings. Otherwise, a network fix can appear ineffective because the client is rejected later for a version or mod reason.

3. Use the correct protocol and port

Factorio uses UDP only for multiplayer traffic. The default server port is 34197/UDP, although the port can be changed in configuration. A TCP-only rule, a forwarding rule for the wrong number, or a firewall rule that allows TCP but blocks UDP will not make the server reachable.

Verify the configured port

If you changed Factorio’s port, write down the new number before testing. A common failure is forwarding UDP 34197 while the server is listening on another port. The same mismatch can occur when a container publishes one host port but Factorio listens on another internal port.

Allow the port on the host

Permit inbound UDP traffic on the selected port in the operating system firewall and in any security product that filters network traffic. If the server runs behind a cloud security group, that layer must also allow the same UDP port. Temporarily disabling protection can be a diagnostic experiment only; restore protection and create a narrow rule for the Factorio port after the test.

4. Separate LAN failure from Internet failure

When LAN connections fail

If a client on the same LAN cannot connect by private address, stay on the host and local network. Check that the process is still running, the save loaded, the versions and mods match, and the host firewall allows the configured UDP port. A router’s public-facing forwarding rule cannot repair a process that is not reachable locally.

Rank #2

ZER-LON Prebuilt Gaming PC Desktop, Core I7 up to 3.9 GHz, RX 550 4GB GDDR5

• 【PC Gaming System】This gaming PC is loaded with Intel Core I7 up to 3.9GHz and AMD Radeon RX 550 4G graphics card, allowing you to experience top-notch gaming performance. This system features 16GB of high-speed memory and 512GB SSD Solid State Drive for lightning-fast load times
• 【Superior Gaminig Experience】This high-performance Gaming Computer Desktop is capable of running a wide range of popular PC games for pc gamer, including Fortnite, Call of Duty Warzone, Escape from Tarkov, GTA V, World of Warcraft, LOL, Valorant, Apex Legends, Roblox, Overwatch, CSGO, Battlefield V, Minecraft, Elden Ring, Rocket League, The Division 2, and Hogwarts Legacy with 60+ FPS
• 【Multifunctional Use】This tower computers gaming pc desktop is designed to meet the needs of different people on the computer, powerful performance not only in the game to show quality graphics, the face of the office, design, audio and video can also be comfortable, multi-tasking, fast switching smooth operation
• 【Tower Gaming PC Desktop】The gaming computer desktop is designed for versatile connectivity, featuring 2x USB 3.0 ports, 6x USB 2.0 ports, 1x RJ-45, 1x Serial, and built-in Wi-Fi. The AMD Radeon RX 550 4G GDDR5 Graphics Card supports multiple display options including 1x HDMI, 1x DisplayPort, and 1x DVI, ensuring compatibility with a wide range of monitors

$469.99

Buy on Amazon

When LAN works but the Internet does not

This result is valuable: Factorio is probably listening and the local path is functional. Concentrate on the public-network boundary:

• Router forwarding sends the correct UDP port to the correct private address.
• The host firewall or antivirus permits inbound UDP.
• Players are using the current public address, not the server’s private address.
• Docker or another network layer publishes the port from the host to the container.
• The Internet service is not placing the router behind carrier-grade NAT (CGNAT) or another upstream NAT that prevents inbound connections.

The official multiplayer guidance requires a publicly accessible IP for Internet play behind NAT, or a port-forwarding solution. Local players should use the LAN address; an internal client may not be able to reach the public address when the router lacks NAT loopback support, so test the public path from a genuinely external network.

Identify which address to give players

A private address is used inside your home or office network and is normally not reachable from the Internet. Internet players need the router’s current public address together with the configured Factorio port. If your public address changes, players must use the new one unless you have a separate address-management arrangement. Never expose a private LAN address as though it were a public server address.

5. Build and verify the router forwarding rule

1. Find the server’s private address. Check the server computer’s network information and confirm that it matches the address reserved for the machine.
2. Open the router’s port-forwarding page. Product labels vary, but the rule normally asks for an external port, an internal port, a protocol, and a destination address.
3. Create a UDP rule. Forward the Factorio port, 34197 by default, from the router’s Internet interface to the server’s private address on the same internal port unless you intentionally configured a different mapping.
4. Save and apply the configuration. Some routers require a reboot or a separate apply action.
5. Check for more than one router. A modem-router plus a second router can create double NAT. The forwarding path must reach the server through every NAT layer, or the upstream device must be placed in a mode that provides a direct public address to the forwarding router.
6. Test from outside the LAN. Ask a player on another Internet connection to connect using the public address and port. A test from inside the same network may only test local NAT-loopback behavior.

Do not forward TCP instead of UDP, and do not forward the port to an address that belongs to a different computer. If the rule looks correct but there is no response, check whether the ISP uses CGNAT: in that case, the address shown by the router may not be directly reachable from the Internet, and ordinary home-router forwarding cannot solve the upstream NAT.

6. Check every firewall and security layer

A Factorio server can be blocked by more than the operating system’s basic firewall. Check, in order, the host firewall, antivirus or endpoint security, a cloud security group if applicable, and the router’s own inbound filtering. Each layer must permit inbound UDP on the actual configured port.

Use a narrow diagnostic rule

Create an inbound rule for the Factorio executable or for the selected UDP port, limited to the networks you intend to serve. If you briefly disable a firewall to confirm the cause, reconnect the firewall immediately and replace the broad test with a specific allow rule. A successful test while protection is disabled proves that a rule is missing; it is not a safe permanent configuration.

Read the result correctly

• If localhost works but another LAN device fails, the host firewall or local network isolation is a prime suspect.
• If LAN works but an external player times out, inspect the router, public address, ISP NAT, and any upstream firewall.
• If a client reaches the server and then receives a compatibility error, return to the exact version and mod comparison rather than opening more ports.

7. Troubleshoot Docker and other network layers

Running Factorio in Docker adds a second network boundary. The container must receive the UDP port from the host, and the host must receive it from the router. The factoriotools Docker documentation notes that when the IP address and port are correct, port-forwarding or firewall problems are likely. Its notes also warn that port mappings can affect server-browser port detection.

Trace the port through both sides

• Confirm which UDP port Factorio listens on inside the container.
• Confirm which host port is published to that container port.
• Confirm the router forwards the public port to the Docker host’s private address, not to an unreachable container address.
• Confirm the host firewall allows the published UDP port.

A direct connection by address is a better first test than relying on a browser listing. If direct connection succeeds but the browser does not show the server, inspect the mapping and the server-browser behavior rather than changing the save or mods.

Eliminate layers temporarily

For diagnosis, connect a local client directly to the Docker host’s LAN address and published port. If that fails, the problem is between the container and host. If it succeeds locally but fails externally, continue with router forwarding, firewall, public addressing, and ISP NAT. Restore the intended container isolation after testing.

Rank #3

Sale

Mumba Mouse Grip for Nintendo Switch 2 Joy-Con, [2 Pack] Ergonomic Gamer Grip Holder with Super Smooth PTFE Glide Pads Portable Gaming Controller Stand for Switch 2 Joy Con Accessories (2025), Black

• Compatibility: Designed specifically for the Nintendo Switch 2 Joy-Con controllers, with dedicated left and right grips. It provides a more comfortable and precise control experience for smoother gameplay.
• Ergonomic Design: This comfortable Switch 2 controller grip is designed to fit the shape of your hand, with finger grooves for a stable and secure grip, helping you stay relaxed during long gaming sessions.
• Zero Resistance: The precision-crafted ABS shell and unique Teflon feet provide an ultra-smooth movement experience, making your control more precise. Whether it's shooting, strategy, or simulation games, you can enjoy an intuitive and seamless connection with the game.
• Quick & Easy Setup: Align the "+" and "-" buttons on your Switch 2 Joy-Con with the corresponding markings on the mouse grip, then snap it into place for immediate use, so you’re ready to game in seconds with enhanced precision.
• Lightweight and Portable: Weighing only 34.2g, it’s easy to carry and lets you enjoy a professional-grade gaming experience anytime, anywhere.

$24.29

Buy on Amazon

8. Use controlled tests instead of guesswork

Change one variable at a time

Record the current port, private address, public address, version, mod set, and whether the test was local or external. Then change one item and repeat the same connection attempt. This prevents a successful change from being hidden by a simultaneous, conflicting edit.

Try a local client

The March 2025 Factorio forum discussion recommends checking firewall rules and trying a local client. Treat that discussion as a troubleshooting idea rather than a universal fix, but the test is useful because it divides the problem into local and public paths. A local success narrows the investigation to the Internet boundary; a local failure keeps the focus on Factorio, compatibility, or the host.

Use an SSH tunnel only as a diagnostic

The same forum discussion mentions an SSH tunnel when a direct UDP connection receives no response. Tunneling changes the path and adds another system to configure; it is not proof that the normal public UDP path is correct and it is not a substitute for proper forwarding. Use it to answer a narrow question—whether an alternate path can reach the server—then fix the ordinary UDP path or choose a hosting arrangement designed for it.

9. Decide whether to keep self-hosting

Self-hosting is practical when you control the router and firewall, can keep the server online, and are comfortable maintaining the operating system or Docker. Managed Factorio server hosting can remove router, firewall, and operating-system administration, but it shifts responsibility to the provider. Compare the two options against the needs of your group rather than treating hosting as an automatic network fix.

Before choosing a provider, confirm current US availability, pricing, backups, mod support, save access, expected player count, uptime commitments, and any partner terms. Those details change and should be checked on the provider’s current pages rather than assumed from a generic hosting description.

Symptom-by-symptom recovery paths

“Could not establish network communication” appears immediately

1. Confirm the server process is running and the intended save loaded.
2. Confirm the client and server have exactly matching versions and mods.
3. Connect locally by LAN address and configured UDP port.
4. If local access works, verify public address, UDP forwarding, host firewall, Docker publishing, and ISP NAT.

Friends cannot join, but you can play locally

This is a public-boundary problem until proven otherwise. Recheck the router’s UDP rule, the destination private address, the host firewall, the address given to friends, and whether an upstream NAT prevents inbound traffic. Have one friend test from a different Internet connection so the result is not confused with local NAT-loopback behavior.

The server disappears after a reboot

Check whether the private address changed, whether the server process restarted with the same save and port, and whether the router rule still targets the correct machine. A forwarding rule is only useful while the intended process is listening on the forwarded port.

A Docker server is reachable locally but not externally

Verify the container’s listening port, the host’s published UDP port, the host firewall, and the router’s destination. Then test by direct public address. Browser detection can be affected by port mappings even when direct connectivity works.

Changing the port made the problem worse

Return to one known configuration and document it: Factorio’s configured port, host firewall rule, Docker mapping if used, router forwarding rule, and the port in the client address. The default is UDP 34197, but every layer must use the custom value when you change it.

Final verification checklist

• The server starts with --start-server SAVE and remains running.
• The intended save is loaded and the server console shows no startup failure.
• Every client and the server use exactly the same game version and mods.
• The selected port is known; UDP is used, not TCP.
• A local client can connect through the host’s LAN address and port.
• The server’s private address is stable and matches the router’s destination.
• The host firewall, antivirus, cloud security group, and router permit inbound UDP on that port.
• Docker, if present, publishes the same UDP path from the host to the container.
• Internet players use the current public address, not the private LAN address.
• The ISP is not blocking inbound access through CGNAT or another upstream NAT.
• An external player has tested the connection from outside the server’s LAN.

Once these checks pass, a “server not responding” report has been reduced to a specific layer instead of a vague Factorio error. Keep the working port, address, version, mod list, and forwarding destination recorded so the next update or router restart can be checked quickly.

Quick Recap

SaleBestseller No. 1

CyberPowerPC Gamer Xtreme VR Gaming PC, Intel Core i5-13400F 2.5GHz, GeForce RTX 5060 8GB, 16GB DDR5, 1TB PCIe 4.0 SSD, WiFi Ready & Windows 11 Home (GXiVR8060A40)

Graphics: NVIDIA GeForce RTX 5060 8GB Graphics | 1x HDMI | 2x DisplayPort; Tempered Side Case Panel | Custom RGB Lighting | Keyboard and Mouse

$1,285.00

Bestseller No. 2

ZER-LON Prebuilt Gaming PC Desktop, Core I7 up to 3.9 GHz, RX 550 4GB GDDR5

$469.99

SaleBestseller No. 3

Mumba Mouse Grip for Nintendo Switch 2 Joy-Con, [2 Pack] Ergonomic Gamer Grip Holder with Super Smooth PTFE Glide Pads Portable Gaming Controller Stand for Switch 2 Joy Con Accessories (2025), Black

$24.29

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.