Dify Block Internal Server Error(selfhost)
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:
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"
}
}
}
15 Replies
What's the configuration of your block?
It is most likely misconfigured
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
Remove
v1 in your API endpoint. Typebot handles the versioning
This should look like: https://api.dify.aiIt 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.
Provide the URL you entered please 🙂
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
Are you using a Self hosted dify? Or the cloud version?
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
Then this should work for you
Put that link as the endpoint , your api key and the name. That worked for me. Just not with the selfhost
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
We just merged a potential fix. @NerQuiLes can you try again?
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
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.
Alright, I'm pushing a fix now 👍
There was indeed still an issue if Inputs are empty
Man, could you send me the step by step, please?