reverend_paco
I am deploying an Elixir application behind an Nginx proxy (multiple Elixir applications actually) and am having some issues specific (I think) to live_redirect.
I have
- changed the
urlin my config.exs by adding thepathas such:url: [host: "localhost", path: "/campaign"] - prepended the base-url to the app.js as such:
let liveSocket = new LiveSocket("/campaign/live", Socket, {params: {_csrf_token: csrfToken}})
I have another application that uses LiveView that works fine, but this campaign application, which another developer has developed, manifests the problems.
In the backend I see:
[error] an exception was raised:
** (ArgumentError) cannot invoke handle_params nor live_redirect/live_link to "https://[ELIDED]/campaign/dashboard/nonode%40nohost" because it isn't defined in CampaignsLiveWeb.Router
(phoenix_live_view 0.12.1) lib/phoenix_live_view/utils.ex:209: Phoenix.LiveView.Utils.live_link_info!/3
(phoenix_live_view 0.12.1) lib/phoenix_live_view/channel.ex:600: Phoenix.LiveView.Channel.verified_mount/4
(phoenix_live_view 0.12.1) lib/phoenix_live_view/channel.ex:34: Phoenix.LiveView.Channel.handle_info/2
I am wondering if anyone has seen anything similar to this before, and can give me a hint as to where I might explore?
Again, I have successfully deployed another LiveView application using the above 2 points, so I know that nginx is properly passing/upgrading the websockets. I feel that this is related to the issue here, although in my case, I know what the top-level URL is going to be and am not using dynamic re-writing.
Thanks,
Daniel
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #ai
- #elixirconf-us
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
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!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sfusato
Are those liveviews defined at the router level?
reverend_paco
Yes, they are.
I’ve been peeking at the phoenix_live_view/util.ex (the
live_link_info!method, in particular) and I think if pass the endpoint in there, I could grab the config-ed:urlkey and remove the proxy path there. Gonna see if I can hack this to understand what’s going on.sfusato
How are you calling
live_dashboardinrouter.ex?live_dashboard("/campaign/dashboard")?reverend_paco
Sorry, that was a stacktrace from when I went to the dashboard, I was getting it the same way with other URLs:
I am noticing one thing in my codebase that might be problematic (and might have nothing to do with this particular error or is the problem). In the eex templates, I see that the action is using a old-style to: action,
instead of the Routes.live_path that I see in the documentation.
I wonder if this might be related.
reverend_paco
Well, my hack worked. I changed utils.ex and channel.ex and static.ex to pass in the endpoint to the
live_link_infoand then used the path to remove the prefix coming in from websocket and things started working.Feeling proud of myself, I wanted to see if I could contribute it back and checked on github and saw that this has been fixed with the following patch: Consider script_name on client URLs, closes #805 · phoenixframework/phoenix_live_view@06b3e81 · GitHub
So if anyone is having a similar problem, grab the latest from master (I was on version 0.12.0)
EDIT: if you don’t want master, it looks like this fix is on 0.13.0