Mtg arena network error

How to Fix MTG Arena Network Error

Get back into the game!

MTG Arena is one of the most popular online trading card games of all time. Players spend many hours building the best decks to absolutely annihilate the competition. So, it can be pretty frustrating if you happen to run into a network error while you’re playing or trying to log in. If you’re having an issue with the network or connecting to a server, the following fixes might be your ticket back into the game. Please note, we are not responsible for any issues that may occur during this process while following any of these steps.

1. Check your router and ensure that it is working.
   • You can try to reset your router if it is not working by turning it off for a short period of time before turning it back on.
2. Close the game and then relaunch it.
3. Temporarily disableyour firewalls or add exceptions for MTG Arena.
   • Open Control Panel.
   • Select System and Security.
   • Select Windows Firewall.
   • Turn the firewall on or off.
4. Check out if there are any reported issues with the game at that moment.
5. Try to connect to another network if possible to see if the issue persists.
6. Perform a flush of your DNS cache.
   • Close the MTG Arena client.
   • Launch the Command Prompt app by pressing the Windows + R and typing cmd.exe.
   • In the command prompt, type in ipconfig /flushdns and hit Enter.
   • Next, type ipconfig /registerdns and click Enter.
   • Next, type in ipconfig /release and press Enter.
   • Lastly, type ipconfig /renew and hit Enter.
   • The last thing you’ll need to do is type in netsh winsock reset and press Enter.
   • You’ll then want to reset your PC before relaunching the game.

Feel free to leave a comment if you find another way that works for you different from any of the above. If none of them worked for you, then we would recommend reaching out to the MTG Arena support team and submitting a request.

For more MTG Arena, check out Best Starter Decks in MTG Arena and Is MTG Arena Down? How to check MTG Arena Server Status only on Pro Game Guides.

How to Fix MTG Arena Network Error

Cancel reply

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Источник

Magic The Gathering (MTG) Arena: How To Fix Network Errors In-Game?

Are you facing network issues in Magic The Gather (MTG) Arena? Follow this guide to get fixes for your network issues!

Players in Magic The Gathering (MTG) Arena are in dire need of a fix to the various network errors that keep arising in-game. These network errors have been frequently brought up by the community, especially in the last few months. To assist you in fixing these errors, we’ve created this guide. Follow all the steps mentioned below for a quick and easy fix to all the network errors in Magic The Gathering (MTG) Arena.

How To Fix Network Errors in Magic The Gathering (MTG) Arena?

These steps should help you in getting a fix to the network errors in MTG Arena:

1. Check your internet connection and see if it’s working by performing a search in your browser.
2. Close your game and relaunch it to see if it is working.
3. Ensure your internet access provision device like your Wi-Fi router, modem, or portable hotspot is functioning, or else simply restart it.
4. Check to see if any antivirus is blocking your server access by temporarily disabling it.
5. Similarly, temporarily disable your firewall and check if your game works without the network error.
6. Alternatively, try connecting to another network and see if the issue persists.
7. In addition to the network checks, you can check out the server status of Magic The Gathering(MTG) Arena.
8. Whitelist MTG Arena on the software that might be blocking access to it (windows defender for example).
9. In addition to switching networks, consider using a VPN and see if it solves the issue.
10. Furthermore, you can perform a flush on your DNS cache as well as carry out a Winsock reset. To do this:
    • End the MTG Arena client.
    • Launch the Windows command prompt as administrator.
    • You simply need to hold Windows+R and in the resultant text space enter cmd.exe.
    • In the command prompt, enter ipconfig /flushdns and hit enter.
    • Similarly, enter ipconfig /registerdns and click enter.
    • Now type in ipconfig /release and press enter.
    • Finally, input ipconfig /renew and hit enter.
    • In order to get it all done, type netsh winsock reset and press enter.
    • Now restart your pc.
    • Launch the Magic The Gathering (MTG) Arena client.
    • Additionally, if none of these fixes helped, consider reaching out to MTG Arena support.

