Flycast unavailable after removing public IPs?

Questions / Help
1

Hi, I’ve tried to reach an appname.flycast address from postman or another app in the same org, and I’m seeing connection refused and connection reset errors. I’ve redeployed after removing public ip’s and reassigning a private ipv6. appname.internal resolves fine. Relevant sections of my fly.toml:

[[services]]
  force_https = false
  internal_port = 8080
  auto_stop_machines = true
  auto_start_machines = true
  min_machines_running = 1

[[vm]]
  cpu_kind = "shared"
  cpus = 1
  memory_mb = 1024

Could this be because I had public ips and certificates assigned before assigning the private v6?

1 Like
2

Hi… I don’t think so; I’ve converted an app that originally had public IPs over to being Flycast-only and didn’t encounter any problems.

The fly.toml snippet that you posted is missing the mandatory services.ports section, though.

(My own just sticks with http_service, and it’s accessible on port 80 via Flycast—not on the internal_port.)

Hope this helps!

3

Ohhh yep, just sloppy…force_https is totally the wrong section. Thanks for helping! :melting_face:

4

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