A clear path to your server.

From plan to invoice

1. Choose a location and a plan. Select a compatible operating system and control panel.
2. Add the server to your cart and sign in with Google, or use email and password for an existing account. Phone and address are optional in the Google sign-in flow. If scripts cannot load, use the Basic checkout link on your plan.
3. Review the total prepaid amount, selected billing period, optional upgrades and service terms, then create your order.
4. Open My orders and continue from its invoice. The final invoice includes any applicable taxes or credits.

Your software selections stay attached to the order. Delivery begins after payment verification and depends on the selected service.

An empty cart can be normal.

The cart holds configurations you have not submitted yet. Once your order is saved, those items move to My orders and the draft cart clears.

Open the saved order to pay, see its invoice or cancel an eligible unpaid request. Avoid placing the same order again while its invoice is being checked.

Match the currency and network.

1. Open the invoice from My orders. Choose a method marked as available in that invoice's payment window.
2. USDT may be offered on different networks. Use only a network shown in your invoice's payment window. BTC uses Bitcoin mainnet, SOL uses Solana mainnet and native ETH uses Ethereum. Other methods are shown only when ready.
3. In your sending wallet, select the same currency and network. Native TRX, BNB and ETH do not pay an amount quoted in USDT.
4. Copy the receiving address and the exact amount, including its reference digits. The recipient must receive the exact invoice amount. If your wallet or exchange deducts a withdrawal/network fee from the amount sent, account for it before submitting the transfer. Never guess a fee or send on a network absent from your invoice. The exchange's minimum deposit is not the invoice amount.
5. Send within the payment window. Keep the transaction ID and wait for network confirmations. You can use the address QR or the payment QR; check the currency, network, amount and recipient in your wallet before sending.

When the payment window expires, checkout returns to method selection and keeps the same invoice. A transfer sent in time can still confirm later: check the invoice before paying again. A paid invoice, an order awaiting provisioning and a delivered server are separate states. Do not send a second transfer solely because the VPS has not been provisioned yet. If a method is unavailable or you sent a different amount, contact support with the invoice and transaction ID. Do not send a currency that is not offered on your invoice.

Pick a configuration that fits.

cPanel does not run on Windows. Windows with an offered Plesk image needs a compatible plan. Resource requirements and available images limit your choices; checkout explains an incompatible selection in one line.

Choose only offered, compatible software. Exact version and image availability depend on the supported installation template; contact support before payment if you need a particular version.

Versions depend on the provider’s supported images. OS and panel choices are recorded on the same WHMCS service. A public SSH-key field appears only where installation is configured.

Do not reinstall a server before copying any files you need to keep. Customer backups are not included; maintain tested copies of your data outside the VPS.

Connect after delivery.

Open your service details in the client area for the assigned IP address and access information.

For Linux, use your SSH client with ssh username@SERVER_IP. If a public key was installed, use its matching private key locally.

For Windows, enter the assigned IP in Remote Desktop and use the delivered account. Treat every server credential as private.

Send a useful support request.

Include your invoice or service number, the exact message and the time of the problem. For a payment question, include its network and transaction ID.

We help with network issues, provisioning, Windows and Linux, software installation, configuration and troubleshooting. Tickets are typically answered in under 60 minutes; this is not a guaranteed SLA.

A code beginning ZG- identifies a website error for support. Never send Google passwords, wallet recovery phrases, private keys or full server credentials in a general support message.

support@zagrosvps.com

Protect your data before expiry.

VPS access is disabled immediately when the paid term expires without renewal; the original server, IP address and stored data are not guaranteed afterwards. Continuing service after expiry requires a new service order. Maintain your own tested off-server backups, because data recovery after hardware or infrastructure failure is not guaranteed.

Provisioned VPS subscriptions are generally non-refundable. When a technical fault is on our side, support will investigate and work to resolve it; mandatory legal remedies remain applicable.