forge app external request ends up with 502

[Roman Kern]

Hello together,

I'm facing a problem with external API call. It's end up with 502, even the api is available and manifest allows the api call

the code

  const response = await api.fetch('https://myapi.com/v1/retrieve',{

    method: 'POST',

    headers: {

      'api-key': `${process.env.auth}`,

      'Content-Type': 'application/json'

    },

    body: JSON.stringify(request)

  });

  if(!response.ok){

    console.error(JSON.stringify(response));

    throw new Error(`Error: ${response.status} ${response.statusText} ${await response.text()}`);

  }

Manifest.yml

permissions:

  external:

    fetch:

      backend:

        - 'https://myapi.com'

modules:

  jira:issuePanel:

...

ERROR 10:23:14.409  {"size":0,"timeout":0} --> first line of console.error(JSON..

ERROR 10:23:14.423  Error: Error: 502 Bad Gateway Bad Gateway

is that beacause, I'm using url without www?

[Roman Kern · Accepted solution]

I asked on developer platform. found some similar ticket their

https://community.developer.atlassian.com/t/forge-app-reports-an-error-502-after-changing-baseurl/87795

[Mohamed Benziane]

Hi,

The 502 error indicate an error on the server side. Did you try your API with postman on your local machine ?

[Roman Kern]

yes, everything works fine... is their any way to see internal logs, except forge logs/tunnel for the api call?why the external api was blocked, etc?