WebDashboardEnabled but not loading during startup

LennyPane

Refugee
Hello! I'm encountered with WebDashboard problem. It isn't starting even when Enabled in serverconfig.xml
<property name="WebDashboardEnabled" value="true"/>
<property name="WebDashboardPort" value="8080"/>
<property name="WebDashboardUrl" value="https://www.mydomain.com:8080"/>
<property name="EnableMapRendering" value="true"/>

Alloc's fix installed. 
Pastebin with Server Output
Ports Forwarded, IP is Public Static, Game Server and Telnet is works. 
Problem with Webserver only. Thanks in advance!

 
do we have a full set of documented options for that file documented anywhere?
No, because the feature is still in Alpha development. It is basically an Alpha inside of an Alpha. I imagine @Alloc will get around to posing actual documentation on it at some point and discontinue his 3rd-party tool.
 
Options for what file exactly? Serverconfig.xml? That has its documentation included already.
For the serverconfig.xml there are instructions.

For the permissions for the web console that goes into admins.xml, there is nothing aside from some posts with partial information that may or may not be entirely accurate.

It's kind of like the Twitch tool instructions, where there is some old data posted somewhere that is incomplete and not up to date. Someone should take care of ensuring there is documentation for the tools included in the client, and that said documentation is easily accessible. Like putting pdf's into the client folder, instead of some note attached to the one patch note post where it was implemented.
 
For the serverconfig.xml there are instructions.

For the permissions for the web console that goes into admins.xml, there is nothing aside from some posts with partial information that may or may not be entirely accurate.

It's kind of like the Twitch tool instructions, where there is some old data posted somewhere that is incomplete and not up to date. Someone should take care of ensuring there is documentation for the tools included in the client, and that said documentation is easily accessible. Like putting pdf's into the client folder, instead of some note attached to the one patch note post where it was implemented.
boot.config
serveradmin.xml

are two config files that don't have any options documentation. or any documentation I could easily find.

As you have stated serverconfig.xml is extremely well commented and documented.
 
boot.config isn't even a game file but rather Unity. You don't expect us to document what each byte of the Unity executable does either, right? ;)

serveradmin.xml is not meant to be touched at all actually - other than potentially setting up a single first admin if you neither want to use the dedicated server terminal window (on Windows) nor the network socket terminal ("Telnet"). That part is documented though in the file - as well as a bunch of other sections. But in the end you're supposed to use the console commands to manage that file as that way you're guaranteed to get proper entries in there. And the console commands also tell you what the options are and e.g. what Web APIs exist that can be specified.
 
Back
Top