Find why X-Plane crashes when connected to the internet and apply targeted fixes for weather, multiplayer, plugins, firewalls and streamed scenery.
X-Plane usually freezes or crashes online because an internet-enabled plugin, real-weather download, multiplayer connection, firewall filter or damaged network cache fails—not because the simulator simply has internet access. Test with manual weather, multiplayer off and third-party plugins removed, then inspect Log.txt immediately after the failure to identify the component.
These checks apply primarily to desktop versions of X-Plane 11 and 12. Menu wording varies between releases, while X-Plane Mobile does not use the desktop plugin and scenery folders described below.
What causes X-Plane to crash when it connects?
Most cases come from a feature that starts using the connection, rather than from the connection itself.
| When it fails | Likely cause | Best first test |
|---|---|---|
| Immediately after internet access becomes available | Plugin updater, online service, VPN or security filtering | Start without third-party plugins |
| When real weather loads | Incomplete weather data, cache problem or heavy cloud rendering exposing GPU instability | Use manual clear weather |
| When joining multiplayer or an online network | Client plugin, firewall, UDP or connection problem | Disable the online client and multiplayer |
| While crossing scenery tile boundaries | Streamed scenery, cache, disk or external helper failure | Use default scenery with streaming disabled |
| Only with one aircraft | Aircraft-specific plugin contacting an online service | Load a default aircraft |
Real weather can create a misleading correlation. If a downloaded weather set introduces dense clouds and the same crash occurs with a similarly demanding manual weather preset, the internet is not the underlying problem; graphics memory, rendering settings or the display driver are more likely.
How do I isolate the internet-related crash?
The fastest method is to establish a clean offline baseline, reconnect without enabling online features, and then add one feature at a time.
- Preserve the evidence. After the crash, copy
Log.txtfrom the main X-Plane folder before launching the simulator again. X-Plane rewrites this file each session. - Establish a baseline. On an already activated installation, disconnect from the internet and load a default aircraft at a default airport with manual clear weather. Turn multiplayer and external online clients off.
- Reconnect without changing anything else. If X-Plane remains stable, internet access alone is not the trigger. An online feature activated later is responsible.
- Remove third-party plugins properly. Close X-Plane and move third-party folders from
Resources/pluginsinto a temporary folder outside the simulator. Do not remove components supplied with X-Plane. Disabling a plugin after startup is not always sufficient because its network code may already have loaded. Aircraft plugins, scripts and external scenery-streaming helpers also need separate attention; our advice on avoiding incompatible or duplicated add-ons explains the common installation conflicts. - Enable one online function per launch. Test real weather, multiplayer, an online client and streamed scenery separately. Restart between tests because some plugins do not unload cleanly.
- Check the security layer. Permit X-Plane and any required helper application through the firewall. Temporarily test without a VPN, proxy or encrypted-traffic inspection, but do not leave antivirus protection disabled. A firewall block normally causes a timeout, not a stock-simulator crash; a crash points to software mishandling that failed request.
- Test fresh preferences. Back up and temporarily rename
Output/preferences, allowing X-Plane to create fresh settings. This resets controls and other options, so retain the original folder and do not immediately copy all its files back. - Repair the installation. Use the X-Plane installer or the platform's file-verification function to replace damaged simulator files. If a clean installation still fails, follow the broader X-Plane 12 crash-isolation steps, including graphics-driver and operating-system checks.
What should I look for in X-Plane Log.txt?
Log.txt can normally separate a plugin crash, weather failure and graphics problem, provided it is examined before another X-Plane session overwrites it.
- An explicitly named plugin near the crash record is strong evidence. Update it for the installed X-Plane release or leave it removed.
- Repeated download, connection or weather errors identify the feature being blocked, although the final message is not always the component that caused the crash.
- An abrupt end after graphics or cloud-loading messages can indicate a display-driver or memory failure rather than a network fault.
- The same aircraft, scenery package or external helper appearing before every failure provides a repeatable test target.
A freeze differs from a crash. If X-Plane stays open and disk or network activity continues, it may be waiting for weather, compiling scenery or filling a streaming cache. The operating system reporting that the application is not responding does not prove it has crashed. Our guide to separating a slow X-Plane 12 load from a true freeze covers those storage, antivirus and scenery bottlenecks.
What should I test when only one online feature fails?
A feature-specific failure should be reproduced with that feature enabled in an otherwise clean default flight.
Real weather
Switch to manual weather first. If manual weather works, restart X-Plane and request fresh real-weather data without restoring an old downloaded-weather cache. Cache locations and file names differ between X-Plane 11 and 12, so back up the relevant downloaded data before removing it rather than following instructions written for another version.
If an equally cloudy manual preset also crashes, reduce cloud and texture demands temporarily and check the graphics driver. If only live weather fails, inspect firewall permissions, folder write access and Log.txt for repeated download or decoding errors.
Multiplayer and online clients
Test X-Plane's multiplayer function separately from third-party network clients, and run only one client during diagnosis. A disconnect or packet-loss problem should not normally close stock X-Plane; a crash limited to one client usually means that client plugin is incompatible or damaged. Use our firewall, UDP and NAT checks for X-Plane multiplayer before opening ports or changing router settings blindly.
Streamed scenery
A freeze that occurs at tile boundaries, accompanied by network and disk activity, usually belongs to the scenery streamer or its cache. Test the same route using default scenery, confirm that the cache drive has free space, and keep the cache out of cloud-synchronised folders. Antivirus scanning of thousands of newly created scenery files can also make a download appear frozen.
If clean stock X-Plane crashes merely when the computer regains internet access—with default aircraft, default scenery, manual weather and no third-party plugins—repair the simulator, test fresh preferences and try another trusted network. Failure on one network points to its VPN, router or filtering; failure on every network points back to the installation, security software or operating-system network stack.