Category: Getting Started
- An active Nesva account with verified email access.
- A valid payment method added in the billing section.
- Target workload requirements (CPU, RAM, storage, and region).
- SSH public key ready if you plan to use key-based login.
- Log in to cloud.nesva.net and switch to the project you will use for deployment.
- Open billing and confirm account balance or payment method status is healthy.
- Review quota limits for instances, IPs, and storage in your dashboard account area.
- Upload your SSH public key in the access or key management area.
- Create a naming convention for instances (for example: env-role-region-number).
- Collect required application ports and DNS names before provisioning.
- Billing page shows active payment method and no account blocks.
- SSH key appears in your key list and is selectable in deploy flow.
- You can identify your target project and region before clicking deploy.
- Skipping SSH key setup and then needing password reset steps later.
- Deploying in the wrong project or region due to no naming standard.
- Ignoring quota limits and failing at the final provisioning step.