A while I ago I created a Discourse plugin which calls a controller method via ajax and then returns the result. This particular request can run for a few minutes, and this was running fine. But now after a long while I tried the plugin in the current Discourse version and I’m running into an issue where the request is aborted after 1 minute. So the code looks like this: ajax("/my-plugin/import", { type: "POST", data: { categoryId: this.categoryId, otherData: ... } }).then((result) => { ... }); And the error message I see after 1 minute is: Discourse Ember CLI Proxy Error FetchError: request to http://127.0.0.1:3000/my-plugin/import failed, reason: socket hang up at ClientRequest. (file:///src/app/assets/javascripts/node_modules/node-fetch/src/index.js:108:11) at ClientRequest.emit (node:events:526:35) at Socket.socketOnEnd (node:_http_client:525:9) at Socket.emit (node:events:526:35) at endReadableNT (node:internal/streams/readable:1359:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) What I’m trying to understand is why this behaviour might have changed in the past year? And if there is any option to change the timeout setting.

Maybe you want to schedule jobs to process the import.

I don’t think there has been any recent change here. Discourse’s backend is configured to timeout requests after 60 seconds in development, or 30 seconds in production config/unicorn.conf.rb cdcf53573 if ENV["RAILS_ENV"] != "production" logger Logger.new(STDOUT) # we want a longer timeout in dev cause first request can be really slow timeout (ENV["UNICORN_TIMEOUT"] && ENV["UNICORN_TIMEOUT"].to_i || 60) else # By default, the Unicorn logger will write to stderr. # Additionally, some applications/frameworks log to stderr or stdout, # so prevent them from going to /dev/null when daemonized here: stderr_path "#{discourse_path}/log/unicorn.stderr.log" stdout_path "#{discourse_path}/log/unicorn.stdout.log" # nuke workers after 30 seconds instead of 60 seconds (the default) timeout 30 end It looks like this is configurable in development via the UNICORN_TIMEOUT env variable. But production is hard-coded to 30 seconds.

AJAX request times out after 1 minute

Development

tomve (Tom) November 30, 2023, 12:46pm 4

In the end I did rewrite it to handle the import in a scheduled job, which turned out to be a lot better.

Topic		Replies	Views
Oops error due to database timeout Self-hosting	13	886	April 15, 2021
Can't delete invitations sent or abandon post draft Bug	3	810	March 18, 2021
Connection getting killed off Development	1	482	October 2, 2022
Discourse ai 的工具调用超时如何解决？是否可以调整discourse超时时间，如何调整？ Product Support ai	9	339	October 20, 2026
How to avoid upstream timeouts? Product Support	24	9738	February 25, 2019

AJAX request times out after 1 minute

Related topics