# Welcome ## Welcome to PreVPS This is the documentation hub for **PreVPS**. Use it to get started fast, manage your services, and troubleshoot common issues. ### Documentation
TitleLink
Products/spaces/laEWHyEhXmGEBBoSUuh5/pages/sOnjpxV8q1AVGA8BpFTL
Domains/spaces/laEWHyEhXmGEBBoSUuh5/pages/wimBupRqd3jyQz0KAc9R
Billing + Client Area/spaces/laEWHyEhXmGEBBoSUuh5/pages/yFgUm5Z6bWwJHVKn5x22
Guides/spaces/laEWHyEhXmGEBBoSUuh5/pages/njeWajsgTMVXnuGgyBPV
Resources (Announcements + Knowledge Base)/spaces/laEWHyEhXmGEBBoSUuh5/pages/649if3Fd5WZmEpf2wOr5
### Products #### VPS * [SSD VPS](https://prevps.com/ssd-vps/) * [n8n VPS](https://prevps.com/n8n-vps/) * [SSD Arm64 Linux VPS](https://prevps.com/ssd-arm64-linux-vps/) #### Dedicated Server * [Dedicated Server Windows with Android Emulator](https://prevps.com/vps-windows-with-android-emulator/) * [Dedicated GPU Server](https://prevps.com/dedicated-gpu-server/) #### Android Emulator (Dedicated) * [NoxPlayer](https://prevps.com/server-run-noxplayer/) * [Bluestacks](https://prevps.com/server-run-bluestack/) * [MEmu](https://prevps.com/server-run-memu/) * [LDPlayer](https://prevps.com/server-run-ldplayer/) #### Domain * [Register a new domain](https://prevps.com/clients/cart.php?a=add\&domain=register) * [Transfer a domain](https://prevps.com/clients/cart.php?a=add\&domain=transfer) #### Website & security * [VPN (NordVPN)](https://prevps.com/clients/index.php?rp=/store/nordvpn) * [SSL certificates](https://prevps.com/clients/index.php?rp=/store/ssl-certificates) Go to prevps.com Open Client Area # SSD VPS Getting started with PreVPS SSD VPS. ## SSD VPS **Order:** SSD VPS is a Linux virtual server backed by SSD storage. Manage it in the Client Area. You can also SSH directly into the server. ### Key features in the Client Area You’ll typically see these sections: * **Server Information**: hostname, status, specs, location, IPv4/IPv6, initial user/pass. * **Quick Actions**: reboot, power off. * **Console**: use the console when SSH fails. * **Firewalls**: allow/deny inbound rules by port. * **ISO Images**: mount an ISO to install a custom OS. * **Rebuild**: reinstall the OS. * **Rescue Mode**: boot into a rescue environment. * **Backups**: manage backups (if your plan includes them). * **Snapshots**: create manual point-in-time snapshots. * **View Server Metrics**: CPU/RAM/disk/network usage charts. * **Primary IP Address**: IP info, blocked status, reverse DNS (PTR). {% hint style="warning" %} Actions like **Rebuild** and **Restore** can erase data. Always create a backup or snapshot first. {% endhint %} ### Quickstart {% stepper %} {% step %} ### 1) Get access details 1. Check your provisioning email. 2. Open the Client Area. 3. Open your **SSD VPS** service. Keep these details: * IPv4 (or hostname) * Username (usually `root`) * Initial password Client Area: {% endstep %} {% step %} ### 2) SSH into the server {% tabs %} {% tab title="macOS / Linux" %} ```bash ssh root@YOUR_SERVER_IP ``` {% endtab %} {% tab title="Windows" %} Use Windows Terminal (OpenSSH) or PuTTY. Host: `YOUR_SERVER_IP`. User: `root`. {% endtab %} {% endtabs %} {% endstep %} {% step %} ### 3) Minimum day-one setup * Change the default password. * Update OS packages. * Add an SSH key. * Disable password login if possible. * Enable a firewall and open only required ports. {% endstep %} {% endstepper %} ### Manage your VPS (Server Management) #### Server Information Use this to quickly copy your server details: * **Hostname**: server name. * **Status**: Running / Stopped. * **Server type**: vCPU, RAM, SSD. * **Location**: datacenter location. * **IPv4 / IPv6**: access addresses. * **Username / Password**: initial login details. {% hint style="info" %} The password shown in the portal is the initial password. Change it right after your first login. {% endhint %} #### Quick Actions: Reboot / Power Off * **Reboot Server**: restart the server. * **Power Off**: power off the server. Use this if the server is stuck. It’s also common after a kernel update. {% hint style="warning" %} Powering off can corrupt data during disk writes. Shut down from the OS first when possible. {% endhint %} #### Console Console is useful when: * SSH is blocked by a firewall rule. * Networking is broken. * You misconfigured the SSH daemon. Open the console, then fix the issue from inside the server. #### Firewalls Use this to control inbound traffic. Start with an allowlist of ports you need. Common ports: * SSH: `22` * HTTP: `80` * HTTPS: `443` {% hint style="danger" %} Don’t block SSH before you have console access. You can lock yourself out. {% endhint %} #### ISO Images ISO lets you boot from an image. Use it when you need a custom OS install. Typical workflow: 1. Mount the ISO. 2. Reboot the server. 3. Open Console and run the installer. #### Rebuild (reinstall OS) Rebuild reinstalls the operating system from scratch. This usually wipes disk data. Use Rebuild when: * The OS is badly broken. * You want to switch distros. * You want a clean slate. #### Rescue Mode Rescue mode boots into a recovery environment. Use it to recover data or fix boot issues. Common cases: * Wrong network configuration. * GRUB issues. * Full disk. #### Backups If your plan includes backups, you can: * Enable a backup schedule. * View the backup list. * Restore when needed. {% hint style="info" %} Backups and snapshots are different. Snapshots are best right before risky changes. {% endhint %} #### Snapshots Snapshots are point-in-time images of your VPS. Create one before: * Major updates. * App upgrades. * Firewall or network changes. #### View Server Metrics Metrics help you decide whether you need an upgrade. Track: * CPU usage * RAM usage * Disk usage / IOPS (if available) * Network traffic Related: * [Upgrades and downgrades](/billing-+-client-area/upgrades-and-downgrades) ### Primary IP Address + Reverse DNS (PTR) In the IP section, you’ll see: * IP address * Blocked status * Reverse DNS (PTR) * **Edit** and **Reset** buttons PTR is often required for mail servers. It can also improve IP trust with some services. {% hint style="warning" %} PTR should point to a hostname you control. That hostname should resolve back to the same IP. {% endhint %} ### If you can’t access the server Try in this order: 1. Check the status is **Running**. 2. Reboot using Quick Actions. 3. Use **Console** to check SSH and firewall rules. 4. Confirm your firewall allows SSH (port `22`). See also: * [Troubleshooting checklist](/support/troubleshooting-checklist) ### Need help Open a ticket and include: * Server IP * When the issue started * Screenshots (if any) * Logs or the exact error message Links: * Knowledge Base: * Support: # n8n VPS Run n8n reliably on a VPS. ## n8n VPS **Order:** ### Related guide * [Access and set up your n8n VPS](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/BoDPxozpgQ40q0BzU95a) ### What this is for Use this plan to host **n8n** automations on your own server. ### Typical setup (high level) * Install n8n (commonly via Docker). * Put it behind a reverse proxy (Nginx / Caddy) with HTTPS. * Persist data to disk. {% hint style="warning" %} If you expose n8n to the public internet, protect it. Use HTTPS and strong auth. {% endhint %} ### Key features in the Client Area You’ll typically see these sections: * **Server Information**: hostname, status, specs, location, IPv4/IPv6, initial user/pass. * **Quick Actions**: reboot, power off. * **Console**: use the console when SSH fails. * **Firewalls**: allow/deny inbound rules by port. * **ISO Images**: mount an ISO to install a custom OS. * **Rebuild**: reinstall the OS. * **Rescue Mode**: boot into a rescue environment. * **Backups**: manage backups (if your plan includes them). * **Snapshots**: create manual point-in-time snapshots. * **View Server Metrics**: CPU/RAM/disk/network usage charts. * **Primary IP Address**: IP info, blocked status, reverse DNS (PTR). {% hint style="warning" %} Actions like **Rebuild** and **Restore** can erase data. Always create a backup or snapshot first. {% endhint %} ### Quickstart {% stepper %} {% step %} ### 1) Get access details 1. Check your provisioning email. 2. Open the Client Area. 3. Open your **n8n VPS** service. Keep these details: * IPv4 (or hostname) * Username (usually `root`) * Initial password Client Area: {% endstep %} {% step %} ### 2) SSH into the server {% tabs %} {% tab title="macOS / Linux" %} ```bash ssh root@YOUR_SERVER_IP ``` {% endtab %} {% tab title="Windows" %} Use Windows Terminal (OpenSSH) or PuTTY. Host: `YOUR_SERVER_IP`. User: `root`. {% endtab %} {% endtabs %} {% endstep %} {% step %} ### 3) Minimum day-one setup * Change the default password. * Update OS packages. * Add an SSH key. * Disable password login if possible. * Enable a firewall and open only required ports. {% endstep %} {% endstepper %} ### Manage your VPS (Server Management) #### Server Information Use this to quickly copy your server details: * **Hostname**: server name. * **Status**: Running / Stopped. * **Server type**: vCPU, RAM, SSD. * **Location**: datacenter location. * **IPv4 / IPv6**: access addresses. * **Username / Password**: initial login details. {% hint style="info" %} The password shown in the portal is the initial password. Change it right after your first login. {% endhint %} #### Quick Actions: Reboot / Power Off * **Reboot Server**: restart the server. * **Power Off**: power off the server. Use this if the server is stuck. It’s also common after a kernel update. {% hint style="warning" %} Powering off can corrupt data during disk writes. Shut down from the OS first when possible. {% endhint %} #### Console Console is useful when: * SSH is blocked by a firewall rule. * Networking is broken. * You misconfigured the SSH daemon. Open the console, then fix the issue from inside the server. #### Firewalls Use this to control inbound traffic. Start with an allowlist of ports you need. Common ports: * SSH: `22` * HTTP: `80` * HTTPS: `443` {% hint style="danger" %} Don’t block SSH before you have console access. You can lock yourself out. {% endhint %} #### ISO Images ISO lets you boot from an image. Use it when you need a custom OS install. Typical workflow: 1. Mount the ISO. 2. Reboot the server. 3. Open Console and run the installer. #### Rebuild (reinstall OS) Rebuild reinstalls the operating system from scratch. This usually wipes disk data. Use Rebuild when: * The OS is badly broken. * You want to switch distros. * You want a clean slate. #### Rescue Mode Rescue mode boots into a recovery environment. Use it to recover data or fix boot issues. Common cases: * Wrong network configuration. * GRUB issues. * Full disk. #### Backups If your plan includes backups, you can: * Enable a backup schedule. * View the backup list. * Restore when needed. {% hint style="info" %} Backups and snapshots are different. Snapshots are best right before risky changes. {% endhint %} #### Snapshots Snapshots are point-in-time images of your VPS. Create one before: * Major updates. * App upgrades. * Firewall or network changes. #### View Server Metrics Metrics help you decide whether you need an upgrade. Track: * CPU usage * RAM usage * Disk usage / IOPS (if available) * Network traffic Related: * [Upgrades and downgrades](/billing-+-client-area/upgrades-and-downgrades) ### Primary IP Address + Reverse DNS (PTR) In the IP section, you’ll see: * IP address * Blocked status * Reverse DNS (PTR) * **Edit** and **Reset** buttons PTR is often required for mail servers. It can also improve IP trust with some services. {% hint style="warning" %} PTR should point to a hostname you control. That hostname should resolve back to the same IP. {% endhint %} ### If you can’t access the server Try in this order: 1. Check the status is **Running**. 2. Reboot using Quick Actions. 3. Use **Console** to check SSH and firewall rules. 4. Confirm your firewall allows SSH (port `22`). See also: * [Troubleshooting checklist](/support/troubleshooting-checklist) ### Recommended next reads * Knowledge Base: * Announcements: # SSD Arm64 Linux VPS ARM64 VPS notes, compatibility, and setup. ## SSD Arm64 Linux VPS **Order:** ### Overview This is a Linux VPS running on **ARM64** CPU. ARM64 is great for: * Modern Linux distros * Multi-arch Docker images * Cost-efficient compute ### Compatibility notes * Not every prebuilt binary supports ARM64. * Some Docker images are x86\_64-only. * If you compile from source, ARM64 is usually fine. ### Getting access 1. Get your IP and credentials from the provisioning email. 2. SSH into the server. ### Key features in the Client Area You’ll typically see these sections: * **Server Information**: hostname, status, specs, location, IPv4/IPv6, initial user/pass. * **Quick Actions**: reboot, power off. * **Console**: use the console when SSH fails. * **Firewalls**: allow/deny inbound rules by port. * **ISO Images**: mount an ISO to install a custom OS. * **Rebuild**: reinstall the OS. * **Rescue Mode**: boot into a rescue environment. * **Backups**: manage backups (if your plan includes them). * **Snapshots**: create manual point-in-time snapshots. * **View Server Metrics**: CPU/RAM/disk/network usage charts. * **Primary IP Address**: IP info, blocked status, reverse DNS (PTR). {% hint style="warning" %} Actions like **Rebuild** and **Restore** can erase data. Always create a backup or snapshot first. {% endhint %} ### Quickstart {% stepper %} {% step %} ### 1) Get access details 1. Check your provisioning email. 2. Open the Client Area. 3. Open your **SSD Arm64 Linux VPS** service. Keep these details: * IPv4 (or hostname) * Username (usually `root`) * Initial password Client Area: {% endstep %} {% step %} ### 2) SSH into the server {% tabs %} {% tab title="macOS / Linux" %} ```bash ssh root@YOUR_SERVER_IP ``` {% endtab %} {% tab title="Windows" %} Use Windows Terminal (OpenSSH) or PuTTY. Host: `YOUR_SERVER_IP`. User: `root`. {% endtab %} {% endtabs %} {% endstep %} {% step %} ### 3) Minimum day-one setup * Change the default password. * Update OS packages. * Add an SSH key. * Disable password login if possible. * Enable a firewall and open only required ports. {% endstep %} {% endstepper %} ### Manage your VPS (Server Management) #### Server Information Use this to quickly copy your server details: * **Hostname**: server name. * **Status**: Running / Stopped. * **Server type**: vCPU, RAM, SSD. * **Location**: datacenter location. * **IPv4 / IPv6**: access addresses. * **Username / Password**: initial login details. {% hint style="info" %} The password shown in the portal is the initial password. Change it right after your first login. {% endhint %} #### Quick Actions: Reboot / Power Off * **Reboot Server**: restart the server. * **Power Off**: power off the server. Use this if the server is stuck. It’s also common after a kernel update. {% hint style="warning" %} Powering off can corrupt data during disk writes. Shut down from the OS first when possible. {% endhint %} #### Console Console is useful when: * SSH is blocked by a firewall rule. * Networking is broken. * You misconfigured the SSH daemon. Open the console, then fix the issue from inside the server. #### Firewalls Use this to control inbound traffic. Start with an allowlist of ports you need. Common ports: * SSH: `22` * HTTP: `80` * HTTPS: `443` {% hint style="danger" %} Don’t block SSH before you have console access. You can lock yourself out. {% endhint %} #### ISO Images ISO lets you boot from an image. Use it when you need a custom OS install. Typical workflow: 1. Mount the ISO. 2. Reboot the server. 3. Open Console and run the installer. {% hint style="info" %} On ARM64, some older ISO images may not boot. Prefer ARM64-native images. {% endhint %} #### Rebuild (reinstall OS) Rebuild reinstalls the operating system from scratch. This usually wipes disk data. Use Rebuild when: * The OS is badly broken. * You want to switch distros. * You want a clean slate. #### Rescue Mode Rescue mode boots into a recovery environment. Use it to recover data or fix boot issues. Common cases: * Wrong network configuration. * GRUB issues. * Full disk. #### Backups If your plan includes backups, you can: * Enable a backup schedule. * View the backup list. * Restore when needed. {% hint style="info" %} Backups and snapshots are different. Snapshots are best right before risky changes. {% endhint %} #### Snapshots Snapshots are point-in-time images of your VPS. Create one before: * Major updates. * App upgrades. * Firewall or network changes. #### View Server Metrics Metrics help you decide whether you need an upgrade. Track: * CPU usage * RAM usage * Disk usage / IOPS (if available) * Network traffic Related: * [Upgrades and downgrades](/billing-+-client-area/upgrades-and-downgrades) ### Primary IP Address + Reverse DNS (PTR) In the IP section, you’ll see: * IP address * Blocked status * Reverse DNS (PTR) * **Edit** and **Reset** buttons PTR is often required for mail servers. It can also improve IP trust with some services. {% hint style="warning" %} PTR should point to a hostname you control. That hostname should resolve back to the same IP. {% endhint %} ### If you can’t access the server Try in this order: 1. Check the status is **Running**. 2. Reboot using Quick Actions. 3. Use **Console** to check SSH and firewall rules. 4. Confirm your firewall allows SSH (port `22`). See also: * [Troubleshooting checklist](/support/troubleshooting-checklist) ### Need help? * Knowledge Base: * Support: # Dedicated GPU Server Getting started with a dedicated GPU server. ## Dedicated GPU Server **Order:** ### Before you start Dedicated servers usually take longer to provision than VPS. Check your email for delivery details. ### Access methods Your access depends on the OS you order: * Linux: SSH * Windows: RDP If your service includes out-of-band access (IPMI/KVM), use the credentials provided. ### Power Controls (Client Area) In the Client Area, you may see **Power Controls** for your dedicated server. Use it when you need to restart the machine, or when remote access is down. Available actions: * **Reboot**: graceful restart. * **Shutdown**: power off the server. * **Start**: power on the server (**coming soon**). * **Rescue Mode**: boot a recovery system (**coming soon**). Limits: * You can perform power actions **once every 15 minutes**. {% hint style="warning" %} Prefer shutting down from the OS when possible. Forced power actions can cause data loss during disk writes. {% endhint %} ### GPU verification (Linux) Once you can log in, verify drivers and GPU visibility. A common check is `nvidia-smi` for NVIDIA. ### Security basics * Update the OS. * Restrict remote access by IP if possible. * Use strong passwords and rotate them. ### Help & updates * Announcements: * Support: # Dedicated Windows with Android Emulator Windows dedicated server intended for running Android emulators. ## Dedicated Windows with Android Emulator **Order:** ### Related guides * [Access your Windows VPS (RDP)](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/bUYvfHb6xw7kgTvmQIAo) * [Change password on Windows Server (2008–2022)](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/IgrYg7sghSH9FMyGAjGu) * [Enable microphone in Windows Server](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/mBrwJVbONZbNHaKZcZ1j) * [Change display language on Windows Server 2019/2022](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/kru2mWZrhOLrIiNcm2dk) * [Run an Android emulator without a dedicated GPU](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/1RRvIRgf5Gg3oucvIA8S) * [Reboot an AndroidDE server](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/ifqpUgbDD8aucusNXR33) ### Overview This is a Windows dedicated server designed for emulator workloads. Common emulator options include: * NoxPlayer * BlueStacks * MEmu * LDPlayer ### Connect (RDP) 1. Get the server IP, username, and password from the delivery email. 2. Use Remote Desktop (RDP) to connect. 3. Change the password after first login. {% hint style="info" %} If the portal shows `IP:PORT`, use that port for RDP. {% endhint %} ### Client Area features (Server Panel) In the Client Area, your server page is split into cards. You can copy most values by clicking them. #### API error banner (temporary) If you see **“Unable to load server data”**, the upstream API is unavailable. Some server information may be outdated. Click **Retry** and reload the page after a minute. #### Server Details Use **Server Details** to quickly grab access information: * **Hostname** and current status. * **Primary IP** (sometimes shown as `IP:PORT`). * **IPv6 network** (if enabled). * **Username** (usually `Administrator`). * **Initial password**. * **Operating system** (example: Windows Server 2022 Datacenter). * **Location / Datacenter**. * **Traffic** (example: unlimited). {% hint style="warning" %} Treat the portal password as sensitive. Rotate it after first login. {% endhint %} #### Additional IP Addresses If your service includes extra IPs, they appear in **Additional IP Addresses**. Use those IPs for extra RDP endpoints or outbound IP separation. #### Billing Information Billing shows: * Product name. * Service status. * Registration date. * Recurring amount and billing cycle. * Next due date and remaining days. * Payment method. ### Power Controls Power controls help when Windows is frozen, or RDP is down. You may see multiple reset types: * **Software**: sends `Ctrl+Alt+Del` (when available). * **Power**: presses the power button (ACPI signal). * **Force Off**: long power press. Immediate shutdown. * **Hardware**: reset button. Hard reboot. * **Manual**: technician reset in the datacenter. * **Wake on LAN**: sends a magic packet to power on. How it works: * **Power (press power button)** turns on the server if off. * If running, it triggers a graceful OS shutdown signal. * **Force Off (long power press)** cuts power immediately. * Use it only when the OS is unresponsive. * **Hardware reset** is like pressing a physical reset button. * **Manual power cycle** is the most drastic option. Notes: * **Wake on LAN** only helps when the server is powered off. * **Manual** may take time. Support confirms completion by email. {% hint style="danger" %} Force Off and Hardware reset can corrupt disks. Use them last. {% endhint %} ### Rescue Mode Rescue mode boots a minimal recovery OS over the network. Use it for: * Emergency access when Windows won’t boot. * Disk checks and file recovery. * Repairing boot issues. {% stepper %} {% step %} ### 1) Enable Rescue Mode 1. Open **Rescue Mode**. 2. Choose an **operating system** (example: `linux` or `vkvm`). 3. Choose your **keyboard layout**. 4. Click **Enable**. The portal will show a temporary rescue password. {% endstep %} {% step %} ### 2) Reboot into Rescue Perform a reset from **Power Controls**. The server boots into rescue on the next reboot. {% endstep %} {% step %} ### 3) Work, then exit Rescue activation is valid for **60 minutes**. After that, reboot again to start the installed OS. {% endstep %} {% endstepper %} {% hint style="info" %} Rescue mode is not Windows. It is mainly for recovery tasks. {% endhint %}
How Rescue Mode works After activation, a configuration is created on the DHCP side. On the next reboot, the server boots from the network. A minimal OS is loaded via TFTP. Rescue activation stays valid for 60 minutes.
### Firewall Firewall lets you control inbound and outbound traffic from the portal. Key points: * Rules are processed **top to bottom**. * Unmatched packets are blocked by default. * Applying changes can take **30–40 seconds**. Use **Manage Rules** to edit inbound and outbound rules. {% hint style="warning" %} Do not block RDP unless you have an alternative access path. {% endhint %} IPv6 notes: * ICMPv6 is always allowed. * IPv6 rules may not support IP-based filtering. ### Reverse DNS (PTR) Reverse DNS lets you set a PTR record for an IP. Workflow: 1. Select the IP address. 2. Enter a PTR hostname (example: `server.example.com`). 3. Optionally load the current PTR. 4. Click **Save**. {% hint style="warning" %} PTR must point to a valid hostname. That hostname must resolve back to the same IP. {% endhint %} ### Stability tips * Keep Windows updated. * Avoid installing unnecessary background apps. * Monitor CPU/RAM/disk usage during emulator runs. ### Need support? Include these details in your ticket: * Your server IP * Emulator name + version * Screenshot of the error * What changed right before it started failing Support: # Register a domain Buy a new domain from the PreVPS client portal. ## Register a domain **Order link:** ### What you need * The domain name you want * A valid registrant email address * Payment method ### Tips before you buy * Prefer short names. * Avoid trademarks. * If you need email deliverability, plan SPF/DKIM/DMARC early. ### After purchase * Set your nameservers. * Add DNS records (A/AAAA/CNAME/MX/TXT). Next: * [Set up nameservers](/domains/set-up-nameservers) * [Manage DNS records](/domains/manage-dns-records) # Transfer a domain Move an existing domain to PreVPS. ## Transfer a domain **Order link:** ### Before you transfer * Make sure the domain is **unlocked**. * Get the **EPP/Auth code** from your current registrar. * Confirm the registrant email can receive messages. * Check you are not within a transfer lock period. ### During transfer * Enter the domain + EPP code at checkout. * Approve transfer emails if required. {% hint style="info" %} Most transfers take hours to days. The exact timing depends on the TLD. {% endhint %} ### Avoid downtime Keep current nameservers until you confirm DNS is correct at the new registrar. # Set up nameservers Point your domain to the right DNS provider. ## Set up nameservers Nameservers decide **where DNS is managed**. ### Common scenarios * You manage DNS at PreVPS. * You manage DNS at Cloudflare. * Your website provider manages DNS. ### Steps (generic) 1. Open the domain management page in the Client Area. 2. Find **Nameservers**. 3. Replace the current nameservers with the new ones. 4. Save. ### DNS propagation Changes can take time to propagate. Expect minutes to 24–48 hours depending on caching. ### Next * [Manage DNS records](/domains/manage-dns-records) # Manage DNS records A/AAAA/CNAME/MX/TXT basics and common setups. ## Manage DNS records DNS records connect your domain to servers and services. ### Common record types * **A**: points a name to an IPv4 address. * **AAAA**: points a name to an IPv6 address. * **CNAME**: alias one name to another name. * **MX**: mail routing. * **TXT**: verification and email auth (SPF/DKIM/DMARC). ### Typical setups #### Website on a VPS * `A` record for `@` → your VPS IPv4 * Optional `A` record for `www` → your VPS IPv4, or `CNAME www → @` #### Email deliverability * SPF (TXT) * DKIM (TXT) * DMARC (TXT) {% hint style="warning" %} Bad MX/TXT records can break email. Make one change at a time. {% endhint %} # Renewals and expiration Avoid losing a domain by renewing on time. ## Renewals and expiration ### Best practices * Enable auto-renew if available. * Keep your billing email up to date. * Renew early for critical domains. ### If a domain expires * Websites and email may stop working. * You may enter a redemption period (varies by TLD). * Fees may increase after expiration. ### Where to check * Client Area: * Invoices: {% hint style="info" %} Exact grace and redemption rules depend on the TLD. If you’re unsure, open a ticket before the expiry date. {% endhint %} # Client Area Where to manage services, domains, and invoices. ## Client Area The Client Area is where you manage everything after checkout. ### What you can do here * View and manage your services * View invoices and pay * Open support tickets ### Account hygiene * Keep your email address up to date. * Use a strong, unique password. # Invoices and payments Find invoices, pay, and confirm payment status. ## Invoices and payments ### Related guides * [Add funds (credit balance)](/billing-+-client-area/add-funds-credit-balance) * [Supported payment gateways](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/BWZCHbvPVOCNV8Ut9TBF) * [Pay an invoice with crypto (BTC/BCH/ETH/LTC/USDC)](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/jfZe0BZDBl2ybypeynz0) * [Enable auto credit payment for invoices](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/faNZ8PX7pd1iAFW8tzys) * [Automatic renewal with credit balance](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/h5vSPhgzunDxqScNV1CK) ### Where to find invoices * Client Area → Invoices * Direct link (may require login): ### Payment flow (typical) 1. Open the invoice. 2. Choose a payment method. 3. Complete payment. 4. Re-open the invoice and confirm it shows as paid. ### Invoice timing, reminders, and late fee These are our current billing timings. They can change later. #### Invoice generation * Invoices are generated **14 days before** the due date. #### Reminder emails If reminder emails are enabled, the typical schedule is: * **Unpaid reminder:** **4 days before** the due date. * **Overdue reminder #1:** **2 days after** the due date. * **Overdue reminder #2:** **1 day after** the due date. * **Overdue reminder #3 (final):** **disabled**. #### Late fee * A late fee can be added **1 day after** the due date. {% hint style="info" %} If you already paid but still receive a reminder, re-open the invoice and check its status first. If it still shows unpaid, open a ticket with the invoice number. {% endhint %} #### Automatic payment capture (cards) For supported card payments, the system may try to capture payment **1 day before** the due date. #### Payment reversals (chargebacks / disputes) If a payment is reversed, the system may: * Change the **invoice status** (back to unpaid), and/or * Change the related service **due date** #### Overage / metered billing (if applicable) If your service has usage-based charges, overage is typically calculated at the **end of the month**. It may generate a separate invoice, or be added to the next invoice. ### Paying with credit balance (optional) If you keep a credit balance, you can pay invoices without running a separate payment each time. Typical flow: 1. Add credit to your account: 2. Enable **Auto Credit Balance** (so credit is applied to unpaid invoices). 3. Re-check the invoice status after it generates. ### If an invoice looks wrong Open a ticket and include: * Invoice number * Screenshot of the totals * What you expected (renewal, upgrade, promo) # Upgrades and downgrades Change plan/resources for an existing service. ## Upgrades and downgrades ### Related guide * [Upgrade or downgrade server options](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/XatDm2pGzL9WaCHbujG6) ### When to upgrade * You hit CPU/RAM limits. * Disk is close to full. * You need more bandwidth. ### What to expect * Some changes are instant. * Some changes may require downtime. * Charges may be prorated. ### Best practice Before changing a plan: * Take a backup. * Note your current IPs and config. * Confirm the maintenance window if the service is production. ### Need help choosing a plan? Contact support with your current usage and workload details. # Cancellations and refunds How to cancel a service and where refund rules live. ## Cancellations and refunds ### Related guide * [Cancel or delete your VPS / Server](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/gcOcFOqY4REEqv3fn7Uf) ### Cancel a service 1. Log in to the Client Area. 2. Open the service. 3. Submit a cancellation request (end of term vs immediate, if available). ### Refund rules Refund eligibility depends on the product and your order. Use the official policy pages: * Terms of service: * Privacy policy: {% hint style="info" %} If you’re not sure, open a ticket before cancelling. Ask what happens to data, IPs, and remaining time. {% endhint %} # Add funds (credit balance) Top up your account credit and use it to pay invoices automatically. ## Add funds (credit balance) Adding funds creates a **credit balance** on your account. Use it to avoid many small transactions. You can also auto-pay new invoices from this balance. ### Where to add funds Client Area → **Add Funds** Direct link (may require login): ### Minimum deposit Minimum deposit: **$5.00 USD**. ### Payment methods The exact options depend on your account and currency. Typical options include: * **Credit/Debit Cards** (Stripe) * **Heleket** (Cryptocurrencies) * **Cryptomus** (Cryptocurrencies) ### Auto Credit Balance Auto Credit Balance automatically applies your credit balance to **unpaid invoices**. #### Enable / disable You can usually toggle it in the Client Area: * In the **Client Balance** sidebar widget, or * On the **Add Funds** page {% hint style="info" %} If your credit balance is lower than the invoice total, the invoice can remain unpaid. Keep a buffer. {% endhint %} {% hint style="warning" %} When sharing screenshots or HTML with support, redact sensitive values (tokens, session IDs). {% endhint %} ### What happens after you add funds * Your account credit increases. * New invoices can be paid automatically (if Auto Credit Balance is enabled). * You can still pay invoices manually using gateways. # Contact Support The official support channels for PreVPS. ## Contact Support ### Best channel Use the Client Area for account-specific requests. It keeps your request tied to your services and invoices. * Client Area: * Login: ### General contact * Contact page: ### Before you contact support Have this ready: * Service type (VPS / Dedicated / Domain) * Service IP (if applicable) * What changed right before the issue started * Exact error text or a screenshot # Open a support ticket What to include so support can solve it fast. ## Open a support ticket ### What to include (copy/paste checklist) * Subject: short and specific * Service ID or domain name * IP address (for VPS/Dedicated) * OS and version * Exact error message * Timestamps + your time zone * Steps to reproduce ### Examples * "Cannot SSH: Connection timed out" * "RDP black screen after Windows update" * "Domain DNS changes not propagating" {% hint style="info" %} Attach screenshots. Avoid sending passwords in plain text. {% endhint %} # Troubleshooting checklist Quick self-checks before escalating. ## Troubleshooting checklist ### Related guides * [Test network connectivity with ping (macOS)](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/mBrwJVbONZbNHaKZcZ1j) * [VPS delivery time](broken://spaces/laEWHyEhXmGEBBoSUuh5/pages/1RRvIRgf5Gg3oucvIA8S) ### 1) Confirm the basics * Is the invoice paid? * Is the service active in the Client Area? * Any related announcement? Links: * Invoices: * Announcements: ### 2) Network symptoms * If it’s a timeout: check firewall rules on the server. * If it’s authentication: confirm username/password/key. * If DNS-related: confirm nameservers and record values. ### 3) Safe actions * Reboot the service (if available). * Try from another network. * Collect logs and exact error output. ### 4) When to open a ticket Open a ticket if: * You suspect hardware/network issues. * You can’t access the server after basic checks. * You need billing/domain actions.