(ArgumentError) could not fetch application environment :ash_domains for application :test

I just ran the startup script, here: https://ash-hq.org/#get-started But after pasting the command, I straight up get this error message
[info] == Migrated 20250829135349 in 0.0s
[notice] Application venirdotdev exited: exited in: Venirdotdev.Application.start(:normal, [])
** (EXIT) an exception was raised:
** (ArgumentError) could not fetch application environment :ash_domains for application :venirdotdev because configuration at :ash_domains was not set
(elixir 1.18.1) lib/application.ex:771: Application.fetch_env!/2
(venirdotdev 0.1.0) lib/venirdotdev/application.ex:17: Venirdotdev.Application.start/2
(kernel 10.2) application_master.erl:295: :application_master.start_it_old/4
[info] == Migrated 20250829135349 in 0.0s
[notice] Application venirdotdev exited: exited in: Venirdotdev.Application.start(:normal, [])
** (EXIT) an exception was raised:
** (ArgumentError) could not fetch application environment :ash_domains for application :venirdotdev because configuration at :ash_domains was not set
(elixir 1.18.1) lib/application.ex:771: Application.fetch_env!/2
(venirdotdev 0.1.0) lib/venirdotdev/application.ex:17: Venirdotdev.Application.start/2
(kernel 10.2) application_master.erl:295: :application_master.start_it_old/4
This is where the error is raised:
# inside `Application.start`
# inside `children` list
{Oban,
AshOban.config(
Application.fetch_env!(:venirdotdev, :ash_domains),
Application.fetch_env!(:venirdotdev, Oban)
)},
# inside `Application.start`
# inside `children` list
{Oban,
AshOban.config(
Application.fetch_env!(:venirdotdev, :ash_domains),
Application.fetch_env!(:venirdotdev, Oban)
)},
I'm not sure how to solve this.
Ash HQ
Ash Framework
Model your domain, derive the rest.
Solution:
Please open issues describing the exact steps to reproduce each issue and I will look into it. You should be able to install packages into a new app one at a time to avoid the issues for now.
Jump to solution
7 Replies
ZachDaniel
ZachDaniel•2mo ago
🤔 Can I see the command you ran?
venir.dev
venir.devOP•2mo ago
the one that's copied from ash-qh.org meaning
mix archive.install hex igniter_new --force
mix archive.install hex phx_new 1.8.1 --force

mix igniter.new venirdotdev --with phx.new --install ash,ash_phoenix \
--install ash_postgres,ash_admin --install ash_oban,oban_web \
--install ash_state_machine,live_debugger --install ash_money,beacon \
--install beacon_live_admin --beacon.site cms \
--beacon-live-admin.path /cms/admin --yes

cd venirdotdev && mix ash.setup
mix archive.install hex igniter_new --force
mix archive.install hex phx_new 1.8.1 --force

mix igniter.new venirdotdev --with phx.new --install ash,ash_phoenix \
--install ash_postgres,ash_admin --install ash_oban,oban_web \
--install ash_state_machine,live_debugger --install ash_money,beacon \
--install beacon_live_admin --beacon.site cms \
--beacon-live-admin.path /cms/admin --yes

cd venirdotdev && mix ash.setup
I just tried again point blank, like so:
mix archive.install hex igniter_new --force
mix archive.install hex phx_new 1.8.1 --force

mix igniter.new testing_one_two_three --with phx.new \
--install ash,ash_phoenix --install ash_postgres,ash_admin \
--install ash_oban,oban_web --install ash_state_machine,live_debugger \
--install ash_money,beacon --install beacon_live_admin --beacon.site cms \
--beacon-live-admin.path /cms/admin --yes

cd testing_one_two_three && mix ash.setup
mix archive.install hex igniter_new --force
mix archive.install hex phx_new 1.8.1 --force

mix igniter.new testing_one_two_three --with phx.new \
--install ash,ash_phoenix --install ash_postgres,ash_admin \
--install ash_oban,oban_web --install ash_state_machine,live_debugger \
--install ash_money,beacon --install beacon_live_admin --beacon.site cms \
--beacon-live-admin.path /cms/admin --yes

cd testing_one_two_three && mix ash.setup
in this case no errors were printed and then:
mix phx.server
mix phx.server
result:
** (Mix) Could not start application testing_one_two_three: exited in: TestingOneTwoThree.Application.start(:normal, [])
** (EXIT) an exception was raised:
** (ArgumentError) could not fetch application environment :ash_domains for application :testing_one_two_three because configuration at :ash_domains was not set
(elixir 1.18.1) lib/application.ex:771: Application.fetch_env!/2
(testing_one_two_three 0.1.0) lib/testing_one_two_three/application.ex:18: TestingOneTwoThree.Application.start/2
(kernel 10.2) application_master.erl:295: :application_master.start_it_old/4
** (Mix) Could not start application testing_one_two_three: exited in: TestingOneTwoThree.Application.start(:normal, [])
** (EXIT) an exception was raised:
** (ArgumentError) could not fetch application environment :ash_domains for application :testing_one_two_three because configuration at :ash_domains was not set
(elixir 1.18.1) lib/application.ex:771: Application.fetch_env!/2
(testing_one_two_three 0.1.0) lib/testing_one_two_three/application.ex:18: TestingOneTwoThree.Application.start/2
(kernel 10.2) application_master.erl:295: :application_master.start_it_old/4
I can confirm I went into that "state" (in the first message above) because I tried running mix phx.server to try stuff out; from then, I get the error even with e.g. mix ecto.reset update: I am totally able to mix phx.new hello and starting a dev server with phoenix, without ash, that works. now I tried something simpler
mix archive.install hex igniter_new --force
mix archive.install hex phx_new 1.8.1 --force

