ERR_CONNECTION_REFUSED, after npx create-medusa-app@latest on REMOTE_IP:7001 about medusa HOT 10 CLOSED

@stelasido I see the issue now, and will open a PR to fix it. In the meantime, you can set the serve option in the admin plugin options to false:

options: {
  serve: false,
  // ...other options
}

And then the backend should be picked up correctly. Remember to also update your ADMIN_CORS to match the custom host you have set for the admin development server.

from medusa.

@stelasido, can you give the following snapshot a try and let us know if the issue is resolved:

yarn add @medusajs/[email protected]

from medusa.

@stelasido, any luck? We have a release later today and would like to include it if possible.

from medusa.

To open the login REMOTE_IP:7001, I need to add exactly that, all other envs, doesn't matter:

Then I see that:

As you can see, it requests to localhost:9000 from origin REMOTE_IP:7001, there is no logic for that

from medusa.

U can simply test, by creating an EC2 instance for less than an hour, allow 7001, 7000, 8000, 9000 ports and use npx create-medusa-app@latest

from medusa.

@stelasido you need to set the backend param in the admin plugin options, the default value is http://localhost:9000, which is wrong in your case.

options: {
  autoRebuild: true,
  backend: <here>,
  develop: {
    open: true,
    port: "0.0.0.0"
  }
}

from medusa.

@stelasido you need to set the backend param in the admin plugin options, the default value is http://localhost:9000, which is wrong in your case.

options: {
  autoRebuild: true,
  backend: <here>,
  develop: {
    open: true,
    port: "0.0.0.0"
  }
}

Still the same. Also, when I run it, it uses the private IP, but not the public/elastic IP

This is with 0.0.0.0:

This is without, any develop.host:

from medusa.

@stelasido

What are you setting the backend prop to? And is the dashboard not making requests to that URL?

from medusa.

@kasperkristensen without host: 0.0.0.0:

ERR_CONNECTION_REFUSED
with host: '0.0.0.0':

I can access login, but there is still problem. Now, not bloked request, but:

This is after npm build, in case of some static cache.
Also REMOTE_URL:9000 works fine in all cases, I can access it via browser Cannot GET / - which means the API works

from medusa.

hi, yes. Thx, will close the case.

from medusa.