Difference between revisions of "Web Launcher Change Log"
| Line 1: | Line 1: | ||
===Launcher 0.6.1=== | ===Launcher 0.6.1=== | ||
| − | * Machine SSL certificates which are normally valid for a duration of 1 year, now attempt to auto-renew when expiration time is within 30 days. | + | * Machine SSL certificates which are normally valid for a duration of 1 year, now attempt to auto-renew when expiration time is within 30 days. Previously if a certificate expired, the machine would be unable to connect to the web launcher server, and a new machine would need to be created. |
===Launcher 0.5.24=== | ===Launcher 0.5.24=== | ||
Revision as of 14:33, 13 May 2019
Launcher 0.6.1
- Machine SSL certificates which are normally valid for a duration of 1 year, now attempt to auto-renew when expiration time is within 30 days. Previously if a certificate expired, the machine would be unable to connect to the web launcher server, and a new machine would need to be created.
Launcher 0.5.24
- Fixed a bug that prevented lua server commands to be sent to running region servers if the starting server index was over 9.
Launcher 0.5.23
- Due to community request now supports the option of spawning region server processes with a visible console. To enable this in the launcher_data/settings.json file set "serverconsole" to true. Make sure to restart the launcher process afterwards for the change to take affect.
- Note: This spawns a console per region server process, it is recommended to use a software solution like ComEnu (https://conemu.github.io/) to move these into a tabbed interface if so desired.
Logbrowser-launcher-plugin 1.0.11
- Now defaults to binding to localhost port 1776 only. If you wish to have it bind to all interfaces for remote access set "remoteAllowed" to true inside of settings.json launcher_data folder, and restart your launcher process. Note remote access should be considered a security risk unless appropriate measures are taken to lock it down.
