Current Response Times
Due to an increase in workload, and a change in our working practices due to Covid-19; we are having to prioritise help tickets that are preventing users from playing our games. Whilst we aim to address every ticket in the order received, this may mean some tickets receive a reply outside of the response time below. We apologise for this inconvenience and thank you for your patience and understanding.
If you are receiving an authentication error after installing the latest update, please select "Options" -> "Log out machine" on the launcher and then log back in. 


This is the Frontier Developments Customer Support site.

How do I obtain a netlog file?

Updated: Saturday 29th September 2018

In order to tell Elite Dangerous to create Netlog files you will need to perform the following steps:

  1. If you are currently playing the game please select Save and Exit to exit to the main menu. This will allow you to access the Network section of the Options menu.
  2. Open the Network options menu.
  3. Set the option labelled Logging to On.
  4. Play Elite Dangerous once more until you encounter the problem you wish to learn more about.
The option labelled Path underneath the Logging option indicates where to find all Netlogs that are created by the game. You can also check this FAQ article.

If you cannot get in-game to activate this in the options menu:

To enable this extra detail out of game, download the attached AppConfigLocal.xml file and place it into your game installation folder. The game should now create fully detailed files that you can send to us.

Finding the correct Netlog file for the issue

It is very important that the log file we receive is from the time the issue occurred to help us diagnose the problem.

The file will look something like this: netLog.1234567890.01.log

The first part of the file indicates that it is a netlog and the number sequence that follows is the time and date that the log was started. 

As an example netLog.170302153108.01.log has the first six numbers 170302, This goes Year/Month/Day so that file is from the 2nd of March 2017. The next six numbers represent the time 153108 Hour/Min/Seconds, so in this case the time is 3.31pm.

Another good way of finding the needed file is to search the Logs folder by Date Modified, this is the time the file was last changed.

Attachments: AppConfigLocal.xml (178 bytes) 

Do you need additional support on your issue?

Yes, Open a Ticket

Please Wait!

Please wait... it will take a second!