Why, even though I have configured http_service.internal_port, am I still getting the warning "app is not listening on the expected address"

1

Why, even though I have configured http_service.internal_port, am I still getting the warning “WARNING The app is not listening on the expected address and will not be reachable by fly-proxy. You can fix this by configuring your app to listen on the following addresses:”?

image
image822×786 50.1 KB

2

share full toml file?

3 
# fly.toml app configuration file generated for fitment-tool on 2024-05-16T13:50:56+08:00
#
# See https://fly.io/docs/reference/configuration/ for information about how to use this file.
#

app = 'f***l'
primary_region = 'nrt'

[build]

[env]
  HOST = '0.0.0.0'
  PORT = '8081'
  SCOPES = 'write_products'
  SHOPIFY_APP_URL = 'https://fi***l.fly.dev'

[http_service]
  internal_port = 8081
  force_https = true
  auto_stop_machines = true
  auto_start_machines = true
  min_machines_running = 1
  processes = ['app']

[scale]
  count = 1

[[vm]]
  memory = '1gb'
  cpu_kind = 'shared'
  cpus = 1
4

Looks good, how about Dockerfile?
maybe the HOST/PORT env is screwing w/ the fly infra? I usually put those env in my Dockerfile

5

That warning happens when the app process isn’t listening on port 8081, it actually checks within the VM.

This is usually because it’s listening on 127.0.0.1, it needs to be listening on 0.0.0.0 for our proxy to be able to access it.

6

Is this because of an update from fly.io? The issue suddenly started from yesterday.

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.