alisyd
Hello there, we have an app built with phoenix liveview which shows tick by tick market data for selected stocks every second, the app works fine on local network, but the websocket connection keeps disconnecting with 1006 when using a public IP or a reverse proxy. We have been trying to debug this for a while, any help is appreciated. Phoenix doesn’t reconnect when the websocket disconnect occurs, instead the entire page is reloaded again, even if we have turn off the code reloader
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.
Supporting innovation across the BEAM ecosystem.
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.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
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 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Hermanverschooten
Hi @alisyd
To answer the second part of your question first, live views are processes managed by a supervisor.
The supervisor restarts the process if it crashes, this is by design in OTP and is totally distant from the code reloading that happens in development.
If you say it keeps disconnecting, does this mean it does connect or never connects?
What is your setup? Are you connecting directly to the Phoenix app or is there a reverse-proxy or load-balancer or … in between?
What is in the log of the Phoenix app?
LostKobrakai
That‘s not fully correct. LiveViews are processes, yes, but they‘re not restarted by the supervisor. That doesn‘t make sense as the server has no way to connect back to the client with the websocket connection gone.
Given you mention the code reloader would this be with a dev build?
Generally you want to understand that there are two distinct tools in phoenix around keeping things up to date. There‘s the code reloader, which does track elixir source files and recompiles them if they have changed whenever a new (http) request comes in. So that cannot be what you‘re looking for.
There‘s also the live reloader, which reloads the website whenever templates or assets have changed. That one might be it.
alisyd
thanks for the responding, turns out it was because of delayed replies to heartbeat message from js client, so heartbeat timeout occurs and liveView reconnects agains. And also this does not occur when connected to local network and the issue is more prominent when phoenix app is put behind a reverse proxy, and yes this is with a dev build, we have disabled code reloader. I am assuming this has something to do with the udp listener, I have in the application which listens for data from a different application. when I turn off the udp listener everything works fine, and also I am updating socket assigns, every second. udp listener is a genserver that listens for data over a port, I have put a large value for recbuf (65536), Idk if that is causing the issue.