Provisioning

Beta

Create a VPS using the options offered in your hosting provider's panel. Available controls depend on the installed PteroCloud release, your plan and the provider. If an option is missing, ask your provider whether it is supported for your account.

Before You Start

• Check the plan's CPU, memory, disk space and included network access.
• Choose a location that offers the operating system you need.
• Check the image's minimum disk size and default login username.
• Have your SSH public key ready if key-based access is offered.

See Images for image selection and SSH Access for keys and usernames.

Creating a VPS

1. Enter a recognizable name and, if requested, a hostname.
2. Select an available plan and location.
3. Choose an operating system compatible with the selected resources.
4. Select your SSH public key or another login method offered by the provider.
5. Review the selections before submitting the request once.
6. Wait for the panel to report the result before attempting another action.

Do not upload a private SSH key. Keep it on your own device. If your release shows operation progress, use it to check the request; see Tasks.

Cloud-Init

Some images use Cloud-Init for first-boot setup. Allow that setup to finish before changing the guest's network or login configuration. Follow the selected image's instructions rather than assuming every image uses the same defaults.

Record the displayed username, assigned address and SSH port. The VPS login can differ from your panel account, and the username is not always root.

Generated Passwords

If a password is displayed, store it securely in a password manager. Do not assume it will remain available to view later. Never include passwords in public screenshots, logs or support messages.

After Creation

Check that the panel reports the VPS as running before connecting. Use SSH or an enabled console to verify access. Install operating system updates and configure only the services you need.

Use the power actions your panel offers, and prefer a normal shutdown over a forced stop. A forced stop can interrupt writes and damage application data.

Failed Provisioning

If creation fails or remains pending, do not repeatedly submit the same request. Check the visible error and any service notices from your hosting provider. Do not assume that a failed request left no instance behind; ask the provider to confirm before ordering again.

For help, see Troubleshooting. Send your hosting provider the instance name, selected image and location, time of the request and redacted error text. Keep credentials and unrelated customer information out of diagnostics.