FS2 WebUI Standalone - Revision history

Echelon9: Clarify that WebUI standalone works on Mac as well

2014-03-24T13:02:32Z

Clarify that WebUI standalone works on Mac as well

← Older revision		Revision as of 13:02, 24 March 2014
Line 1:		Line 1:
	The WebUI standalone was created by SCP member Eli2 to enable *nix machines to run a standalone FS2 server.		The WebUI standalone was created by SCP member Eli2 to enable *nix and Mac machines to run a standalone FS2 server.

	==How to Use==		==How to Use==

Echelon9: /* Sample multi.cfg */

2013-12-05T09:52:24Z

Sample multi.cfg

← Older revision		Revision as of 09:52, 5 December 2013
Line 63:		Line 63:
	*Servers (whether WebUI standalone or otherwise) do not feature NAT punchthrough, as much of the traffic is UDP traffic. This means the standalone host must be on a public facing IP address, or you must set up port forwarding using standard FreeSpace 2 Open ports. For those on cable or ADSL modem connections, the "DMZ" feature of your modem/router will achieve the equivalent outcome.		*Servers (whether WebUI standalone or otherwise) do not feature NAT punchthrough, as much of the traffic is UDP traffic. This means the standalone host must be on a public facing IP address, or you must set up port forwarding using standard FreeSpace 2 Open ports. For those on cable or ADSL modem connections, the "DMZ" feature of your modem/router will achieve the equivalent outcome.

	==Sample multi.cfg==		==Sample multi.cfg for WebUI standalone server==

	<pre>		<pre>

Chief1983: /* Sample multi.cfg */

2013-12-05T09:02:08Z

Sample multi.cfg

← Older revision		Revision as of 09:02, 5 December 2013
Line 72:		Line 72:
	+max_players 12		+max_players 12
	+use_pxo		+use_pxo
	+pxo #~~autoselect~~		+pxo #Eleh
	+pxo_login chief_standalone		+pxo_login chief_standalone
	+pxo_password [Insert Password]		+pxo_password [Insert Password]

Chief1983: /* Sample multi.cfg */

2013-12-04T22:30:01Z

Sample multi.cfg

← Older revision		Revision as of 22:30, 4 December 2013
Line 74:		Line 74:
	+pxo #autoselect		+pxo #autoselect
	+pxo_login chief_standalone		+pxo_login chief_standalone
	+pxo_password ~~password~~		+pxo_password [Insert Password]
	+webui_root /home/chief1983/fs2open_webui		+webui_root /home/chief1983/fs2open_webui
	+webapi_username [Insert Username]		+webapi_username [Insert Username]

Chief1983: /* Known Issues */

2013-12-04T22:29:16Z

Known Issues

← Older revision		Revision as of 22:29, 4 December 2013
Line 61:		Line 61:

	*No SSL to protect your authentication password, which is why the SSH tunnel is currently recommended, as that essentially solves the issue for the time being.		*No SSL to protect your authentication password, which is why the SSH tunnel is currently recommended, as that essentially solves the issue for the time being.
	*Servers (whether WebUI standalone or otherwise) do not feature NAT punchthrough, as much of the traffic is UDP traffic. This means the standalone host must be on a public facing IP address. For those on cable or ADSL modem connections, the "DMZ" feature of your modem/router will achieve the equivalent outcome.		*Servers (whether WebUI standalone or otherwise) do not feature NAT punchthrough, as much of the traffic is UDP traffic. This means the standalone host must be on a public facing IP address, or you must set up port forwarding using standard FreeSpace 2 Open ports. For those on cable or ADSL modem connections, the "DMZ" feature of your modem/router will achieve the equivalent outcome.

	==Sample multi.cfg==		==Sample multi.cfg==

Echelon9: /* Known Issues */

2013-12-04T13:01:18Z

Known Issues

← Older revision		Revision as of 13:01, 4 December 2013
Line 61:		Line 61:

	*No SSL to protect your authentication password, which is why the SSH tunnel is currently recommended, as that essentially solves the issue for the time being.		*No SSL to protect your authentication password, which is why the SSH tunnel is currently recommended, as that essentially solves the issue for the time being.
	*Servers (whether WebUI standalone or otherwise) do not feature NAT punchthrough, as much of the traffic is UDP traffic. This means, the standalone host must be on a public facing IP address. For those on cable or ADSL modem connections, the "DMZ" feature of your modem/router will achieve the equivalent outcome.		*Servers (whether WebUI standalone or otherwise) do not feature NAT punchthrough, as much of the traffic is UDP traffic. This means the standalone host must be on a public facing IP address. For those on cable or ADSL modem connections, the "DMZ" feature of your modem/router will achieve the equivalent outcome.

	==Sample multi.cfg==		==Sample multi.cfg==

Echelon9: /* Known Issues */ Clarify that standalone servers can be connected to over PXO fine

2013-12-04T13:00:51Z

