{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by SesePlus+:
3/20/2022 12:08:05 AM
8
Constantly contacting destiny 2 servers
So I've been hoping that my network problems were just because of my internet, but I've had the same problem for a few days now, so I'm pretty sure it's not my internet anymore. Got the baboon error a few times and tried nearly everything in the help forums already, but nothing's helped so far. Anyone know anything else I can do?
Edit 1: After getting the baboon error once or twice and reconnecting to the server, it would kick me out completely with the error bat popping up. Friend of mine are both having the same issue and we're both n the westcoast.
-
Edited by Mowbray: 3/31/2022 4:11:59 AMYep, I've been seeing this since Preservation came out. I've updated firmware on my router, tweaked settings on my wireless cards, messed with Steam networking stuff - its getting progressively worse. I'm in Wisconsin, US, so not west coast or CA, but its possible my internet may feed through a common provider somewhere. Its infuriating. No other game has these issues. Its almost 100% certain that its a configuration issue on Bungies side. EDIT: Pulled the Server Log from my Dream Machine router after this happened most recently. I'm not a network engineer, but these are the last three lines on my log. [2022-03-30T22:25:31,217] <webapi-79> WARN sanitize - Invalid key exists in Setting payload, key=chatEnabled [2022-03-30T22:25:31,217] <webapi-79> WARN sanitize - Invalid key exists in Setting payload, key=chatAdminsEnabled [2022-03-30T22:39:35,596] <webapi-84> WARN api - websocket session error:Connection reset by peer
