Discourse Ember CLI Proxy Error

Product Support

AI-generated summary

The user Wilson_Wang encountered a Discourse Ember CLI proxy error indicating a connection refusal to 127.0.0.1:3000, suggesting the Rails server wasn’t running. pfaffman asked whether this was a standard or development install, and Wilson_Wang confirmed following the development setup guide. merefield advised ensuring the Rails server is running or using the -u flag to start both servers together. pfaffman recommended using a dev container and asked if Rails was started manually. Wilson_Wang shared additional logs showing a failure to locate magick, pointing to a missing ImageMagick installation. pfaffman clarified that ./bin/rails s must be run in a separate terminal before launching ./bin/ember-cli. merefield emphasized installing the correct ImageMagick version. Finally, pfaffman provided a script using asdf and Docker to install the exact ImageMagick version required by Discourse, ensuring compatibility. The core issue stems from either not running the Rails server or missing system dependencies like ImageMagick.

1

Discourse Ember CLI Proxy Error

FetchError: request to http://127.0.0.1:3000/ failed, reason: connect ECONNREFUSED 127.0.0.1:3000
    at ClientRequest. (file:///home/xxx/discourse/node_modules/.pnpm/node-fetch@3.3.2/node_modules/node-fetch/src/index.js:108:11)
    at ClientRequest.emit (node:events:524:28)
    at emitErrorEvent (node:_http_client:101:11)
    at Socket.socketErrorListener (node:_http_client:504:5)
    at Socket.emit (node:events:524:28)
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

How to fix the error?

Thanks

2

Is this a standard install? A development install?

3

Follow the guide Install Discourse on Ubuntu or Debian for Development

4

You need to have the rails server running.

Or you can use -u to run both.

5

Consider Developing Discourse using a Dev Container. Say more about what you did. Did you start rails?

6

I, [2025-07-22T11:01:04.131140 #169405] INFO – : listening on addr=127.0.0.1:3000 fd=28
[ember-cli] …[@embroider/webpack]
#<Thread:0x00007f3f66f43c18 /home/xxx/discourse/lib/discourse.rb:1189 run> terminated with exception (report_on_exception is true):
/home/xxx/discourse/lib/letter_avatar.rb:112:in ‘Kernel#': No such file or directory - magick (Errno::ENOENT) from /home/xxx/discourse/lib/letter_avatar.rb:112:in 'LetterAvatar.image_magick_version' from /home/xxx/discourse/lib/discourse.rb:1189:in 'block in Discourse.preload_rails!' E, [2025-07-22T11:01:14.236992 #169405] ERROR -- : No such file or directory - magick (Errno::ENOENT) /home/xxx/discourse/lib/letter_avatar.rb:112:in 'Kernel#’
/home/xxx/discourse/lib/letter_avatar.rb:112:in ‘LetterAvatar.image_magick_version’
/home/xxx/discourse/lib/discourse.rb:1189:in ‘block in Discourse.preload_rails!’
[bin/ember-cli] unicorn process stopped. Terminating ember-cli.

7

Did you do something like:

cd ~/discourse
./bin/rails s

You need to do that in another terminal before running ./bin/ember-cli

8

Make sure the right version of imagemagick is installed.

9

Looks like good advice. Here’s how I do that. It assumes you’ve got asdf and docker.

  IMAGE_MAGICK_VERSION=$(docker run discourse/base:release bash -c 'magick --version'|head -1|cut -d' ' -f3)
  echo "Got IMAGE_MAGICK_VERSION: $IMAGE_MAGICK_VERSION"
  asdf install imagemagick $IMAGE_MAGICK_VERSION 2>&1 |grep -v "already"
  echo "installed imagemagic, now set global"
  asdf global imagemagick $IMAGE_MAGICK_VERSION 2>&1 |grep -v "already"
  echo "global done."