UDP app no longer working?

Questions / Help
1

Hey - I have been running a DNS server on Fly for a long time, but this morning it suddenly seems to have stop working? these listeners haven’t changed:

# netstat -pal
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 3d8d7947f1e908:domain   0.0.0.0:*               LISTEN      665/coredns
tcp        0      0 fly-global-servi:domain 0.0.0.0:*               LISTEN      665/coredns
tcp6       0      0 3d8d7947f1e908:domain   [::]:*                  LISTEN      665/coredns
tcp6       0      0 [::]:2020               [::]:*                  LISTEN      659/image.binary
tcp6       0      0 fly-local-6pn:domain    [::]:*                  LISTEN      665/coredns
tcp6       0      0 fly-local-6pn:ssh       [::]:*                  LISTEN      640/hallpass
tcp6       0      0 [::]:8888               [::]:*                  LISTEN      659/image.binary
tcp6       0      0 [::]:20202              [::]:*                  LISTEN      639/litefs
tcp6       0      0 172.19.5.122:8888       172.19.5.121:45410      TIME_WAIT   -
tcp6       0      0 172.19.5.122:8888       172.19.5.121:59582      TIME_WAIT   -
tcp6       0      0 172.19.5.122:8888       172.19.5.121:47672      TIME_WAIT   -
tcp6       0      0 172.19.5.122:8888       172.19.5.121:62634      TIME_WAIT   -
tcp6       0      0 172.19.5.122:8888       172.19.5.121:47664      TIME_WAIT   -
tcp6       0      0 172.19.5.122:8888       172.19.5.121:61144      TIME_WAIT   -
tcp6       0      0 172.19.5.122:8888       172.19.5.121:62620      TIME_WAIT   -
tcp6       0      0 172.19.5.122:8888       172.19.5.121:61152      TIME_WAIT   -
tcp6       0      0 172.19.5.122:8888       172.19.5.121:45406      TIME_WAIT   -
tcp6       0      0 172.19.5.122:8888       172.19.5.121:62368      TIME_WAIT   -
tcp6       0      0 172.19.5.122:8888       172.19.5.121:59592      TIME_WAIT   -
tcp6       0    632 fly-local-6pn:ssh       fdaa:2:9fa2:a7b:8:62324 ESTABLISHED 640/hallpass
tcp6       0      0 fly-local-6pn:50610     908061eec60078.vm:20202 ESTABLISHED 639/litefs
tcp6       0      0 172.19.5.122:8888       172.19.5.121:62382      TIME_WAIT   -
udp        0      0 fly-global-servi:domain 0.0.0.0:*                           665/coredns
udp        0      0 3d8d7947f1e908:domain   0.0.0.0:*                           665/coredns
udp6       0      0 3d8d7947f1e908:domain   [::]:*                              665/coredns
udp6       0      0 fly-local-6pn:domain    [::]:*                              665/coredns

and using the eth0 address, I can successfully get a reply. however, if I hit the public ipv4 address it no longer works.

I believe I followed the directions here when I first wrote this app as the listeners above show. did something change about how UDP apps work on Fly?

2

Same here, it’s not just you.

3

Hi all, we have opened a status page for this incident and will post further updates there: Fly.io Status - UDP service issues

1 Like
4

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