Sign In Register

How can we help you today?

Start a new topic

Steam - partner.steam-api.com:443 failed to respond

Hi,


Moving an issue from the ticketing system to the Forums as I have been informed to do so. For the sake of clarity I will copy paste the already existing ticket information to this post.


Reported Thu, 28 Mar, 2019 at 09:52 am


Good morning,

We have been experiencing random issues regarding the connectivity of the players with Steam. These connectivity issues seem to be related with a "443 (failed to response)" issue being received when attempting random api calls (we understand that all of them are related to transactions), these are some of the responses received (and tracked) in the ScriptLog:


{"message":"Error performing POST for the URL https://partner.steam-api.com/ISteamMicroTxn/InitTxn/v3/:partner.steam-api.com:443 failed to respond"}

{"message":"Error performing POST for the URL https://partner.steam-api.com/ISteamMicroTxn/FinalizeTxn/v2/:partner.steam-api.com:443 failed to respond"}

 

After googling a bit we found two potential links that may contain information relevant to this case, in both cases the links are from Gamesparks clients experiencing the very same issue, these are the links:

 

https://steamcommunity.com/groups/steamworks/discussions/0/2381701715730857649/?tscn=1553755547

https://support.gamesparks.net/support/discussions/topics/1000085926?page=1


The first link would be (for us) key, since it's a customer that had the same issue and you guys actually got it fixed for you.

I appreciate your help beforehand,

Regards,


Customer Support

said 24 days ago


Hi Christian,

Is this error popping up when you are using SparkHTTP or our system Steam requests ?

Regards,




Christian G.

said 24 days ago


The calls that are generating those errors are the following:

//Build the data

var dataStr = "orderid=" + orderid + "&key=" + SteamApiKey + "&steamid=" + steamid + "&appid=" + SteamAppId + "&itemcount=1&language=EN&itemid[0]=" + itemid + "&qty[0]=1&amount[0]=" + price + "&description[0]=" + product["description"] + currencyChunk;

//Init txn

var respPurchaseStr = Spark.getHttp("https://partner.steam-api.com/ISteamMicroTxn/InitTxn/v3/").setHeaders({"Content-Type": "application/x-www-form-urlencoded"}).postString(dataStr);

//Build the data

var dataStr = "orderid=" + orderid + "&key=" + SteamApiKey + "&appid=" + SteamAppId;

//Finalize txn

var respFinalizePurchaseStr = Spark.getHttp("https://partner.steam-api.com/ISteamMicroTxn/FinalizeTxn/v2/").setHeaders({"Content-Type": "application/x-www-form-urlencoded"}).postString(dataStr);

I can provide the dataStr fully disclosed if you need to.

Thanks,




Customer Support

said 24 days ago


Hi Christian,

Are you trying to initialize and finalize a purchase in the same script ? 

Regards




Christian G.

said 24 days ago


Uhmm, I'm not entirely sure about what you mean? If you mean if those lines of code are located in the same script yes (it's called SteamUtils). If you mean if those calls are called right away one after the another no, we are not doing that, I just thought you needed to know the calls we were using, those are just chunks of the purchase process on Steam. We first init the transaction, as soon as everything's ok and Steam has replied (and the Steam Native In-App popup has prompted) we finalize it.

Christian G.

said 11 days ago

Hi, I'd like to know if there's been any progress here. We are still getting these often. Also, from time to time the error code is 500 instead of 443.

Thanks,




Christian G.

said 8 days ago

This particular player (5c72f9a1724f110523a01f74) also wrote a ticket today because he's been trying to purchase a product and he hasn't able to because he always get an error (I've checked the logs, and it's indeed the same one, the error ending in 443). 

Please help,


Hi, we just setup our integration with Steam API and it seems no problem for us. However, the difference is, instead of using SparkHttp.postString(), we used SparkHttp.postForm(). Maybe you guys can try that and see if you get a differenet result.

Hi Sida, thanks for replying. We actually did try out that option (since it was once suggested by the support guys on GS), we didn't notice any difference, it was also randomly failing. Must be something else.

I thought they fixed this bug -- I reported this roughly 6 months ago and it was fixed on my side, but seems like it was only manually fixed instead of universally fixed:


GS was using the PUBLIC api, by accident, instead of the private API: This means you're getting rate-limited by Steam and they don't handle their response well.


GS would need to fix their Steam API call param to ensure they're calling to your private dev API uri with your secret key and such, instead of the public API. 


I'm happy they fixed it for me a while back, but a bit surprised they didn't fix it for all.


1 person likes this

@ staff: Check out my ticket history and search for Steam -- you'll find the answer within.

Hi Dylan, thank you for chiming in! I definitely think that's the issue here, since I also asked on SteamWorks Dev's official forums and some guy also told me he had the same issue with the Public / private API. Just one question now that I have the chance, this 443 failed response is only received sometimes, meaning that some players indeed have been (and are) able to properly purchase items, was that the case for you guys as well?


Also, not sure if GS staff look at this forums at all so I'm starting to think that my possibilities of getting this fixed are small.

Login to post a comment