Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
Buy a VPS by matching its CPU, memory, storage, transfer allowance, operating system, and network features to the workload you will actually run—not by choosing the largest or cheapest bundle. Reserve a stable public IP, point the correct DNS records at it, then harden and monitor the server before putting an application online.
This guide explains how to size a VPS for a website, application, database, or background job; how shared and dedicated resources differ; which DNS records you need; and the practical steps from purchase to a working, secured hostname.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesWhat a VPS is and what you are buying
A virtual private server is a virtual machine rented from a cloud provider. The provider runs the physical infrastructure while you administer an isolated operating-system instance. Amazon Web Services describes a Lightsail instance as “a virtual private server (VPS) that lives in the AWS Cloud.” A plan normally bundles virtual CPUs (vCPUs), RAM, SSD storage, and a data-transfer allowance. You are responsible for the operating system, applications, updates, credentials, firewall, and data unless the selected service explicitly manages some of those tasks.
Different providers expose the bundle differently. Lightsail packages vCPUs, memory, SSD storage, transfer, a static IPv4 address, and DNS management in predictable plans. DigitalOcean Droplets are VPS choices with shared or dedicated CPU families; the selected configuration determines CPU, RAM, disk capacity, and network bandwidth. The labels differ, but the buying decision is the same: identify the workload, translate it into resource limits, and leave room for growth and failure recovery.
#1 Best Overall
- [INTEL POWERED CONTENT] - Built with a 8th Generation Hexa-Core Intel i5 and 32GB of DDR4 RAM; Modern, Windows 11 ready, with 4K support, Executive multitasking, media streaming and smooth, multi-tab web browsing; Perfect as an all-purpose multimedia computer; built for content creators; Plenty of RAM and Mass storage for photo and video editing powered by Intel HD 630
- [LATEST WIRELESS TECH] - This Dell Desktop Computer easily connects to the internet through the Built In WiFi / Bluetooth
- [SOLID STATE STORAGE] - This Dell Computer setup comes with an ultra-fast 1TB Solid State Drive (SSD); Setup as the primary boot device; Boot and load programs with lightning speed ; Additional expansion available
- [BUY & OWN WITH CONFIDENCE] - From the world's largest Microsoft Authorized Refurbisher; Quality Guarantee and Free Tech Support; Award-winning Customer Service; | Support Sustainable Business
- [MODERN HI-SPEED PORTS] - USB 3.0 (x4) | USB 2.0 (x4) | DisplayPort (x1) | HDMI Port (x1) | Audio Combo Jack (x1) | Audio Out (x1) | RJ-45 Ethernet (x1) | Internal SATA (x3)
Start with the workload, not a plan name
Write down what the server must do during a normal day and during a spike. A brochure’s “small,” “general purpose,” or “developer” label is not a sizing method. List the software, expected concurrent users or jobs, data volume, peak times, and whether a brief slowdown is acceptable. Then identify the resource that is most likely to become the first bottleneck.
Websites and content-management systems
A mostly static site or a low-traffic application usually spends more time waiting for network requests, disk reads, or a database than performing sustained CPU work. Shared CPU is often economical for this pattern. Reserve memory for the operating system, web server, runtime, database, filesystem cache, and traffic bursts instead of allocating nearly all RAM to the application.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
APIs and interactive applications
For an API, measure concurrent requests, response-time targets, runtime memory use, and database connections. A plan with more vCPUs does not automatically improve latency if the application is blocked on a database or external service. Check whether the provider’s CPU is shared or dedicated and whether the instance can be resized without changing its public address.
Databases and in-memory caches
Databases need predictable memory for their working set, connection pools, and caches. Memory-optimized plans are intended for in-memory caching, analytics, and high-performance databases. Storage latency and durable backup options matter as much as raw capacity. Keep free space for transaction logs, indexes, operating-system updates, and temporary files; a disk that reaches 100 percent can stop writes even when CPU is idle.
Builds, encoding, and batch jobs
Video encoding, continuous-integration builds, scientific jobs, and other sustained workloads benefit from dedicated or CPU-optimized resources. Shared CPU can be cost-effective for occasional bursts, but performance may vary when neighboring tenants are busy. If a job has a deadline, compare sustained CPU capacity and upgrade options rather than relying on a short benchmark or a “burstable” label.
Streaming and other bandwidth-heavy services
Streaming, downloads, and large software artifacts can exhaust a transfer quota before CPU or RAM becomes a problem. Estimate monthly outbound bytes, peak concurrent connections, and the cost of additional transfer. Confirm whether traffic between regions, backups, and IPv4 addresses is charged separately.
How to choose CPU, RAM, storage, and transfer
| Resource | What it limits | Questions to answer before purchase | When to choose an optimized tier |
|---|---|---|---|
| vCPU | Parallel application work, request handling, compilation, and background jobs | Is the workload bursty or continuously CPU-bound? Are CPUs shared or dedicated? | Dedicated or CPU-optimized plans suit sustained encoding, CI/CD, batch processing, and high-traffic front ends. |
| RAM | Operating system, processes, database buffers, caches, and traffic spikes | How much memory does the full stack use at peak, and what must remain available for the kernel? | Memory-optimized plans fit in-memory caches, analytics, and high-performance databases. |
| SSD/NVMe storage | Operating-system files, application data, databases, logs, snapshots, and temporary files | What capacity and performance are supplied? Is storage expandable? How are backups charged? | Storage-optimized plans fit data-heavy workloads; choose headroom rather than sizing to today’s file total. |
| Transfer and network | Outbound and inbound traffic, public access, and service-to-service communication | What monthly transfer is included? What are IPv4, IPv6, bandwidth, and overage rules? | Higher-transfer or network-focused options suit downloads, streaming, and busy APIs. |
CPU: shared versus dedicated
Shared CPU lowers the entry cost and is suitable for light or bursty sites. A dedicated or CPU-optimized plan assigns more predictable processing capacity for sustained work. Ask whether a provider can move you to a larger plan in place, whether a resize requires a reboot, and whether CPU credits or burst limits apply. Do not treat a vCPU count as an equivalent to a physical-core benchmark; providers can use different host hardware and scheduling policies.
RAM: calculate the whole stack
RAM is a hard limit. Add the operating system, web server, language runtime, workers, database, cache, monitoring agents, and a margin for deployments and traffic spikes. A server that swaps heavily may appear to have “enough” memory while delivering poor response times and wearing out storage. Monitor used memory, swap activity, and per-process peaks after launch, then resize before the system reaches the limit.
Rank #2
- Entry-level NAS Personal Storage：UGREEN NAS DH2300 is your first and best NAS made easy. It is designed for beginners who want a simple, private way to store videos, photos and personal files, which is intuitive for users moving from cloud storage or external drives and move away from scattered date across devices. This entry-level NAS 2-bay perfect for personal entertainment, photo storage, and easy data backup (doesn't support Docker or virtual machines).
- Set Your Devices Free, Expand Your Digital World: This unified storage hub supports massive capacity up to 64TB.*Storage drives not included. Stop Deleting, Start Storing. You can store 22 million 3MB images, or 2 million 30MB songs, or 43K 1.5GB movies or 67 million 1MB documents! UGREEN NAS is a better way to free up storage across all your devices such as phones, computers, tablets and also does automatic backups across devices regardless of the operating system—Window, iOS, Android or macOS.
- The Smarter Long-term Way to Store: Unlike cloud storage with recurring monthly fees, a UGREEN NAS enclosure requires only a one-time purchase for long-term use. For example, you only need to pay $459.98 for a NAS, while for cloud storage, you need to pay $719.88 per year, $2,159.64 for 3 years, $3,599.40 for 5 years. You will save $6,738.82 over 10 years with UGREEN NAS! *NAS cost based on DH2300 + 12TB HDD; cloud cost based on 12TB plan (e.g. $59.99/month).
- Blazing Speed, Minimal Power: Equipped with a high-performance processor, 1GbE port, and 4GB RAM on Board, this NAS handles multiple tasks with ease. File transfers reach up to 125MB/s—a 1GB file takes only 8 seconds. Don't let slow clouds hold you back; they often need over 100 seconds for the same task. The difference is clear.
- Let AI Better Organize Your Memories: UGREEN NAS uses AI to tag faces, locations, texts, and objects—so you can effortlessly find any photo by searching for who or what's in it in seconds. It also automatically finds and deletes similar or duplicate photo, backs up live photos and allows you to share them with your friends or family with just one tap. Everything stays effortlessly organized, powered by intelligent tagging and recognition.
Canonical’s Ubuntu Server requirements list a minimum of 1 GB RAM for cloud images. That is a boot and installation floor, not a production recommendation: extra services increase memory and storage requirements, and a database-backed application normally needs more room.
Storage: capacity is not performance
Confirm whether the disk is SSD or NVMe, the included capacity, achievable I/O, and any separate volume service. Allocate space for logs, package caches, database growth, uploads, temporary build files, and at least one recovery path. Snapshots are useful for rollback but are not a substitute for an independent backup; a deleted instance, compromised account, or corrupted snapshot can otherwise remove every copy.
Transfer, addresses, and network behavior
Compare included transfer and the treatment of public IPv4 and IPv6. A static public address keeps DNS valid when an instance is replaced. If an address is ephemeral, stop-and-recreate operations can change it and make the hostname point to the wrong machine. Verify reverse-DNS controls if the server will send mail, and check whether the provider filters inbound ports.
Operating-system image
Ubuntu, Debian, and other Linux images are common choices. Select an image that your application, package repositories, monitoring tools, and support process recognize. Record the exact release and lifecycle dates. A minimal image reduces attack surface, but you must install every required runtime, certificate tool, firewall rule, and agent yourself.
Compare providers on the features that affect operations
Compare like-for-like resources rather than headline monthly prices. Use this checklist when reading a plan page:
- Resource model: shared, dedicated, burstable, or CPU-optimized; note any credit or throttling rules.
- RAM-to-CPU ratio: a database may need more memory per vCPU, while a build worker may need the opposite.
- Disk: SSD or NVMe type, capacity, I/O expectations, additional-volume support, and snapshot pricing.
- Network: included transfer, port speed, IPv4 charges, IPv6 availability, and regional egress rules.
- Location: choose a region close to users and dependent services to reduce latency and data-transfer costs.
- Recovery: automated backups, on-demand snapshots, retention, restore testing, and whether a snapshot can be copied to another region.
- Operations: monitoring, alerting, console access when SSH fails, support hours, and documented maintenance practices.
- Upgrade path: resize choices, expected downtime, volume expansion, and whether the public IP can be retained.
Lightsail emphasizes predictable bundles with built-in static-IP and DNS tooling. DigitalOcean offers a broader set of workload-specific Droplet families and one-click Linux application images. Neither model removes the need to check transfer, backup, IPv4, region, and upgrade terms for the exact plan and date you will buy.
Understand the price without relying on an old comparison
Prices, quotas, IPv4 charges, and promotional terms change. Recheck the provider’s checkout page and current pricing documentation immediately before ordering, and distinguish recurring charges from introductory credits.
For a concrete reference point, AWS pricing information in 2026 lists a Linux Lightsail bundle at $5 per month with 0.5 GB memory, 2 vCPUs, 20 GB SSD storage, and 1 TB of transfer. That figure is a provider-published plan example at that time, not a universal VPS price or a recommendation for every workload. Check whether backups, additional disks, static addresses, data transfer, and taxes add to the bill.
Rank #3
- 【Advanced Home Data & Media Hub】For advanced home users who need phone backup, file storage, and centralized data management. Centralize family photos, 4K videos, movies, computer backups, and personal files in one place while running multiple apps for home entertainment and everyday data management. Suitable for households with growing digital libraries and multiple NAS use cases.
- 【Built for Creators, Media Servers & Advanced Apps】Powered by the Intel N100 Quad-Core CPU, 8GB DDR5 RAM, 2.5GbE networking, and dual M.2 NVMe slots, DXP2800 handles large files and heavier workloads with ease. Run Docker, virtual machines, and media server applications compatible with Plex—ideal for content creators, tech enthusiasts, and advanced home users managing 4K videos, RAW photos, personal media libraries, and multiple NAS apps.
- 【Up to 80TB for Growing Digital Libraries】 Supports up to 80TB of storage using two HDD bays and two M.2 NVMe SSD slots for family photos, movies, RAW photos, 4K videos, work files, and device backups. AI photo management supports recognition of people, objects, scenes, and locations, album organization, and duplicate photo detection. HDDs and SSDs are not included.
- 【AI-powered Home Surveillance】Turn DXP2800 into a centralized home surveillance hub by connecting compatible network cameras and storing recordings locally on your NAS. AI-powered features include Face Recognition, People Detection, and Pet Detection, helping advanced home users review important events more efficiently while managing home surveillance and personal data in one place.
- 【One data Center Across Your Devices】Keep files from desktops, laptops, phones, tablets, and other devices together instead of scattered across cloud accounts and external drives. Access, back up, organize, and share data across Windows, macOS, Android, iOS, web browsers, and compatible smart TVs—ideal for creators and advanced home users working across multiple devices.
Point your domain at the VPS
DNS translates names into routing information. AWS explains that a DNS zone contains records for a domain and its subdomains, and that an A record maps a domain such as example.com or a subdomain such as blog.example.com to a web server’s IP address.
1. Decide where authoritative DNS will live
You can keep DNS at your registrar or create a zone with the VPS provider. If the provider hosts the authoritative zone, copy its nameservers exactly and replace the domain’s nameservers at the registrar. If you keep the registrar’s DNS, add the records there instead; do not edit a non-authoritative zone and expect it to publish.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →2. Reserve a stable address
Attach a static public IPv4 address when the service supports one. Without it, replacing an instance can change the address and invalidate the A record. Enable IPv6 only after the server, firewall, and web service are configured for it.
3. Add the address records
| Record | Name | Value | Purpose |
|---|---|---|---|
| A | @ or the apex domain |
VPS public IPv4 address | Maps example.com to the server. |
| AAAA | @ or the apex domain |
VPS IPv6 address | Provides IPv6 access when the service is configured and reachable over IPv6. |
| CNAME | www or another alias |
Apex domain or canonical hostname | Points an alias to the canonical name; do not use a CNAME at the zone apex where the DNS provider disallows it. |
| MX | A mail subdomain or apex, as required | Mail provider’s hostnames and priorities | Routes mail only when a mail service handles the domain. |
| TXT | Provider-specified name | Verification or authentication text | Used for ownership checks and email policies such as SPF, DKIM, or DMARC. |
4. Set a sensible TTL and wait for caches
TTL controls how long recursive resolvers may cache an answer. Lightsail DNS records default to a 60-second TTL, according to AWS documentation. Other DNS services may use a different default. Lower the TTL before a planned migration, make the change, and allow existing longer-lived cache entries to expire; changing a record is not an instant global flush.
5. Verify from outside your network
Query the authoritative nameservers and several public resolvers. Confirm that the A and AAAA answers are the intended addresses, that www resolves as designed, and that no stale address remains. Test from an IPv4-only and an IPv6-capable connection before announcing the site.
Free tools Windows power users keep installed
One-click scans. No signup required.
Complete the initial server setup
The following sequence is a practical baseline for an Ubuntu or Debian image. Adapt package names and firewall commands to the chosen operating system and application.
- Record recovery details. Save the instance ID, region, public addresses, image release, billing plan, console access method, and backup location in an access-controlled record.
- Connect with an SSH key. Use the provider’s initial user and key rather than a password where possible:
ssh initial-user@SERVER_IP. Confirm the host fingerprint through the provider console or another trusted channel. - Create a non-root administrator. Add a personal account, grant it sudo access, install its SSH public key, and test a second login before disabling direct root login. Keep an emergency console path.
- Patch the image. On Ubuntu or Debian, run
sudo apt updatefollowed bysudo apt upgrade. Reboot if the kernel or other core components require it, then reconnect and confirm the expected release. - Restrict the host firewall. Allow only required ports—normally SSH, HTTP (80), and HTTPS (443)—and limit SSH by source network when practical. Enable the firewall only after verifying that your SSH session will remain permitted.
- Automate security updates. Enable the distribution’s unattended security-update mechanism or a tested patch process. Schedule maintenance windows for updates that require restarts.
- Install the application stack. Add the web server, language runtime, process manager, database, queue, and TLS tooling required by the application. Remove services and packages you do not need.
- Configure time and logs. Enable network time synchronization, set the correct timezone for operations, rotate logs, and send important logs off the instance when compliance or incident recovery requires it.
- Protect data. Enable automated backups or snapshots, define retention, and perform a restore test to a separate instance. A backup that has never been restored is an assumption, not a recovery plan.
- Add monitoring and alerts. Track CPU, memory, swap, disk usage and I/O, transfer, service health, certificate expiry, and backup success. Alert before disk or memory exhaustion becomes an outage.
- Install and test TLS. Issue a certificate for every hostname you serve, redirect HTTP to HTTPS where appropriate, and renew it automatically. Test both the apex and aliases after DNS resolves.
Make the web server and DNS agree
DNS only delivers a client to an IP address; the web server still must recognize the hostname. Configure a virtual host or server block for the apex domain and each required alias, set the application’s trusted host list, and ensure the certificate includes every name. A correct A record with a default server that serves the wrong site usually indicates a hostname or virtual-host configuration error, not a DNS failure.
Test the full path: resolve the name, establish TCP connectivity on 443, complete TLS with the expected certificate, and request a page that proves the intended application is running. Repeat after deployment, IP changes, certificate renewal, and firewall edits.
Rank #4
- Dell PowerEdge R730xd 24B SFF 2U Server
- 2x Intel Xeon E5-2690 v4 2.6Ghz 14-Core (28-cores Total)
- 128GB DDR4 RAM – 4x 1.2TB 10K SAS 2.5” 12Gb/s
- Dell H730P mini 2GB 12Gb/s RAID
- 2x 750W PSU - 2x 10Gb SFP+ 2x 1Gb (RJ45) NIC
Common buying and setup mistakes
Choosing on vCPU count alone
Two plans with the same vCPU number can behave differently because one uses shared scheduling and the other dedicates cores. Read the resource model and monitor sustained CPU usage after launch.
Recommended Free Tools
Filling the disk on day one
Leaving no space for logs, updates, indexes, and temporary files creates avoidable outages. Include growth headroom and a tested expansion procedure.
Pointing DNS at an ephemeral address
A replacement instance can receive a new address. Reserve and attach a static address, or plan a controlled DNS change with a short TTL and a migration window.
Publishing an AAAA record prematurely
Some clients prefer IPv6. If the firewall, route, or web server is not ready, those clients can fail even though IPv4 works. Add AAAA only after end-to-end IPv6 testing.
Running mail without planning mail DNS
An MX record does not create a mail service. If another provider handles mail, use its MX and TXT instructions. If the VPS sends mail, verify reverse DNS, authentication, reputation, and provider port policies before relying on it.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Treating a snapshot as a complete backup
A snapshot tied to one account, region, or compromised server may not satisfy recovery needs. Keep an independent copy and regularly restore it.
When to resize or change plans
Resize when measurements—not guesswork—show a persistent constraint. Sustained CPU saturation suggests a dedicated or CPU-optimized tier; swap activity and memory pressure suggest more RAM; high disk latency or low free space suggests faster or larger storage; transfer alerts suggest a larger allowance or a delivery architecture designed for heavy outbound traffic. Before resizing, verify whether the operation reboots the instance, changes its address, alters billing immediately, or requires a separate volume migration.
Keep a record of baseline CPU, memory, disk, latency, error rate, and transfer after the first stable week. Review those figures after a major feature, traffic increase, database growth, or change in backup policy. A smaller plan that remains comfortably below its limits is usually safer and cheaper than a large plan chosen without measurements, while a plan operating at the edge leaves no room for incidents or deployments.
Quick Recap
A purchase-day checklist
- Workload, peak traffic, background jobs, data growth, and recovery objectives are written down.
- CPU sharing or dedication, RAM, disk type and capacity, transfer, IPv4/IPv6, region, and upgrade behavior are understood.
- The operating-system image supports the application and has a clear update lifecycle.
- A static address, backups, snapshots, monitoring, and console recovery are included or budgeted.
- DNS authority is identified, and the required A, AAAA, CNAME, MX, and TXT records are planned.
- SSH keys, a non-root administrator, firewall rules, updates, TLS, and restore testing are scheduled before launch.
- Current pricing, quotas, IPv4 fees, taxes, and promotional expiry are confirmed at checkout.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
