We are deploying apps using fly CLI, to SJC. Starting getting “ip allocation errors” during
deploy today. Following the instructions in the log, we use
fly ip allocate-v4 -a ... --shared. The remediation worked once, but not again. Possibly the first time remediation worked due to time delay only.
Doesn’t work means the app’s host’s 443 cannot be connected to.
% curl -I https://rxhtest-1689978287-crm-1689978287.fly.dev curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to rxhtest-1689978287-crm-1689978287.fly.dev:443
Any color on this? In our automation scripts that does
deploy, we may start to always run
fly ip allocate-v4 following
fly deploy - based on the CLI output, the command appears to be idempotent.
In any case, right now… even though fly ips list shows ipv4 and v6 entries, still cannot connect.
Wondering if other folks hitting this?
2023-07-21 15:40:27 [info ] [RX:twitter-1689979110] Failed to provision IP addresses, use `fly ips` commands to remmediate it. ERROR: error allocating ipv6 after detecting first deploy and presence of services: server returned a non-200 status code: 504 Machine 6e82dd3b265487 [app] was created 2023-07-21 15:40:27 [info ] [RX:twitter-1689979110] Finished launching new machines 2023-07-21 15:40:27 [info ] Ensure that fly IP allocation is good (just allocate-v4 again... idempotent) 2023-07-21 15:40:27 [info ] Running sys_run cmd=fly ip allocate-v4 -a rxhtest-1689979110-twitter-1689979110 --shared cwd=None label=_system timeout=5 2023-07-21 15:40:27 [info ] [RX:_system] VERSION IP TYPE REGION 2023-07-21 15:40:27 [info ] [RX:_system] v4 188.8.131.52 shared global