Your VPS is unmanaged. You are responsible for its operating system, applications, security and backups. EDBB support helps with the infrastructure, control panel, account and billing, and can point you to configuration guides.
Restart or complete a cold boot
For routine maintenance, use the operating system’s normal restart command when it responds. This allows applications to close and finish pending writes. A restart interrupts SSH, RDP and hosted services. The EDBB panel offers these separate actions:
These panel actions do not replace an orderly operating-system shutdown. Save your work before using them.
Activate hardware changes
When an upgrade requires a cold boot, shut down cleanly and then start the VPS from the panel:1
Shut down inside the VPS
Save your work. On Linux, run
shutdown -h now as root. On Windows, run shutdown /s /t 0 from an Administrator command prompt.2
Check that the VPS is off
Wait for Turned off. If the operating system has finished shutting down but the panel still shows Running, click Server On, then confirm Power Off.
3
Start and verify
Click Server Off to start it. Wait for the OS to boot, reconnect, and check the new resources inside the operating system. Enable VNC again if needed.
Reinstall or change operating system
Reinstallation replaces your existing system with a clean Linux or Windows installation. It does not by itself change the assigned IP addresses.- Check the available operating systems.
- Open Installation → Automated Installers, select the OS family and Version, and set your access credentials.
- Store the new password securely. A reinstall does not send a new welcome email. For Linux, the optional SSH key field accepts a public key, never a private key.
- Check that you selected the correct VPS, then click Start the installation. This starts the destructive operation; do not expect another confirmation.
- Wait for installation to finish before connecting. Linux normally takes up to five minutes and Windows up to fifteen minutes. Do not power off or restart during setup.
Change an IP address
An IP change replaces an address on the same VPS. It does not change the server location, plan or billing cycle.
For paid options, use IP Change below the Dashboard cards or Product Addons. Select your VPS and old IP, review the current price and applicable VAT, and follow the Standard or Bespoke guide.
Prepare VNC access before confirming a replacement. The old IP is released and stops working immediately; you cannot switch back to it. After assignment:
- Copy the new IP, subnet mask and gateway from Network.
- Use the VNC console to configure the OS. Follow the Ubuntu or Windows Server guide.
- Update DNS records, VPN endpoints, allowlists and application settings that use the old address.
- Test access and applications on the new address before closing the console.
Manage billing and renewals
Your VPS renews unless you cancel it. Renewal and successful payment are separate: keep your payment method current and check that the invoice is paid. For the automated non-payment workflow, day 0 is the renewal invoice’s due date:
If suspended for non-payment, pay the outstanding renewal invoice to reactivate the VPS automatically. If already terminated, contact support promptly to request recovery before deletion; do not assume that paying an old invoice alone restores a terminated service. After permanent deletion, recovery requires your own backup.
Retention is not a backup service or an extension of the payment deadline. Customer-requested cancellation follows the separate timetable below. A cancelled invoice alone does not prove that VPS data has been deleted.
Review PayPal subscriptions separately after upgrades or cancellation: their amount and schedule do not automatically follow VPS changes.
Billing and renewals · Find invoices · Payment methods · Data retention
Create backups you can restore
EDBB does not supply routine backups of your VPS. Keep an independent copy of the data you need to rebuild it.- Identify files, databases, uploaded content, application settings and recovery keys.
- Make a consistent backup. Use database or application export tools rather than copying live database files while they change.
- Transfer the backup outside the VPS, for example by SFTP to your computer or through a scheduled backup to separate storage.
- Keep several dated versions. A single synchronised copy can also reproduce deletion or corruption.
- Test restoration in a separate location and verify the application works.
Upgrade your VPS
Open Upgrades. Choose Upgrade Your Plan for a higher tier, or Upgrade Now under Upgrade Components for individual RAM, vCPU, Drive Boost or IPv4 additions. Review the resource totals, recurring price and prorated charge before checkout. Follow the activation email after payment:- Traffic increases are available immediately.
- RAM and vCPU increases require a full cold boot.
- Larger virtual drives require the specified cold boot, then a check and expansion of the partition and filesystem inside the OS.
- Additional IPv4 addresses must also be configured inside the operating system.
Manage traffic and monthly refills
Open Traffic to check usage, allowance and the next monthly refill. Incoming and outgoing traffic both count. Your shared Traffic Pool can supply additional allowance to any VPS in your account. Each new VPS contributes 100 GB starter credit. In Manual Hydration, select an amount and click Assign Traffic. Buying Pool Traffic alone does not assign it to a VPS or restore its speed. For automatic assignments, enable Auto Hydration for the VPS and choose 100, 200, 300 or 500 GB. At 99% of the current allowance, it assigns that amount if your pool has sufficient balance. It never purchases traffic automatically.
If the allowance runs out, the VPS remains online but can be rate-limited. Check Traffic before treating a slow connection as a server failure. Assign sufficient Pool Traffic, upgrade where available, or wait for the monthly refill.
Traffic Pool and Auto-Hydration · Traffic statistics · Traffic limits and restoring speed
Recover access
Check the VPS power state and the shared infrastructure status page. If it is powered on but SSH or RDP fails, open the VNC console to inspect boot progress and OS errors independently of the guest network. Choose the guide that matches the problem:- Diagnose an unreachable VPS.
- Reset a Linux root password.
- Reset a Windows Administrator password.
- Resolve RDP account lockout.
- Recover Linux with rescue media.
Networking and location changes
Use Network for your IPv4, IPv6, gateway and DNS details. Configure addresses inside the OS using the values shown for your own VPS. See IP settings, additional IPv4 configuration and IPv6 configuration. Use rDNS to manage reverse-DNS PTR records. PTR records are separate from the forward DNS records that point a domain to your VPS. Reverse-DNS guide. A different server location requires a replacement VPS, not a simple IP edit. An eligible one-time free replacement within 24 hours keeps the plan and billing cycle but provides new login details and a new IP. Data and configuration do not move automatically. Back up and plan the migration first. Once the replacement is provisioned, the order is no longer eligible for a refund. For a later move, order a VPS in the new location, migrate and test your services, update DNS, then cancel the old VPS. Allow for overlapping billing. Location-change conditions.Cancel a VPS correctly
Powering off a VPS does not cancel it or stop billing. Download and verify your backups before opening Request Cancellation on the service.- Immediate: the service stops when termination is processed.
- End of Billing Period: it continues until the service due date, then terminates.