Guild Wars 2

Hi guys,
We are looking into this issue. If you are still affected, please send us some info that will help us debugging.
1. Your location and ISP
2. open a command prompt and run “tracert cligate-dfw.101.ncplatform.net” if you are on a NA server, run “tracert cligate-fra.101.ncplatform.net” if you are on an EU server. 3. 3. Include the output from step 2 in your reply.

Thank you!

Hi, Azu
Your error is different from what OP reported.
In any case, please attach the Gw2.log file. I think you pasted GFXSettings.gw2.exe.xml. They should be in the same folder.

If you are still having this issue. Please send us your client log. Here’s how to do it:

1. Run the Gw2 executable with the “-log” argument. The easiest way is to open a command prompt, go to your install directory, and then execute “gw2.exe -log”
2. A few seconds after you receive the connection error message, close the client.
3. Post your client log here. You can find the log at "C:\Users\<your username>\AppData\Roaming\Guild Wars 2\Gw2.log

Thanks!

It is fixed now!

Shuai Liu.5631:

Hello guys,

If you are still affected by the issue (or you are only able to patch by using one of the workarounds), we can use your help again to collect some more debug info. Here’s what I would like you to do:

1. (Optional) If you used the google DNS workaround, please reset the changes.
2. Download cURL from https://curl.haxx.se/. (cURL is a tool that can be used to test http requests. You can remove it after the test. For more info on the app, visit https://en.wikipedia.org/wiki/CURL)
3. Open a command prompt, and run
curl -i http://assetcdn.101.arenanetworks.com/latest64/101
4. Open http://d7uri8nf7uskq.cloudfront.net/JsCustomerTesting.html in your browser and run the test

When you are done, please reply to this thread with the following information
1. Your location
2. Your ISP
3. entire output from cURL (step 3 in the instructions above)
4. Your customer GUID from the CloudFront test (step 4 from the instructions above)

Once we collect enough data, we will continue the investigation with our CDN provider.

Thank you for your help!

The issue should be fixed now. If you are still affected, please run the tests above again and post the output here. We will investigate.

The problem was that the CloudFront (our CDN provider) edge nodes in St Louis were not able to communicate with our backend server. We are contacting our internet provider to get it resolved. For now, we are routing the traffic through a different provider.

Thank you again for the debug info. It provided great help to identify the issue.

Thank you all for running the tests! I will update this thread when we learn more.

Hello guys,

If you are still affected by the issue (or you are only able to patch by using one of the workarounds), we can use your help again to collect some more debug info. Here’s what I would like you to do:

1. (Optional) If you used the google DNS workaround, please reset the changes.
2. Download cURL from https://curl.haxx.se/. (cURL is a tool that can be used to test http requests. You can remove it after the test. For more info on the app, visit https://en.wikipedia.org/wiki/CURL)
3. Open a command prompt, and run
curl -i http://assetcdn.101.arenanetworks.com/latest64/101
4. Open http://d7uri8nf7uskq.cloudfront.net/JsCustomerTesting.html in your browser and run the test

When you are done, please reply to this thread with the following information
1. Your location
2. Your ISP
3. entire output from cURL (step 3 in the instructions above)
4. Your customer GUID from the CloudFront test (step 4 from the instructions above)

Once we collect enough data, we will continue the investigation with our CDN provider.

Thank you for your help!

Thank you all for sending the client logs. We believe the issue is caused by regional ISPs. There are outage reports from CenturyLink customers in the same areas. It’s likely causing network issues between our game clients and our CDN provider and possibly between the CDN edge nodes to our backend servers.

I see some players having success working around this issue by using the “-assetsrv” command argument point to a specific IP. The workaround could work temporarily. It is not recommended for the future because it connects the game client to our old CDN provider. It will be deactivated later this year.

Hi guys,

We are investigating this issue. Can you help us by sending us the client logs? Here’s how to do it:

1. Run the Gw2 executable with the “-log” argument. The easiest way is to open a command prompt, go to your install directory, and then execute “gw2.exe -log”
2. A few seconds after you receive the connection error message, close the client.
3. Post your client log here. You can find the log at "C:\Users\<your username>\AppData\Roaming\Guild Wars 2\Gw2.log

Please also let me know:
1. When does the error occur? Is it right after you start the app, before you get to the login screen?
2. Where are you located.

We will keep you posted with our progress as well.

Thank you!