Menu
 

Fix Timeout Error

Fix Timeout Error

__Outdated Guide as of Release of Satisfactory 1.0__

Satisfactory currently has a known bug where the server times out. Here are a few steps to help fix this issue:

Legacy Timeout Error Analysis

Historical context for pre-1.0 Satisfactory networking issues (may not apply to current game):

Historical Timeout Causes

  • Network Timeout: Connection between client and server interrupted or too slow
  • Server Response: Server took too long to respond to client requests
  • Configuration Issues: Network settings not optimized for connection type
  • Hardware Limitations: Server or client hardware couldn't handle connection load
  • Mod Conflicts: Some mods introduced network latency issues

Historical Note: These timeout issues were primarily addressed in later game updates. If experiencing current connection problems, please refer to our updated Connection Issues (1.0) guide for modern troubleshooting.

Client-Side Network Optimization

Accessing Configuration Files

Modify your local game configuration to improve network stability:

  1. Locate Config Directory:
    • Steam: %LOCALAPPDATA%/FactoryGame/Saved/Config/Windows/
    • Epic Games: %LOCALAPPDATA%/FactoryGame/Saved/Config/Windows/
    • Alternative Method: Press Win + R, paste the path, and press Enter.
  2. Backup Files: Always backup configuration files before modifying them.
  3. Edit with Caution: Incorrect settings can prevent game from starting.

Engine.ini Modifications

Open Engine.ini and locate [/Script/OnlineSubsystemUtils.IpNetDriver] section:


[/Script/OnlineSubsystemUtils.IpNetDriver]
MaxClientRate=120000
MaxInternetClientRate=120000
InitialConnectTimeout=300.0
ConnectionTimeout=300.0

Parameter Explanations

  • MaxClientRate: Maximum bandwidth for local network (120000 recommended).
  • MaxInternetClientRate: Maximum bandwidth for internet connections (120000 recommended).
  • InitialConnectTimeout: Time in seconds before initial connection attempt fails (300 seconds = 5 minutes).
  • ConnectionTimeout: Time in seconds before established connection is considered lost (300 seconds = 5 minutes).

Game.ini Network Settings

Open Game.ini and add or modify [/Script/Engine.GameNetworkManager] section:


[/Script/Engine.GameNetworkManager]
TotalNetBandwidth=104857600
MaxDynamicBandwidth=104857600
MinDynamicBandwidth=10485760

Bandwidth Configuration

  • TotalNetBandwidth: Total network capacity in bytes/second (104857600 = 100 MB/s = 1 Gbps).
  • MaxDynamicBandwidth: Maximum dynamic bandwidth allocation.
  • MinDynamicBandwidth: Minimum bandwidth allocation for stable connection.
  • Adjustment: Lower values for slower connections, higher values for gigabit networks.

Scalability.ini Network Quality

Open Scalability.ini and modify [NetworkQuality@3] section:


[NetworkQuality@3]
TotalNetBandwidth=104857600
MaxDynamicBandwidth=104857600
MinDynamicBandwidth=10485760

Quality Settings

  • Network Quality Level: Adjust based on connection stability (1-5 scale).
  • Bandwidth Consistency: Higher values provide smoother gameplay but use more data.
  • Latency Tolerance: Higher tolerance for unstable connections, lower for fast stable networks.

Server-Side Optimization

Dedicated Server Configuration

  • Tick Rate: Set server tick rate to 120 for smooth gameplay.
  • Timeout Values: Increase timeout values for players with slower connections.
  • Bandwidth Limits: Set appropriate bandwidth limits per player.
  • Network Quality: Configure server network quality to match average player connection.

Server Command Line Options

  • Multihome: -multihome=IP_ADDRESS (Use carefully, can cause API issues in 1.0).
  • Port Configuration: Ensure Port 7777 is properly forwarded.
  • Max Players: Set appropriate player limit for server hardware.
  • Log Level: Increase logging for debugging timeout issues.

Common Timeout Scenarios

