why I can't reach my app through domain and ip

i have an golang app that listens I can see that in logs

 http server started on [::]:8080

my config.toml

app = "misty-sunset-7756"
kill_signal = "SIGINT"
kill_timeout = 5
processes = []

  allowed_public_ports = []
  auto_rollback = true

  http_checks = []
  internal_port = 8080
  processes = ["app"]
  protocol = "tcp"
  script_checks = []
    hard_limit = 25
    soft_limit = 20
    type = "connections"

    force_https = true
    handlers = ["http"]
    port = 80

    handlers = ["tls", "http"]
    port = 443

    grace_period = "1s"
    interval = "15s"
    restart_limit = 0
    timeout = "2s"

However, when I click misty-sunset-7756.fly.dev I can’t reach my app. I assigned ip (v6) to that machine and I am still having same problem. I saw another post that mentions domain resolving issues but that seem to be gone by now. How can I debug this issue?

Possibly due to Fly.io Status - DNS resolution failures for fly.dev

Does accessing it via the assigned IP directly work?

@jerome thanks for your answer, I created ipv4 and ipv6 so I should be able to reach them through ip at this stage without setting custom domain?

Not via https. We don’t handle TLS without a SNI.

Since the http handle forces an https redirect by default, this can be hard to test with the IP.

Looks like it’s working now.

@jerome thanks for the update, I am tryig to setup custom domain now. I followed these steps

I am getting strange error when I do this

A Record ( does not match app's IP (<assigned v4>
AAAA Record (2606:4700:3031::ac43:cfb9) does not match app's IP (<assigned v6>)

I also added acme challenge to my subdomain but it doesn’t seem to verify certificate. Is it possible for you to guide me ? → is cloud flare’s I am using CF to resolve domain but I want to point out subdomain to point out fly VM

I figure this one out. You need to disable CF proxy.