Shared IPv4 stuck at “Jan 1 0001” and not attaching to Machines

Questions / Help
1

Hi all,

My app is unable to attach a shared IPv4 address. Every IPv4 I allocate shows a creation timestamp of “Jan 1 0001 00:00” and never binds to any machine. As a result, the app is unreachable over IPv4.

This breaks inbound TCP/TLS connections (in my case, Telnyx media WebSocket connections). IPv6 works, but Telnyx requires IPv4.

What I’ve tried:

  • Released all IPv4s
  • Allocated new shared IPv4s
  • Restarted machines
  • Stopped and started machines
  • Destroyed and recreated machines
  • Redeployed the app
  • Ensured only one machine is running

The IPv4 always appears in fly ips list but with the “Jan 1 0001” timestamp, which indicates it is not attached at the data-plane level.

Current state:

  • App: piperlocal-media
  • Region: fra
  • Machines: 2871700a4e36d8 (running)
  • IPv4: 66.241.124.123 (shared, but stuck at Jan 1 0001)

It looks like a ghost IPv4 / ghost machine routing issue in the control plane. Could you please reset the IPv4 assignment for this app or rebind the IPv4 to the active machine?

Thank you!

2

shared IPs are handled a little differently in the platform and the zero timestamp shown is correct. if I dig piperlocal-media.fly.dev I do get the shared IP address; if I curl -4 piperlocal-media.fly.dev I get a response from your app.
what is the exact error message received on your client when you try to connect via ipv4?

3

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