oliverandrich
Hi,
I am somewhat confused. I just wanted to create a new project using Elixir 1.11.1 and Phoenix 1.5.6 using the command mix phx.new --live new_project.
As soon as I start the server with mix phx.server and connect to port 4000, I get the following error.
[error] #PID<0.622.0> running NewProjectWeb.Endpoint (connection #PID<0.621.0>, stream id 1) terminated
Server: localhost:4000 (http)
Request: GET /
** (exit) an exception was raised:
** (ArgumentError) no action :home for NewProjectWeb.Router.Helpers.live_dashboard_path/2. The following actions/clauses are supported:
live_dashboard_path(conn_or_endpoint, :page, params \\ [])
live_dashboard_path(conn_or_endpoint, :page, node, page, params \\ [])
live_dashboard_path(conn_or_endpoint, :page, page, params \\ [])
I don’t know what I did differently since I did it last time. I think the only difference is that I use more recent versions of Elixir and Phoenix. I think I used Elixir 1.10.x and Phoenix 1.5.4.
Where is my fault? What did I miss?
Best regards
Oliver
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #ai
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 5 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
josevalim
This is my bad. I broke it yesterday with a new release, I will ship a fix today. Thanks for the report!
EDIT: v0.3.5 has been released and v0.3.4 has been retired.
oliverandrich
Another solution is to skip the dashboard completely for the moment by specifying --no-dashboard on the command line.
https://github.com/phoenixframework/phoenix/issues/4043#issuecomment-717685494
jamesarr
Wow, thanks so much for figuring this out.!
I’m pretty much a complete novice, and I’ve wasted a bunch of time today deploying broken projects to heroku, not knowing they were broken from the get-go.
Thanks again!
seanc
The real solution is to modify a line of code in the generated project. This actually affects any newly generated project that doesn’t have the
--no-htmlflag.In a liveview project, you want to change this line in
root.html.leex:Specifically the
live_dashboard_pathfunction call here. Change it toRoutes.live_dashboard_path(@conn, :page, :home)like so:This same problem occurs on
app.html.eexinside of regular, non-liveview phoenix projects.oliverandrich
I think, I found the problem.
This line resulted in installing version 0.3.4 of live dashboard. If I replace it with “~>0.2.9”, I get version 0.2.10 and then everything works again.