Not Able to Run ElsaDemoApp #10846

5 Answer(s)

• 

  0

  AI-Bot created one month ago

  Support Team ABP Agent

  • Your log shows two separate connectivity problems while starting ElsaDemoApp.Server:
    1. RabbitMQ connection refused: 127.0.0.1:5672
    2. Redis connection timeout/unreachable: 127.0.0.1:6379

  1) Fix RabbitMQ (5672)

  1. Ensure the RabbitMQ broker is actually listening on port 5672 (the Windows service being “Running” doesn’t always guarantee the listener is reachable).
  2. Ensure your ElsaDemoApp.Server configuration points to the correct host/port and credentials.

  In ElsaDemoApp.Server/appsettings.json (or the environment-specific variant), ensure you have a correct RabbitMQ section similar to:

  "RabbitMQ": {
    "Connections": {
      "Default": {
        "HostName": "localhost",
        "Port": "5672"
      }
    }
  }
  

  If your RabbitMQ uses non-default credentials, also set UserName / Password (ABP reads RabbitMQ connection settings from configuration).

  2) Fix Redis (6379) OR disable Redis for local run

  Your startup fails later because ABP is trying to use Redis distributed cache at 127.0.0.1:6379:

  • If you want to use Redis: install/run Redis and make sure it listens on 6379.
  • If you don’t want Redis for local demo: remove/disable Redis caching configuration so the app falls back to in-memory distributed cache (common for single-node local dev).

  If Redis is enabled in config, verify something like this in appsettings.json:

  "Redis": {
    "IsEnabled": "true",
    "Configuration": "127.0.0.1:6379"
  }
  

  Make it consistent with your actual Redis endpoint. If you don’t have Redis, set IsEnabled to false or remove the Redis configuration section used by the solution.

  3) Important note about “updating all NuGet packages”

  For samples like ElsaDemoApp, upgrading packages arbitrarily can introduce version mismatches. Prefer keeping package versions aligned with the sample’s original ABP version (you mentioned ABP 10.6.0). If you already upgraded, revert to the original versions shipped with the sample (or align all ABP packages to the same version).

  ---

  (sources)

  • https://abp.io/docs/10.6/samples/elsa-workflows-demo
  • https://abp.io/docs/10.6/framework/fundamentals/redis-cache
  • https://abp.io/docs/10.6/framework/infrastructure/background-jobs/rabbitmq
  • https://stackexchange.github.io/StackExchange.Redis/Timeouts

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  bpdeveloper created one month ago

  Point 1 and 2 checked and implemented For point 3 -- the downloaded project have build error so i updated i can attach the version information here ElsaDemoApp.Server.csproj.txt

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  AI-Bot created one month ago

  Support Team ABP Agent

  • The stack trace you shared is not a NuGet/package-version problem anymore. It’s a runtime connectivity problem:
    • RabbitMQ: No connection could be made because the target machine actively refused it (127.0.0.1:5672)
    • Redis: UnableToConnect on 127.0.0.1:6379

  Updating packages may have fixed your build, but it won’t fix these two services being unreachable.

  1) RabbitMQ: “service running” but port 5672 refused

  This error means nothing is accepting TCP connections on 127.0.0.1:5672. Even if the Windows service shows “Running”, the broker may not actually be listening (or it’s bound differently / blocked).

  Fix options (pick one):

  • Ensure RabbitMQ is listening on 5672 and reachable on localhost.
  • Or change ElsaDemoApp.Server RabbitMQ configuration to match the actual host/port you have.

  In ElsaDemoApp.Server appsettings (the one actually used at runtime), verify the RabbitMQ endpoint is correct, e.g.:

  "RabbitMQ": {
    "Connections": {
      "Default": {
        "HostName": "localhost",
        "Port": "5672"
      }
    }
  }
  

  2) Redis is also required by this demo (and it’s not running)

  Your log shows ABP is using Redis for distributed cache at 127.0.0.1:6379, and that connection is failing. You must either:

  A) Start Redis on localhost:6379 (recommended for the demo), or
  B) Change the Redis connection string to wherever your Redis actually is, or
  C) Disable Redis for local run (only if the sample supports that in its configuration; otherwise you’ll keep hitting caching initialization failures).

  Given your exception comes from ABP’s feature/permission static savers hitting distributed cache, running Redis is the simplest path.

  3) About the csproj you attached

  I can’t access /QA/Files/Download/... from here, so I can’t verify the exact package versions you updated. But again: your current crash is clearly from RabbitMQ + Redis connectivity, not package resolution.

  If you want the quickest “known-good” environment to run ElsaDemoApp:

  • Run RabbitMQ and Redis locally (or via Docker), and keep the demo’s endpoints pointing to localhost:5672 and localhost:6379.

  (sources)

  • https://abp.io/docs/10.6/samples/elsa-workflows-demo
  • https://abp.io/docs/10.6/modules/elsa-pro
  • https://stackexchange.github.io/StackExchange.Redis/Timeouts

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created one month ago

  Support Team Fullstack Developer

  Hi,

  The demo needs SQL Server, Redis and RabbitMQ all reachable before it can start. Redis isn't reachable at 127.0.0.1:6379 and RabbitMQ isn't accepting connections on 127.0.0.1:5672 (the Windows service being Running doesn't mean the broker is listening).

  The safest way on Windows is to run both in Docker instead of installing them locally:

  docker run -d --name redis -p 6379:6379 redis:alpine
  docker run -d --name rabbitmq -p 5672:5672 -p 15672:15672 rabbitmq:management-alpine
  

  If the RabbitMQ Windows service is still installed, stop it first so it doesn't hold port 5672.

  Two more things for the sample itself. The download still ships ABP 10.0.0-rc.1 packages, so keep all Volo.Abp.* packages aligned on 10.6.0 after your update. The Identity schema changed between those versions, so add a migration in the ElsaDemoApp.Server folder and apply it:

  dotnet ef migrations add Upgrade_To_10_6
  dotnet run --migrate-database
  

  Without it, seeding fails with Invalid column name 'LastSignInTime'.

  The sample also doesn't ship wwwroot/libs, so run this once in the same folder:

  abp install-libs
  

  Then start the projects in the order from the docs: ElsaDemoApp.Server, ElsaDemoApp.Studio.WASM, ElsaDemoApp.Ordering, ElsaDemoApp.Payment.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created one month ago

  Support Team Fullstack Developer

  Hi,

  We've updated the sample, so grab a fresh copy from https://abp.io/api/download/samples/elsaworkflow and work with that one. It ships with ABP 10.5.0 now and builds as it is, so you no longer need to update the packages yourself or add a migration.

  Two things from my previous answer still apply:

  • Redis and RabbitMQ have to be up and reachable before you start ElsaDemoApp.Server.
  • Run abp install-libs once in the ElsaDemoApp.Server folder, the sample doesn't ship wwwroot/libs.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel