Jump to content

"Could not connect to master server"


Go to solution Solved by Brady_The,

Recommended Posts

Posted
I can't access the public servers, I always get the same error from previous versions.
 
 I already uninstalled and reinstalled, checked the firewalls, reinstalled the .NET and nothing works.
 
 Has anyone had the same problem and managed to solve it?
  • Solution
Posted (edited)

Open "clientsettings.json" in %appdata%/VintageStoryData/ and check what the "masterserverUrl" is set to. It should read: "https://masterserver.vintagestory.at/api/v1/servers/". If it is set to something else, fix the line to the correct one mentioned in this post. That should do the trick.

Edited by Brady_The
  • Like 2
  • 6 months later...
  • 1 month later...
Posted
On 9/13/2024 at 3:21 AM, Brady_The said:

Open "clientsettings.json" in %appdata%/VintageStoryData/ and check what the "masterserverUrl" is set to. It should read: "https://masterserver.vintagestory.at/api/v1/servers/". If it is set to something else, fix the line to the correct one mentioned in this post. That should do the trick.

mine was correct already

  • 1 month later...
Posted (edited)

Open "clientsettings.json" in %appdata%/VintageStoryData/ and look for "webRequestTimeout". The default setting was 10 for me, I changed it to 30 and this solved the issue for me.

Edited by Lenvda
  • Like 2
  • 2 months later...
  • 1 month later...
  • 3 weeks later...
Posted

I ran into this as well and after a bit of troubleshooting managed to figure out why the issue was happening to me. By running Vintage Story from my terminal and looking at the output after trying to pull the server list, I could see that it was trying to query https://masterserver.vintagestory.at/api/v1/servers/list for the server list but was timing out after only 10 seconds. I slapped that address in a browser and managed to get a rather large JSON object containing connection details for a lot of servers but it took more than 10 seconds to download the full list. So I went ahead and increased the "webRequestTimeout" value in my clientsettings.json file to a value that would give my system enough time to download the full list and tried again with resounding success. I can't say for sure that this is the cause of the issue for everyone else here but I hope that this helps.

Also, if the devs are reading this, I think you might want to consider pagination to avoid downloading the full list of servers every time and ensure that results can be returned in a reasonable amount of time.

  • Like 1
  • Thanks 1
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.