Receiving 502 Bad gateway when requesting Landing pages
SOLVE
When I make the call /content/api/v2/pages I receive a 502 every-time however the calls to emails, blog posts, and forms works fine. Is there anything that I could do to avoid this or have some light shined upon this issue?
Could you send me a link to the HubSpot app you're using? I see that a "Lingotek Translation" app with the ID 30703 is connected to hub 4203244, however it's coming from developer portal 1813149, which was deactivated on 10 October 2017.
I found another "Lingotek Translation" app with the ID 41569 associated with developer portal 3025944, but it's not connected to hub 4203244, which could explain the issues you're experiencing.
Could you send me a link to the HubSpot app you're using? I see that a "Lingotek Translation" app with the ID 30703 is connected to hub 4203244, however it's coming from developer portal 1813149, which was deactivated on 10 October 2017.
I found another "Lingotek Translation" app with the ID 41569 associated with developer portal 3025944, but it's not connected to hub 4203244, which could explain the issues you're experiencing.
Receiving 502 Bad gateway when requesting Landing pages
SOLVE
https://api.hubapi.com/api/v2/pages
We have a guzzle client handling are requests where we pass it the url and headers/ query
$response = $this->client->get($url, ['headers' => $headers, 'query' => ['limit' => 100]]);
and we receive a 502 Bad Gateway when we make the call
This suggests there may be an issue with the implementation in the Guzzle client rather than the endpoint itself. Are you authorizing through the " Lingotek Translation" app?
Receiving 502 Bad gateway when requesting Landing pages
SOLVE
Yeah the weird thing is we use the same guzzle client to hit all the other ones and this call use to work. yes I'm authorizing through the Lingotek Translation app. It seems to only fell when the code is in production just for pages.