server:hosting
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
server:hosting [2016/04/18 21:32] saru Added a section on where account and player data is stored so that server hosts can archive it |
server:hosting [2018/03/03 15:47] karl [Requirements] Change Port "13327" to "13227" and "13326" to "13226" |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| * Connections issues can occur within the Crossfire client if the domain name is not full qualified. | * Connections issues can occur within the Crossfire client if the domain name is not full qualified. | ||
| - Network security to allow remote connections and communication to the metaserver (if a public server). | - Network security to allow remote connections and communication to the metaserver (if a public server). | ||
| - | * The server runs on port 13327 | + | * The server runs (by default) on port 13227 |
| * if you have a firewall, it will need to allow that port for incoming connections, | * if you have a firewall, it will need to allow that port for incoming connections, | ||
| - | * if you are running NAT, you will need to make sure that the connection to port 13327 gets routed to the correct server. | + | * if you are running NAT, you will need to make sure that the connection to port 13227 gets routed to the correct server. |
| - | * The metaserver runs on port 13326 and 80 (HTTP) | + | * The metaserver runs (by default) on port 13226 and 80 (HTTP) |
| - | * if you have a firewall, it will need to allow 13326 and 80 for incoming connections, | + | * if you have a firewall, it will need to allow 13226 and 80 for incoming connections, |
| - | * if you are running NAT, you will need to make sure that the connection to port 13326 gets routed to the correct server. | + | * if you are running NAT, you will need to make sure that the connection to port 13226 gets routed to the correct server. |
| * For metaserver2 updates, it is an outgoing connection to standard HTTP port (80), so very few firewalls should block it. | * For metaserver2 updates, it is an outgoing connection to standard HTTP port (80), so very few firewalls should block it. | ||
server/hosting.txt · Last modified: 2024/05/20 16:24 by leaf
Page Tools