Known Issues: Clarify that standalone servers can be connected to over PXO fine

← Older revision		Revision as of 13:00, 4 December 2013
Line 61:		Line 61:

	*No SSL to protect your authentication password, which is why the SSH tunnel is currently recommended, as that essentially solves the issue for the time being.		*No SSL to protect your authentication password, which is why the SSH tunnel is currently recommended, as that essentially solves the issue for the time being.
	*Servers ~~are showing up on FS2NetD when using +use_pxo~~, ~~but I have been unable to connect to~~ the ~~standalone using FS2NetD in game~~. ~~Disabling FS2NetD and adding the standalone's IP has worked~~, ~~as has finding~~ the standalone ~~when~~ on ~~the same LAN with FS2NetD turned off. This also seems to be~~ a ~~problem I'm having with my Windows standalone and 3~~.~~7.0 too~~, ~~so it might not be a WebUI issue at all~~.		*Servers (whether WebUI standalone or otherwise) do not feature NAT punchthrough, as much of the traffic is UDP traffic. This means, the standalone host must be on a public facing IP address. For those on cable or ADSL modem connections, the "DMZ" feature of your modem/router will achieve the equivalent outcome.

	==Sample multi.cfg==		==Sample multi.cfg==

Echelon9: /* Known Issues */ Reflect significant steps taken to improve WebUI standalone

2013-12-04T11:43:01Z

Known Issues: Reflect significant steps taken to improve WebUI standalone

← Older revision		Revision as of 11:43, 4 December 2013
Line 58:		Line 58:
	==Known Issues==		==Known Issues==

	This server is still in ~~alpha~~ stage. So far, the current issues still exist:		This server is still in beta stage. So far, the current issues still exist:

	*No SSL to protect your authentication password, which is why the SSH tunnel is currently recommended, as that essentially solves the issue for the time being.		*No SSL to protect your authentication password, which is why the SSH tunnel is currently recommended, as that essentially solves the issue for the time being.

Chief1983: /* Known Issues */ Removed other server name issue since I fixed it.

2013-11-19T06:50:30Z

Known Issues: Removed other server name issue since I fixed it.

← Older revision		Revision as of 06:50, 19 November 2013
Line 60:		Line 60:
	This server is still in alpha stage. So far, the current issues still exist:		This server is still in alpha stage. So far, the current issues still exist:

	*Pre-configured server names now show up on FS2NetD and in game, but saving a new server name in the WebUI does not appear to affect its display on FS2NetD yet.
	*No SSL to protect your authentication password, which is why the SSH tunnel is currently recommended, as that essentially solves the issue for the time being.		*No SSL to protect your authentication password, which is why the SSH tunnel is currently recommended, as that essentially solves the issue for the time being.
	*Servers are showing up on FS2NetD when using +use_pxo, but I have been unable to connect to the standalone using FS2NetD in game. Disabling FS2NetD and adding the standalone's IP has worked, as has finding the standalone when on the same LAN with FS2NetD turned off. This also seems to be a problem I'm having with my Windows standalone and 3.7.0 too, so it might not be a WebUI issue at all.		*Servers are showing up on FS2NetD when using +use_pxo, but I have been unable to connect to the standalone using FS2NetD in game. Disabling FS2NetD and adding the standalone's IP has worked, as has finding the standalone when on the same LAN with FS2NetD turned off. This also seems to be a problem I'm having with my Windows standalone and 3.7.0 too, so it might not be a WebUI issue at all.

Chief1983: /* Known Issues */

2013-11-18T17:22:39Z

Known Issues

← Older revision		Revision as of 17:22, 18 November 2013
Line 60:		Line 60:
	This server is still in alpha stage. So far, the current issues still exist:		This server is still in alpha stage. So far, the current issues still exist:

			*Pre-configured server names now show up on FS2NetD and in game, but saving a new server name in the WebUI does not appear to affect its display on FS2NetD yet.
	*No SSL to protect your authentication password, which is why the SSH tunnel is currently recommended, as that essentially solves the issue for the time being.		*No SSL to protect your authentication password, which is why the SSH tunnel is currently recommended, as that essentially solves the issue for the time being.
	*Servers are showing up on FS2NetD when using +use_pxo, but I have been unable to connect to the standalone using FS2NetD in game. Disabling FS2NetD and adding the standalone's IP has worked, as has finding the standalone when on the same LAN with FS2NetD turned off. This also seems to be a problem I'm having with my Windows standalone and 3.7.0 too, so it might not be a WebUI issue at all.		*Servers are showing up on FS2NetD when using +use_pxo, but I have been unable to connect to the standalone using FS2NetD in game. Disabling FS2NetD and adding the standalone's IP has worked, as has finding the standalone when on the same LAN with FS2NetD turned off. This also seems to be a problem I'm having with my Windows standalone and 3.7.0 too, so it might not be a WebUI issue at all.