Flycast issue - Can't find myaddress.flycast: No answer

Hey there,

I remember I had it working but anyway, now I’m trying to use flycast, it doesn’t work anymore.

Steps I followed:

1) Fly deploy

Updating existing machines in 'myaddress' with rolling strategy

-------
 ✔ Cleared lease for ......
-------
Checking DNS configuration for myaddress.fly.dev

Visit your newly deployed app at https://myaddress.fly.dev/

2) listing IP

$ fly ips list 
VERSION IP                      TYPE    REGION  CREATED AT        
v6      fdaa:9:a154:0:1::3      private global  Aug 31 2024 14:58

3) fly machine run --shell ubuntu

root@6830749c111038:/# nslookup myaddress.flycast
Server:         fdaa::3
Address:        fdaa::3#53

*** Can't find myaddress.flycast: No answer

4) This is fly.toml

app = 'myaddress'
primary_region = 'ams'

[build]

[http_service]
  internal_port = 8080
  # must be false - Flycast is http-only
  force_https = false
  # Fly Proxy stops Machines based on traffic
  auto_stop_machines = "stop"
  # Fly Proxy starts Machines based on traffic
  auto_start_machines = true
  # Number of Machines to keep running in primary region
  min_machines_running = 0
  processes = ['app']

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

I don’t see any sign my app getting called when calling from another machine http://myaddress.flycast address , just getting error and also the manual way I mentioned above also not working.

Any idea what’s wrong?

Hm… What you have there should be working, :umbrella:. How about the following?

$ fly dig myaddress.flycast
$ fly dig myaddress.internal  # merely for comparison
$ fly services list
$ fly machine run --shell ubuntu
# apt-get update
# apt-get install --no-install-recommends curl
# curl -i 'http://myaddress.internal:8080/'
# curl -i 'http://[fdaa:9:a154:0:1::3]/'

If all else fails, I think I would release the old Flycast address and allocate a new one, although that really shouldn’t be necessary…

Hope this helps a little!

Added proxy

Thanks for the answer!

Both first commands have kinda similar answer except the id

;; opcode: QUERY, status: NOERROR, id: 32112
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;myaddress.flycast.   IN       AAAA (1)
;myaddress.internal.  IN       AAAA (2)
fly services list
Services
PROTOCOL        PORTS           HANDLERS        FORCE HTTPS     PROCESS GROUP   REGIONS MACHINES 
TCP             80 => 8080      [HTTP]          False           app             ams     1       
TCP             443 => 8080     [HTTP,TLS]      False           app             ams     1

Last two curl result in error
Couldn't connect to server

Then I guess releasing is the only way.

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