Failed due to unhealthy allocations - Rails

Questions / Help
1 
--> release v5 created

--> You can detach the terminal anytime without stopping the deployment
==> Release command detected: bin/rails fly:release

--> This release will not be available until the release command succeeds.
	 Starting instance
	 Configuring firecracker
	 Starting init (commit: 249766e)...
	 no label, UUID=260c84d3-ac54-44a1-a777-040afe46750c
	 Preparing to run: `bin/rails fly:release` as root
	 Starting clean up.
	 Starting instance
	 Configuring firecracker
	 Starting init (commit: 249766e)...
	 no label, UUID=260c84d3-ac54-44a1-a777-040afe46750c
	 Preparing to run: `bin/rails fly:release` as root
	 Starting clean up.
==> Monitoring deployment

 1 desired, 1 placed, 0 healthy, 1 unhealthy
--> v5 failed - Failed due to unhealthy allocations - no stable job version to auto revert to and deploying as v6

This is very confusing and frustrating. There are no indications in the logs about why there are no healthy allocations. I cannot deploy anything to repair this condition. What is the expected next step?

2

fly status, etc:

App
  Name     = faxjar          
  Owner    = personal        
  Version  = 5               
  Status   = running         
  Hostname = faxjar.fly.dev  
  Platform = nomad           

Deployment Status
  ID          = 1887e7e2-6366-6259-1112-31f6f3b8f77a                                           
  Version     = v5                                                                             
  Status      = failed                                                                         
  Description = Failed due to unhealthy allocations - no stable job version to auto revert to  
  Instances   = 1 desired, 1 placed, 0 healthy, 1 unhealthy                                    

Instances
ID      	PROCESS	VERSION	REGION	DESIRED	STATUS  	HEALTH CHECKS      	RESTARTS	CREATED   
10742a86	app    	5 ⇡    	iad   	run    	running 	1 total, 1 critical	0       	1h35m ago	
4dec8bca	app    	1      	iad   	stop   	failed  	1 total, 1 critical	2       	1h40m ago	
22c9131a	app    	0      	iad   	stop   	complete	                   	1       	1h35m ago	
dbddc7cb	app    	0      	iad   	stop   	failed  	1 total, 1 critical	2       	1h39m ago	
5f4422fc	app    	0      	iad   	stop   	failed  	1 total, 1 critical	4       	1h48m ago	

jdjeffers@dq2xxx:~/faxjar$ fly vm status 10742a86
Instance
  ID            = 10742a86             
  Process       = app                  
  Version       = 5                    
  Region        = iad                  
  Desired       = run                  
  Status        = running              
  Health Checks = 1 total, 1 critical  
  Restarts      = 0                    
  Created       = 1h38m ago            

Events
TIMESTAMP           	TYPE           	MESSAGE                                                  
2022-09-24T12:16:39Z	Received       	Task received by client                                 	
2022-09-24T12:16:39Z	Task Setup     	Building Task Directory                                 	
2022-09-24T12:16:43Z	Started        	Task started by client                                  	
2022-09-24T12:21:39Z	Alloc Unhealthy	Task not running for min_healthy_time of 10s by deadline	
2022-09-24T12:27:31Z	Alloc Unhealthy	Task not running for min_healthy_time of 10s by deadline	
2022-09-24T13:36:39Z	Alloc Unhealthy	Task not running for min_healthy_time of 10s by deadline	
2022-09-24T13:49:30Z	Alloc Unhealthy	Task not running for min_healthy_time of 10s by deadline	

Checks
ID                              	SERVICE 	STATE   	OUTPUT                                                   
3df2415693844068640885b45074b954	tcp-8080	critical	dial tcp 172.19.10.114:8080: connect: connection refused	

Recent Logs
111