question

oin avatar image
oin asked

playfabapi is making Vermintide 2 impossible to play

For many players it is impossible to launch the Vermintide 2. RECV_ERROR occurs at loading screen.It happens every time. Developers are currently ignoring the problem so I thought that maybe I should create a topic here. Before they added your api to the game everything was running just fine.

Excerpt from Vermintide 2 console log and additional details below:

[Lua] Curl Manager Error, Code: 0, Url: https://5107.playfabapi.com//Client/ExecuteCloudScript, Name: RECV_ERROR
[Lua] [error] = ServiceUnavailable (string)
[Lua] [errorCode] = 1123 (number)
[Lua] [code] = 0 (number)
[Lua] [status] =  (string)
[Lua] [errorMessage] = Could not deserialize response from server: RECV_ERROR (string)
[Lua] [BackendManagerPlayFab] adding error:    510 RECV_ERROR
[Lua] [BackendManagerPlayFab] Showing error dialog: "510", "RECV_ERROR"
[Lua] backend error    510 backend_err_playfab
nslookup https://5107.playfabapi.com
Server:  resolver1.ipv6-sandbox.opendns.com
Address:  2620:0:ccc::2

Non-authoritative answer:
Name:    master-ma-elasticl-relh4k6bkukz-614676218.us-west-2.elb.amazonaws.com
Addresses:  52.11.30.13
          34.214.93.85
          34.214.93.8
Aliases:  https://5107.playfabapi.com
          master.playfabapi.com
tracert 5107.playfabapi.com
Tracing route to master-ma-elasticl-relh4k6bkukz-614676218.us-west-2.elb.amazonaws.com [34.214.93.85]
over a maximum of 30 hops:

  1     3 ms     2 ms     3 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    23 ms    26 ms    22 ms  pl-ktw01a-rc1-ae18-0.aorta.net [84.116.253.129]
  4    22 ms    22 ms    38 ms  pl-waw26b-rc1-ae40-0.aorta.net [84.116.133.29]
  5    23 ms    20 ms    24 ms  pl-waw02a-ri1-ae0-0.aorta.net [84.116.138.94]
  6    23 ms    29 ms    18 ms  pni-pl-waw05a-as1299-telia.aorta.net [213.46.178.50]
  7    37 ms    38 ms    38 ms  hbg-bb4-link.telia.net [62.115.135.182]
  8    52 ms    54 ms    49 ms  ldn-bb4-link.telia.net [62.115.122.161]
  9   132 ms   217 ms   134 ms  nyk-bb4-link.telia.net [62.115.136.185]
 10   154 ms   157 ms   153 ms  chi-b21-link.telia.net [62.115.137.59]
 11   203 ms   196 ms   198 ms  sea-b2-link.telia.net [62.115.117.48]
 12   201 ms   194 ms   195 ms  sea-b1-link.telia.net [62.115.115.2]
 13   197 ms   197 ms   197 ms  amazon-ic-307564-sea-b1.c.telia.net [62.115.46.2]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17   204 ms   203 ms   203 ms  54.239.43.118
 18     *        *        *     Request timed out.
 19   220 ms   234 ms   237 ms  52.93.12.54
 20   211 ms   220 ms   203 ms  52.93.12.37
 21   271 ms   243 ms   206 ms  52.93.12.180
 22   220 ms   205 ms   208 ms  52.93.12.209
 23   205 ms   208 ms   208 ms  52.93.240.61
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.
apis
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

·
brendan avatar image
brendan answered

I'm sorry, but we're not going to be sharing details of a game we provide services for to anyone other than the developer or publisher that owns the title. If a member of their team posts here or wants to post into this thread, we're happy to answer their questions here, but we also provide private support for our Pro and Enterprise tier customers in a ticket-based system.

So as an end-user, you'll have to work with the developer or publisher for the title to get support for your questions. What I can say more broadly is that I do see a couple of disruptions to several titles due to the Steam Web API not responding to server-to-server calls at a couple of points over the last few days, and we do provide specific details of any performance issues that occur in PlayFab on our Status page (http://status.playfab.com). We unfortunately have two incidents this past week that caused brief periods of poor performance for a few API calls. It's quite possible that what you're seeing is due to one of those instances (though a timeout such as the one you have in your trace just looks like a basic internet routing issue).

6 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

oin avatar image oin commented ·

@Brendan, I don't want you to share any details. I couldn't care less about any bloody details even if I wanted to. I just want it fixed so I can play the game. And your "answer" is completely and utterly useless. You don't acknowledge the bug. You don't say it will be fixed. You don't say it won't. You don't say it may be a problem on my side and how to fix it if it is. You write a wall of text with literally zero information anyone can use. It is improbable that this is due to one of you two "incidents" because you supposedly resolved them and the problem still occurs. And if it is a routing issue then who is at fault and should fix it?

1 Like 1 ·
brendan avatar image brendan oin commented ·

My apologies for not being more clear. 100% of all incidents that cause issues for titles in PlayFab are taken extremely seriously. We have monitoring on all services and anytime there's an issue, we have a realtime alerting system that calls our on-call engineers and lets them know. So immediately after any incident starts, someone is looking into it, and working towards a fix.

What I was highlighting was that we cannot support end users of games, as a) we don't have bandwidth, and b) it's not possible for us to debug the games, as we don't have the game code. There are multiple ways the issue you've described could occur. If there are no current issues in the service and the game isn't working for you, they'll be best positioned to help you out.

As to the routing, it depends. Sometimes, that'll be due to a fault at a major internet node. Another example would be the recent blocking of parts of AWS by the Russian government, preventing users in that country from being able to use many services in AWS.

-1 Like -1 ·
oin avatar image oin brendan commented ·

@Brendan, once again, wall of text, zero useful information, ignoring literally everything I wrote.

  1. Your monitoring won't tell you anything because I can't connect to your servers. There will be no incidents reported because I can't reach the servers. No incident, nothing to fix, right? Really nice approach you got there.
  2. The game is very unlikely at fault. It's not the game that's crashing, it's your servers that are unreachable. The game was working just fine before devs added your stupid API. What's likely at fault is your infrastructure, your servers, your constantly changing dynamic IP addresses and whatnot. Fix your DNS, your network settings or whatever and make your servers visible for everyone. Or at least make a little bloody effort of investigating this and for once in your life write something useful, a definite answer, not diplomatic bullshit. I'm not from Russia, by the way. It's Poland.
1 Like 1 ·
Show more comments

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.