Glass Gaming — powered by GlassHosting
Vintage Story co-op on a listen host works until the host sleeps, updates mid-season, or sits behind residential CGNAT. Friends time out, world progress stalls, and someone always asks whether the server is up. A dedicated Vintage Story instance on GlassHosting (Glass Gaming — powered by GlassHosting) stays on in a datacenter so the group can join on their own schedule.
This guide is the main-site hub for first launch: panel start, ports, password and advertise settings, world saves, and how friends join. Deeper ticket-style how-tos live in the GlassHosting knowledgebase as articles land.
After checkout, open your Vintage Story service in panel.glasshosting.com. Note the allocated public IP and the game port shown for the service. You will share that address with friends later—do not invent a home router port forward.
New to the panel? Skim the game panel beginner guide for console, files, SFTP, and safe restarts. Background on why home hosting fails for friends: CGNAT explained and home Wi-Fi vs datacenter.
Vintage Story stores most server settings in serverconfig.json (panel File Manager or SFTP). Common day-one knobs:
false for friends-only so the world stays off the public masterserver browse list.Stop the server cleanly before editing serverconfig.json, save, then Start again so changes take effect. Treat join credentials like any other shared secret.
Vintage Story’s usual default is port 42420. Current builds expect TCP and UDP on the published game port. On GlassHosting you do not configure home router forwarding—the datacenter path already publishes the allocation. Share the panel IP and port exactly as listed.
If friends still cannot join, verify the console shows the world loaded, that they used the password you set, and that you did not paste a home LAN address. Related join walkthrough: how friends join with IP:port.
If boot fails, stop, re-check serverconfig.json (especially Port, Password, and AdvertiseServer), and start again. Avoid rapid restart loops that interrupt saves.
Friends need a matching Vintage Story client build. They join with:
Have one trusted friend smoke-test before you announce to everyone. Confirm they load into the correct world and that crafting/combat feels normal. If only some players fail, compare client versions before wiping the world.
World and config files live under the server data path. Before mods, map experiments, or major config changes:
Named backups beat “I think there was an auto copy.” Related habit: backups before mods. Panel-level file tips: SFTP workflow.
GlassHosting runs Vintage Story as always-on Glass Gaming capacity—panel control, datacenter connectivity, and backup hygiene—not a PC that sleeps after work. Order or manage plans at billing.glasshosting.com; operate day-to-day at panel.glasshosting.com.
Order a plan or browse the knowledgebase for deeper how-tos.