Cloudmos will be moving to console.akash.network soon. Please try out Console and let us know if you run into any issues.

Cloudmos Logo

Frequently Asked Questions

My lease is closed, but the deployment isn't.

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:

  • Your docker image was not able to be downloaded or crashed on launch.
  • Your deployment was using more resources than what was specified in your sdl. For example, you used more disk space than allowed.
  • Your deployment did not meet the terms of service of the provider. Ultimately, each provider can choose what workload they allow.
  • The provider had to close your lease due to some outage or maintenance on their servers.

To know the exact cause you can try contacting your provider in the #provider discord channel.

Can't access shell: 'The connection to your Cloudmos Shell was lost.'

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:

  • You can try the "UPDATE DEPLOYMENT" button in the "UPDATE" tab of your deployment. Even without changing your SDL, this should temporarily restore the shell access.
    Update Deployment
  • A permanent solution would be to add your own ssh access to your deployment, here is an example SDL with ssh.

Shell: UP arrow and TAB autocompletion does not work

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.

Error while sending manifest to provider. Error: manifest cross-validation error: group "X": service "X": CPU/Memory resources mismatch for ID 1

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.

My issue is not listed

Here are some actions you can take to fix most of the errors you may encounter:

  • Change the selected node in the settings. Nodes are public services and can have outages and rate limiting.
    Change Node
  • Try using another provider. The provider may be misconfigured or suffering from an outage.
  • Wait a bit and try again later. Some problem are temporary and simply waiting a bit and trying again will work.

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).