Connection Timeout During Load

  • Symptom: Timeout when server has many players or large factories.
  • Cause: Server CPU or network cannot handle load.
  • Solution:
    • Reduce player count or factory complexity.
    • Increase timeout values in configuration files.
    • Upgrade server hardware if necessary.
    • Reduce mod count, especially performance-heavy mods.

Timeout on Startup

  • Symptom: Server fails to respond to initial connection attempts.
  • Cause: Server hardware insufficient or configuration issues.
  • Solution:
    • Check server logs for specific error messages.
    • Verify server meets minimum hardware requirements.
    • Check for corrupted save files.
    • Restart server service/application.
    • Review recent server configuration changes.

Timeout During Gameplay

  • Symptom: Disconnection during active gameplay despite good connection.
  • Cause: Network instability or client configuration issues.
  • Solution:
    • Verify client configuration files are correct.
    • Check internet connection stability.
    • Disable VPNs or proxies that may interfere.
    • Close bandwidth-intensive applications.
    • Test with different network connection if available.

Advanced Troubleshooting

Diagnostic Commands

  • Network Test: Run ping and traceroute to server to identify network issues.
  • Port Check: Verify Port 7777 is accessible from your location.
  • Bandwidth Test: Test available bandwidth to server location.
  • Firewall Verification: Confirm no firewall is blocking connections.

Mod-Specific Timeout Issues

  • Mod Conflicts: Some mods introduce network latency or timeout issues.
  • SML (Satisfactory Mod Loader): Ensure SML is updated to latest version.
  • Mod Dependencies: Verify all mod dependencies are installed and compatible.
  • Performance Mods: Some mods significantly increase server load and network traffic.
  • Mod Removal: Test vanilla (no mods) to isolate mod-related timeout issues.

Network Environment Issues

  • ISP Throttling: Some ISPs throttle continuous connections.
  • Network Congestion: High-traffic periods may cause timeouts.
  • Router Configuration: Quality of Service (QoS) settings may interfere.
  • WiFi Interference: Use wired connection when possible for stability.
  • VPN/Proxy: These can introduce additional latency and timeout issues.

Best Prevention Practices

Regular Maintenance

  • Server Restarts: Schedule regular restarts to clear memory and network issues.
  • Configuration Reviews: Regularly review and update network settings.
  • Mod Updates: Keep all mods updated to latest compatible versions.
  • Performance Monitoring: Monitor server performance metrics for developing issues.

Configuration Optimization

  • Balanced Settings: Choose settings appropriate for your connection type.
  • Conservative Timeouts: Use longer timeout values for stability.
  • Appropriate Bandwidth: Set bandwidth based on actual network capacity.
  • Regular Testing: Test connections after configuration changes.

Historical Note: This legacy guide may contain outdated information that does not apply to Satisfactory 1.0. Always backup your configuration files before modifying them.

Transition to Satisfactory 1.0

In September 2024, Satisfactory 1.0 introduced major networking changes that obsolete most of the information in this historical guide:

  • Port Changes: Port 7777 replaced old ports (15777, 15000) as the primary connection port
  • TLS Encryption: New authentication system replaced basic token-based auth
  • In-Game Server Manager: Dedicated servers now use integrated in-game management instead of external tools
  • EOS Authentication: Epic Online Services integration for secure player identity

When to Use This Historical Guide

This legacy information may still be useful in these specific scenarios:

  • Early Access Servers: Running older pre-1.0 dedicated servers with original networking model
  • Single-Player Testing: Testing connection configurations in single-player mode
  • Understanding Changes: Learning how pre-1.0 differed from 1.0 for educational purposes
  • Legacy Systems: Maintaining or troubleshooting older hardware/software configurations

Current Players: For actual 1.0 connection troubleshooting and modern networking issues, please refer to our comprehensive Connection Issues (1.0) guide which covers TLS encryption, Port 7777, EOS authentication, and all current server problems.

*Satisfactory dedicated servers are in early access, if you need additional support please reach out to our support team.*

Top