Your fixed Magic The Gathering(MTG) Arena client should now launch smoothly without network errors. We hope this guide helped you and fixed your network error issues! If you still continue to face problems in MTG Arena, here is a guide to Fix MTG Arena Not Working.

Источник

Investigating and Mitigating MTG: Arena Network Errors

While I was in the process of gathering packet captures for this write-up on 07/03/20 Arena decided to be extremely stable network wise for me. This may mean they fixed the stability issues which is awesome. The packet capture snippets I’ll be posting are from when I did get timeouts on 07/01/20.

If you’re just interested in the mitigation and not the investigation scroll down to the last section.

I’m sure every single MTG: Arena player has experienced this at least once. You’re playing a match (or drafting, or building a sealed deck, etc) and all of a sudden you can’t click on anything. Then it happens.

You scramble to gather a log, maybe check your internet connection and restart the client before you time out and lose the match. Sometimes you’re quick enough, sometimes you’re not. You go and look at MTG Arena bug reporting page and find that this sort of thing is extremely common.

After this happened to me multiple times in one play session I decided to dig into it a little bit more and maybe find a way to mitigate the problem.

The most obvious place to look would be the log files. If you happen to have saved a log from the client those live here:

Otherwise the running log files live here (yes it’s actually LogsLogs):

If you’ve ever looked at an MTG: Arena log file you’ve probably noticed that they’re pretty hard to read.

The logs are a mixture of plain text and JSON so I opened it up in Atom and turned on JSON syntax highlighting to make it slightly easier to parse by eye. Any text editor that supports language highlighting will do the trick.

Much better. It’s still a pretty big log file but at least I can pick out the JSON blocks and hopefully find the sections that pertain to the disconnects. Since I grabbed the log right after a disconnect the relevant sections are at the bottom.

Here’s the first one:

That’s still pretty hard to read so I did some magic. By magic I mean copied the JSON section into another document and ran it through jq . Here’s the first snippet of that. The stack trace section is still pretty hard to read but we’re not trying to debug the program itself so I’m going to ignore that.

Time to pull out the relevant sections and take a look at them. The first section of the error message tells us pretty succinctly what happened. There was an error reading the SSL stream and the remote host closed the connection.

Key word here is remote which points to issues on the server end and not on the local end.

Then skipping over the stack trace we find the MTG: Arena server I was connected to and the port it uses. This will come in handy as we can search through the log file for that. The host that shows up in your log file may be different.

Searching through the log file for magic-the-gathering-arena.com lets us find the related log entries. Most of them are related to the disconnects but there are a couple that are not.

From this we can surmise that there are two servers:

It looks like one is for the game as a whole and the other is match specific. When you start the game you connect to the arenagame endpoint and when you start a match you appear to connect to the arenamatch endpoint.

In this case a bunch of TCP and SSL related errors started happening on the arenamatch endpoint and it ended with me getting disconnected from the game. This is about all we can do with the log files but it did give us enough information to move onto the next step of investigation: playing a bunch of matches with Wireshark open.

Before we get to that we need to get a little more info on the MTG: Arena servers so we know what to look for in Wireshark. A few minutes using nslookup and we have our answer.

If there are b servers then there also must be a servers so I checked those too.

So there are a total of four servers that we could connect to all of which are living in the East US 2 region of Azure. Remember this, it’ll be important later.

Now that we have some IPs we can boot up Wireshark and MTG: Arena and hope we get disconnected while Wireshark is running. The safe way to do this would probably be to play against bots but where’s the fun in that?

The process for gathering packet captures for this issue was pretty simple. I played MTG: Arena with Wireshark open and waited until I got disconnected. As I mentioned at the beginning of this article I did manage to capture a disconnect on 07/01/20 but when I tried to replicate the behavior for fresh data on 07/03/20 I didn’t get disconnected.

When going through the packet capture I found that a pattern started to emerge. It would start with a series of three TCP Retransmission errors from my local machine to the server, two packets of normal communication and then a series of TCP Spurious Retransmission, TCP DUP ACK and TCP Retransmission errors between my local machine and the server. Finally after a certain time period (anywhere from 3–4 seconds to 8–10 seconds) it would resolve itself.

