Dify Block Internal Server Error(selfhost)

JJesús Pacheco

So I was super excited for this block I spend some time building bots in Dify and everything but at the moment of making a connection Im having this error code 500 when Dify block tries to run.

Have anyone experience the same problem?

I am using a self-hosted Dify with custom API endpoint so I used that endpoint on typebot.

But then thinking it was my Dify installation I went to the cloud based Dify and used their API to find myself with the same error code 😦 Sad.

Error:


{
  "status": 500,
  "body": {
    "message": "Response code 404 (Not Found)",
    "code": "INTERNAL_SERVER_ERROR",
    "data": {
      "code": "INTERNAL_SERVER_ERROR",
      "httpStatus": 500,
      "path": "continueChat"
    }
  }
}

23 comments

BBaptiste

What's the configuration of your block?

BBaptiste

It is most likely misconfigured

JJesús Pacheco

Hmm, I made sure to follow your lume video a few times, what's different is that mines goes straight to the prompt and I did not used the conversation ID since it is optional right?. This is my block configuration. "xyz" represents my anonymous website. I also used the cloud based dify app with this endpoint > https://api.dify.ai/v1

Attachments

BBaptiste

Remove v1 in your API endpoint. Typebot handles the versioning

BBaptiste

This should look like: https://api.dify.ai

JJesús Pacheco

It worked with the cloud version but for the self hosted(dify)keeps giving me the error. I created a similar api subdomain and put it without the /v1 to see if worked but no.

BBaptiste

Provide the URL you entered please 🙂

NNerQuiLes

Hi, I have the same error and I followed the tutorial step by step. any idea about this error?

NNerQuiLes

Attachments

JJesús Pacheco

Are you using a Self hosted dify? Or the cloud version?

NNerQuiLes

Cloud

JJesús Pacheco

Then this should work for you

JJesús Pacheco

Put that link as the endpoint , your api key and the name. That worked for me. Just not with the selfhost

NNerQuiLes

It doesn't work for me... no idea what's wrong, but I have the same error as you, but in Cloud.

BBaptiste

We just merged a potential fix. @NerQuiLes can you try again?

NNerQuiLes

Sorry @Baptiste , but this doesn't work for me, same error.... I have checked the API, the route, the inputs... but I can't get it to work. If you want I can send you the link to check it... https://app.typebot.io/typebots/clsddfuzi001xvh4op5oxomjb

NNerQuiLes

{
"status": 500,
"body": {
"message": "Response code 400 (Bad Request)",
"code": "INTERNAL_SERVER_ERROR",
"data": {
"code": "INTERNAL_SERVER_ERROR",
"httpStatus": 500,
"path": "continueChat"
}
}
}

NNerQuiLes

Finally, I got it by setting up my own API connection. If anyone has trouble with the connector, just know that it can be done with the API connection as well.

NNerQuiLes

Attachment

JJesús Pacheco

That's awesome but also the whole point of having a block is to do all that work. I'll just wait until the fix is released in the next docker update. Thanks for sharing.

BBaptiste

Alright, I'm pushing a fix now 👍

BBaptiste

There was indeed still an issue if Inputs are empty

AAlex

Man, could you send me the step by step, please?

Add a reply

Share feedback, ideas and get community help

Dify Block Internal Server Error(selfhost)