Handling Error (502) Bad Gateway

[Milan]

Hi,

has anyone recently been experiencing the following error message
sporadically (but with increased frequency at the same time)?
"ERROR (502) Bad Gateway
The server encountered a temporary error and could not complete your
request. Please try again in 30 seconds."

Trying to figure out a potential cause for this issue and am
interested in any best-practice recommendations on how to handle this
scenario.

Thanks a lot!

[DFA API Advisor]

Hi Milan,

The HTTP 502 errors have been an issue recently. The networking team
is currently investigating the DFA API looking for the cause.

Since these requests are not making it to the server, I would assume
just repeating these failed requests is a good way to handle it.
Perhaps some other users can share their experiences and how they've
dealt with this?

Regards,
- Joseph DiLallo, the DFA API Team

[john.mi...@gmail.com]

Since 7/17 we've been getting 15 or so of these 502 errors in a row before it finally completes. I've tried everything. Is theresomething going on w/ double click since 7/17? This issue is causing our reporting to be an extra day behind. We need to have our dfp api calls to complete by 5:50 am eastern time in order to hit our reporting SLA. Lately we havent been able to get the data until around 9am which is a huge problem for us. Are you guys actively working to resolve this issue or is this just the way it's going to be?

thank you for you're time!

[jo...@travelspike.com]

I know this is over a year old, but I am encountering the same issue.

I have DFA Reporting calls work great locally but on our production Azure server, I get a 502 consistently. I have NEVER seen it work from our production site.

Is there a domain config I need to update, we are using a p12 key for cert auth. and I know the account is valid, since it works locally.

What should I do?

-john-

[Jonathon Imperiosi (DCM API Team)]

Hi John,

In general, 5xx errors are transient and can be retried. If you’re seeing 502s consistently, however, that’s probably indicative of some networking issue between you and us. I recommend:

1. Determining which specific requests are failing and making note of the hostname(s)
2. Running standard networking diagnostics (mtr or traceroute + ping) on those hosts from your production machines to see where the requests fail.

Regards,

- Jonathon Imperiosi, DCM API Team

[John Mann]

Thank you so much for the response.

I JUST figured it out... It was a cert error not being loaded due to Azure (NOT Google) and permissions problem so it couldn't even make the call to DFA.

For those using Azure and p12 certs for auth, server.mappath will NOT work, it is suggested to use private blob storage for keys and read it in as a byte[].

It is all working now.

Thanks again.

-john-

--
You received this message because you are subscribed to a topic in the Google Groups "Google's DoubleClick Campaign Manager API Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-doubleclick-for-advertisers-api/_scm0XL6FfY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-doubleclick-for-ad...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.