dantodor

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 http and the one configured via the env variable?

Showing Posts 1 to 4

LostKobrakai

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

dantodor OP

Is there any kind of doc for this?

garrison

garrison

If you are terminating TLS at your reverse proxy and you want to force HTTPS note also the Plug.SSL docs 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:4480 instead. 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.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
ryanwinchester
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted” Version...
New

Other Trending Topics Top

JesseHerrick
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
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews