ricw
Hi,
I’ve written a small plug that depending on the host that is connecting injects host specific parameters. This seems to work fine for the initial connection and mount, but fails when mounting the web socket connection afterwards (as described in the Liveview behaviour), ie here:
[info] CONNECTED TO Phoenix.LiveView.Socket in 16µs
Transport: :websocket
Parameters: %{"_csrf_token" => "asdfasdf", "_live_referer" => "undefined", "_mounts" => "0", "_track_static" => %{"0" => "http://localhost:4000/assets/app.css", "1" => "http://localhost:4000/assets/app.js"}, "vsn" => "2.0.0"}
The page now renders (due to the first mount succeeding), but shows a “Something went wrong! Hang in there while we get back on track” error message when attempting the web socket connection afterwards.
Is this expected? Can i somehow make the plug be executed like with the initial connection?
Tried to find documentation on this but to no success.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
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
- #elixirconf-us
- #ai
- #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.
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!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
Enabling companies to succeed by building software people love.
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 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
ricw
Wasn’t able to get the plugs to work reliably with liveview, so i instead used an on_mount function that acts the same (link to the docs). Shame, as it means one can’t share the same plug between liveview and normal views, but it works.
derek-zhou
Isn’t it a proof that liveview web socket is calling your plug? Otherwis, it wouldn’t be broken. Maybe the parameters you injected interfere with liveview connection, so it think the connection attempt is from a unauthorized party, ie. cross-site attack.
What did you do in your plug?
tubedude
The fact is that LiveView only passes through the Plug pipeline on the first connection.
So you could have a plug that adds information into the session for example.
On the
mount/3callback you could take the info from the session, add it to the state of the LiveView and use it on all other LiveView interactions.After LiveView is mounted, it will not go through the plug pipeline again