mix igniter.new another_test --with phx.new --install ash,ash_phoenix \
--install ash_postgres,ash_authentication \
--install ash_authentication_phoenix,ash_admin --install live_debugger \
--auth-strategy magic_link --yes

cd another_test && mix ash.setup
mix archive.install hex igniter_new --force
mix archive.install hex phx_new 1.8.1 --force

mix igniter.new another_test --with phx.new --install ash,ash_phoenix \
--install ash_postgres,ash_authentication \
--install ash_authentication_phoenix,ash_admin --install live_debugger \
--auth-strategy magic_link --yes

cd another_test && mix ash.setup
and then
mix test
mix test
result:
# installation logs
Running ExUnit with seed: 648471, max_cases: 28

.....
Finished in 0.02 seconds (0.01s async, 0.01s sync)
5 tests, 0 failures
# installation logs
Running ExUnit with seed: 648471, max_cases: 28

.....
Finished in 0.02 seconds (0.01s async, 0.01s sync)
5 tests, 0 failures
so, this works as well, meaning it's some ash library messing up with the installatino process, somehow looks like the culprit is Beacon the following setup
mix archive.install hex igniter_new --force
mix archive.install hex phx_new 1.8.1 --force

mix igniter.new venir_dev_website --with phx.new --install ash,ash_phoenix \
--install ash_postgres,ash_admin --install live_debugger,beacon \
--install beacon_live_admin --beacon.site cms \
--beacon-live-admin.path /cms/admin --yes

cd venir_dev_website && mix ash.setup && mix.test # !
mix archive.install hex igniter_new --force
mix archive.install hex phx_new 1.8.1 --force

mix igniter.new venir_dev_website --with phx.new --install ash,ash_phoenix \
--install ash_postgres,ash_admin --install live_debugger,beacon \
--install beacon_live_admin --beacon.site cms \
--beacon-live-admin.path /cms/admin --yes

cd venir_dev_website && mix ash.setup && mix.test # !
venir.dev
venir.devOP•2mo ago
results in this error, although it's different from before
ZachDaniel
ZachDaniel•2mo ago
So without beacon there is no error?
venir.dev
venir.devOP•2mo ago
For sure, but I'm on the lookout for the original error, which is different from this one. Ok my final sympthoms review is the following: 1. from ashhq home page, select phoenix preset, add beacon --> results in that long error message after a mix test or a mix phx.server
mix archive.install hex igniter_new --force
mix archive.install hex phx_new 1.8.1 --force

mix igniter.new with_beacon --with phx.new --install ash,ash_phoenix \
--install ash_postgres,ash_authentication \
--install ash_authentication_phoenix,ash_admin \
--install live_debugger,beacon --install beacon_live_admin \
--auth-strategy magic_link --beacon.site cms \
--beacon-live-admin.path /cms/admin --yes

cd with_beacon && mix ash.setup && mix test
mix archive.install hex igniter_new --force
mix archive.install hex phx_new 1.8.1 --force

mix igniter.new with_beacon --with phx.new --install ash,ash_phoenix \
--install ash_postgres,ash_authentication \
--install ash_authentication_phoenix,ash_admin \
--install live_debugger,beacon --install beacon_live_admin \
--auth-strategy magic_link --beacon.site cms \
--beacon-live-admin.path /cms/admin --yes

cd with_beacon && mix ash.setup && mix test
2. from ashhq home page, select phoenix preset and add oban this time, while removing auth --> results in the error I originally posted this thread
mix archive.install hex igniter_new --force
mix archive.install hex phx_new 1.8.1 --force

mix igniter.new venir_dev_website --with phx.new --install ash,ash_phoenix \
--install ash_postgres,ash_admin --install ash_oban,oban_web \
--install live_debugger --yes

cd venir_dev_website && mix ash.setup
mix archive.install hex igniter_new --force
mix archive.install hex phx_new 1.8.1 --force

mix igniter.new venir_dev_website --with phx.new --install ash,ash_phoenix \
--install ash_postgres,ash_admin --install ash_oban,oban_web \
--install live_debugger --yes

cd venir_dev_website && mix ash.setup
point 2 is what caused this thread in the first place, I just thought "naahhhh I'll add authentication later if I need" I want to write my first personal website and I wanted to do so with ash so I can excercise and learn it better
Solution
ZachDaniel
ZachDaniel•2mo ago
Please open issues describing the exact steps to reproduce each issue and I will look into it. You should be able to install packages into a new app one at a time to avoid the issues for now.
venir.dev
venir.devOP•2mo ago
thank you zach, you're awesome

Did you find this page helpful?