Upgrading rack destroyed it

[tech]

We upgraded from rack 20220427210019 to 20241112202208 and the rack is completely unreachable but the web app is still running. New ec2 instances were created by the rack upgrade, but now all convox commands (except convox racks) shows “ERROR: response status 502”

We tried to downgrade the rack back to 20220427210019 but it gives the same error. The web console suggests the rack is gone.

To be honest, it’s been a long time since we created this app and we didn’t anticipate that a rack upgrade would [apparently] destroy the rack.

Would appreciate any advice on this matter. I guess the next step would be to create a new rack and try to re-create our app from scratch… Thanks in advance.

[Nick-Convox]

Hey @tech,

In mid-2022, we updated the load balancers for v2 racks, which also involved updating the racks’ domain organization for our internal routing. This is the cause of the 502 errors you’re seeing with your Convox commands.

This update required certain backend workflows to be running on our side during the rack update, which we retired in 2024 as part of the new Console update. Apologies if you missed our previous messaging and warnings about this change.

If you haven’t already recreated the applications, I can manually assist with the move on our backend. I’ve also sent you an email to follow up further.