A tip: If you compile flyctl yourself, such failing commands should then print the actual stack trace. There’s a bunch of nil references that trip the code up, which are quick fixes.
I think, flyctl should have a switch, say -vv, to show underlying errors. I mean, flyctl users are all developers, anyway.