Error Bad Gateway (and others) most of time since this morning

[Pierre Augereau]

Good afternoon,

Since this morning (May 7th 2015), I have got many errors : 

- "Bad Gateway"

- "Failed to load response into DOM: DOMDocument::loadXML(): Empty string supplied as input in **************/Google/src/Google/Api/Ads/Common/Lib/AdsSoapClient.php on line 268"

- "[WSDL] SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201502/AdGroupCriterionService?wsdl' : failed to load external entity "https://adwords.google.com/api/adwords/cm/v201502/AdGroupCriterionService?wsdl"

 in **************/Google/src/Google/Api/Ads/Common/Lib/AdsSoapClient.php:172"

- Uncaught exception 'ReportDownloadException' with message 'Report download failed.' in **************/Google/src/Google/Api/Ads/AdWords/Util/ReportUtils.php:211

I'm currently using the PHP librairy v201502.

I already have asked to my network administrators if there were any update on the network. All requests sent through the API are correctly transmitted

Moreover, I did not have updated any source code from those past few days

It seems to that most of request to get data from Adwords accounts have this problem...

However, some requests to put data (such as new amount on a spécific key words) works fine 2/3 call

So, I really do not understand what is happening since this morning

Best regards.

[Nadine Sundquist (AdWords API Team)]

Hello Pierre,

Check out this post to see if the solutions provided there will fix you problem.

Thanks,

Nadine, AdWords API Team

[Pierre Augereau]

Good morning Nadine !!!

Thank you a lot for your answer.

I did not have try those solutions from the post because, every thing seems to work fine again this morning o_O 

But, I will keep this post preciously !!

My network administrator has found out that Google has changed some DNS... Maybe, that was the cause of "Bad gateway error" and others.

I will come back if this problem happen again.

One more time, Thank you a lot,

Have good day,

Best regards.

[Pierre Augereau]

Good morning Nadine and everyone !!!

Since Yesterday, I get the same issues as previously wrote.

I still do not understand what is happening. I did not have change anything in the code, server or network.

I have tried to update my code as in the post gave by Nadine. Unfortunately, that did not resolved my issues.

This morning, the issues seem to be stabilised a little bit... But I still get random errors from time to time : 

- PHP Notice:  Failed to load response into DOM: DOMDocument::loadXML(): Empty string supplied as input in /************************************/Google/Api/Ads/Common/Lib/AdsSoapClient.php on line 305

- PHP Notice:  Failed to load response into DOM: DOMDocument::loadXML(): Empty string supplied as input in /************************************/Google/Api/Ads/Common/Lib/AdsSoapClient.php on line 404

- PHP Notice:  Failed to load response into DOM: DOMDocument::loadXML(): Empty string supplied as input in /************************************/Google/Api/Ads/Common/Lib/AdsSoapClient.php on line 422

- Exception : Bad Gateway

- SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201502/AdGroupCriterionService?wsdl' : failed to load external entity "https://adwords.google.com/api/adwords/cm/v201502/AdGroupCriterionService?wsdl"

Moreover, It does not happen every time on the same sevice (CampaignCriterionService, CampaignService, AdGroupService, AdGroupCriterionService, ReportDefinitionService, etc....)

Does it have a restriction about the call number to the API maybe  ? Or anything else ?

By the way, I precise that we use an AdWords API token for Standard Access.  

Thank you in advance,

Have a good day,

Best regards,

[Pierre Augereau]

Little Update !! 

I get a new error : 

- Error finding "uri" property (I did not find anything about this one in this forum)

If I follow the calls, usually, it starts with :

1 -- SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201502/AdGroupCriterionService?wsdl' : failed to load external entity "https://adwords.google.com/api/adwords/cm/v201502/AdGroupCriterionService?wsdl"

2 - All kind of "Failed to load response into DOM: DOMDocument::loadXML(): Empty string supplied as input...." or "Failed to load request into DOM: DOMDocument::loadXML(): Empty string supplied as input...."

3 - "Bad gateway" or "Error finding "uri" property" errors

Hope this help...

Have a good day,

Best regards,

[Nadine Sundquist (AdWords API Team)]

Hi Pierre,

I don't believe that you are having rate limit issues because you would be getting an error if you had hit the rate limit. Does the request succeed if you try again? If you're getting back a request ID in your error, I can try to trace it down further. If you do not have a request ID coming back, then it's highly likely that the request is not even making it to our servers.

Regards,

Nadine, AdWords API Team

[Pierre Augereau]

Good morning Nadine.

Once again, thank you a lot for your answers !!

Today, it seems to work fine again. But, I turned off all access from the API yesterday all day long. I do not know if it is a coincidence or the good thing to do...

Some requests succeed if I try again. But, the number of errors are increasing (eg : 1 error on 5 requests without trying again ; 3 errors on 5 requests with trying again) 

About the request ID, I checked all logs (request_info.log - soap_xml.log - report_download.log). There is no request ID for each error. 

So, it seems to have a problem while sending requests... I also checked all logs on my side and, all request have been correctly send from my server.

I will still investigate with my network administrator to, maybe, find something. But, I still do not know why that kind of errors appears suddently without any change on my side...

Thank you again,

Have a good day,

Best regards.

Le jeudi 7 mai 2015 17:33:02 UTC+2, Pierre Augereau a écrit :

[Nadine Sundquist (AdWords API Team)]

Hi Pierre,

If you are not getting back a request ID, this means that the failed requests are not making it to our servers. In that case, I can't troubleshoot from our side. You may need to sit down with a network administrator to trace the failed requests. 

Best,

Nadine, AdWords API Team