You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TL;DR: Most likely port forwarding not set up correctly or limited by ISP, check instructions on the wiki.
Trying to host a gameserver one might see the following log entry:
[19:41:37] [NORTHSTAR] [errr] Failed reading masterserver authentication response: encountered parse error "Invalid value."
[19:41:37] [NORTHSTAR] [errr] Reached max ms server registration attempts
The reason behind this is that if Atlas cannot reach the gameserver that is trying to host it will send back a 5XX HTTP error response with appropriate error information in a JSON file.
For some reason, Cloudflare, the CDN we use for DDoS protection and caching, modifies this response on travel to add its own information to it.
This results in the client not being able to parse the resulting response and showing the unhelpful Invalid value message instead.
To fix this, we need to figure out why Cloudflare is modifying the response and prevent it from doing so.
(There's probably a setting for this in the dashboard somewhere)
The text was updated successfully, but these errors were encountered:
TL;DR: Most likely port forwarding not set up correctly or limited by ISP, check instructions on the wiki.
Trying to host a gameserver one might see the following log entry:
The reason behind this is that if Atlas cannot reach the gameserver that is trying to host it will send back a 5XX HTTP error response with appropriate error information in a JSON file.
For some reason, Cloudflare, the CDN we use for DDoS protection and caching, modifies this response on travel to add its own information to it.
This results in the client not being able to parse the resulting response and showing the unhelpful
Invalid value
message instead.To fix this, we need to figure out why Cloudflare is modifying the response and prevent it from doing so.
(There's probably a setting for this in the dashboard somewhere)
The text was updated successfully, but these errors were encountered: