dantodor
I’m trying to wrap my head around the endpoint configuration, especially in prod settings.
Generally I have something like this:
config :btest, BtestWeb.Endpoint,
url: [host: "localhost", port: 4480, scheme: "http"],
http: [
# Enable IPv6 and bind on all interfaces.
# Set it to {0, 0, 0, 0, 0, 0, 0, 1} for local network only access.
# See the documentation on https://hexdocs.pm/bandit/Bandit.html#t:options/0
# for details about using IPv6 vs IPv4 and loopback vs public addresses.
ip: {127, 0, 0, 1},
port: port
],
The idea is to have the Phoenix app behind an nginx load balancer, offloading the SSL handshake to it, I’d say not a very unusual set up if you want to run more than one app on the same server. I do care only about binding to localhost on a certain port and that’s that.
What I can’t understand: I can set the port variable to a different value than the one hardcoded in the url , let’s say 4481. The server goes up, but the messages are a little bit confusing:
[info] Running BtestWeb.Endpoint with Bandit 1.6.10 at 127.0.0.1:4481 (http)
[info] Access BtestWeb.Endpoint at http://localhost:4480
Actually, it listens on 4481 only.
So, my questions are:
- why do I need the port two times, and what parts of the Endpoint are configured via these two options? (I tried to look in the code with no success)
- In which specific situation I would need to provide a different value for the port in
httpand the one configured via the env variable?
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app?
Looking for hints regarding:
Addi...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
Hi all, I wanted to ask how the community is dealing with post-release steps.
Today we have Ecto migrations, which make sure that the db...
New
Hello,
I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance o...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
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
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










Showing Posts 1 to 4- Show Best Posts
- Show All Posts (oldest first)
- Show All Posts (newest first)
LostKobrakai
The http/https configuration is for where the endpoint will be listening.
The url config is for url generation wherever your phoenix app might do so. You likely want to use https there even if you listen on http (given nginx in front). With https and a default port the url port should also be 443.
dantodor
Is there any kind of doc for this?
LostKobrakai
These here following up on each other:
garrison
If you are terminating TLS at your reverse proxy and you want to force HTTPS note also the
Plug.SSLdocs which are linked by the above but easy to miss when scanning:Those messages do appear very confusing in your case. It’s much clearer when you have a domain configured, because it would say
Access ... at https://yourdomain.com:4480instead. The point being: if that was your nginx port, that really would be where you access the site! But it is not where the Phoenix endpoint is listening.