I’m trying to deploy my app but I’m getting this: **
Uh oh, deployment failed**
Your deployment failed, you might want to read the logs and check if there’s something you need to change in your repo or if you just need a new retry.
The deployment does not get to the Build Image step and I can’t seem to find a place where there would be any sort of log message that says what went wrong. Please advise how I can determine what is causing the build failure.
Is there anything to be found in https://fly.io/apps/{your-app}/monitoring?
Do you have a Dockerfile and a fly.toml in your project root?
There is nothing new posted in the logs during the deploy. Those logs only show running machines, not anything from the deploy machine.
I have toml in config/fly/staging.toml and I have a Dockerfile at config/docker/Dockerfile. The staging.toml references this Dockerfile, and I have also saved the toml configuration to the app itself on fly. Also, when I deploy from CLI, it works fine. It breaks when I use the ‘deploy’ button in the UI, but gives no reason why
At a guess, the config/fly/staging.toml can’t be found by the automatic deployer; it’s expecting fly.toml in the root. Deploying from the CLI works because you can use --config to point to your .toml file.
If you want a more automatic deployment, I’d suggest wiring it up to CI. My main app deploys when I merge to main, using CircleCI.
Then what is the point of the field that says “Config path”
Hey @jnankin, taking a look at the logs from our end, the deploy was indeed hitting an error pulling the config specified.
message":"unsuccessful command 'flyctl config show --local --config config/fly/staging.toml'","exit_code":1,
You mentioned that a local flyctl run succeeds. If you run that same flyctl config show --local --config config/fly/staging.toml command from the root of your repo, does it return the config successfully?
It might just be a misconfigured toml location in the UI deployer, or you might need to explictly set a working directory as well as the toml location.
yes it returns the config successfully.
Hey @jnankin, I was able to replicate the issue you’re having on my own app and i’ll raise this to get fixed internally, sorry about that!
It seems it’s specific to using our dashboard to deploy using a custom fly.toml path but I was successfully able to deploy using fly deploy --config config/fly/staging.toml locally within my test repo. Otherwise @halfer’s suggestion to perform deployments via CI is also a valid way to do this.
We’ll let you know once we have an update 
Hey @jnankin, good news!
We’ve released a change that brings the deployer errors up in the Launch UI. I’ve tested it with the app that I was replicating the issue on and it showed me the error which then helped me work out what was wrong with my setup.
Feel free to reach out of you’d like any further help.