Hi, i always get an 504 in the console when using 4ai, i tried with gtp4 and 3.5. When i click on the link that throws the error in the console i can see that the answer from chatgpt is already there, but will not show up in the tool.
What can i do?
Last post
9 hours 44 min ago
Posts last week
94
Average response time last week
37 min
All time posts
70817
All time tickets
10917
All time avg. posts per day
20
Helpdesk is open from Monday through Friday CET
Please create an (free) account to post any question in the support area.
Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!
All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.
#10802 – Error 504 when using 4AI
Posted in ‘4AI’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
wb_weeblr
Hi
That error is a timeout. It means that your server (or maybe Cloudflare?) is stopping the request after some time but it's too early and the OpenAI API has not responded yet to your question.
Things to consider:
- OpenAI API can be quite slow at times, so it may be a matter of just trying at another time.
- after how much time does the error happens? depending on what you are doing, your server should allow 60 seconds or better: 90 seconds for the response to come in
- GPT4 is going to be much slower than GPT 3.5, so if you ask 4AI to work on a long text (ie spell, translate or create a full blog post), then it's best to try with GPT 3.5 first.
But again, the simplest thing is normally to configure your server to allow a longer response time, so that OpenAI has enough time to respond.
Best regards
Yannick Gaultier
weeblr.com / @weeblr
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.