TMoore
Hello!
I’m working on incorporating the ingress capability of Home Assistant into an add-on that utilizes a websocket. The challenge is that the web application expects a base URL of / but the Home Assistant ingress feature uses a base URL of /api/hassio_ingress//. The web application utilizes a websocket at /live. I’ve setup NGINX to provide the necessary proxying and filtering in order to dynamically modify the URL references in the web application. This seems to work well for the main page, but there are two secondary pages that don’t work. When I look at the Messages for the websocket in the developer tools, I see that the websocket is sending a phx_reply with a “join crashed” error.
At this point, I’m hoping someone might have some ideas as to why it might work on the main page but not on the secondary pages.
Thanks!
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
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
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
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.
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 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
tcoopman
Can you provide the full error message and the relevant code?
TMoore
The application is TeslaMate (GitHub - teslamate-org/teslamate: A self-hosted data logger for your Tesla 🚘 [main maintainer=@JakobLichterfeld] · GitHub). The prod.exs sets the root to “.”, which then causes all of the endpoints defined in the app to start at /. I’m basically looking for a way to dynamically change that root path.
Home Assistant provides a request header X-Ingress-Path that contains the root path that is actually used (e.g. /api/hassio_ingress/id_of_addon). As such, I’m looking a way to cause Phoenix to utilize that new root path in the artifacts that are generated.
I read about one possible solution of setting
X-Forwarded-Host to something like “localhost:8080/api/hassio_ingress/id_of_addon”. Would Phoenix process that in the way I’m looking for? If not, are there any other headers that Phoenix looks at that might cause it to change it’s root path?