blob: 79f3a35b8154d55db5eb1c9ffb6145edb829c8de (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
# Document is empty
`[error] Failed reading masterserver authentification response: encountered parse error 'The document is empty.'`
The masterserver needs to request your gameserver for it to be authentified and registered.
This error means that masterserver can't access your server's tcp port.
It can come from many reasons, but you can narrow them down by checking if your server is reacheable from the outside.
## Check if server is reachable
One can check if the server is reachable using their browser.
example : `http://{server_ip}:{server_tcp_port}/verify` should answer you `I am a northstar server!`
Your server **must** be running while you check if the port is open.
## If server is reacheable using external IP
#### Your GameServer is out of date
Check that your server is running on the latest Northstar release as it can sometimes include breaking changes.
#### Mastserver is down
Check Northstar's Discord for annoucements.
https://northstar.tf giving you a HTTP 523 error means that the masterserver is offline.
#### Ports are not the same
Your gameserver is configured to listen to a given TCP port.
Masterserver needs to be able to contact your gameserver though that same port.
#### Another Northstar Server is using the port
Shutdown every other server to narrow down the problem
This won't generally help but will allow you to avoid checking for the wrong server.
## If server is not reacheable using external IP
Check if your server is reacheable from your internal network's IP (often starts with `192.168.x.x`)
#### Firewall is blocking tcp ports
In some cases your Firewall or antivirus can prevent your ports to be exposed to your local network.
To fix this issue, make a rule to allow your server to listen on your network.
Disabling the firewall and antivirus can also work, even if it's not reccomended.
## If server is not reacheable using external IP but reacheable using internal IP
#### Router configuration is incorrect
If your port can be accessed from your local IP but not from your public IP, then it's very likely that your NAT rules aren't properly configured.
#### CGNAT
See [CGNAT](https://r2northstar.gitbook.io/r2northstar-wiki/hosting-a-server-with-northstar/prerequisites#cgnat)
## If server is not reacheable using external IP nor using internal IP
Try checking your loopback network interface `http://127.0.0.1:{server_tcp_port}/verify`
#### Another program is using the port
Sometimes another program listens to the same tcp port as Northstar.
You can check if that's the case by running `netstat -a -b` using CMD as admin
As two programs cannot listen to the same port and IP at the same time, changing the TCP listen port can sometimes solve the problem.
#### Server is using the wrong port
You can use `netstat -a -b` using CMD as admin to check which process listens on which port
|
