pg9182
pg9182
No issues for the last month after switching to Atlas.
This is one reason I'm proposing (and working on) a relocatable launcher.
cc @L1ghtman2k
#448 possibly related
Starting and then leaving a listen server on an account without persistence can break authentication
> you will get the following error when you try to go back into the lobby What's the API error in the logs?
Starting and then leaving a listen server on an account without persistence can break authentication
> the mainmenupromos no longer load at all, and the issue persists? That makes me think it's at least partly a launcher issue.
Starting and then leaving a listen server on an account without persistence can break authentication
> This could be something to do with how ive got my local MS set up You should just be able to do a `go run ./cmd/atlas`, and set the...
Starting and then leaving a listen server on an account without persistence can break authentication
This issue is caused by a port conflict. I've updated the default atlas port to 8080 instead of 8081, so it should work fine now.
Starting and then leaving a listen server on an account without persistence can break authentication
We also need to handle HTTP errors properly instead of passing empty buffers to rapidjson on error.
I will be doing this as part of APIv1, which is also when we'll be changing the hostname.