Im getting this same error. Followed Bungie's Weasel code troubleshooting guide and im still getting the weasel code. The other 2 players i was playing with are still live and not having any issues.
Playing on PC and am not using a VPM. Internet connection is strong and fast, and not over wifi. Files seem uncorrupted and functioning properly though i still cannot connect to the servers.
I got kicked out of a match and was not able to get beyond the start-up screen and I tried for a good hour or so. I do have a VPN on my system, but it was disconnected at the time of the error. I restarted, verified file integrity in steam, confirmed my VPN was off after the restart since it's set to auto-launch on login, and still doesn't work as of 60 seconds ago. I've also been running a VPN on this system since well before Marathon came out and all through season 1 without issue. I play Over Ethernet, every other service works perfectly fine, other games work fine. It's only Marathon that's screwed up.
For what it's worth, the people I had been playing with were both on the East coast while I am on the West coast of the United States. They seemed entirely unaffected by this issue, the same goes for the other folks on the East Coast I play with. The couple of West Coast people all seem to have been kicked out, too, so the problem may be regional.
This is really frustrating. I'm just trying to play season 2 and there's been instabilities since the start of the season. Yesterday was the best day and I still had random connection issues on occasion.
I also had this issue tonight. Between rounds I started getting Weasel codes, but my friends in my party did not. Resetting my router, restarting my PC, clearing Steam cache didn't help.
Useless canned Bungie response is useless. The info provided doesn't help or fix anything. the MarathonStatus.com website had a major outage for Marathon for over 2 hours last night.
This error code shouldn't just be cropping up without any changes to the player's network setup or their service provider, especially when the game was working perfectly fine moments beforehand. Considering there was a major outage reported in the time frame that most of us posted, there is something that causes the weasel error to trigger that is not related to your internet, network configuration or your service provider. Whether Bungie knows what that is or not is another question, but a massive amount of players all getting a 'weasel' error at the same time just shouldn't be a wide scale problem. That error sounds like it should be reserved for local network/configuration problems or an issue with the service provider.
Maybe we are all running through the same ISP, but I also wouldn't bet on it, or were all routing through some network backbone that was having a problem last night, but again, all other services and games I tested during this time worked perfectly fine, speed tests and route traces were all clean.
I realize this is likely an issue that we couldn't fix, but having a canned response that is actually useful or informative might be better than getting a response like "It's your fault, your internet, computer, or network is screwed up..." When it's very clear that at least a few of us have done enough work to show that, that's almost certainly not the case.
Comentarios
Hi there,
Thanks for reaching out.
Error code: WEASEL typically signifies you’re encountering a broad networking problem. We recommend you refer to our Network Troubleshooting Guide to explore potential solutions to your problem. We also have an Advanced Troubleshooting Guide, if the Network Troubleshooting Guide did not help.
Im getting this same error. Followed Bungie's Weasel code troubleshooting guide and im still getting the weasel code. The other 2 players i was playing with are still live and not having any issues.
Playing on PC and am not using a VPM. Internet connection is strong and fast, and not over wifi. Files seem uncorrupted and functioning properly though i still cannot connect to the servers.
I got kicked out of a match and was not able to get beyond the start-up screen and I tried for a good hour or so. I do have a VPN on my system, but it was disconnected at the time of the error. I restarted, verified file integrity in steam, confirmed my VPN was off after the restart since it's set to auto-launch on login, and still doesn't work as of 60 seconds ago. I've also been running a VPN on this system since well before Marathon came out and all through season 1 without issue. I play Over Ethernet, every other service works perfectly fine, other games work fine. It's only Marathon that's screwed up.
For what it's worth, the people I had been playing with were both on the East coast while I am on the West coast of the United States. They seemed entirely unaffected by this issue, the same goes for the other folks on the East Coast I play with. The couple of West Coast people all seem to have been kicked out, too, so the problem may be regional.
This is really frustrating. I'm just trying to play season 2 and there's been instabilities since the start of the season. Yesterday was the best day and I still had random connection issues on occasion.
I also had this issue tonight. Between rounds I started getting Weasel codes, but my friends in my party did not. Resetting my router, restarting my PC, clearing Steam cache didn't help.
Useless canned Bungie response is useless. The info provided doesn't help or fix anything. the MarathonStatus.com website had a major outage for Marathon for over 2 hours last night.
This error code shouldn't just be cropping up without any changes to the player's network setup or their service provider, especially when the game was working perfectly fine moments beforehand. Considering there was a major outage reported in the time frame that most of us posted, there is something that causes the weasel error to trigger that is not related to your internet, network configuration or your service provider. Whether Bungie knows what that is or not is another question, but a massive amount of players all getting a 'weasel' error at the same time just shouldn't be a wide scale problem. That error sounds like it should be reserved for local network/configuration problems or an issue with the service provider.
Maybe we are all running through the same ISP, but I also wouldn't bet on it, or were all routing through some network backbone that was having a problem last night, but again, all other services and games I tested during this time worked perfectly fine, speed tests and route traces were all clean.
I realize this is likely an issue that we couldn't fix, but having a canned response that is actually useful or informative might be better than getting a response like "It's your fault, your internet, computer, or network is screwed up..." When it's very clear that at least a few of us have done enough work to show that, that's almost certainly not the case.
Iniciar sesión para dejar un comentario.