Game Server inaccesable
Posted by charlie
Hey, i cannot seem to be able to access the game server from immediate setup i kept getting a timed out error i checked the config.json and the ip was set to 127.0.0.1:8443 (which is the sparkbox address) but supposedly re routes to 8447 somehow ive tried changing it to 0.0.0.0:8443 to make it accessible outside of its own container but does nothing tom ai seems to think its not something i can fix so i thought id send it in. --------------------------------------------------------------------------------------------------------------- My question: yeah but how do i fix this SparkBox AI replied: Honest answer: you probably can't fully fix this one from your end — not because you're doing anything wrong, but because the two real problems are baked into how the games module packages Crafty, and one of them (config getting overwritten on every boot) means even a correct manual edit won't hold. Here's what's actually happening and why user-side fixes keep failing: 1. Bind stuck on 127.0.0.1 — you already tried the right fix (edit baseurl/bind to 0.0.0.0), but the log shows Checking for remote changes to config.json on every start — meaning something is re-pulling/overwriting that file at boot, wiping your edit before Crafty even starts listening. That's why the restart came back identical. 2. Container can't resolve DNS (no connection to the internet, can't resolve its own hostname) — that's not a config value you edit in a JSON file, that's the container's network setup, which lives in the games module's compose file, not something you touch by hand safely. Things you could try that are still within your control, no guarantees: - Check if there's a .env var for Crafty's bind/host in /opt/sparkbox/.env (something like CRAFTYHOST or similar) — if the module supports overriding it via env instead of the config file, that survives the config-overwrite step. I don't have a confirmed variable name for this though — I don't want to hand you a guess that does nothing. - Conf …(reply truncated — full chat sent to Tom)
1 replies
Chris wrote:
Hey charlie -- sorry this one's giving you grief, and you're right that this isn't something you did wrong. Game Servers is a very new module (it only shipped a few days ago), and what you're describing -- your edit to the server address not holding, plus the container losing its network -- points at something in how the module's own setup behaves, not a setting you can fix by hand. I don't want to hand you a guess that might not work, so I've flagged this for Tom's team to actually dig into it. Sorry for the extra hassle in the meantime.