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.
-
This has been happening to me since mid March update. Never had issues before. I've tried every suggestion on YouTube. I've replaced my modem. I've tried multiple router configs. The issue persists and other games work just fine. Connection tests good. NAT is open. Has to be something broken from the update. It is becoming a real problem as I get kicked from GMs and raids. I'm on Xbox. MN, USA.
-
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
-
It's mostly not an internet issue on our part. I've been in a full party where we all received that "contacting Destiny 2 servers." All 6 of us from different locations getting the same message at the same time is not an individual internet connection issue. This connecting has been an issue since Forsaken.
-
Been having the exact same problem, started a few days ago, have done every trouble shooting g thing and can confirm 100% it’s not my connection. I hope bungie responds to this eventually, it’s frustrating having a constantly laggy game and baboon errors
-
A LOT of people are having the same problem. Started happening a few days ago. Never ever have I had a problem with connections issues. I'm in Canada, West Coast with Telus Fibre (Gigabit) internet. No issues on my side whatsoever, no packet loss or anything. I know its not just my problem, because its happening to my entire clan (who is also all West-Coast based). Same exact problem as you. Launch the game and choose a character, and immediately after get the "Contacting Destiny 2 Servers". And then when in activities I would get the error code "Baboon". And it would temporarily kick me out of whatever activity, then reconnect me back in. On PC with STEAM, and again multiple people having the same problem. There is another thread here: https://www.bungie.net/en/Forums/Post/260785848?sort=0&page=0 Maybe post/upvote in that forum, so it gets Bungies attention hopefully.
-
Spread awareness of this issue as wide as you can. Not every Destiny player will come to these forums. Respond to this reddit thread as well! https://www.reddit.com/r/DestinyTheGame/comments/tka9vj/destiny_2_is_borderline_unplayable_for_many_in/
-
Edited by B0Y GEN1US: 3/22/2022 2:22:05 AMYeah you are not alone in this issue. I am from Vancouver and I am having the same issue. I am not on fiber BUT I am with Telus. I tried to see if I could find the issue but I keep getting stuck. I managed to find the IP address of the server I was connecting to via resource monitor and found that I was connecting to Bellevue Washington with 120-150 ping which would normally be no more than 20-30 ping. I tried to ping the server through command prompt and through my Modem and both timed out with 100% packet loss. It could be possible that this might also be a Telus issue as most users with this same issue seem to be with Telus. Might be something to do with UPnP port and how Telus handles traffic on that port. Or it could be a Destiny/Bugnie issue. If it is a Bungie issue then its most likely something to do with servers on the west coast. Unfortunately I do believe that this issue is out of our hands as there is nothing that we can do. Just need to hope that Bungie see's this and fixes it.
-
The "Contacting Destiny 2 Servers" message indicates that there is a connection issue of some kind happening between you and Destiny 2. This may be an internet service provider issue. Here are some steps you can take to try and resolve the issue: [quote] [b]1.[/b] A wired connection is recommended to play Destiny, and if your connection is being used for other things when playing the game, such as streaming, it's recommended to quit those programs. [b]2.[/b] [url=https://www.bungie.net/en/Help/Article/12539]Clearing your console cache[/url] or, if on PC, [url=https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335]verify the integrity of your game files[/url]. [b]3.[/b] Power cycling your internet router [b]4.[/b] Review our guide on [url=https://www.bungie.net/en/Help/Troubleshoot?oid=13603]improving latency and packet loss[/url] to see if that might help [b]5.[/b] Following our [url=https://www.bungie.net/en/Support/Troubleshoot?oid=12915]Network Troubleshooting Guide[/url] for best optimizing your connection to Destiny. If issues persist, try our [url=http://www.bungie.net/en/Help/Troubleshoot?oid=13610]Advanced Steps Networking Guide[/url] for possible router solutions, such as enabling UPnP. You may also want to enable IPV6 on your router if you have it. [b]6.[/b] [url=https://www.bungie.net/en/Forums/Post/253755591]This player found a solution that involves installing new network driver[/url] [b]7.[/b] You may want to change your DNS server on your console to Google's Nameservers (8.8.8.8. and 8.8.4.4.) [b]8.[/b] Contact your internet service provider to see if there are any issues with your connection. [/quote]