Without going too deep into the TCP Protocol basically these errors mean there was some sort of network packet loss going on and my machine and the MTGA server were trying to rectify it. As this article mentions a small number of these errors may be considered normal.

However it appears that if the time delta between the start of the errors and the end of the errors reached a certain threshold I would get a Network Error and have to restart the MTGA client to reconnect.

After looking at a number of these “fights” my computer and the Arena server had I found that if time delta between the start and the end of the errors reached a certain threshold I would get a Network Error and have to restart the MTGA client to reconnect.

Most of the errors (like the one above) cleared themselves up within 3–4 seconds and if they happened on my opponent’s turn I didn’t even notice any lag. However if the errors lasted between 8–10 seconds (see below) before they recovered I got the dreaded Network Error message.

I also found that the errors affect both the arenagame and arenamatch servers at around the the same time though only the arenamatch server errors get put into the log.

It doesn’t appear to put anything in the log if you don’t actually get disconnected. I found this out after I had the client freeze on me and a bunch of errors spawned in Wireshark but I didn’t get kicked off and the client unfroze.

Basically this is a lot of words to say that these TCP Retranmission errors happen every so often but if they last longer than

10 seconds you’re probably going to get kicked off.

Update 07/07/20: I am no longer able to connect to MTG: Arena while I’m behind the VPN. Not sure exactly what changed between last week and today but I hope the network stability issues are fixed so I don’t need to rely on the VPN.

Now that I had a hypothesis about why I was getting Network Disconnect errors I wanted to figure out if I could mitigate it somehow. Since the MTGA servers are hosted in Azure I decided to spin up an OpenVPN server in Azure in the same region.

I wrote up a guide for getting the server up and running. You can find that below along with the Azure Quickstart Template for it.

Источник

Как исправить MTG: Ошибка сети Arena

Magic: The Gathering Arena — это коллекционная карточная игра, которая позволяет игрокам открывать свою стратегию, исследовать цифровую мультивселенную, встречаться с planeswalker-ами и сражаться с друзьями по всему миру. Игроки также могут собирать, создавать и улучшать свою уникальную колоду, которая впоследствии станет их собственной легендой.

Это одна из самых популярных карточных онлайн-игр, когда-либо выпущенных. Игрокам придется потратить десятки часов на создание лучших колод, чтобы уничтожить конкурентов в цифровой мультивселенной, сражаясь на потрясающих полях сражений и наслаждаясь играми Arena of Battle Эффектs. Итак, в этой статье мы расскажем вам, как исправить MTG: Arena Network Error.

Как исправить сетевую ошибку MTG: Arena

Скорее всего, вы потратите часы на сбор своей колоды в этой игре, и если вы приложите столько усилий, то потом получите сетевую ошибку , это просто расстраивает. Так что, если это так, мы составили список исправлений, которые могут помочь вам решить проблему с сетевой ошибкой в ​​Magic: The Gathering Arena.

Первое, что вы должны попробовать, это проверить свой интернет-маршрутизатор и убедиться, что он работает нормально. Если вы заметили что-то странное, вы можете попробовать перезагрузить маршрутизатор, если он не работает, выключив его и снова включив через пару минут. Затем закройте игру и попробуйте сыграть еще раз.

Еще один шаг — отключить брандмауэры в настройках ПК с Windows. Вы можете сделать это, открыв панель управления, затем выбрав «Система и безопасность», найдя «Брандмауэр Windows» и отключив брандмауэр.

Если это не сработает, вы также можете попробовать подключиться к другой сети, которая полностью отличается от вашей, и посмотреть, решит ли это проблему. И, наконец, обязательно проверьте, не сообщали ли другие игроки о каких-либо проблемах с этой ошибкой. Если она была, то вы не единственный, кто столкнулся с сетевой ошибкой, и есть вероятность, что разработчики знают об этом и работают над ее исправлением.

Поэтому обязательно следите за официальными социальными каналами игры всякий раз, когда публикуется обновление. Вы также можете обратиться в службу поддержки MTG Arena и отправить собственный запрос.

Источник