#Execution failed with status 5000

1 messages · Page 1 of 1 (latest)

queen vault
#

So I'm getting this odd error with a POST API.

Execution failed with status 5000

NotAfter: Fri Jan 06 13:07:00 UTC 2023
{
"actionId":"63d4328510321b1d8e389d6e"
"requestedAt":1674852400.2463515
"body":""
"headers":[...]
"httpMethod":"POST"
"url":"https://computeportal.pliant.io/a/pc/prod/Administration/Locations/List_Locations?api_key=blahblahblah"
}

I like to triangulate, so I can confirm that the query works in Postman. I can also confirm that the datetime settings on the client and server are correct.

dapper novaBOT
#

Hey There,

We've registered your query, and our team will get back to you soon.

Regards,
Team Appsmith

dapper novaBOT
#

Please help us with the following information for faster debugging.

Which version of Appsmith are you on?
Provide screenshots/screen recordings of the original error/code snippet.
Add details about your use case and provide steps to reproduce the issue, if
possible.

wide musk
#

Hello, in addition to the information requested in the previous message, could you please share this other information with us?

  1. You use the cloud version or self/hosted
  2. This worked before
  3. You could run the same query from Postman
queen vault
#

Hi @wide musk . This is a brand new docker install today, so self hosted. it's a new app completely, so it has not had the opportunity to work prior to now. 🙂 And yes, I can run the query and get the expected data from postman.

dapper novaBOT
#

Hi there!
Thank you for the shared information!

I would like to confirm one last thing, does this api call require any form of
authentication or key to run?
If yes, can you share details on what type of authentication it is and a
screenshot of how you're doing this on appsmith? (Feel free to blur out any
sensitive information on the screenshot)

queen vault
#

Yep, it's an api_key field:

wide musk
#

Hello, could you show me the configuration you used in postman, please?

queen vault
#

Hi @wide musk . It turns out the issue was with an expired cert. Postman was ignoring the cert, but Appsmith was not, so I suppose that is actually by design. Is there a way to toggle ssl safety off?

dapper novaBOT
marsh portal
#

Hello I have the same problem but I'm using a self-hosted version

dapper novaBOT
marsh portal
#

nevermind I found the reason, the server that host appsmith suddenly lost the outbound connection connectivity so all API doesnt work