Edproxy is not being maintained at this time.
Elite: Dangerous Netlog proxy server (edproxy) replicates the netLog entries (currently System only) out to any registered listeners via TCP so that an application may run from anywhere.
edproxy now fully supports Elite: Dangerous screen shots. The images may be renamed to the current system automatically, and may be converted to either JPG or PNG.
Installation Instructions
If you find an issue please create a new ticket in Jira.
I would like to give special thanks to CMDR Bam and CMDR Myshka for beta testing the Windows versions for me!
Version 2.3.2
- Fixed handling of duplicate entries within EDSM nightly json file.
** This should address an issue where the download/sync gets stuck.
- Hardened all database interactions.
- Fixed startup issue for UI display thread.
- Added support for websockets.
** URL is "ws://<ip/v1"
- Changed EDSM sync behavior. The initial database download will be modal (synchronous), however updates will be performed in the background.
Version 2.2.2
- EDSM now requires the application version number.
Version 2.2.1
- Add support for the Engineers release
- Add support for new (x, y, z) API with the EDSM plugin
Version 2.2.0
- Edproxy now downloads the EDSM database.
* Distance information will now be added into the System event. (up to 25 entries)
* You may retrieve distances between two systems using the "GetDistances" API. This API is an array so you may ask for multiple at a time.
- Fixed parsing error with the netLog. "System" netLog lines are being concatenated with their previous line.
- Edproxy now supports "SendKeys" on Windows only (sorry Mac folks).
* The keys will be sent out via DirectX key events. They will be broadcast to the PC and not just to Elite. Thus whatever application is in the foreground will receive the key event.
Version 2.1.5
- Now using AppConfigLocal.xml instead of AppConfig.xml.
- Separated out the net Log directory and AppConfig directories in the configuration and settings.
- Auto-detect directory paths if none have been set.
- Do not allow special characters from systems names when saving image files.
Version 2.1.4
- New image event was not transmitted due to bad date/time.
-----
Version 2.1.3:
- Horizons release changed netLog naming format. This update handles that change.
-----
Version 2.1.2:
- New support for 3rd party plugins!
** Support is limited to those items included by hand currently. Sorry to say this is not truly dynamic yet.
** Added new View into active 3rd party plugins.
- Support for EDSM 3rd party plugin
** Cloud based storage for all the systems you have visited!
** Edproxy is designed to only *read* the netLog. Thus it does not have a concept of exploration notes or anything like that. Here we are *only* sending the systems you have visited just like Edproxy currently events out to listening applications.
How to setup Edproxy to transmit your system logs to EDSM
1. Go create an EDSM (www.edsm.net) account.
2. Look in your Account settings for your API Key.
3. Open Edproxy->Settings (MacOSx->Preferences)
4. Enter your API key AND the commander name you registered.
5. Click OK!
6. If you have auto-start on then Edproxy will automatically Stop then Start the server. Otherwise click on the "Start" button.
If you have a lot of systems in your log file the initial upload may take a very long time depending where you are in the world. It could be more than 30 minutes to get everything up-to-date. HOWEVER, you do NOT have to wait! Edproxy remembers where you are in the update process so even if you close the application, and restart, it will begin the update from where you left off. Also, you do NOT need to wait for it to finish to continue your exploration, or movement in the game. Edproxy will automatically send out all systems in order until it has caught up with your current location.
-----
Version 2.0.4:
* Fixed several crashes, or lockups, due to networking
* Fixed High Resolution images not being converted.
* Added new Ping/Pong heartbeat so both Edproxy and clients may react faster to disconnects.
-----
Version 2.0.3:
* Fixed startup issue where the .edproxy did not exist so the application would crash.
* Added 'Heartbeat' flag to 'Init' message. This is optional and will function without a heartbeat.
* Added 'Heartbeat' message type.
** A client sends a heartbeat at an assigned (better to be a few seconds before) interval. If edproxy misses two heartbeats in a row then it will close down the connection.
Big thank you to @silence_please for looking into the root cause!
-----
Version 2.0.2:
* Now supports Windows *and* Mac installers!
** Full support for "automatic" updates.
The major version was rolled to 2.x to delineate between auto-install and self install.
-----
Releasing version 1.2.1:
- New "Settings" or "Preferences" interface!
** It is now easier than ever to setup the netlog path.
** Now contains settings for starting the server automatically on edproxy launch.
** There is now an Image acquisition section.
** The multicast Time-to-Live (TTL) is now configurable.
- New configuration and log files.
** Configuration and Log files are now stored in <User Dir>/.edproxy
- Added Image acquisition!
** Listeners to edproxy will be notified of new images files on "creation"
** Images will be automatically renamed to the current "system" with existing date/time stamps.
** Automatic file format conversion to PNG or JPG supported.
** Replace "space" with other characters supported. (NOTE: It is recommended for AndDiscovered to leave spaces!!!!)
** Option to automatically delete old BMP after conversion. (Those high resolution files are 99.5MB folks!)
- Properly handle reconnection of client.
- Many bugs have been squashed. Many I say!
-----
Releasing version 1.1.0:
- Added log into <UserDir>/.edproxy/edproxy.log
- Added list view that shows actively connected client IP address and port.
Elite: Dangerous Netlog proxy server (edproxy) replicates the netLog entries (currently System only) out to any registered listeners via TCP so that an application may run from anywhere.
edproxy now fully supports Elite: Dangerous screen shots. The images may be renamed to the current system automatically, and may be converted to either JPG or PNG.
Installation Instructions
- Download Edproxy
- Install the application through the normal means for your OS.
- On first launch Edproxy will attempt to locate your E
Log and AppConfig directories. If it fails to find these directories in their default paths you will need to manually enter them in Settings.
- Common Windows Log locations:
- <user_dir>\AppData\Local\Frontier_Developments\Products\elite-dangerous-64\Logs
- <user_dir>\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1010\Logs
- C:\Program Files (x86)\Steam\steamapps\common\Elite Dangerous\Products\elite-dangerous-64\Log
- C:\Program Files (x86)\Steam\steamapps\common\Elite Dangerous\Products\FORC-FDEV-D-1010\Log
- Common Windows AppConfig locations:
- <user_dir>\AppData\Local\Frontier_Developments\Products\elite-dangerous-64
- <user_dir>\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1010
- C:\Program Files (x86)\Steam\steamapps\common\Elite Dangerous\Products\elite-dangerous-64
- C:\Program Files (x86)\Steam\steamapps\common\Elite Dangerous\Products\FORC-FDEV-D-1010
- Common MacOSx Log locations:
- <user_dir>/Library/Application Support/Frontier Developments/Elite Dangerous/Logs
- <user_dir>/Library/Application Support/Steam/steamapps/common/Elite Dangerous/Products/elite-dangerous-64/Logs
- <user_dir>/Library/Application Support/Steam/steamapps/common/Elite Dangerous/Products/FORC-FDEV-D-1010/Logs
- Common MacOSx AppConfig locations:
- <user_dir>/Library/Application Support/Frontier_Developments/Products/elite-dangerous-64/EliteDangerous.app/Contents/Resources
- <user_dir>/Library/Application Support/Frontier_Developments/Products/FORC-FDEV-D-1010/EliteDangerous.app/Contents/Resources
- <user_dir>/Library/Application Support/Steam/steamapps/common/Elite Dangerous/Products/elite-dangerous-64/EliteDangerous.app/Contents/Resources
- <user_dir>/Library/Application Support/Steam/steamapps/common/Elite Dangerous/Products/FORC-FDEV-D-1010/EliteDangerous.app/Contents/Resources
- Common Windows Log locations:
- If you wish to event your snapshot images set your Images path within Settings.
- You may also wish to have the name of the snapshot image converted to the system name.
- Click on Start to start Edproxy.
If you find an issue please create a new ticket in Jira.
I would like to give special thanks to CMDR Bam and CMDR Myshka for beta testing the Windows versions for me!
Version 2.3.2
- Fixed handling of duplicate entries within EDSM nightly json file.
** This should address an issue where the download/sync gets stuck.
- Hardened all database interactions.
- Fixed startup issue for UI display thread.
- Added support for websockets.
** URL is "ws://<ip/v1"
- Changed EDSM sync behavior. The initial database download will be modal (synchronous), however updates will be performed in the background.
Version 2.2.2
- EDSM now requires the application version number.
Version 2.2.1
- Add support for the Engineers release
- Add support for new (x, y, z) API with the EDSM plugin
Version 2.2.0
- Edproxy now downloads the EDSM database.
* Distance information will now be added into the System event. (up to 25 entries)
* You may retrieve distances between two systems using the "GetDistances" API. This API is an array so you may ask for multiple at a time.
- Fixed parsing error with the netLog. "System" netLog lines are being concatenated with their previous line.
- Edproxy now supports "SendKeys" on Windows only (sorry Mac folks).
* The keys will be sent out via DirectX key events. They will be broadcast to the PC and not just to Elite. Thus whatever application is in the foreground will receive the key event.
Version 2.1.5
- Now using AppConfigLocal.xml instead of AppConfig.xml.
- Separated out the net Log directory and AppConfig directories in the configuration and settings.
- Auto-detect directory paths if none have been set.
- Do not allow special characters from systems names when saving image files.
Version 2.1.4
- New image event was not transmitted due to bad date/time.
-----
Version 2.1.3:
- Horizons release changed netLog naming format. This update handles that change.
-----
Version 2.1.2:
- New support for 3rd party plugins!
** Support is limited to those items included by hand currently. Sorry to say this is not truly dynamic yet.
** Added new View into active 3rd party plugins.
- Support for EDSM 3rd party plugin
** Cloud based storage for all the systems you have visited!
** Edproxy is designed to only *read* the netLog. Thus it does not have a concept of exploration notes or anything like that. Here we are *only* sending the systems you have visited just like Edproxy currently events out to listening applications.
How to setup Edproxy to transmit your system logs to EDSM
1. Go create an EDSM (www.edsm.net) account.
2. Look in your Account settings for your API Key.
3. Open Edproxy->Settings (MacOSx->Preferences)
4. Enter your API key AND the commander name you registered.
5. Click OK!
6. If you have auto-start on then Edproxy will automatically Stop then Start the server. Otherwise click on the "Start" button.
If you have a lot of systems in your log file the initial upload may take a very long time depending where you are in the world. It could be more than 30 minutes to get everything up-to-date. HOWEVER, you do NOT have to wait! Edproxy remembers where you are in the update process so even if you close the application, and restart, it will begin the update from where you left off. Also, you do NOT need to wait for it to finish to continue your exploration, or movement in the game. Edproxy will automatically send out all systems in order until it has caught up with your current location.
-----
Version 2.0.4:
* Fixed several crashes, or lockups, due to networking
* Fixed High Resolution images not being converted.
* Added new Ping/Pong heartbeat so both Edproxy and clients may react faster to disconnects.
-----
Version 2.0.3:
* Fixed startup issue where the .edproxy did not exist so the application would crash.
* Added 'Heartbeat' flag to 'Init' message. This is optional and will function without a heartbeat.
* Added 'Heartbeat' message type.
** A client sends a heartbeat at an assigned (better to be a few seconds before) interval. If edproxy misses two heartbeats in a row then it will close down the connection.
Big thank you to @silence_please for looking into the root cause!
-----
Version 2.0.2:
* Now supports Windows *and* Mac installers!
** Full support for "automatic" updates.
The major version was rolled to 2.x to delineate between auto-install and self install.
-----
Releasing version 1.2.1:
- New "Settings" or "Preferences" interface!
** It is now easier than ever to setup the netlog path.
** Now contains settings for starting the server automatically on edproxy launch.
** There is now an Image acquisition section.
** The multicast Time-to-Live (TTL) is now configurable.
- New configuration and log files.
** Configuration and Log files are now stored in <User Dir>/.edproxy
- Added Image acquisition!
** Listeners to edproxy will be notified of new images files on "creation"
** Images will be automatically renamed to the current "system" with existing date/time stamps.
** Automatic file format conversion to PNG or JPG supported.
** Replace "space" with other characters supported. (NOTE: It is recommended for AndDiscovered to leave spaces!!!!)
** Option to automatically delete old BMP after conversion. (Those high resolution files are 99.5MB folks!)
- Properly handle reconnection of client.
- Many bugs have been squashed. Many I say!
-----
Releasing version 1.1.0:
- Added log into <UserDir>/.edproxy/edproxy.log
- Added list view that shows actively connected client IP address and port.
Last edited: