Proxy not recognising healthy instance

1

Hi there,

I have an app with a single instance (I’m aware of the limitations of single instance apps) and the proxy keeps refusing to send requests claiming that there are no healthy instances but the healthchecks on the instance is passing. Redeploying seems to fix it for a few requests but then stops working. It seems nothing I do convinces the proxy that the instance is healthy.

2023-04-26T04:43:10.691 proxy[6e82dd0ea11487] syd [warn] Failed to proxy HTTP request (error: no known healthy instances found for route tcp/443. (hint: is your app shutdown? is there an ongoing deployment with a volume or using the 'immediate' strategy? if not, this could be a delayed state issue)). Retrying in 1000 ms (attempt 80)

Here’s the fly.toml

app = "[REDACTED]"
kill_signal = "SIGINT"
kill_timeout = 5
primary_region = "syd"  # See a list of regions here: https://fly.io/docs/reference/regions/

[experimental]
    auto_rollback = true
    private_network = true  # Allows Coder to connect to the database

[build]
     image = "ghcr.io/coder/coder:latest"

[env]
    CODER_ACCESS_URL = "[REDACTED]"
    CODER_HTTP_ADDRESS = "0.0.0.0:3000"
    #CODER_VERBOSE = "true" # Uncomment this if you want to see more logs
    CODER_TELEMETRY_INSTALL_SOURCE = "fly.io"

[[services]]
    protocol = "tcp"
    internal_port = 3000
    processes = ["app"]

    [[services.ports]]
        port = 80
        handlers = ["http"]
        force_https = true

    [[services.ports]]
        port = 443
        handlers = ["tls", "http"]

    [services.concurrency]
        type = "connections"
        hard_limit = 25

    [[services.tcp_checks]]
        grace_period = "1s"
        interval = "15s"
        restart_limit = 4
        timeout = "2s"

Any ideas?

2

Contacted fly.io support and determined that it was due to the hard limit being reached. Increasing the hard limit fixed the issue. Thanks Brian!

3

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