If your lease is closed, but your deployment isn't, that means your provider closed it. You will need to close your deployment and create a new one. You can try deploying on a different provider to see if that helps.
Here's some possible reasons why a provider could close your lease:
To know the exact cause you can try contacting your provider in the #provider discord channel.
There is a known issue where the shell access will stop working if the provider pod gets restarted. Here's two workarounds you can try:
Some docker images use "sh" as the default shell. This shell does not support up arrow and TAB autocompletion. You may try sending the "bash" command to switch to a bash shell which support those feature.
This commonly happen if you try to change the hardware specs of your deployment. For example, if you try to increase the amount of memory or cpu. If you need to change the hardware spec you will need to close your deployment and create a new one.
This can also happen if your deployment has multiple services and was created before the Mainnet 6 upgrade on August 31st, 2023. In this case, you will also need to close your deployment and create a new one.
Here are some actions you can take to fix most of the errors you may encounter:
If you still have an issue after taking these steps, please ask your question in the #ecosystem-cloudmos channel. If you have issue creating or updating a deployment, it can help to include your SDL. Make sure to remove any sensitive information from it before sharing (ex: secrets in your env variables).