I used to just run e. g. `fly console –vm-memory 768` and it spun up a machine and connected to it. Since a few days, it spins up a machine and apparently connects, but I don’t get a console at all.
```
$ fly console --vm-memory 768
Created an ephemeral machine 080e525a25d9e8 to run the console.
Connecting to fdaa:24:b14e:a7b:13c:f4ad:a6ac:2… complete
```
It just hangs there and does not respond to any inputs. The logs in the dashboard also only show “Waiting for logs…”. Does anybody else encountered this and has a solution, or a few pointers on how to debug this?
Hm… There really should be at least a few logs, since the ephemeral Machine clearly did boot…
The historical logs don’t always display correctly, so it’s best to start fly logs in a separate terminal and leave it running in there the whole time.
I would also increase RAM, since this might just be OOM.
A few other things that have been useful to people in the past:
Use --image to select an older image, from back when it definitely was working for you. (You can see the history via fly releases --image.)
Use the lower-level fly m run <image> --shell, which gives you more control. It will drop you into Bash, rather than immediately into the console_command from fly.toml.
Use the --region flag to put things in a different region.
Try fly ssh console on an existing, non-ephemeral Machine, just to test whether it yields a Bash prompt at all. (You will need to ensure that at least one such Machine is already running, beforehand.)