# VPSDime > Self-managed VPS hosting since 2013, sold on resources per dollar: high-memory Linux VPS from $5/month, KVM Premium VPS with fully dedicated resources, and Hyper-V Windows VPS with the licence included. Locations in the US and Europe. Owned and operated by Nodisto F.Z.E (Ajman Free Zone, United Arab Emirates), which also runs the Winity and Backupsy brands. Site: https://vpsdime.com Support: 24/7 by ticket only (https://vpsdime.com/open-ticket), in English, typical first reply within minutes. No phone or live chat. Abuse: abuse@nodisto.com Status: https://vpsdime.com/service-status Knowledge base index: https://vpsdime.com/knowledgebase/llms.txt Full site text in one file: https://vpsdime.com/llms-full.txt (1,399 KB; fetch it only when a task needs the whole site) ## What is true about this service - Every product is self-managed: VPSDime runs the hardware, network and virtualization; the operating system and everything inside it is the customer's job. No managed migrations, no software management, no cPanel or Plesk licences sold. Paid one-off help exists (server management at $10 per 10 minutes, Varnish, FTP and remote-desktop setup, cPanel hardening). - Prices are in USD, exclude tax, have no setup fee, and renew at the same rate; they have not been raised since 2013. There are no promotions, coupons or bulk discounts. Quarterly, semi-annual and annual cycles are priced proportionally. - Payment: credit and debit cards (including prepaid and virtual), PayPal, Google Pay, Alipay, Bitcoin, USDT (TRC20, BEP20, ERC20). Refunds for crypto and Alipay payments are issued as account credit. - Refunds: 72-hour money-back guarantee on a customer's first service only, claimed by cancelling "Immediate" and opening a ticket. No prorated refunds after that. - Sign-up needs accurate contact and billing details. No ID or KYC, but every order gets a human review (a first order may take about 15 minutes). Orders placed over a VPN or proxy are flagged. Service is not offered to nationals or residents of Türkiye. - SLA: 99.9% network uptime and 99.99% power uptime, with credits on request. - Network: one dedicated IPv4 per VPS, IPv6 on request by ticket, self-service reverse DNS, metered monthly traffic on a 10 Gbps uplink, outbound port 25 open for low-volume mail. No floating IPs and no private VLAN (use an overlay such as Tailscale). Large DDoS attacks are null-routed. - Not offered: GPU instances, nested virtualization, free trial, Terraform provider. A management API exists and is enabled on request by ticket. - Prohibited: torrents and P2P, Tor nodes, public VPN or proxy services, crypto mining (staking is fine), bulk email, adult content, gambling, reselling. Full list at https://vpsdime.com/aup - Two-factor authentication is mandatory on every account. ## Product lines ### Linux VPS — https://vpsdime.com/linux-vps LXC containers (new deployments since 2026), shared Intel Xeon CPU, dedicated RAM, enterprise NVMe in RAID10. Resize up or down live with no downtime and the same IP. Managed network firewall included. Optional Nightly Backups. Order any plan at https://vpsdime.com/buy/{plan code in lower case}, for example https://vpsdime.com/buy/linux6gb. | Plan | vCPU | RAM | NVMe | Traffic | Price/month | | --- | --- | --- | --- | --- | --- | | Linux4GB | 2 | 4 GB | 20 GB | 1 TB | $5 | | Linux6GB | 4 | 6 GB | 30 GB | 2 TB | $7 | | Linux12GB | 4 | 12 GB | 60 GB | 4 TB | $14 | | Linux18GB | 4 | 18 GB | 90 GB | 6 TB | $21 | | Linux24GB | 4 | 24 GB | 120 GB | 8 TB | $28 | | Linux30GB | 4 | 30 GB | 150 GB | 10 TB | $35 | | Linux36GB | 4 | 36 GB | 180 GB | 12 TB | $42 | | Linux72GB | 4 | 72 GB | 360 GB | 24 TB | $84 | | Linux108GB | 4 | 108 GB | 540 GB | 36 TB | $126 | | Linux144GB | 4 | 144 GB | 720 GB | 48 TB | $168 | | Linux288GB | 4 | 288 GB | 1440 GB | 96 TB | $336 | Operating systems: Ubuntu 24.04, Ubuntu 26.04, Ubuntu 22.04, Ubuntu 25.04, Debian 13, Debian 12, AlmaLinux 10, AlmaLinux 9, Rocky Linux 10, Rocky Linux 9, Arch Linux, CentOS 10 Stream, CentOS 9 Stream, Fedora 43, Fedora 42, OpenSUSE 16, Devuan Excalibur, Slackware, Alpine 3.23, Alpine Edge, VoidLinux, Oracle Linux 9. One-click applications (installed on Ubuntu 24.04): Coolify, Traccar, Immich, Code Server. ### Premium VPS — https://vpsdime.com/premium-vps KVM with fully dedicated CPU, RAM and write-intensive NVMe. Nightly Backups included. Custom ISO, BSD, kernel modules and kubeadm Kubernetes supported. Upgrade-only: cannot be moved to a smaller plan later. | Plan | Dedicated cores | RAM | NVMe | Traffic | Price/month | | --- | --- | --- | --- | --- | --- | | Premium4GB | 1 | 4 GB | 60 GB | 2 TB | $20 | | Premium8GB | 2 | 8 GB | 120 GB | 4 TB | $40 | | Premium12GB | 3 | 12 GB | 180 GB | 6 TB | $60 | | Premium16GB | 4 | 16 GB | 240 GB | 8 TB | $80 | | Premium24GB | 6 | 24 GB | 360 GB | 12 TB | $120 | | Premium32GB | 8 | 32 GB | 480 GB | 16 TB | $160 | | Premium64GB | 16 | 64 GB | 960 GB | 32 TB | $360 | Operating systems: Ubuntu 25.04, Ubuntu 24.04, Ubuntu 22.04, Debian 13, Debian 12, AlmaLinux 10, AlmaLinux 9, Rocky Linux 10, Rocky Linux 9, Arch Linux; any other non-Windows OS by custom ISO on request. ### Windows VPS — https://vpsdime.com/windows-vps Hyper-V, Windows Server Datacenter with the licence included, RDP plus a browser console. Optional Nightly Backups. | Plan | vCPU | RAM | NVMe | Traffic | Price/month | | --- | --- | --- | --- | --- | --- | | WIN6GB | 2 | 6 GB | 50 GB | 4 TB | $15 | | WIN8GB | 4 | 8 GB | 100 GB | 8 TB | $20 | | WIN12GB | 5 | 12 GB | 150 GB | 12 TB | $30 | | WIN16GB | 6 | 16 GB | 200 GB | 16 TB | $40 | | WIN32GB | 8 | 32 GB | 400 GB | 32 TB | $80 | | WIN64GB | 12 | 64 GB | 800 GB | 64 TB | $160 | | WIN128GB | 16 | 128 GB | 1600 GB | 128 TB | $320 | Operating systems: Windows Server 2025, Windows Server 2022, Windows Server 2019. ### Storage VPS — https://vpsdime.com/storage-vps Not currently orderable: every Storage VPS plan is out of stock. The product page still describes the line (enterprise HDD in RAID10 for backups and archives). Check the page or ask support before recommending it. Add-ons, from the Linux VPS order form: Nightly Backups $5/month, Additional vCPU $5/month per 1 vCPU, Additional Storage $2.50/month per 10GB, Extra Bandwidth $4/month per 1TB, Extra IP Address $2/month each. Nightly Backups are included on Premium VPS, kept three days, stored off-site and downloadable as a disk image. Also available: Offloaded MySQL $20 one-off, free DNS hosting, location move $4 one-off. ## Locations Dallas TX, Los Angeles CA, Seattle WA and Piscataway NJ (United States); London/Maidenhead (United Kingdom); Amsterdam (Netherlands). Not every line is stocked in every location. IP addresses belong to a location and change if a VPS is moved. Orderable on 2026-09-16, from the live catalogue: - Linux VPS: Dallas (US), Los Angeles (US), Amsterdam (NL), London (UK) - Premium VPS: Los Angeles (US), Dallas (US), Amsterdam (NL) - Windows VPS: Dallas (US), Los Angeles (US), Amsterdam (NL) - Storage VPS: not currently orderable Plans out of stock on 2026-09-16: none. - [Looking glass](https://vpsdime.com/looking-glass): test IPs, ping, mtr and download files per location - [Dallas](https://vpsdime.com/dallas-vps) · [Seattle](https://vpsdime.com/seattle-vps) · [Los Angeles](https://vpsdime.com/los-angeles-vps) · [New Jersey](https://vpsdime.com/new-jersey-vps) · [London](https://vpsdime.com/london-vps) · [Amsterdam](https://vpsdime.com/amsterdam-vps) ## Pages that answer a specific question - [Pre-sales FAQ](https://vpsdime.com/knowledgebase/presales/pre-sales-faq): pricing, billing, specs, virtualization, network, email, backups, support, privacy and ordering on one page - [Compare services](https://vpsdime.com/compare-services): Linux vs Premium vs Windows vs Storage, feature by feature - [Linux VPS vs Premium VPS](https://vpsdime.com/knowledgebase/presales/linux-vps-vs-premium-vps) · [Choosing a plan size](https://vpsdime.com/knowledgebase/presales/choosing-a-vps-plan-size) · [Managed vs self-managed](https://vpsdime.com/knowledgebase/presales/managed-vs-unmanaged) - [Hardware](https://vpsdime.com/hardware): Dell nodes, dual Intel Xeon Gold, 384 GB+ ECC per node, 3 DWPD NVMe in RAID10, Juniper network, A+B power - [What support covers](https://vpsdime.com/knowledgebase/support-coverage/what-support-covers) · [Response times](https://vpsdime.com/knowledgebase/support-coverage/response-times-and-priorities) - [What you can run](https://vpsdime.com/knowledgebase/acceptable-use/whats-allowed) · [Acceptable Use Policy](https://vpsdime.com/aup) · [Terms of Service](https://vpsdime.com/tos) · [Privacy policy](https://vpsdime.com/privacy-policy) - [Payment methods](https://vpsdime.com/knowledgebase/billing/payment-methods) · [Refunds](https://vpsdime.com/knowledgebase/billing/refunds) · [Taxes](https://vpsdime.com/knowledgebase/billing/taxes) · [Billing timeline](https://vpsdime.com/knowledgebase/billing/billing-timeline) - [Service status and incident history](https://vpsdime.com/service-status) - [Customer reviews](https://vpsdime.com/customer-reviews) · [About](https://vpsdime.com/about-us) · [Why choose us](https://vpsdime.com/why-choose-us) - [Free sponsored VPS](https://vpsdime.com/free-vps) for open-source projects and communities · [Affiliate program](https://vpsdime.com/affiliate-program): 10% recurring ## Knowledge base 203 articles at https://vpsdime.com/knowledgebase, every one indexed with a one-line summary at https://vpsdime.com/knowledgebase/llms.txt. Every article is also available as Markdown at its URL with .md appended, and all of them in one file at https://vpsdime.com/knowledgebase/llms-full.txt. - [Getting started](https://vpsdime.com/knowledgebase/getting-started): 21 articles - [Client area](https://vpsdime.com/knowledgebase/client-area): 53 articles - [Billing policies](https://vpsdime.com/knowledgebase/billing): 11 articles - [Technical questions](https://vpsdime.com/knowledgebase/technical-questions): 32 articles - [Troubleshooting](https://vpsdime.com/knowledgebase/troubleshooting): 28 articles - [Windows VPS](https://vpsdime.com/knowledgebase/windows-vps): 35 articles - [Buying a VPS](https://vpsdime.com/knowledgebase/presales): 15 articles - [Support coverage](https://vpsdime.com/knowledgebase/support-coverage): 3 articles - [Acceptable use](https://vpsdime.com/knowledgebase/acceptable-use): 5 articles - [My VPS is down](https://vpsdime.com/myvpsisdown): self-service troubleshooter ## Guidance for agents - Quote the plan tables above for specs and prices; they are read from the product catalogue on the date in the footer. Stock changes, so confirm a location on the order form before promising it. - Ordering, cancelling, resizing and tickets happen in the client area (https://vpsdime.com/clientarea) after the user signs in. There is no self-service API key, so an agent cannot order or resize on a user's behalf. Treat any order as a purchase and confirm with the user first. - Good fit: high-RAM Linux workloads on a budget, Windows RDP servers, self-hosted apps (Coolify, Docker), dev and test boxes, game servers, AI inference. Not a fit: GPU workloads, anything needing managed services, torrents, Tor or public VPNs, bulk email, or users in Türkiye. - Support tickets should contain real command output, not chatbot transcripts. ## Use of this content VPSDime permits search indexing, AI training, and AI-generated answers based on its public pages, and states this in robots.txt as `Content-Signal: search=yes, ai-input=yes, ai-train=yes`. When quoting, attribute VPSDime and link the page. The knowledge base is the authoritative source for how the service behaves; marketing pages summarise it. ## Optional - [News and announcements](https://vpsdime.com/news): incident and maintenance history back to 2013 - Articles: [Benefits of a VPS](https://vpsdime.com/benefits-of-vps) · [Can a cheap VPS be reliable?](https://vpsdime.com/can-a-cheap-vps-be-reliable) · [Serverless vs servermore](https://vpsdime.com/serverless-vs-servermore-high-ram-vps) · [Coolify one-click](https://vpsdime.com/coolify-one-click-vps-deployment) · [Developer sandbox VPS](https://vpsdime.com/developers-sandbox-throwaway-vps) · [Windows build server](https://vpsdime.com/windows-vps-build-server) - [Careers](https://vpsdime.com/careers) · [Contact](https://vpsdime.com/contact-us) - Sitemap: https://vpsdime.com/sitemap.xml ## Notes for anyone quoting this Prices are USD per month unless marked per year, exclude VAT and sales tax, and have not changed since 2013. Plan tables, operating-system lists and stock were generated on 2026-09-16 from the product catalogue; the order form is authoritative for anything newer. --- # Full site content Everything below is the text of vpsdime.com, one page per section, in the order: products, company and infrastructure, locations, policies, the knowledge base, then articles. Each page starts with its URL and, for knowledge base articles, the date it was last reviewed. Prices are USD and exclude tax. # Products ## Cheap VPS Hosting Starting at $5/Month URL: https://vpsdime.com/ Summary: VPSDime offers the best cheap VPS for just $5.00 USD ### Trusted by 60000+ businesses and entrepreneurs. [Buy VPS Now ($7 USD)](https://vpsdime.com/buy/linux6gb) 974818 GB RAM Provisioned 15 Min Support Response Times 6 Diverse Locations 2013 Founded ### What Makes Us Stand Out Fast, Inexpensive, Reliable VPS Hosting with Awesome Support Owned and Operated by System Admins Our team is entirely made up of seasoned industry veterans who genuinely enjoy what they do. We have made our hobby our business. Designed to be Affordable We prove that cheap VPS services can be fast and reliable at the same time. VPSDime is founded to fill the gap in the market. Why pay more when you don't have to? We Actually Care You are not just a number in our books. We are big enough to provide top notch service and small enough to appreciate your patronage. Extreme and consistent performance High frequency CPUs, ample RAM and storage built with write intensive enterprise NVMe SSDs coupled with 10Gbps uplinks is the recipe of our chart-topping performance. Non-tiered, Direct Support We don't believe in tier based support where the customer needs to jump through hoops to get meaningful replies. We reply in 15 minutes and to the point. Mission-Critical Infrastructure Operating in fully staffed, SSAE 16 compliant data centers with diverse fibre paths and redundant power feeds to guarantee 99.99% uptime. You know what you pay Completely transparent, old school monthly billing with no contract lock-ins. You get a service that lasts for years without the worry of keeping your balance in check. Scale up and down with no downtime Our Linux VPS product line enables you to transparently upgrade or downgrade at any time. You can scale up or down easily with just a few clicks. Proven Reliability 13 years of dedication. 13 years of passion. 13 years of growth. 13 years of excellent track record. VPSDime services both enterprises and enthusiasts. No overselling. No overloading. We do not overload. In fact, we load our hardware nodes under their capacity to make sure all of our customers have spare capacity when needed. High Performance Network. Healthy Environment. Carefully engineered, constantly monitored, highly available network with reputable IP space and abuse-free environment. Simplified Management Manage your VPS easily with our custom developed, intuitive control panel. ### Our Locations VPSDime provides 6 geographically diverse locations allowing you to host your application across 2 different continents. [Seattle, WA](https://vpsdime.com/seattle-vps) [Los Angeles, CA](https://vpsdime.com/los-angeles-vps) [Dallas, TX](https://vpsdime.com/dallas-vps) [Piscataway, NJ](https://vpsdime.com/new-jersey-vps) [London, UK](https://vpsdime.com/london-vps) [Amsterdam, NL](https://vpsdime.com/amsterdam-vps) ### Powerful Control Panel Simplified management with a ton of features - Scale up and down Easily upgrade or downgrade your VPS's resources with a few clicks - Out-of-band Console Connect to your VPS's console directly on the control panel when needed - Performance Graphs Track the performance of your VPS by visually appealing graphs that make sense - Power Functions Power on, reset, power off your VPS ### Frequently Asked Questions - Billing / Payments - Technical - Support - Legal / Privacy - About VPSDime Billing / Payments #### What payment methods do you accept? All major credit and debit cards (Visa, MasterCard, American Express, Discover, JCB, UnionPay), PayPal, Apple Pay, Google Pay, Samsung Pay, Alipay, WebMoney, iDEAL, Bancontact, Sofort, GiroPay, DOKU, Boleto, PIX and more, plus Bitcoin and USDT. Prepaid and virtual cards work too. #### Do you offer a money back guarantee? Yes. Your first order is covered by our 72-hour money-back guarantee. If VPSDime isn't what you're looking for, cancel within 72 hours and ticket us, and we'll refund the full amount. No refunds are provided if there has been an infraction of the Terms of Service or Acceptable Use Policy (TOS/AUP). #### Do you accept Bitcoin? Yes, we accept both Bitcoin and USDT. Together with prepaid and virtual cards, they're a good option if you'd rather keep your payment private. #### How will I be billed for my services? You choose the cycle: monthly, quarterly, semi-annual or annual billing. Longer cycles are priced proportionally, and you can change your billing cycle yourself from the client area at any time. #### How long does VPS provisioning take? Your VPS is provisioned within minutes of payment. Because we manually verify every order to keep our network clean, a first order may take around 15 minutes before it provisions. #### Can I upgrade/downgrade my account? Yes, it's self-service from the client area. On Linux VPS, plan changes are live and instant with no downtime and the same IP. Windows VPS upgrades and downgrades apply with a quick reboot. Premium VPS is upgrade-only, so start with the size you need and grow from there. #### Can I purchase an additional IP Address? Yes, additional IPv4 addresses are $2 per month each, ordered from the client area. All IP address orders are subject to a short justification before being provisioned. #### Am I locked in to a contract? No. There's no contract and no minimum term. Cancel any time from your client area, effective immediately or at the end of your billing period. #### What happens if I run out of traffic allocation? Our system emails you at 75% and again at 100% of your monthly allowance. If you don't add traffic or upgrade within 24 hours of hitting 100%, the VPS is suspended until you do, or until your allowance resets on the 1st of the month. #### Can I purchase additional traffic? Of course. Extra traffic allocation is available any time from the Extra Features tab in your client area, prorated to your renewal date. #### Do you have an affiliate program? Sure, we do. You earn a generous 10% recurring commission on every customer you refer, for as long as they stay. Withdraw your earnings as account credit (from $5) or via Payoneer (from $50). #### Can I set automated payments for my VPS? Of course. Save your card and set it to renew your VPS's automatically, or set up a PayPal billing agreement instead. You can switch back to manual renewal whenever you like. #### Can I load funds into my credit balance with you? Yes. Top up a credit balance from the Add Funds page in your client area, and your invoices are paid from it automatically. #### How are you able to provide cheap VPS? We own the whole stack: our network, IP space, hardware and virtualization software, so nobody else's margin is baked into the price. Our servers are hand-built with high-capacity hardware and run efficiently with plenty of headroom. It's also why we've never raised our prices since 2013. ### What Our Clients Say About Us Highly recommended by thousands of real customers VPSDime's offerings fit the needs of developers looking for low-cost and high-performant VPS hosting. [Read more](https://www.hostingadvice.com/blog/vpsdime-offers-stable-and-reliable-vps-hosting-on-a-budget/) @ HostingAdvice An excellent service, fast servers, cheap, fast and kind support. I love this company. [Read more](https://www.trustpilot.com/reviews/5eac3a08086b6409bc92e522) @ TrustPilot Price - Service - Reliability: the three things that matter most with VPS hosting are the three things VPSDime focus on. I highly recommend them! [Read more](https://hostadvice.com/hosting-company/vpsdime-hosting-solutions-reviews/121796/) @ HostAdvice I love VPSDime. Brilliant value for money. 100% top notch support and customer service. Used them for 2 years now with no problems. [Read more](https://www.trustpilot.com/reviews/5ee973ff7dd7530828c2f2ca) @ TrustPilot And the support of vpsdime is one of the best i have ever seen. Every ticket i create, i receive a response within minutes. Sometimes it even seems they are waiting for my ticket to respond immediately. [Read more](https://community.centminmod.com/threads/4gb-vpsdime-premium-kvm-vps-benchmarks-review.10646/#post-45580) @ CentminMod VPSdime is simply amazing. Stability, uptime, price and incredible support. [Read more](https://www.trustpilot.com/reviews/5cd435cba843690980d43f8e) @ TrustPilot Impressive response time, a minute later got a response for my ticket. Enjoying the service so far, thanks. [Read more](https://twitter.com/CommissarVoop/status/1296145553420582912) @ Twitter VPSDime shows they truly care about their clients by helping in any way they can. I am continuously impressed by their service and uptime, and recommend them to everyone I know looking for a VPS solution. Very friendly and good support. I had a problem caused by me and it has been solved positively for me. That's really nice. About VPS: runs very smoothly and without downtimes. [Read more](https://www.trustpilot.com/reviews/6017e940679d9701d07f1c08) @ TrustPilot VPSDime provides really great services. ... VPSDime offers VPS servers for a cheap price. But the VPS servers work fast and are reliable. [Read more](https://webhostreviews.com/reviews/vpsdime) @ WebHostReviews This company is legit, the service is awesome, the VPSes aren't oversold and it's really, really inexpensive. [Read more](https://www.trustpilot.com/reviews/60a30560f9f4870b70069975) @ TrustPilot Long story short. These guys are brilliant. By any means host your server there, not somewhere else. I have only tried a few other hosters, for big projects and small, and nobody gets close in terms of support. [Read more](https://hostadvice.com/hosting-company/vpsdime-hosting-solutions-reviews/85562/) @ HostAdvice Support is very good and pricing is excellent. Also other providers will shut you down when you go over limit, VPSDime support politely asked what the issue with our machine is and they even help solving it. [Read more](https://webhostinggeeks.com/providers/vpsdime/review-id34101) @ WebHostingGeeks Using their hosting services since a few days and I am completely amazed about their quality and services. VPS's are very reliable, enormous fast and easy to deploy [Read more](https://www.trustpilot.com/reviews/5e4705b53c93ae0bc4023aca) @ TrustPilot I've been using VPSDime's high memory VPSes for 4 years now as my main hosting solution and couldn't be happier. [Read more](https://hostadvice.com/hosting-company/vpsdime-hosting-solutions-reviews/77073/) @ HostAdvice Tops. I would highly recommend. Had services with them for about 3 years. Best bang for buck especially for with high-memory instances. [Read more](https://www.trustpilot.com/reviews/5f744f1d798e6f0aa4e7c13a) @ TrustPilot VPSDime probably has one of the best customer support for server providers I've ever seen! Responsive and very helpful people. :) [Read more](https://twitter.com/johnrequiroso/status/927932336745758720) @ Twitter I am a customer of VPSDime since 2014. They have been a truely great hosting company and have some great services. [Read more](https://www.trustpilot.com/reviews/5c1e99269d378004f0e36720) @ TrustPilot I'm hosting only one cheap VPS at VPSDime, but I can't say I've ever seen anything less than top-notch service there. [Read more](https://webhostinggeeks.com/providers/vpsdime/review-id34841) @ WebHostingGeeks Had to get support from VPSDime today. I was skeptical if they will still reply fast as the first time. They didn't disappoint me. [Read more](https://twitter.com/_aminulhaque/status/1285586483835879425) @ Twitter I'm absolutely getting for what I'm paying. Customer support is really good and man they have the skills to troubleshoot. [Read more](https://www.trustpilot.com/reviews/60a10a36f9f4870a94a3c1ae) @ TrustPilot If you are looking for a robust hosting, with a good price, with incredible support, VPSDime is your best option, without a doubt! [Read more](https://webhostinggeeks.com/providers/vpsdime/review-id35417) @ WebHostingGeeks I have nothing but high praise for VPSDime. In the 14+ months I've been with them I've had nothing but the very best support and service. They have been up 100% too which is a bit rare these days! [Read more](https://twitter.com/EdKings/status/1037300847645020161) @ Twitter #### Cheap VPS Hosting That Actually Works: The Engineering Behind $5/Month Performance The word "cheap" can make you nervous, and for good reason. Webster's Dictionary defines it in two ways: 1. Obtainable at a low price. 2. Of inferior quality or worth. When searching for a "cheap VPS," you're hoping for the first definition but rightfully worried you'll get the second. You’re not wrong to be cautious. In the hosting industry, "cheap" is often a red flag for overloaded servers, sluggish performance, and fly-by-night operations run by people who only know one thing: a low price sells. They build unsustainable products, oversell resources to the breaking point, and when it inevitably fails, they vanish, leaving you with nothing. But what if you could get the low price *without* the inferior quality? It's not a fantasy. It's just a matter of engineering. --- #### How We Make Quality Affordable: The VPSDime Difference We don't offer a cheap service. We offer a **high-value service at a low price**. The difference is in our philosophy. Instead of cutting corners, we eliminated them entirely by building a lean, efficient, and automated platform from the ground up. ##### 1. Radical Efficiency & Automation We believe your money should go towards steel and silicon, not glass offices and bloated payroll. - **We keep our operations lean.** We don't have fancy headquarters or a marketing department spending millions on Super Bowl ads. Our growth comes from word-of-mouth, driven by a product that speaks for itself. - **We automate everything.** We are engineers and developers first. We’ve built our own systems to handle server deployments, fraud monitoring, abuse management, and maintenance. This reduces our human overhead, minimizes errors, and allows our expert team to focus on network performance and hardware optimization—the things that directly impact your server's speed. - **We write our own code.** We don't pay expensive licensing fees for bloated third-party software. By using and contributing to open-source projects, we stay in full control of our stack, reduce costs, and pass those savings directly to you. ##### 2. End-to-End Ownership We are not resellers or middlemen. We are the source. - **We own our hardware.** We don't rent servers from someone else. Every CPU, RAM stick, and NVMe drive is our own. This gives us complete control over performance, security, and reliability. - **We own our network and IP space.** We build and manage our own network, using our own gear and our own IP addresses. This means we aren't at the mercy of another provider's routing decisions or network congestion. The result is lower latency and more consistent bandwidth for you. - **We shop smarter.** As veterans in the hardware industry, we know what truly matters for performance. We don't chase bleeding-edge, overpriced components. We invest in proven, enterprise-grade hardware in bulk, focusing on high-frequency CPUs and robust NVMe storage that deliver real-world speed and reliability. ##### 3. A Laser Focus on What Matters We provide what you need and nothing you don't. - **Self-managed freedom.** Our service is for users who are comfortable in the command line and want total control. We provide a rock-solid server and network, and you handle the rest. We don't bundle expensive, managed support or control panels you don't need, which keeps your price radically low. - **No phone or live chat support.** This is a deliberate choice. Instead of paying staff to sit by a phone, we invest in a highly-skilled ticket-based support team. They are real technicians, not script-readers. When you have an issue with our network or hardware, you get a fast, expert response—**typically in under 5 minutes.** --- #### Who is Our VPS For? We provide a powerful, affordable foundation for a wide range of projects and people. - **Developers & System Admins:** Get full root access to a powerful sandbox for testing, deploying applications, and taking complete control of your environment. - **Entrepreneurs & Startups:** Launch your proof of concept or run your business-critical applications on a platform that offers reliability without demanding a huge chunk of your seed money. - **Small Businesses:** Host your website, CRM, and email servers on a fast, reliable platform that can scale with your success. - **Self-Hosters & Hobbyists:** Take back control of your data from Big Tech. Learn Linux, run a media server, or host your personal projects without breaking the bank. - **Gamers:** Spin up a private, high-performance server for your community with the generous bandwidth you need for a lag-free experience. --- #### Who Isn't This For? We believe in transparency. Our service is not the right fit for everyone, and that's okay. We are likely **not** for you if: - You need hand-holding or step-by-step guidance to manage a server. - You require managed hosting where a provider handles your software, updates, and security. - You absolutely must have phone or live chat support. --- #### Simple, Predictable Pricing. The Way It Should Be. In a world of complex cloud billing, we keep it simple. - **No hourly rates.** Stop worrying about a surprise bill at the end of the month. - **No calculators needed.** Our pricing is flat, simple, and listed right on the page. - **No overage fees.** You know exactly what you will pay, every single month. This isn't about being cheap. This is about being smart. This is high-performance hosting, engineered to be affordable. ### Latest Blog Posts Articles related to VPS industry from VPSDime Staff 15Apr 11Nov 28Oct --- ## Linux Virtual Private Servers URL: https://vpsdime.com/linux-vps Summary: Extremely affordable Linux VPS plans with enterprise NVMe SSDs offered by VPSDime High Memory VPS Solutions At An Affordable Price. #### Deploy Your Linux VPS in Minutes What makes our Linux VPS services stand out from the rest of the competition is our very generous RAM allocations coupled with lightning fast enterprise NVMe SSD storage on every plan, enabling you to run resource-demanding applications at a perfectly affordable price point, coupled with responsive support 24 hours a day, 7 days a week. | CPU | Core | RAM | Storage | Transfer | Uplink | Price | | | --- | --- | --- | --- | --- | --- | --- | --- | | Intel® Xeon® Gold | 2 CPU | 4GB ECC | 20GB SSD | 1TB | 10Gbps | $5.00/mo | [Order Now](https://vpsdime.com/buy/linux4gb) | | Intel® Xeon® Gold | 4 CPU | 6GB ECC | 30GB SSD | 2TB | 10Gbps | $7.00/mo | [Order Now](https://vpsdime.com/buy/linux6gb) | | Intel® Xeon® Gold | 4 CPU | 12GB ECC | 60GB SSD | 4TB | 10Gbps | $14.00/mo | [Order Now](https://vpsdime.com/buy/linux12gb) | | Intel® Xeon® Gold | 4 CPU | 18GB ECC | 90GB SSD | 6TB | 10Gbps | $21.00/mo | [Order Now](https://vpsdime.com/buy/linux18gb) | | Intel® Xeon® Gold | 4 CPU | 24GB ECC | 120GB SSD | 8TB | 10Gbps | $28.00/mo | [Order Now](https://vpsdime.com/buy/linux24gb) | | Intel® Xeon® Gold | 4 CPU | 30GB ECC | 150GB SSD | 10TB | 10Gbps | $35.00/mo | [Order Now](https://vpsdime.com/buy/linux30gb) | | Intel® Xeon® Gold | 4 CPU | 36GB ECC | 180GB SSD | 12TB | 10Gbps | $42.00/mo | [Order Now](https://vpsdime.com/buy/linux36gb) | | Intel® Xeon® Gold | 4 CPU | 72GB ECC | 360GB SSD | 24TB | 10Gbps | $84.00/mo | [Order Now](https://vpsdime.com/buy/linux72gb) | | Intel® Xeon® Gold | 4 CPU | 108GB ECC | 540GB SSD | 36TB | 10Gbps | $126.00/mo | [Order Now](https://vpsdime.com/buy/linux108gb) | | Intel® Xeon® Gold | 4 CPU | 144GB ECC | 720GB SSD | 48TB | 10Gbps | $168.00/mo | [Order Now](https://vpsdime.com/buy/linux144gb) | | Intel® Xeon® Gold | 4 CPU | 288GB ECC | 1440GB SSD | 96TB | 10Gbps | $336.00/mo | [Order Now](https://vpsdime.com/buy/linux288gb) | #### Key Features of Linux VPS Excellent value for your money. Great for Most Workloads Whether you are an established enterprise, independent contractor or a small start-up, our Linux VPS will handle every task you throw at it without breaking a sweat. It's a virtualized environment that comes with full root access. Best Bang for Your Buck Our Linux VPS product is designed with the highest performance to cost ratio in the market. It's a workhorse with a cost of a cup of coffee a month. Its abilities are limited only by your imagination. On-the-fly Scaling You can start with our cheapest plan and then upgrade to a higher plan without a second of downtime. Scale from 4GB memory to 288GB memory with a few mouse clicks or the other way around. All the upgrades/downgrades are completely transparent to you. #### High RAM Capacity We offer generous memory allocations which are completely dedicated to you at all times. Our Linux VPS are perfect for hosting RAM intensive applications without risking server crashes during high traffic for your application. #### Enterprise NVMe SSD Storage Enterprise-grade NVMe Solid State Drives ensure consistent performance for I/O-intensive applications and website, enabling you to serve files and query databases at blazing speeds. Say goodbye to bottlenecks. #### No Overselling Our non-oversold servers means high availablity and less downtime for you. Memory and storage resources are totally dedicated to you 24/7, whilst only CPU and network are shared with you and your neighbors. #### Eliminate noisy neighbours We hand pick your VPS neighbours. Our system automatically load balances our host nodes and this enables us to provide highly consistent performance. ### Deploy your VPS with any of these available distributions Ubuntu, Debian, AlmaLinux, Rocky Linux, CentOS Stream, Fedora, openSUSE, Arch, Alpine, Void, Devuan, Slackware and Oracle Linux: 22 images to pick from at deploy time, or a one-click Coolify, Immich, Traccar or Code Server install. - Ubuntu - CentOS - Debian - Fedora - Alma Linux - Rocky Linux #### Our Locations VPSDime provides 6 geographically diverse locations allowing you to host your application across 2 different continents. [Seattle, WA](https://vpsdime.com/seattle-vps) [Los Angeles, CA](https://vpsdime.com/los-angeles-vps) [Dallas, TX](https://vpsdime.com/dallas-vps) [Piscataway, NJ](https://vpsdime.com/new-jersey-vps) [London, UK](https://vpsdime.com/london-vps) [Amsterdam, NL](https://vpsdime.com/amsterdam-vps) #### Valuable Addon Features You'll be impressed with our offerings. - ### Offloaded MySQL For a $20 one time fee, we provide access to our high-performance Offloaded MySQL services, managed in your client area. - ### Free DNS Hosting Ability to use any domain, from any domain registrar. Manageable directly from our client panel for ease of use. - ### Nightly Backups For just $5 per month, your server can be backed up by our nightly automated backup system. Your backups will have a 3 day retention period. - ### Remote Desktop Setup For a $20 one time fee, we can install a remote desktop where we install a window manager from a selection of popular choices. - ### Varnish Setup For a $20 one time fee, we will install and configure Varnish caching server on your services for improved performance and responsiveness. - ### FTP Server Setup For a $10 one time fee, we will install and configure an FTP server to enable you to easily transfer files. - ### Server Management For $10 per 10 minutes, our highly skilled technicians can perform management tasks on your server at your request. - ### cPanel Hardening For a $25 one time fee, we will harden your cPanel installation's security by setting up a firewall and tweaking common settings. #### Easy to Manage Our easy-to-use custom control panel helps you manage your VPS easily #### Common Features of VPSDime Services #### 99.99% Power & Network SLA If we fail to deliver, we’ll credit you for the amount of time that service was unavailable. #### Sub 15 minute Support Response We pride ourselves with the speediness of our customer support department. #### Enterprise-grade NVMe SSDs We only use write intensive enterprise-grade NVMe solid state drives for stable performance and latency. #### 72 Hour Money Back Guarantee Should you not satisfied for any reason, you can contact us to get your payment refunded. #### Frequently Asked Questions Answers to the most frequently asked questions about Linux VPS are below. Have another question? Simply contact us at [sales@vpsdime.com](mailto:sales@vpsdime.com) #### What is Linux VPS in a nut-shell? Linux VPS is a virtualized container designed to simulate a dedicated server. It's completely private to you and gives you full root access. You interact with it just like you interact with a physical computer with Linux operating system installed on. #### How can I connect to my Linux VPS? Linux VPS's arrive with OpenSSH pre-installed. You could connect to your VPS using industry standard SSH console. Alternatively, you could install a desktop environment such as xFCE or Gnome and connect using remote desktop. #### What virtualization technology do you use? LXC (Linux Containers) is the backend technology for our Linux VPS line. By utilizing this technology, we are able to provide you with real bare metal like performance with no virtualization overhead. #### How long does the VPS provisioning take? If it's your first order with us, then there is going to be a 10-15 minute delay while we manually screen your order. #### What are the advantages of using LXC? With LXC the kernel is not virtualized. This gives you ability upgrading and downgrading your VPS on the fly without a single second of downtime. Also since there is no virtualization overhead on the kernel layer, you feel the power of the hardware underneath the fullest. #### Can I upgrade or downgrade my Linux VPS easily? Scaling up and down Linux VPS is very simple and transparent to the eye. It happens without interruption so you could enjoy downtime free upgrades and downgrades. #### Are the resources dedicated to my VPS? Memory and disk space are completely dedicated to your VPS. CPU power is, however, shared with other VPS's on the host node. As our in-house fully automated monitoring systems consistently taking care of any disturbances, you always have all the power you need when required. Providing shared CPU is helping us passing the savings to our customers and therefore providing an absolute bang for your buck. #### How is Linux VPS so cheap? We own our racks and all of our hardware. Our compute nodes are built for very high capacity coupled with our in-house optimization software to handle high number of VPS without breaking a sweat. All the software we use for virtualization is also built in-house. All of this keeps our running costs at minimum and helps us providing an excellent value to our customers. #### Which Linux distros can I use with my VPS? You could use Ubuntu, Debian, CentOS, Alma Linux or Rocky Linux with your Linux VPS. #### Can I reinstall my VPS's operating system? Of course, you could reinstall your Linux distro on your client area with a few simple clicks. It will only take a few seconds before your VPS is ready for you again. #### What kind of technical support do you provide? Our service is self-managed. This means that our customers are responsible for managing their own VPS's. However, it doesn't mean that you are left alone. Our technicians are always available to reply your questions within minutes and help you in a best effort basis. We are not going to manage everything for you but we are going to help you resolve your issues and will always point you to the right direction. #### Do you backup my VPS? By default, Linux VPS's are not backed up. However, you could purchase a Nightly Backup addon which costs only $5/month to have your VPS backed up nightly with 3 days retention. #### Is my VPS DDoS protected? Our network is able to handle small to medium attacks and for larger attacks, we have automated null-routing system. We recommend using Cloudflare for your website for DDoS protection. #### What are the differences between Linux VPS and Premium VPS? Linux VPS's are great for almost any use case, however if you are looking to use your own kernel or ability to utilize all of the CPU resources at all times without any interruption, then Premium VPS is recommended. #### Can I run Docker on Linux VPS? Sure, Docker is fully supported on our Linux VPS plans. Swarm and Kubernetes might need some tweaking. #### Do you support NFS, FUSE, TUN/TAP, GRE? Linux VPS comes all of these features enabled out of the box. It supports all the VPN software as well. #### Do you offer IPv6? IPv6 is offered multiple locations for our Linux VPS line. Please contact us to inquire more about this. #### A good word from our customers And the support of vpsdime is one of the best i have ever seen. Every ticket i create, i receive a response within minutes. Sometimes it even seems they are waiting for my ticket to respond immediately. [Read more](https://community.centminmod.com/threads/4gb-vpsdime-premium-kvm-vps-benchmarks-review.10646/#post-45580) @ CentminMod VPSDime's offerings fit the needs of developers looking for low-cost and high-performant VPS hosting. [Read more](https://www.hostingadvice.com/blog/vpsdime-offers-stable-and-reliable-vps-hosting-on-a-budget/) @ HostingAdvice #### First Step to Metamorphosis: A Linux VPS In the digital world, there are two distinct roles: the Consumer and the Creator. Most of us, for most of our lives, are Consumers. We scroll through feeds created by others, use software built by others, and store our data on platforms owned by others. We exist within digital structures we did not build and cannot control. It is a passive, comfortable, but ultimately limited existence. The Creator, however, operates on a different plane. A Creator is someone who builds, configures, and controls their own digital space. They don't just use the service; they are the service. A Linux Virtual Private Server (VPS) is the catalyst for this transformation. It is the workshop, the laboratory, and the blank canvas that provides the endless possibilities to begin this journey. It is the first, definitive step in your metamorphosis from a passive Consumer to an active Creator. ##### The Thrill of the First Creation The barrier to becoming a creator isn't intelligence; it's inertia. A Linux VPS shatters that inertia with immediate, tangible results. The experience is profoundly empowering. Imagine installing an open-source photo gallery on your VPS to share family pictures with your spouse, completely private and under your control. Or setting up a secure, personal cloud storage system, your very own Dropbox, for your family to use. That moment it works, that moment your spouse accesses the service you built, triggers a fundamental reward circuit in your brain. It's a powerful feeling of accomplishment and agency. You haven't just consumed a product; you have provided a solution. This small act of creation is the spark that ignites a new way of thinking about technology. ##### Shedding the Old Skin: The Myth of a "Difficult" Linux Let's be honest: Linux had a reputation. It was seen as an opaque, unforgiving system for elite programmers and system administrators. The command line was a black box, usability was an afterthought, and simple tasks often required arcane knowledge and compiling software from source code. Many were intimidated, and rightfully so. That Linux is a ghost. It no longer exists. The modern Linux ecosystem is the polar opposite. Thanks to decades of relentless development, mature software, and polished distributions like Ubuntu and Debian, Linux is now a model of clarity and efficiency. The "scary" command line has been revealed for what it truly is: the fastest and most direct path from intent to action. Consider the simple act of installing software. On a traditional desktop, you must: 1. Open a browser. 2. Search for the software on Google, dodging ads and questionable download sites. 3. Download an installer file. 4. Locate and run the installer. 5. Click "Next," "Agree," and "Next" again, hoping no unwanted bloatware is included. On a modern Linux VPS, you simply type: *$ sudo apt install software-name*. That's it. One clear, logical command. The system finds the official, secure version and handles the entire process. It is faster, safer, and infinitely more elegant. The black box has been opened, and inside is not complexity, but pure simplicity. ##### Your Support System: Learning in a World of Experts Transitioning into a Creator role is not a journey you take alone. The Linux ecosystem is built on a foundation of shared knowledge. - **The Built-in Manual:** Stuck on a command? You don't even need to go online. Simply type *$ man command-name* (e.g., *$ man ls*), and your terminal instantly displays a comprehensive, official manual explaining exactly what it does and how to use it. It's a complete encyclopedia at your fingertips. - **The Global Community:** You are backed by the largest and most active open-source community on the planet. For any problem you might encounter, thousands have encountered it before. A simple, well-phrased Google search will yield countless solutions on forums, blogs, and platforms like Stack Overflow. You are never truly stuck. - **Rock-Solid Stability:** The days of a bad update making a Linux system unbootable are long gone. Linux is the battle-tested core of the internet, powering everything from stock exchanges to planetary rovers. Hardware support is spectacular; developers and manufacturers now build for Linux, ensuring everything works out of the box. ##### The Ultimate Endorsement: The World is Built on Linux If you have any doubt about the relevance of this path, look no further than the industry itself. The vast majority of the public internet, the very services you use every day, runs on Linux. The world's supercomputers run on Linux. The Android phone in your pocket runs on the Linux kernel. The most telling endorsement comes from its biggest historical competitor. Microsoft, once a staunch opponent, now builds Linux directly into Windows via the Windows Subsystem for Linux (WSL). They know what every serious developer and administrator knows: to build the future, you need to use the tools that the future is built upon. ##### The Creator's Reward: Your Value in a SaaS World Here is the ultimate paradox: as more of the world becomes passive Consumers using polished Software-as-a-Service (SaaS) products, the value of a true Creator skyrockets. Companies are finding it increasingly difficult to hire talent with foundational Linux administration and systems knowledge. The skills you develop managing your own VPS (configuring a web server, securing a network, automating tasks with scripts) are no longer just a hobby. They are a direct pathway to a high-paying, in-demand career. By teaching yourself Linux on your own server, you are not just building services; you are building a future-proof skill set. Your metamorphosis begins with a single step. A Linux VPS is that step. It is the investment in yourself, the declaration that you are ready to move beyond consumption and begin the rewarding journey of creation. --- ## Premium Virtual Private Servers URL: https://vpsdime.com/premium-vps Summary: Production ready, premium virtual servers with dedicated resources by VPSDime Production-grade Solutions With Dedicated Resources. #### Deploy Your Premium VPS in Minutes Premium VPS services are the perfect companion to your important business. With dedicated resources, low contention, included backups, and advanced features, all built on enterprise-grade host nodes, Premium VPS will ensure that you can do business uninterrupted. Our fantastic support team is available for you 24/7/365 for anything you need. | CPU | Core | RAM | Storage | Transfer | Uplink | Price | | | --- | --- | --- | --- | --- | --- | --- | --- | | Intel® Xeon® Gold | 1 CPU | 4GB ECC | 60GB SSD | 2TB | 10Gbps | $20.00/mo | [Order Now](https://vpsdime.com/buy/premium4gb) | | Intel® Xeon® Gold | 2 CPU | 8GB ECC | 120GB SSD | 4TB | 10Gbps | $40.00/mo | [Order Now](https://vpsdime.com/buy/premium8gb) | | Intel® Xeon® Gold | 3 CPU | 12GB ECC | 180GB SSD | 6TB | 10Gbps | $60.00/mo | [Order Now](https://vpsdime.com/buy/premium12gb) | | Intel® Xeon® Gold | 4 CPU | 16GB ECC | 240GB SSD | 8TB | 10Gbps | $80.00/mo | [Order Now](https://vpsdime.com/buy/premium16gb) | | Intel® Xeon® Gold | 6 CPU | 24GB ECC | 360GB SSD | 12TB | 10Gbps | $120.00/mo | [Order Now](https://vpsdime.com/buy/premium24gb) | | Intel® Xeon® Gold | 8 CPU | 32GB ECC | 480GB SSD | 16TB | 10Gbps | $160.00/mo | [Order Now](https://vpsdime.com/buy/premium32gb) | | Intel® Xeon® Gold | 16 CPU | 64GB ECC | 960GB SSD | 32TB | 10Gbps | $360.00/mo | [Order Now](https://vpsdime.com/buy/premium64gb) | #### Key Features of Premium VPS Premium features for production hosting. Dedicated Resources Important workloads demand dedicated resources. Enjoy CPU, memory, and disk space fully dedicated to your VPS. Fewer users per host node means maximum performance at all times. Premium Features Included Every Premium VPS comes with nightly backups included. Sleep well knowing that your server can be rolled back in the event of a catastrophic issue. Your Server, Your Way Have a unique setup that requires a special operating system? Want to run a Kubernetes cluster? Need to special network kernel modules or firewall rules? Do all of this and more with Premium VPS. #### Powered By KVM/qemu Premium VPS is powered by the industry-proven KVM virtualization technology to offer a real dedicated server-like environment with ability to use any Linux or BSD operating system. #### Enterprise NVMe SSD Storage Enterprise-grade NVMe Solid State Drives ensure consistent performance for I/O-intensive applications and website, enabling you to serve files and query databases at blazing speeds. Say goodbye to bottlenecks. #### No Overselling Our non-oversold servers means high availablity and less downtime for you. All resources, such as CPU, memory, and storage are totally dedicated to you at all times, with only the network uplink shared with your neighbors. #### Production Ready Built for real world applications, whether you are a start-up or an enterprise. Great power comes with great stability. Ready to handle everything you throw at. Consistently high performance. ### Deploy your VPS with any of these available distributions Ready-made images for Ubuntu, Debian, AlmaLinux, Rocky Linux and Arch. FreeBSD, OpenBSD, Gentoo, Slackware, openSUSE, Red Hat or any other non-Windows OS from your own ISO, attached on request. - Ubuntu - CentOS - Debian - Fedora - OpenSUSE - Redhat Linux - ArchLinux - Gentoo - Slackware - FreeBSD - OpenBSD #### Our Locations VPSDime provides 6 geographically diverse locations allowing you to host your application across 2 different continents. [Seattle, WA](https://vpsdime.com/seattle-vps) [Los Angeles, CA](https://vpsdime.com/los-angeles-vps) [Dallas, TX](https://vpsdime.com/dallas-vps) [Piscataway, NJ](https://vpsdime.com/new-jersey-vps) [London, UK](https://vpsdime.com/london-vps) [Amsterdam, NL](https://vpsdime.com/amsterdam-vps) #### Easy to Manage Our easy-to-use custom control panel helps you manage your VPS easily #### Common Features of VPSDime Services #### 99.99% Power & Network SLA If we fail to deliver, you will receive a refund for the amount of time that service was unavailable. #### Sub 15 minute Support Response We are proud to be known for the efficiency of our customer support department. #### Enterprise-grade NVMe SSDs VPSDime utilizes write-intensive enterprise NVMe SSDs for its storage platform. #### 72 Hour Money Back Guarantee If you are not satisfied for any reason, we will refund your payment instantly. #### Frequently Asked Questions Answers to the most frequently asked questions about Premium VPS are below. Have another question? Simply contact us at [sales@vpsdime.com](mailto:sales@vpsdime.com) #### What is Premium VPS in a nut-shell? Premium VPS are partitions of a host node, where all resources are fully dedicated to your server. It is as close to a dedicated server as possible. You would interface with your Premium VPS in the same way as a physical server. #### What virtualization technology do you use? Our Premium VPS line uses KVM virtualization. Integrated directly into the Linux kernel, KVM provides full virtualization with exceptional performance, and is as close to a physical server as possible. #### How long does the VPS provisioning take? If it's your first order with us, then there is going to be a 10-15 minute delay while we manually screen your order. Once your server is provisioned, OS installation takes 10-15 minutes after that. #### What are the advantages of using KVM virtualization? KVM is included and maintained in the Linux mainline kernel, meaning it has extensive support and performance optimizations that ensure it runs well and will be supported for a very long time. It is "full stack" in that it virtualizes all devices for your VPS. #### Can I upgrade or downgrade my Premium VPS easily? Premium VPS can be upgraded at any time with a few minutes of downtime involved. We can schedule this downtime for any time of day that meets your business needs. Premium VPS cannot be downgraded. #### Are the resources dedicated to my VPS? Yes, CPU, memory, and disk are fully assigned and dedicated to your Premium VPS. The only resource shared is the host node uplink, but our host nodes are monitored to ensure that you get significant uplink speeds at all times. #### How is Premium VPS so cheap? We've built a highly-automated, high performance infrastructure that allows us to provide great services at a great price without any stoppages due to system issues. Because of the performance of our system, we can spend our time assisting our customers, meaning that we do not need to hire additional people to manually work system issues. #### Which Linux distros can I use with my VPS? You could use Ubuntu, Debian, CentOS, Fedora, SUSE, SLES with your Premium VPS. #### Can I reinstall my VPS's operating system? Of course, you could reinstall your Linux distro on your client area with a few simple clicks. It will only take a few minutes before your VPS is ready for you again. #### What kind of technical support do you provide? Our service is self-managed. This means that our customers are responsible for managing their own VPS's. However, it doesn't mean that you are left alone. Our technicians are always available to reply your questions within minutes and help you in a best effort basis. We are not going to manage everything for you but we are going to help you resolve your issues and will always point you to the right direction. #### Do you backup my VPS? Yes, a snapshot is taken of your VPS every night and stored for three days. Please note that our backup process can only restore the entire server image, and in any case you'll still want to build and set up a backup scheme that meets your budget and requirements, that you control. #### Is my VPS DDoS protected? Our network is able to handle small to medium attacks and for larger attacks, we have automated null-routing system. We recommend using Cloudflare for your website for DDoS protection. #### What are the differences between Premium VPS and Linux VPS? Linux VPS's are great for almost any use case, however if you are looking to use your own kernel or ability to utilize all of the CPU resources at all times without any interruption, then Premium VPS is recommended. Premium VPS are great for production workloads, and furthermore, Premium VPS allow you to run your own kernel if desired. #### Can I run Docker on Premium VPS? Yes, as Premium VPS is full virtualization, it can run Docker without issue. Additionally, you can run container orchestrations like Kubernetes, if desired. Operating systems for the purposes of Docker like RancherOS are available on Premium VPS. #### Do you support NFS, FUSE, TUN/TAP, GRE? Yes, Premium VPS is full virtualization, and can run anything that a physical server can run. There is no need to reach out to our team to enable these functions: you get full root access to your server and can set them up as desired. #### Do you offer IPv6? IPv6 is offered in multiple locations for our Premium VPS line. Please contact us to inquire more about this. #### A good word from our customers And the support of vpsdime is one of the best i have ever seen. Every ticket i create, i receive a response within minutes. Sometimes it even seems they are waiting for my ticket to respond immediately. [Read more](https://community.centminmod.com/threads/4gb-vpsdime-premium-kvm-vps-benchmarks-review.10646/#post-45580) @ CentminMod If you are looking for a robust hosting, with a good price, with incredible support, VPSDime is your best option, without a doubt! [Read more](https://webhostinggeeks.com/providers/vpsdime/review-id35417) @ WebHostingGeeks #### Silence the Noise: Why Your Next Move is to a Premium Neighborhood Picture the scene. You're in an apartment building where the walls are paper-thin. Your neighbor's music rattles your windows at 2 a.m. The hallway is a constant stream of noisy foot traffic. You hear sirens outside, a domestic dispute next door, and you can never be sure if you'll get a hot shower because someone else in the building is draining the tank. You don't control the chaos; you can only endure it. This is the reality of a standard, shared VPS environment. It's a crowded digital tenement where you are constantly at the mercy of your neighbors. In this environment, resources are part of a shared pool. If a neighbor's website suddenly goes viral, their VPS can steal your CPU time, leaving your application sluggish and unresponsive. If another user runs a massive backup or a data-intensive script, they can monopolize the disk I/O, making your database queries time out. You are affected by every surge and every crisis, and you have no idea when they will strike. Your performance isn't a guarantee; it's a gamble. It's time to move to a better neighborhood. A premium one. ##### The Architecture of Serenity: Total, Engineered Isolation A VPSDime Premium VPS is not just a more powerful server; it is a fundamentally different architectural philosophy. We have engineered our premium hosts to eliminate the "noisy neighbor" problem entirely by providing true, guaranteed resource isolation. This isn't a promise; it's a physical reality of how your VPS is built. We accomplish this by viewing our powerful host servers as a whole, which we then divide into perfectly equal, high-performance slices. Each slice contains a dedicated portion of the server's CPU cores, ECC RAM, and Enterprise NVMe SSD storage. - Our $20/mo Premium plan is one of these perfect slices. - The $40/mo plan is a seamless combination of two slices, doubling your dedicated resources. - This clean, predictable model continues all the way up to our most powerful offerings, ensuring that no matter your plan, your resources are reserved for you and you alone. ##### Your Private Resources, Guaranteed How do we enforce this digital silence? Through meticulous, uncompromising engineering: - **CPU Pinning:** Your VPS's virtual CPUs are "pinned" directly to specific physical CPU cores on the host machine. No other VPS on the server can use them. Ever. Your neighbor cannot steal your CPU cycles because, from the system's perspective, they don't even know your cores exist. This guarantees that 100% of your processing power is available 100% of the time. - **Dedicated Virtual DIMMs:** We allocate your memory directly to your pinned CPUs in virtual memory modules. This ensures that your RAM is a private, dedicated pool, providing the consistent performance of a physical machine. - **Governed Disk I/O:** Your access to our Enterprise NVMe SSD storage is strictly governed with guaranteed minimum and maximum I/O limits. These limits are not a ceiling to hold you back; they are a floor to stand on. They are meticulously designed to ensure that every single client on a premium host receives the exact same, consistently high-speed disk performance, regardless of what anyone else is doing. ##### The All-Inclusive, Peace-of-Mind Experience Moving to a premium neighborhood is also about the amenities and the quality of life. We intentionally keep the number of clients on each physical host server extremely low. This isn't just a feature; it's a core tenet of our premium promise. - **Abundant Headroom:** We always leave a significant buffer of unused resources on every host. This extra capacity is there just in case, ensuring that even under unexpected circumstances, the environment remains stable and performant. - **Host-Reserved Resources:** A portion of the server's power is dedicated solely to running the host operating system itself. This prevents any background host tasks from ever competing with your VPS for resources. - **Nightly Backups Included:** Peace of mind is paramount. We include nightly backups with every Premium VPS at no extra cost, ensuring your data is always protected by a robust safety net. ##### Is Premium Right for You? Let's be clear: there is nothing inherently wrong with standard, budget-friendly shared VPS hosting. It serves a vital purpose for development, hobbies, and applications where consistent, predictable performance is not a critical requirement. It's a great and affordable way to get started. But if your application is your business… if your website's speed is tied to your revenue… if your database cannot tolerate unpredictable slowdowns… then you can no longer afford to live in the noisy tenement. You need to know, with absolute certainty, that the resources you pay for are yours and yours alone. You need the silence, the stability, and the guaranteed power of your own private space. You need to move into the premium neighborhood. --- ## Affordable Windows VPS URL: https://vpsdime.com/windows-vps Summary: Highly performant, budget-friendly Windows virtual servers provided by VPSDime Easy to manage, highly performant powered by Hyper-V #### Deploy Your Windows VPS in Minutes Carefully built high performance hardware integrated with our in-house automation provides you the best possible Windows VPS experience in the industry. Always available, always performant, always affordable. | CPU | Core | RAM | Storage | Transfer | Uplink | Price | | | --- | --- | --- | --- | --- | --- | --- | --- | | Intel® Xeon® Gold | 2 CPU | 6GB ECC | 50GB SSD | 4TB | 10Gbps | $15.00/mo | [Order Now](https://vpsdime.com/buy/win6gb) | | Intel® Xeon® Gold | 4 CPU | 8GB ECC | 100GB SSD | 8TB | 10Gbps | $20.00/mo | [Order Now](https://vpsdime.com/buy/win8gb) | | Intel® Xeon® Gold | 5 CPU | 12GB ECC | 150GB SSD | 12TB | 10Gbps | $30.00/mo | [Order Now](https://vpsdime.com/buy/win12gb) | | Intel® Xeon® Gold | 6 CPU | 16GB ECC | 200GB SSD | 16TB | 10Gbps | $40.00/mo | [Order Now](https://vpsdime.com/buy/win16gb) | | Intel® Xeon® Gold | 8 CPU | 32GB ECC | 400GB SSD | 32TB | 10Gbps | $80.00/mo | [Order Now](https://vpsdime.com/buy/win32gb) | | Intel® Xeon® Gold | 12 CPU | 64GB ECC | 800GB SSD | 64TB | 10Gbps | $160.00/mo | [Order Now](https://vpsdime.com/buy/win64gb) | | Intel® Xeon® Gold | 16 CPU | 128GB ECC | 1600GB SSD | 128TB | 10Gbps | $320.00/mo | [Order Now](https://vpsdime.com/buy/win128gb) | ### Key Features of Windows VPS Full remote desktop access on Windows Server Easy to use and manage Managing your Windows VPS is extremely easy. It's just like you use your regular Windows computer with a mouse and keyboard. Every task can be automated using very powerful Windows Powershell when needed. Your Remote Office Windows VPS's can be used as a remote office computer. You could connect to it using Microsoft remote desktop and it will be always ready and waiting for you. We also provide HTML5 based remote console so you could even use it on your browser from anywhere. Powered by Hyper-V We leverage Microsoft's award winning Hyper-V technology to keep everything integrated in the Windows kernel. This ensures a rock stable service and reduces overhead for an enhanced user experience around the clock. #### High Specifications Generous specifications at very affordable rates provide you with all the raw power you need for your applications and use cases. Plans starting from 6GB RAM going all the way up to 128GB RAM. #### Enterprise NVMe SSD Storage With our enterprise-grade NVMe solid state drives, we ensure consistent performance for input/output intensive applications and websites. This allows you to serve files and query databases at blazing speeds so that no more bottlenecks will be in the way of your business growth. #### Extremely Affordable The affordability of the Windows VPS plans is unmatched, with one starting at only $15 USD per month. And it comes bundled with the license. You can get started for only $15 USD per month with a pre-installed and licensed version of Windows. #### Developer Friendly Easy to automate tasks using Microsoft Powershell. Ability to reinstall your operating system in just 2-3 minutes. Plus, the HTML5 console allows for a full remote desktop experience right in any browser. #### Our Locations VPSDime provides 6 geographically diverse locations allowing you to host your application across 2 different continents. [Seattle, WA](https://vpsdime.com/seattle-vps) [Los Angeles, CA](https://vpsdime.com/los-angeles-vps) [Dallas, TX](https://vpsdime.com/dallas-vps) [Piscataway, NJ](https://vpsdime.com/new-jersey-vps) [London, UK](https://vpsdime.com/london-vps) [Amsterdam, NL](https://vpsdime.com/amsterdam-vps) #### Easy to Manage Our custom control panel makes managing your VPS a breeze. #### Common Features of VPSDime Services #### 99.99% Power & Network SLA If we fail to deliver, you will be compensated with credit for the time that service was unavailable. #### Sub 15 minute Support Response With our quick response time, we know that you will always be satisfied with the results of the customer support team. #### Enterprise-grade NVMe SSDs We only use NVMe solid state drives with write-intensive enterprise grade storage for the best performance and latency. #### 72 Hour Money Back Guarantee If you are not satisfied for any reason, contact us and we will refund your payment. #### Frequently Asked Questions Below are the answers to the most frequently asked questions regarding Windows VPS Have another question? Simply contact us at [sales@vpsdime.com](mailto:sales@vpsdime.com) #### What is Windows VPS? Windows VPS offers you all the benefits of a dedicated server with Windows operating system without having to pay thousands of dollars for one. It's completely private to you and gives you full Administrator access. You could manage it by using Microsoft Remote Desktop on any computer or smart phone anywhere in the world. #### Can I connect to my Windows VPS using Remote Desktop? Sure, once your VPS is provisioned, our system emails you with the dedicated IP address assigned to your VPS and then you could connect to your VPS using Microsoft Remote Desktop or alternative applications at Administrator level. #### What virtualization technology do you use? VPSDime uses Microsoft's own Hyper-V virtualization technology platform. #### How long does the VPS provisioning take? We want to ensure that your first order with us is as smooth as possible, which means we will manually screen every order placed. This may take up to 15 minutes and you can expect a short delay before receiving access information. #### What are the advantages of using Hyper-V? Hyper-V is deeply integrated with Windows Server. This provides excellent stability and reduces the virtualization overhead. As a microkernelized hypervisor, Hyper-V uses the individual virtual machines to run device drivers. This means that each VPS has its own unique set of devices (and corresponding driver) which allows for better performance because there isn't any unnecessary reliance on other components in order to function properly. #### Can I upgrade or downgrade my Windows VPS? Scaling up and down Windows VPS is very easy and fast. You could place an order for an upgrade or downgrade on your client area. There will be a very small amount of downtime for the upgrades and downgrades. #### Are the resources dedicated to my VPS? Memory and disk space are completely dedicated to your VPS. Our VPS provides an absolute bang for your buck because we pass along the savings from using a shared CPU to our customers. Our in-house fully automated monitoring systems ensure that no disturbances will ever occur, so you'll have all of the power when required - guaranteed! #### Which Windows versions are available? Windows VPS's are available with Windows Server 2025, 2022, or 2019 Datacenter edition. You can select the version you want at order time, and switch between them at any time by reinstalling. #### Can I reinstall my VPS's operating system? Of course, you could do it any time on your client area. The process takes only a few minutes. #### What kind of technical support do you provide? Our service is self-managed. However being self-managed doesn't necessarily mean that you are left alone. We offer support to help our customers with their issues, and we will always point them in the right direction if they need something more than just answering questions or troubleshooting small problems. #### Do you backup my VPS? Windows VPS's do not come with backup support by default. You can purchase a Nightly Backup addon for $5/month, which is only necessary if you want your VPS to be backed up nightly with 3 days retention. #### Is my VPS DDoS protected? We handle small to medium attacks, but larger ones require automated null-routing to avoid disturbance for our other customers. We recommend Cloudflare for DDoS protection on your website. #### How secure is Windows VPS? We take industry standard precautions with our host nodes, and you get full Administrator access to your VPS to implement additional security in your VPS as desired. #### A good word from our customers VPSDime provides really great services. ... VPSDime offers VPS servers for a cheap price. But the VPS servers work fast and are reliable. [Read more](https://webhostreviews.com/reviews/vpsdime) @ WebHostReviews Had to get support from VPSDime today. I was skeptical if they will still reply fast as the first time. They didn't disappoint me. [Read more](https://twitter.com/_aminulhaque/status/1285586483835879425) @ Twitter #### The Ultimate Upgrade: Why Your Next PC is a Windows VPS For decades, our digital lives have been tethered to the physical box under the desk, a single point of failure that can be slow, vulnerable, and restrictive. The time has come for a paradigm shift. A Windows Virtual Private Server (VPS) is not merely a remote server; it is the logical evolution of the personal computer. It's a powerful, secure, and supremely flexible desktop that lives in the cloud, accessible from anywhere, on any device. Shifting your daily workflow to a VPSDime Windows VPS is a revolutionary upgrade. Here's how it transforms your personal and professional computing. ##### The Familiar Desktop, Reimagined The greatest barrier to adopting new technology is often the learning curve. With a Windows VPS, there is none. When you connect via Remote Desktop, you are greeted with the same familiar Windows interface you have used for years. Every skill, from navigating File Explorer to installing software, is instantly applicable. There is no command line to master or complex protocol to memorize. It is simply the Windows you know, liberated from the confines of physical hardware. This freedom allows you to start a complex data analysis at your office desk, check on its progress from a tablet on your couch, and make final tweaks from a laptop at a café. Your desktop, with all its open applications and files exactly as you left them, is always just a click away. ##### The Datacenter Advantage: Unyielding Power and Persistence The true power of a VPS comes from its home: a professional datacenter. This environment provides a level of performance and reliability that consumer-grade hardware and home internet connections simply cannot match. Your home Wi-Fi is prone to dropouts and slowdowns, but your VPS is connected directly to the internet's backbone with a redundant, enterprise-grade network. This means you benefit from symmetrical gigabit speeds, making tasks like uploading multi-gigabyte video files or compiling large codebases practically instantaneous. This unwavering stability is crucial for any long-running task. A trading bot, a data scraping script, or a video render will execute flawlessly without interruption, 24/7. Even if your local connection drops, the VPS continues its work perfectly. Furthermore, a VPS is designed for constant operation in a highly efficient environment. You can close your remote connection and turn off your local computer, confident that your tasks are still running, all while saving a surprising amount on your monthly electricity bill. ##### The Indestructible Sandbox: Freedom to Innovate Are you hesitant to test new software or a risky configuration on your primary computer? A single virus or a critical system error can lead to days of frustrating repairs. A Windows VPS eliminates this fear entirely. Treat your VPS as a powerful, disposable sandbox where you can install anything, configure everything, and push the limits without consequence. If an experiment goes wrong, you are not facing a crisis. Through the VPSDime control panel, you can reinstall a fresh, clean version of Windows in minutes. This ability to instantly reset your environment encourages innovation and learning. For the ultimate peace of mind, our automated nightly backups act as a safety net. If anything goes awry, you can restore your server to its exact state from the previous night with a single click. The ultimate undo button for your entire operating system. ##### A Platform for Ambition and Automation With an always-on, high-performance Windows environment, you can execute tasks that are simply impractical on a local machine. For developers, it's a perfectly consistent coding hub. Code, compile, and test from any device, knowing that your tools and dependencies are identical every time. For automation experts, it's a powerhouse for deploying browser scripts with tools like Selenium or Power Automate to perform 24/7 data scraping, social media management, or quality assurance tests. This persistent environment is the ideal home for any Windows-based bot (for trading in Forex or crypto markets, managing online games, or automating social interactions), with the confidence that it will never be interrupted by a local shutdown or a spotty internet connection. For content creators, it's a rendering workhorse. Offload a heavy 4K video render to the VPS, freeing up your local PC for other tasks. Once complete, upload the massive finished file directly from the datacenter in a fraction of the time it would take from home. ##### The Collaboration Hub: Your Team's Unified Cloud Office Remote work often creates digital chaos, with teams scattered across different machines, software versions, and environments. A Windows VPS solves this by becoming a central, cloud-based office. The key is its ability to function as a true multi-user environment. Unlike a standard desktop that allows only one active user, a Windows Server VPS lets you create separate accounts for each team member. They can all be logged in and working simultaneously, each in their own private desktop session. This creates the "golden environment" for development teams, ending the "it works on my machine" nightmare forever. By setting up a single VPS with the project's exact database, web server, and dependencies, every developer works in an identical, perfectly configured space. For small businesses, it's a cost-effective solution. Instead of buying five separate office PCs and five expensive software licenses, you can install one copy of your accounting or design suite on the central VPS for everyone to access, drastically reducing hardware costs and simplifying license management. ##### The Smart Investment: Escape the Hardware Upgrade Cycle A powerful local PC with a high-end CPU, 64GB of RAM, and a large and fast SSD can cost thousands of dollars, and that hardware becomes outdated in just a few years. A Windows VPS fundamentally breaks this expensive upgrade cycle. You are not buying hardware; you are renting access to a state-of-the-art computing cluster for a low monthly fee. Your VPS runs on powerful server-grade Intel Xeon and Error-Correcting Code (ECC) RAM. These components are far more robust and reliable than their consumer counterparts. You experience the blistering speed of enterprise NVMe SSD storage without the premium cost. And as your needs grow, you can add more RAM, CPU cores, or storage with a few clicks. You pay only for the power you need, precisely when you need it, ensuring you always have access to elite performance without the capital expense. --- ## Storage Virtual Private Servers URL: https://vpsdime.com/storage-vps Summary: High storage VPS plans for mass storage applications and backups by VPSDime High storage solutions for your needs #### Deploy Your Storage VPS in Minutes Storage VPS services are everything you need if you have a lot of data and need to keep it online. Massive storage capacity available at your finger tips at a very cheap price. | CPU | Core | RAM | Storage | Transfer | Uplink | Price | | | --- | --- | --- | --- | --- | --- | --- | --- | | Intel® Xeon® Gold | 1 CPU | 1GB ECC | 100GB | 1TB | 10Gbps | $40.00/yr | [Order Now](https://vpsdime.com/buy/vds100gb) | | Intel® Xeon® Gold | 2 CPU | 2GB ECC | 250GB | 2TB | 10Gbps | $60.00/yr | [Order Now](https://vpsdime.com/buy/vds250gb) | | Intel® Xeon® Gold | 4 CPU | 2GB ECC | 500GB | 4TB | 10Gbps | $7.00/mo | [Order Now](https://vpsdime.com/buy/vds500gb) | | Intel® Xeon® Gold | 4 CPU | 2GB ECC | 750GB | 6TB | 10Gbps | $11.00/mo | [Order Now](https://vpsdime.com/buy/vds750gb) | | Intel® Xeon® Gold | 4 CPU | 2GB ECC | 1000GB | 8TB | 10Gbps | $14.00/mo | [Order Now](https://vpsdime.com/buy/vds1000gb) | | Intel® Xeon® Gold | 4 CPU | 2GB ECC | 2000GB | 12TB | 10Gbps | $28.00/mo | [Order Now](https://vpsdime.com/buy/vds2000gb) | | Intel® Xeon® Gold | 4 CPU | 2GB ECC | 3000GB | 18TB | 10Gbps | $42.00/mo | [Order Now](https://vpsdime.com/buy/vds3000gb) | | Intel® Xeon® Gold | 4 CPU | 2GB ECC | 4000GB | 32TB | 10Gbps | $56.00/mo | [Order Now](https://vpsdime.com/buy/vds4000gb) | ### Key Features of Storage VPS Excellent platform with ample storage. High Storage Get the disk space you need to store your data. Enjoy fast-performing and well-managed host nodes on our network of servers! Dependable Enterprise Quality Built with HGST Enterprise-grade HDDs in RAID10 configuration to offer the best performance and reliability. Very Affordable Our team is available 24/7 on any day of the year, including holidays on any calendar, to assist you with guidance whenever you need it. #### Dedicated Storage Buy an amount of space, and that's the amount of space you'll actually get. Our storage nodes are closely monitored to ensure you'll always be able to upload your data at any time. #### Redundant Disk Arrays For uptime and performance, all Storage VPS are placed onto redundant disk arrays. In the event of a single-disk failure, our tech team can swap the failed disk, with no downtime or data loss. #### No Overselling Our non-oversold servers means highr availablity and less downtime for you. Memory and disk allocations are fully dedicated to your VPS, with only the CPU and network uplink shared with your neighbors. #### Eliminate noisy neighbours We hand pick your VPS neighbours. Our systems are constantly monitored to ensure that you can expect great performance 24/7. #### Deploy your VPS with any of these available distributions Save time by building on the OS that suits your needs. - Ubuntu - CentOS - Debian - Fedora - OpenSUSE - Redhat Linux #### Our Locations VPSDime provides 6 geographically diverse locations allowing you to host your application across 2 different continents. [Seattle, WA](https://vpsdime.com/seattle-vps) [Los Angeles, CA](https://vpsdime.com/los-angeles-vps) [Dallas, TX](https://vpsdime.com/dallas-vps) [Piscataway, NJ](https://vpsdime.com/new-jersey-vps) [Maidenhead, UK](https://vpsdime.com/london-vps) [Amsterdam, NL](https://vpsdime.com/amsterdam-vps) #### Easy to Manage Our easy-to-use custom control panel helps you manage your VPS easily #### Common Features of VPSDime Services #### 99.99% Power & Network SLA If we fail to deliver, you will receive a credit for the amount of time that service was unavailable. #### Sub 15 minute Support Response Our team works hard to provide our customers with the best customer service. #### Enterprise-grade SSDs VPSDime only uses highly write-intensive enterprise-grade SSDs for stable performance and latency. #### 72 Hour Money Back Guarantee If you're not totally stoked about your purchase, we'll give you all of your money back. No questions asked. #### Frequently Asked Questions What are the answers to some frequently asked questions about Storage VPS? Have another question? Simply contact us at [sales@vpsdime.com](mailto:sales@vpsdime.com) #### What is Storage VPS in a nut-shell? Storage VPS provide a large amount of disk space with equivalent resources to ensure proper operation of the operating system. They are fantastic for cold-storage/backup purposes. #### What virtualization technology do you use? Our Storage VPS line is backed by Virtuozzo 7, a backend virtualization technology that provides real bare metal like performance with no overhead. #### How long does the VPS provisioning take? If you are our new customer, then there will be a 10-15 minute delay while we manually screen your order. #### What are the advantages of using Virtuozzo / OpenVZ 7 virtualization? The Virtuozzo virtualization solution allows you to upgrade or downgrade your VPS on the fly without any downtime. You also get more power from your hardware because there is no overhead due to kernel-level virtualization. #### Can I upgrade or downgrade my Storage VPS easily? With Storage VPS, scaling up and down is very simple. This change happens without interruption so you could enjoy downtime free upgrades or downgrade any time! #### Are the resources dedicated to my VPS? When you purchase a VPS from our company, we ensure that your system is always operating at full capacity. This means all of the memory and disk space on the node are dedicated to hosting your server alone - no sharing with other users. However, because CPU power must be shared across many servers in one physical machine due to how virtualization works (so as not waste any resources), it provides an even better value for money than if this was guaranteed fully regardless of occupancy/usage! #### Which Linux distros can I use with my VPS? You could use Ubuntu, Debian, CentOS, Fedora, SUSE, SLES with your Storage VPS. #### Can I reinstall my VPS's operating system? If you want to reinstall your Linux distro on the client area, it will only take a few seconds before your VPS is ready for use again. #### What kind of technical support do you provide? Our service is self-managed. This means that we will not manage your VPS for you, but we provide support and handle issues in an "as best as possible" manner. We can offer technical assistance to resolve problems with your server in a courtesy basis. #### Do you backup my VPS? Storage VPS's are not backed up. If you need your Storage VPS backed up, you could order another one in another one of our locations and set up mirroring. #### Is my VPS DDoS protected? We are able to handle small-medium attacks, but for larger ones we have an automated null routing system. We recommend using Cloudflare because it's great at preventing DDoS attacks on websites! #### What are the differences between Storage VPS and Linux VPS? Storage VPS's are built for high storage capacity for your applications. They are not for to serve websites with high traffic. They are best to serve the files. #### Can I run Docker on Storage VPS? Docker is not supported on Storage VPS's. If you need to use Docker, please check our Linux VPS line. #### Do you support NFS, FUSE, TUN/TAP, GRE? Yes, Storage VPS storage supports these functions. Please contact us to have what you need enabled on your VPS. #### Do you offer IPv6? IPv6 is offered in multiple locations for our Storage VPS line. Please contact us to inquire more about this. #### A good word from our customers And the support of vpsdime is one of the best i have ever seen. Every ticket i create, i receive a response within minutes. Sometimes it even seems they are waiting for my ticket to respond immediately. [Read more](https://community.centminmod.com/threads/4gb-vpsdime-premium-kvm-vps-benchmarks-review.10646/#post-45580) @ CentminMod Using their hosting services since a few days and I am completely amazed about their quality and services. VPS's are very reliable, enormous fast and easy to deploy [Read more](https://www.trustpilot.com/reviews/5e4705b53c93ae0bc4023aca) @ TrustPilot #### The Digital Strongbox: More Than Storage, It's Sovereignty What is a Storage VPS? The name hints at its purpose, but the concept is revolutionary. Imagine a blank canvas, a fresh installation of your favorite Linux distribution. It's a powerful server environment, but it's backed by one crucial difference: a vast, secure, and redundant disk array designed for one primary mission, to hold your digital life. This isn't just a bigger hard drive; it's an industrial-grade storage solution hosted in a professional datacenter. A datacenter is a fortress for data, with redundant power, enterprise-grade cooling, and a staggering 100Gbps of connection capacity to the internet's backbone. It's an environment far superior to your home office, immune to power outages, local network failures, or the risk of a spilled coffee destroying your only copy of a critical file. A Storage VPS gives you a personal, secure foothold in this fortress. ##### Your Digital Insurance Policy: The Unbreachable Vault Backups are not a suggestion; they are a fundamental law of computing. Every hard drive will eventually fail. Every server is a potential target. Every file is one accidental delete command away from oblivion. Without a robust backup strategy, you aren't just taking a risk; you are actively choosing to lose your data. The only question is when. A common, fatal mistake is keeping backups on the same server as the original data. That's like keeping your spare car key in the ignition. A true backup must live on completely separate infrastructure. For ultimate peace of mind, it should even reside on a different continent. This protects you from regional disasters such as fires, floods, or prolonged network outages, that could wipe out an entire datacenter. Let this sink in: one backup is no backup. If you have a single backup copy, you simply have two single points of failure. A proper strategy involves multiple copies in multiple locations, and a Storage VPS is the perfect, affordable cornerstone of that strategy. It is the off-site, off-continent, secure vault your primary servers need. Setting this up is easier than you think. You can install powerful, open-source backup software directly on your Storage VPS to pull data from your other servers: - **Restic or BorgBackup:** These modern tools are incredibly efficient. They offer encryption, compression, and deduplication, meaning they only back up the changes to your files, saving a massive amount of disk space and time. - **Rsync:** The classic, battle-tested command-line utility for simple and lightning-fast synchronization between two Linux servers. Even better, if you use a popular control panel, the process is practically automatic. Panels like cPanel/WHM, Plesk, and DirectAdmin have built-in backup configuration tools. You simply tell your panel the IP address and login details for your Storage VPS, set a schedule (e.g., "daily"), and it handles the rest. Your panel will automatically compress your websites and databases and send them securely to your vault every night. ##### Declare Your Digital Independence: The Private Cloud We've all become accustomed to the convenience of cloud storage. But this convenience comes at a steep price: control. When you upload your files to a third-party cloud, you are handing over your data to a corporation. You are subject to their terms of service, their privacy policies, and their security vulnerabilities. We've all seen the headlines, from celebrity photos being leaked from Apple's iCloud to other services suffering massive data breaches. A Storage VPS lets you reclaim your digital sovereignty. You can build your very own private, secure cloud where you make the rules. With powerful, mature, and user-friendly open-source software, this is easier than ever: - **Nextcloud:** A complete, feature-rich alternative to Google Drive or Microsoft 365. It provides file sync, photo galleries, calendars, contacts, and even online document editing, all hosted on your private server. - **ownCloud:** Another popular choice that offers a secure and robust platform for file sharing and synchronization across all your devices. Installing these applications on a Storage VPS is straightforward. Within a short time, you can have a fully operational, private cloud service for yourself, your family, or your business. You control the encryption, you control the user accounts, and you, and only you, have access to the underlying data. ##### The Infinite Drive: Break Free from Physical Limits Is the hard drive on your MacBook constantly full? Before you spend hundreds on a new laptop or a fragile external drive, there is a better way. A Storage VPS acts as a massive, always-online extension of your local storage. Using intuitive software for macOS like Cyberduck or Transmit, you can easily connect to your Storage VPS and drag-and-drop files as if it were a local folder. For more advanced users, you can set up continuous, automatic synchronization with powerful tools like rsync. It functions just like Apple's iCloud Drive, but with terabytes of space at your command and without the hefty subscription fees. Think of it as the ultimate external drive. A typical USB drive is vulnerable. It can be dropped, lost, stolen, or simply fail from wear and tear. Your Storage VPS, however, lives in a secure datacenter. More importantly, it is protected by RAID, a technology that makes it fundamentally more reliable. What is RAID? Imagine you have a critically important document. Instead of writing it on a single piece of paper, you have a magic pen that writes it on several pieces of paper simultaneously and automatically. If one piece is lost or destroyed, you can perfectly recreate the original from the others without missing a beat. RAID (Redundant Array of Independent Disks) does exactly this for your digital data. Our Storage VPS systems automatically write your data across multiple physical hard drives at once. If a single drive in the array fails (a common hardware event), your data remains completely safe and accessible with zero interruption. A standard USB drive has no such protection. One failure, and everything is gone. A Storage VPS is the smart, secure, and resilient solution for your expanding data needs. It's the backup vault you can't afford to be without, the private cloud you can trust, and the infinite hard drive your devices have been waiting for. --- ## Compare Services URL: https://vpsdime.com/compare-services Summary: Find out the differences between Linux VPS and Premium VPS while comparing them with Windows and Storage VPS Find out the differences between our offerings ### Services To Fit Your Needs VPSDime is committed to offering a wide range of versatile products at an highly affordable price point. Linux VPS Run your applications without compromising on quality or support. Offers gobs of resources at a highly affordable price point. Windows VPS Powered by Microsoft Hyper-V. Convenient and easy to manage by remote desktop. Perfect for development and production. Premium VPS Designed to run enterprise applications with incredible performance, reliability and speed. All resources are fully dedicated. Storage VPS High-storage servers intended for backup use that you can rely on. Allows architecting your very own backup strategy using any software desired. | | Linux VPS | Premium VPS | Windows VPS | Storage VPS | | --- | --- | --- | --- | --- | | Virtualization Technology | LXC | KVM | Hyper-V | Virtuozzo | | Full Root Access | | | | | | Host Websites & Applications | | | | | | Kernel Manipulation | | | | | | Docker Support | | | | | | Dedicated RAM & Storage | | | | | | Dedicated CPU | | | | | | Load Average Limitation | | | | | | Solid State Drive Storage | Enterprise (Mixed Use) | Enterprise (Write Int.) | Enterprise (Mixed Use) | HDD | | Free Nightly Backups | Paid | | Paid | N/A | | Linux Support | | | Windows Only | | | BSD Support | | | Windows Only | | | Windows Support | | | | | | Port Speed | 1 or 10Gbps | 1 or 10Gbps | 1 or 10Gbps | 1 or 10Gbps | | RAID Protected | | | | | | Enterprise Grade Hardware | | | | | | Self Managed Service | | | | | | DDOS Protection | | | | | | No Overselling | | | | | | 24/7 Technical Support | | | | | | Starting from: | $7.00/mo | $20.00/mo | $15.00/mo | $40.00/yr | | | [View Plans](https://vpsdime.com/linux-vps) | [View Plans](https://vpsdime.com/premium-vps) | [View Plans](https://vpsdime.com/windows-vps) | [View Plans](https://vpsdime.com/storage-vps) | --- # Company and infrastructure ## Why Choose Us? URL: https://vpsdime.com/why-choose-us Summary: Why choose VPSDime as your provider? Our Motivation Lies In Achieving Success One Client At A Time. ### Owned and Operated by System Admins Our team is entirely made up of seasoned industry veterans who genuinely enjoy what they do. We have made our hobby our business. ### Designed to be Affordable We prove that cheap VPS services can be fast and reliable at the same time. VPSDime was founded to fill the gap in the market. Why pay more when you don't have to? ### We Actually Care You are not just a number in our books. We are big enough to provide top notch service and small enough to appreciate your patronage. ### Extreme and consistent performance High frequency CPUs, ample RAM and storage built with write intensive enterprise NVMe SSDs coupled with 10Gbps uplinks is the recipe of our chart-topping performance. ### Non-tiered, Direct Support We don't believe in tier based support where the customer needs to jump through hoops to get meaningful replies. Our support team is to-the-point and any member of our team can assist you. ### Mission-Critical Infrastructure Operating in fully staffed, SSAE 16 compliant data centers with diverse fibre paths and redundant power feeds to guarantee 99.99% uptime. ### You know what you pay Completely transparent, old-school monthly billing with no contract lock-ins. You get a service that lasts for years without the worry of keeping your balance in check. ### Scale up and down with no downtime Our Linux VPS product line enables you to transparently upgrade or downgrade at any time. You can scale up or down easily with just a few clicks. ### Proven Reliability 13 years of dedication. 13 years of passion. 13 years of growth. 13 years of excellent track record. VPSDime services both enterprises and enthusiasts. ### No overselling. No overloading. We do not overload. In fact, we load our hardware nodes under their capacity to make sure all of our customers have spare capacity when needed. ### High Performance Network. Healty Environment. Carefully engineered, constantly monitored, highly available network with reputable IP space and abuse-free environment. ### Simplified Management Manage your VPS easily with our custom developed, instinctual control panel. --- ## VPSDime Hardware URL: https://vpsdime.com/hardware Summary: Find out about the hardware that powers VPSDime servers Enterprise grade hardware built by skilled hands VPSDime has been providing clients with enterprise level hardware since our launch in 2013. We custom build all our hardware nodes which allows us to equip them with the newest and most efficient equipment for the ultimate customer experience. Premium Juniper network routers and switches ensure you stay online at all times. All devices are in high-availability pairs, connected to redundant power with redundant uplinks. Junos operating system present on every Juniper device provides premium functionality, like uninterrupted routing and forwarding, with features such as nonstop active routing (NSR) and nonstop bridging (NSB), in addition to commit and rollback functionality that ensures error-free network configurations. Our infrastructure is powered by Dell enterprise-grade servers with dual Intel Xeon Gold or Platinum CPUs and at least 384GB ECC memory per host node. Write intensive Samsung and Intel enterprise NVMe SSDs, rated at 3 DWPD or higher, are deployed in RAID10. Every server is connected with A+B power into redundant power supplies, fed by diverse feeds. VPSDime offers enterprise NVMe SSD storage on all of our servers to provide consistent and high performance services. We employ the lowest latency enterprise NVMe drives, rated at 3 DWPD or higher, which we overprovision at 28% at the least. Whats more, all of them have power-loss capacitors to avoid data corruption in the unlikely event a kernel panic or power failure occurs. The storage infrastructure we use provides consistent low latency and high IOPS. Our RAID10 setup allows for better performance, stability and redundancy, and no more bottlenecks with high read/write speeds. --- ## Security URL: https://vpsdime.com/security Summary: Server security is not a product in itself, but a never ending process - Close Watch - Well Configured - Up-to Date Systems - Tight Controls ### Security. Handled professionally At VPSDime in every decision we make, in every action we take, security is always at the heart and forefront of our minds. We employ the best and recommended industry practices and ensure that we are always up-to date. Security is not a product in itself, but a never ending process and that is why we work 24/7 around the clock to ensure availability, integrity and confidentiality of our services. - #### Physical Security All our data centers employ the best security practices including card-key access to our facilities. - #### Account Security Our security analysts work around the clock to monitor suspicious account activity. - #### Network Security We employ a wide range of methods to protect the underlying network infrastructure from unauthorized access. - #### Server Security Our server infrastructure is built with enhanced security considerations in mind to protect you and your customers. - #### Application Security Controlling what applications can and can't do and looking out for instant threats and attacks. --- ## VPSDime Looking Glass URL: https://vpsdime.com/looking-glass Summary: VPSDime Looking Glass for network tests Run ping and mtr test against our network - Dallas, TX - Seattle, WA - Los Angeles, CA - Piscataway, NJ - London, UK - Amsterdam, NL ### Network Information Server Location: Dallas, TX Test IP: 63.142.241.46 Test Files: [100MB](https://lg.dallas.vpsdime.com/100MB.test) [1GB](https://lg.dallas.vpsdime.com/1GB.test) [10GB](https://lg.dallas.vpsdime.com/10GB.test) Your IP Address: ### Network Tests ### About Our Network 6 Transit Providers + 7 Peer Exchanges + 850 Gbps Transit Capacity + 500 Direct Network Peers Optimized Routing with high quality Tier 1 networks Our network is a blend of Level 3, Century Link, XO Communications, Comcast Business Class NTT America (formerly Cogent), GTT and Hurricane Electric. We also peer with Telia Carrier and Any2 Exchange in New York City; TIE Networks in Los Angeles; DE-CIX Frankfurt Germany's Delegations Internet Exchange (FLiX) peering points across the globe. When you have so many connections to multiple destinations around the world your network will always perform optimally no matter where it goes or what happens along the way because our self-healing infrastructure ensures that there are alternative paths for data transfer should any one connection fail unexpectedly. Tremendous Transit Capacity Thanks to our over 850 Gbps network capacity, we can accommodate even the most demanding bandwidth requirements. Better Than BGP Our Noction Intelligent Routing Platform (IRP) analyzes the internet's performance to find out whether normal BGP route selection is truly the fastest path for data or latency-sensitive applications. It improves over 130,000 network prefixes every day by providing better latency and jitter elimination while improving overall speed. Network Peering with Over 500 Direct Peers Moving data effectively across the Internet requires choosing the best possible route for transmission. Our 300+ direct peer relationships give us the choices we need to find the optimal path for your data. DDoS Protection Our network is DDoS protected and is able to handle small to medium attacks easily. Corero's state of the art security stops over 90% of malicious traffic at the edge, ensuring that every packet is valid. High Capacity Ports Available If you have extraordinary capacity needs, our network can provide 1, 10, 20 and 40Gbps ports for your transmission requirements. Fast Private Network A fast, scalable backend infrastructure is crucial for a successful cluster. Our 10Gbps private network ensures your data can flow quickly and securely across multiple solutions within one location or between locations if necessary. ### Additional Networking Options Powerful networking features to enable enterprises maximum flexibility IPv6 Connectivity IPv6 is the future and most of our locations support IPv6 natively. Contact us to get IPv6 addresses allocated to your VPS. Private Networking To have your VPS's connect each other in a very low latency and private environment you could take advantage of our private networking solutions. Bring your IP Space For your bigger projects, we are able to announce your own IP space to take advantage of our networking with your own space. --- ## About Us URL: https://vpsdime.com/about-us Summary: Read VPSDime's history and its mission Our Motivation Is Achieving Success One Client At A Time. VPSDime is a leading provider of VPS hosting, offering affordable virtual machines for people on a budget. Our self-managed services are the perfect foundation for you or your business to succeed. You'll be impressed by the superior performance of our services and network, our unbeatable uptime, and the uncommonly-good quality of our technical support. ### VPSDime History - 2013 VPSDime brand has been founded - 2014 10000th VPS provisioned - 2015 Seattle and United Kingdom locations launched - 2016 "Self-managed but not abandoned" support policy adopted - 2017 Premium VPS and Storage VPS product lines introduced - 2018 Total of 100TB of RAM provisioned - 2019 Linux VPS product has been refreshed and upgraded to Virtuozzo 7 - 2021 Windows VPS product has been introduced. Powered by Hyper-V - 2026 New Linux VPS deployments moved to LXC for the next generation of container performance. #### Our Mission It is VPSDime's mission to enable new business startups to thrive by offering specialized high storage and high memory virtual private server solutions. We offer 4 distinct types of services that allows businesses to select the best fit for their needs, without compromising quality. You can count on us as your economical VPS hosting provider. Affordable Enterprise Level Hosting Solutions For All Businesses. ### Our Employee Values Accountability Our highly skilled staff are trained to take responsibility, and make the right decisions and actions. Love We love what we do! Our commitment and dedication to our customers is unparalleled and never goes unnoticed. Innovation Thinking outside the box, and taking up new challenges to give something back to the industry and community. Professionalism Professionalism is at the heart of every step. We strive to set a good example as one of the leaders in our market. Proficiency Our team consists of only highly skilled and experienced veterans, ready to provide you with guidance on whatever you need. Dedication Our team will never quit working till you are completely satisfied. Dedication brings success. #### Our History Running under the umbrella of Nodisto F.Z.E, along with our popular Winity and Backupsy brands, VPSDime's founders have many years of experience in the server hosting industry. We strive to provide the highest quality service while still offering the best value for your money. Every member of our team has a lifetime of experience in the hosting industry and you can count on us to go the extra mile. As a leading provider of VPS hosting, we are known for offering High RAM and High Storage services. We work around the clock to deliver your expectations without compromising quality, at an affordable price. Over the years, we have won the hearts of thousands of customers who have never looked back. We can proudly say without a doubt that we receive exceptional praise from our customers due to the hard working team here at VPSDime. We are privileged to have grown into a company that is fully committed to investing in the future of our customers, and we look forward to serving you for many years to come. --- ## Contact Us URL: https://vpsdime.com/contact-us Summary: Contact VPSDime quickly Get In Touch, We Are Always Ready To Lend A Hand ### Current Customers Support, Billing, and other questions regarding your account: [Sales / Billing](https://vpsdime.com/open-ticket/) [Support](https://vpsdime.com/submitticket) ### Mailing Address Nodisto FZE B.C. 1305967 Ajman Free Zone United Arab Emirates ### Pre-Sales Questions Get to know more about VPSDime and how we operate in our Pre-sales FAQ: [Click Here](https://vpsdime.com/presales-questions) ### Pre-Sales Inquiries sales [@] vpsdime.com Contact Form Just want to say Hi? Or have any burning questions in mind? Drop us a line: If you are already a customer, please contact us by submitting a [support ticket here](https://vpsdime.com/submitticket) --- ## Customer Reviews URL: https://vpsdime.com/customer-reviews Summary: Read what customers are saying about VPSDime Read what our customers say about our service May 18, 2021 I agree, this company is legit, the service is awesome, the VPSes aren't oversold and it's really, really inexpensive. See my other trustpilot review of HostSailor -- they're the opposite, just horrible service and people. A note to VPSdime: Oracle has free-for-life VPS micro containers, but I like your responsiveness and polite service -- these things matter to me, and is the reason I've kept my personal sites here. Cheers! May 16, 2021 I'm absolutely getting for what I'm paying. Customer support is really good and man they have the skills to troubleshoot. May 3, 2021 It's the second month I am using the service and ran into a little trouble in setting up an issue the customer support replied within like 15 mins after a back and forth fixed my issue, highly recommend this service, amazing value and amazing customer service! Feb 1, 2021 Very friendly and good support. I had a problem caused by me and it has been solved positively for me. That's really nice. About VPS: runs very smoothly and without downtimes. Sep 30, 2020 Tops. I would highly recommend. Had services with them for about 3 years. Best bang for buck esp for with high-memory instances Sep 26, 2020 These guys are outstanding for value, quality and service. Recently one of their techs took his time to setup HTTPS on my site just because I had been a long time customer. My site is used for educational purposes and didn't really need the HTTPS enabled but the padlock next to the url has stopped repeated questions from kids! Anyways, these guys are highly recommended. Sep 6, 2020 Excellent service! I moved to another vps! But it was the worst deal i ever made! i tried alot of vps and the only cheap and affordable was without a doubt vps dime! Going back to vpsdime and i am willing try out the premium vps! Aug 12, 2020 What can i say... i'v been with this company from few years ago. There been some small issues with the billings but, at the end, I was properly refounded. Now I have up and running only 5 services with them. The support is not the quickest one but they do a very good job. For the money... IS A GREAT VPS PROVIDER. Jun 17, 2020 I love vpsdime brilliant value for money. 100% top notch support and customer service. Used them for 2years now with no problems. Always updating and bringing new features to make life easyer always recommend vpsdime Jun 2, 2020 You get a decent 4 core vCPU, 6 GB of DDR3 memory, 30 GB of space, and 2 TB of traffic with 10 GB/s uplink; for just 7 USD a month. At first, when I first visited their website I was thinking that it's too good to be true but turned out to be even better. Their customer service is amazing, you can expect a swift reply. Not only that if you ever lose access to your server or just somewhere not on your computer and you need to access your server ASAP, but their web interface control panel also lets you access to your server and run commands! May 6, 2020 We've used VPSDime for around a year without any issues. Recently wanted to allow access for a new software integration and spent a couple hours dealing with networking issues. Emailed VPSDime's support to see if they had any idea (I thought it was a long shot but worth a try) and within 5 MINUTES they checked our issue and gave the iptables changes I needed to make! Unreal customer service. May 1, 2020 Is an excellent service, fast servers, cheap, fast and kind support. I love this company. Feb 14, 2020 Using their hosting services since a few days and I am completely amazed about their quality and services. VPS's are very reliable, enormous fast and easy to deploy [Ubuntu 18.04 Server]. The only thing I am wondering. Ordered 2 VPS's now in Seattle and Dallas and by searching on this website [IP Location Website] I am getting for both VPS ip locations the exact same hosting location. So I asked them how that's possible and hopefully I will get an answer soon. For sure I will update/add a notification with their response. At the moment I am using Virtual Private and Dedicated Servers from 33 different hosting companies and - really honestly - VPSDime is one of the fastest and most reliable. Based on my automated services monitoring. Really awesome hosting provider! Jun 9, 2019 Simply perfect. Hosting our discord bot on a linux host with 18 gig ram, 4 core 3ghz. Low latency, database read/write speeds super fast for only $28. I would recommend to everyone. May 9, 2019 VPSdime is simply amazing. Stability, uptime, price and incredible support. The staff is always willing to help and the response is always incredibly quick. I have 18 servers on vpsdime and I can say with confidence that you will not regret it. They are amazing! Jan 11, 2019 Best Price for your Dime, highly recommended. I am getting the benefit of dealing with a small, responsive, very attentive company rather then dealing with endless chat bots and forums of large hosting companies and best of all much lower price. i am able to focus on my work rather then spending countless hours trying to figure how to run a basic service. yes, they are missing some services, but they do compliment this with stellar customer support. Jan 9, 2019 I hired several hosts until I got to VPSDime. The service is fantastic and the staff is incredible. Super affordable price and customer service is extremely fast. Focusing on support is something I've honestly never seen in another company. Extremely proactive and friendly. They are to be congratulated. As I always say in my tickets: You guys are amazing. Dec 22, 2018 Hi all. I am a customer of VPSDime since 2014. They have been a truely great hosting company and have some great services. I would recommend everyone to look at the company's Premium hosting as it includes backup policy. The tech team is very professional and very quick to respond positively with every one of my requests. Aug 13, 2018 It has been a year i am using vpsdime, the best thing is thier support service, mostly i get a reply from them with in half an hour. For my other server like ovh, i have to wait around 24 hours and the asnwer is like that sorry, we cant help you. But vpsdime support is very good and fast Nov 15, 2017 I have searched high and low for a service that is affordable and great quality, my expectations have been blown from start to finish, I recommend VPSdime highly, they are legit, fast and most importantly responsible. June 16, 2021 Honestly, I've been using many VPS providers over the last years, before I've settled on with VPSDIME. Initially, I was very sceptical, however, $7 isn't a big deal to check out. I signed up with them and VPSDIME became my instant favourite. There's nowhere someone can get 6GB Dedicated RAM and 4 core processors for $7. There's also plenty of bandwidth and traffic between VMs (intranet) is unmetered which is really helpful and unlike most other providers. Every time I raised a support ticket (and only for technical support with billing and invoice cycles and for queries), they were very promptly responded to, even at odd times. This is really incredible. PROS: - 4 core processor (hyperthreaded), but do note, the combined power will be close to the advertised GHz, not for a single core. - 6GB Dedicated RAM - Excellent IOPS and Networking to most locations. Honestly, that's a true 10gbps uplink so it's blazing fast. - Support ticket speeds. Do check out the actual measurements on VPSbenchmarks for VPSDime. March 14, 2019 Hello everyone, I've gone through several hosting companies, including several world-famous ones, but they do not even have the quality, price and support that VPS Dime offers to customers. I recently had a problem with a host and they were most willing to adjust the server again. It was simply amazing. And the speed of the bracket is another fantastic point. They answer all questions in minutes. If you are looking for a robust hosting, with a good price, with incredible support, VPSDime is your best option, without a doubt !!! January 16, 2019 i've been working with VPSdime for a couple of years now, their prices are affordable, their support team is extremely responsive and knows what they're doing, i've had a couple of downtimes but they're always on top of things and communicating to us what is happening. 10/10 this is the hosting service to use! December 10, 2018 I'm hosting only one cheap VPS at VPSDime, but I can't say I've ever seen anything less than top-notch service there. Professionally I work in IT as well and I know that low-end customers don't always get the same stellar service as the 'big guys', but this isn't the case here. Excellent price, 100% uptime, 100% service. That's all I can say. September 02, 2018 Support is very good and pricing excellent. Also other provider will shut you down when you go over limit , VPS Dime support politelly asked what the issue with our machine is and they even help solved it. Definetely would recommend!!! Support reacts VERY fast. September 02, 2018 I've been using VPSDime's high memory VPSes for 4 years now as my main hosting solution and couldn't be happier. In that time, we've only faced a handful of tiny outages most of which we were notified ahead of time. For an unmanaged service, their support is exceptional! With most issues I faced, the ticket received a response within 30 minutes. The speed of the service is good overall, although of the 4 nodes we have they all have slightly different performance - not very consistent but they're all more than acceptable. August 30, 2018 I have multiple servers running on both the High Memory VPS and Premium VPS. I've been using them for almost 3 years now. I first tried GoDaddy for my VPSes, but they were overpriced and very unreliable so that prompted me to find a new provider. I'm so glad that I found VPSDime. Just because they are cheap doesn't mean that you get what you pay for. Quite the contrary! I have yet to have one outage in the 3 years. Their customer service is extremely responsive. I usually get a response in under 15 minutes., I even recommended them to a client of mine who was paying $7000+ to host on AWS. I helped them migrate to better, faster, more reliable servers on VPSDime (AWS had 2 outages last year) for a total price point of $1500+. No more worries about incidental charges for bandwidth usage, emails, etc.. either that are always surprises with AWS. My client has never looked back. Jun. 1, 2020 You get a decent 4 core vCPU, 6 GB of DDR3 memory, 30 GB of space, and 2 TB of traffic with 10 GB/s uplink; for just 7 USD a month. At first when I first visited their website I was thinking that it's too good to be true, but turned out to be even better. Their customier service is amazing, you can expect a swift reply. Not only that if you ever lose access to your server or just somewhere not on your computer and you need to access your server ASAP, their web inferace control panel let's you access to your server and run commands! May 9, 2020 The support staff at VPSDime continue to go above and beyond to help fix any issues I experience. It's easy for a company to provide a base level of support for an unmanaged solution, and tell the customer it's up to them to figure the rest out. VPSDime, however, shows they truly care about their clients by helping in any way they can. I am continuously impressed by their service and uptime, and recommend them to everyone I know looking for a VPS solution. Price - Service - Reliability: the three things that matter most with VPS hosting are the three things VPSDime focus on. I highly recommend them! May 6, 2020 May 3, 2020 Is the best company of VPS which i worked ever. 100% Recommended, excellent support and quality of servers. Apr. 7, 2020 VPSdime Hosting Solutions es una maravilla, la probe y me encanto, te ofrecen rapidas soluciones y un soporte tecnico magnifico, muchas gracias Mar. 20, 2020 i am doing business with VPSDime for almost 3 yrs now, and i am extremely happy with the level of service and especially the support. Dec. 8, 2019 One of the best provider in the world. Server is not slow at all. Support is great, nothing to worry about. First i had a storage vps, now i changed for 6gb/4core for 7$. You dont need more. Jan. 12, 2019 I'm hosting a single VPS there for $7 a month, which understandably should put me at the bottom of the priority list. What I experienced - consistently over years - is the exact opposite. As a matter of fact I get things there that are unheard of for most other support departments - Support agents who actually know what they are doing - Extremely swift responses, not matter what time/day - Very professional & friendly, even if the customer (yep, that's me...) is in panic mode Long story short. These guys are brilliant. By any means host your server there, not somewhere else. I have only tried a few other hosters, for big projects and small, and nobody gets close in terms of support. Oh right... the machines. Not much to say. They run. Always. Unless I mess them up. Sep. 3, 2018 Dec. 11, 2017 their support is very helpful and cooperative . Once because of nulled theme, all of my resources start consuming, they help me to figure out this in a very good way. Nov. 7, 2017 When it comes to linux, I experimented a lot and screwed up a lot. Their customer service reps were kind enough to guide me along the way and informed me of any mistakes I made, and helped me fix those mistakes. They were also kind enough to answer any queries I had. Their pricing is very fair and one of the cheapest in the market right now. Reliability? We haven't had any downtime with them in over 2 years! --- ## Free Sponsored VPS URL: https://vpsdime.com/free-vps Summary: Acquire a free VPS for your project #### We'd love to support your next big project ### Our values ##### VPSDime is a values-driven organization. Here is what we believe in: - We love open source - We love giving back - We love what we do Open Source is not just a movement, it's an attitude. It allows for communities to come together and make powerful things happen because they are opening up their development resources - no matter where you're from or what skillset! ##### VPSDime is sponsoring! ##### See the opportunities below to get a free VPS for your project or community. - Open Source Projects - Communities #### Open Source Projects We love to contribute to open source projects in any way we can. You could rely on us to help you power your infrastructure. Whether you need computing power to have your builds compiled and served or need test environment for bug fixing, we are here for you. We could provide you with a VPS to host your website as well. Just fill the form below, tell us more about your project and help us provide you with a free VPS. --- ##### Apply for Sponsored VPS --- ## Affiliate Program URL: https://vpsdime.com/affiliate-program Summary: Affiliate Program by VPSDime Earn 10% Recurring Commission For Each Sale Offering 10% recurring comission Just $50 minimum withdrawal limit ### VPSDime Affiliate Program VPSDime is well-known for providing generous amounts of resources at an inexpensive price to encourage new business startups and innovation in existing enterprises. Continuing our growth, we've come up with a referral program that offers our affiliates a substantial percentage of revenue generated by a referred service as a commission for the life of that service. #### How It All Works It's very easy to get started! Our affiliate scheme provides you 10% commission per sale. What makes us unique is that you will continue to receive 10% for that service every time they renew as well (i.e. every recurring payment). All you need is an account with us and you will receive a unique affiliate link to get you off the ground. | Service | Recurring Commission | Minimum Withdrawal | | --- | --- | --- | | Linux VPS | 10% | $50.00 | | Windows VPS | 10% | $50.00 | | Premium VPS | 10% | $50.00 | | Storage VPS | 10% | $50.00 | #### No need to jump through any hoops. You don’t even need to be a client. All you need to do is sign-up as an affiliate. #### All From Your Client Panel Manage your affiliates and view your stats in one place without hassle so you can spend more time promoting. Generating Commissions We appreciate your work to promote us, and that's why we offer a very generous referral commission. Not only will you gain 10% of the first payment, but also 10% of all future recurring payments for the life of the service. Reliable Tracking Our sophisticated tracking systems are built with reliability in mind. Your unique tracking link, when visited, will automatically set a cookie that lasts for 90 days. Automated Managment Our client panel automatically manages the affiliate program. That means you no longer have to manually notify us of your referrals or jump through extra hoops to get credited for them. #### How to Generate Revenue - Link to us on your website sidebar or footer. - Promote our services in community forums. - Write a review about your VPSDime experiences on your blog. - Put up a banner on your sites to convince your users to signup using your link. #### You're just one click away from making money! ### Become a VPSDime affiliate Two quick steps and you're earning 10% recurring commission. 1. 1 ### Create your account You'll need a VPSDime account first. It's free, and you don't have to be a paying customer to be an affiliate. [Create an account](https://vpsdime.com/register) 2. 2 ### Activate your affiliate account Sign in, open the **Affiliates** page in your client area, and click **Activate Affiliate Account**. Your referral links and dashboard are ready right away. [Go to Affiliates](https://vpsdime.com/affiliates) Already have an account? Just do step 2. [Read the full affiliate guide →](https://vpsdime.com/knowledgebase/client-area/affiliates/affiliate-program) --- ## Career Opportunities URL: https://vpsdime.com/careers Summary: VPSDime is hiring ##### Think You Have What Is Takes To Join Our Family? Why Not Apply? ### VPSDime is hiring! ##### We are always on the lookout for professionals who put love into what they do. - Remote Support Technician #### Remote Support Technician A remote working support technician who would be responsible for handling customer support tickets and monitor the infrastructure. ##### Shift Duration 21:00 - 5:00 GMT Monday - Saturday (You're welcome to apply if you can't work on Saturdays as well) ##### Qualifications A functional and demonstrable of conversational US/UK English Fluent in GNU/Linux (i.e: Using GNU/Linux for at least 5 years in day to day operations) Fluent in LXC, OpenVZ and KVM (i.e: Dealt with bugs and came up with fixes) Have experience with common servers and daemons and deal with their issues (i.e: Apache, nginx, php, python, nodejs, jira, mysql, postgresql, etc.) Windows Server experience is a plus but not necessary Have worked for at least one VPS company in the past and parted ways in good terms Can sympathize with the client and fix issues/offer solutions Loves web hosting business and helping people Doesn't hesitate to ask other technicians for help on Slack when necessary and learn on the way ##### Documents to Sign NDA Non-compete agreement ##### Reimbursement A monthly salary is going to be paid. The amount will be discussed with you privately. ##### Job Description Handle support tickets online during the shift (Average ticket count per day for this shift is 6.87 - data from the past 12 months) Screen new orders against fraud and approve/decline Monitor the infrastructure and act when something is not right (i.e: If there is an issue with a server, detect the issue, attempt to resolve/communicate with the DC technicians, follow up.) Read past tickets handled on other shifts when shift starts Communicate on Slack with other team members Read the past Slack chat and take notes of the Slack chat for new announcements and be aware ##### Explanation of Support Tickets handling You must reply the support tickets within 15 minutes. The reply must be meaningful. It shouldn't be something like, "I'm working on it now." and then start working on it. Ideally, you should attend to the tickets as soon as possible and then reply it with the answer/resolution if the resolution is going to take less than 15 minutes. If it's going to take more than 15 minutes, then you should reply the ticket and make the customer aware that you are working on their ticket. We have either very experienced customers who only ticket us when something is definitely wrong or inexperienced customers whose website is not working due to some error on the VPS OS itself. You should be able to resolve the issue that VPS has if it's not working correctly due to a reason caused by our infrastructure. For example, the server is down or the network is down. We have some inexperienced customers who are not, for example able to fix their httpd.conf syntax error and restart their Apache server. You should ask for permission to take a look at it and then handle their issue and reply their ticket. Most of the issues the inexperienced customers have are very simple issues and as a company, we take pride by not saying no to them as long as they are not abusing our good will. While handling tickets, you should show utmost respect to the customer if they are not abusing you. If you sense the customer is abusing you, you should escalate the ticket. ##### Explanation of screening new orders We have some inner intelligence to screen orders. You should carefully follow the steps and then decide on whether or not to approve the order. If you decide to decline the order, you should refund and then open a ticket to the customer respectfully denying them. You should put a note on the customer profile why you have denied the order as well. ##### Explanation of monitoring the infrastructure and handling issues You will be getting IPMI access and DC portal access. You are expected to detect the issues and come up with a solution. For example, if a VPS is getting SYN attack and the auto nulling mechanism of the DC is not working for that attack, you should be able to detect what IP is getting attacked and then nullroute it manually and then report the incident resolution on Slack. #### Application Form --- # Locations ## Dallas Datacenter URL: https://vpsdime.com/dallas-vps Summary: Get cheap virtual servers in Dallas, Texas from VPSDime Located in the middle of the United States. Best connectivity for continental America. ### All of Our Datacenters - Dallas, TX - [Seattle, WA](https://vpsdime.com/seattle-vps) - [Los Angeles, CA](https://vpsdime.com/los-angeles-vps) - [Piscataway, NJ](https://vpsdime.com/new-jersey-vps) - [London, UK](https://vpsdime.com/london-vps) - [Amsterdam, NL](https://vpsdime.com/amsterdam-vps) ### Carrier-1 Datacenter Located in Dallas, TX The Carrier-1 data center in Dallas, Texas is known for its state of the art technology. Its brand new environmental systems and electrical infrastructure has proven itself to be best for redundancy. The Data Center's full staff (on site) monitors it 24/7 so that 100% uptime can always be guaranteed by them. With direct access to any Tier-1 carrier, incredible availability and high speeds are provided. The latest generation routing and switching equipment is used for the most reliable connections possible. #### Brief Facility Datasheet - #### Location 1515 Round Table in Dallas, TX - #### Test IP 104.237.13.1 - #### Certifications SSAE-16 SOC 1 Type 2 Certified - #### Size 106,866 gross sq. ft. on 8.6 acres; 30,000 sq ft of customer / office / support space - #### Carriers Level3, Cogent, Hurricane Electric, NTT, Telia, GTT, DE-CIX Dallas, Equinix Dallas. - #### Power 100% Power uptime - #### Support 24/7 Critical building monitoring and management systems observed around the clock - #### Security 24/7/365 secured entrance. Card-key access into data center - #### Excellent Connectivity Connected to Equinix via dark fiber to the DALLAS INFOMART providing access to any Tier-1 carrier. #### Test our network speed with a file download 100MB [Download](https://lg.dallas.vpsdime.com/100MB.test) [Download](https://lg.dallas.vpsdime.com/1GB.test) [Download](https://lg.dallas.vpsdime.com/10GB.test) #### Deploy a VPS in Dallas Purchase your cheap Dallas VPS Linux VPS Run your applications without compromising on quality or support. Offers gobs of resources at a highly affordable price point. [Order](https://vpsdime.com/linux-vps) Windows VPS Powered by Microsoft Hyper-V. Convenient and easy to manage by remote desktop. Perfect for development and production. [Order](https://vpsdime.com/windows-vps) Premium VPS Designed to run enterprise applications with incredible performance, reliability and speed. All resources are fully dedicated. [Order](https://vpsdime.com/premium-vps) Storage VPS High-storage servers intended for backup use that you can rely on. Allows architecting your very own backup strategy using any software desired. [Order](https://vpsdime.com/storage-vps) --- ## Seattle Datacenter URL: https://vpsdime.com/seattle-vps Summary: Find out more about VPSDime's VPS offerings in Seattle, Washington Located in the great city of Seattle. Providing excellent connectivity to Pasific North West as well as Asia. ### All of Our Datacenters - [Dallas, TX](https://vpsdime.com/dallas-vps) - Seattle, WA - [Los Angeles, CA](https://vpsdime.com/los-angeles-vps) - [Piscataway, NJ](https://vpsdime.com/new-jersey-vps) - [London, UK](https://vpsdime.com/london-vps) - [Amsterdam, NL](https://vpsdime.com/amsterdam-vps) ### Westin Building Located in Seattle, WA. The Westin Data Center is considered one of the most plugged-into buildings in America's Northwest region after undergoing significant upgrades including an extensive electrical and mechanical infrastructure update throughout its 280 thousand square feet capacity which houses both data center and technical spaces while also housing 1 hundred ten thousand square feet worth of offices on site. The building hosts the main node of the Seattle Internet Exchange. It is staffed around the clock to ensure reliability all year around. #### Brief Facility Datasheet - #### Location 2001 Sixth Avenue in Seattle, WA - #### Test IP 104.237.1.1 - #### Certifications SSAE-16 SOC 1 Type 2 Certified - #### Size The data center is 500000 sqft. There is a total of 7200 sqft in raised floor space for colocation. - #### Carriers Level 3, Cogent, Hurricane Electric, GTT, Telia, SIX Peering. - #### Power 100% Power uptime - #### Support 24/7 Critical building monitoring and management systems observed around the clock - #### Security Dual-factor Authentication for entry - #### Excellent Connectivity Host to over 250 networks, carriers and ISPs, this is one of the most connected buildings in the world. #### Test our network speed with a file download 100MB [Download](https://lg.seattle.vpsdime.com/100MB.test) [Download](https://lg.seattle.vpsdime.com/1GB.test) [Download](https://lg.seattle.vpsdime.com/10GB.test) #### Deploy a VPS in Seattle Purchase your cheap Seattle VPS Linux VPS Run your applications without compromising on quality or support. Offers gobs of resources at a highly affordable price point. [Order](https://vpsdime.com/linux-vps) Windows VPS Powered by Microsoft Hyper-V. Convenient and easy to manage by remote desktop. Perfect for development and production. [Order](https://vpsdime.com/windows-vps) Premium VPS Designed to run enterprise applications with incredible performance, reliability and speed. All resources are fully dedicated. [Order](https://vpsdime.com/premium-vps) Storage VPS High-storage servers intended for backup use that you can rely on. Allows architecting your very own backup strategy using any software desired. [Order](https://vpsdime.com/storage-vps) --- ## Los Angeles Datacenter URL: https://vpsdime.com/los-angeles-vps Summary: Order your Los Angeles VPS for cheap from VPSDime Located in downtown Los Angeles. Providing connectivity to the most crowded part of the United States. ### All of Our Datacenters - [Dallas, TX](https://vpsdime.com/dallas-vps) - [Seattle, WA](https://vpsdime.com/seattle-vps) - Los Angeles, CA - [Piscataway, NJ](https://vpsdime.com/new-jersey-vps) - [London, UK](https://vpsdime.com/london-vps) - [Amsterdam, NL](https://vpsdime.com/amsterdam-vps) ### One Wilshire Datacenter Located in Los Angeles, CA The One Wilshire Data Center is a 300,000 sqft facility located in Los Angeles. The data center has 80000sqft of raised floor space for colocation and features Uninterruptible Power Supplies (UPS), CRAC units, and independent distribution routers to ensure service reliability during power outages or other equipment failure. High bandwidth capacity enables the data center's infrastructure to accommodate virtually unlimited scalability needs when they arise, ensuring that businesses can continue operations without interruption due to network issues at their hosting location. #### Brief Facility Datasheet - #### Location 530 W 6th St in Los Angeles, CA - #### Test IP 104.237.11.1 - #### Certifications SSAE-16 SOC 1 Type 2 Certified - #### Size 60,000 square feet of privately-owned and operated datacenter space - #### Carriers Cogent, Hurricane Electric, NTT, Telia, GTT, LA-IX Los Angeles, Equinix Los Angeles. - #### Power 100% Power uptime - #### Support 24/7 Critical building monitoring and management systems observed around the clock - #### Security 24/7/365 secured entrance. Card-key access into data center - #### Excellent Connectivity Bandwidth capacity exceeds 250 gigabits/second #### Test our network speed with a file download 100MB [Download](https://lg.losangeles.vpsdime.com/100MB.test) [Download](https://lg.losangeles.vpsdime.com/10GB.test) #### Deploy a VPS in Los Angeles Purchase your cheap Los Angeles VPS Linux VPS Run your applications without compromising on quality or support. Offers gobs of resources at a highly affordable price point. [Order](https://vpsdime.com/linux-vps) Windows VPS Powered by Microsoft Hyper-V. Convenient and easy to manage by remote desktop. Perfect for development and production. [Order](https://vpsdime.com/windows-vps) Premium VPS Designed to run enterprise applications with incredible performance, reliability and speed. All resources are fully dedicated. [Order](https://vpsdime.com/premium-vps) Storage VPS High-storage servers intended for backup use that you can rely on. Allows architecting your very own backup strategy using any software desired. [Order](https://vpsdime.com/storage-vps) --- ## New Jersey Datacenter URL: https://vpsdime.com/new-jersey-vps Summary: Get your reasonably priced New Jersey VPS located near New York From VPSDime Located in east of United States for great connectivity for East Coast and Europe. ### All of Our Datacenters - [Dallas, TX](https://vpsdime.com/dallas-vps) - [Seattle, WA](https://vpsdime.com/seattle-vps) - [Los Angeles, CA](https://vpsdime.com/los-angeles-vps) - Piscataway, NJ - [London, UK](https://vpsdime.com/london-vps) - [Amsterdam, NL](https://vpsdime.com/amsterdam-vps) ### Dupont Fabros Datacenter Located in Piscataway, NJ The 360,000 square foot building is equipped with 32 rotary UPS power systems to deliver 1,300 kW of critical output each in an N+2 redundancy configuration. It features 24 hour video surveillance and strictly enforced security access procedures that allow us to directly connect to major backbone providers for outstanding network performance with minimal regional latency. The datacenter is positioned to provide ultra-low latency for traders who desire the best access to financial markets. #### Brief Facility Datasheet - #### Location 101 Possumtown Rd in Piscataway, NJ - #### Test IP 104.237.8.1 - #### Certifications SSAE-16 SOC 1 Type 2 Certified - #### Size 360,000 square feet - #### Carriers Level3, NTT, Telia, GTT, NYIX. - #### Power 100% Power uptime with 36.4 MW Power Feed - #### Support 24/7 Critical building monitoring and management systems observed around the clock - #### Security Electronic monitoring of security and environmentals; Biometric + Card access security controls - #### Excellent Connectivity Connected to major backbone providers in the metropolitan area on-site #### Test our network speed with a file download 100MB [Download](https://lg.newjersey.vpsdime.com/100MB.test) [Download](https://lg.newjersey.vpsdime.com/1GB.test) [Download](https://lg.newjersey.vpsdime.com/10GB.test) #### Deploy a VPS in New Jersey Purchase your cheap New Jersey VPS Linux VPS Run your applications without compromising on quality or support. Offers gobs of resources at a highly affordable price point. [Order](https://vpsdime.com/linux-vps) Windows VPS Powered by Microsoft Hyper-V. Convenient and easy to manage by remote desktop. Perfect for development and production. [Order](https://vpsdime.com/windows-vps) Premium VPS Designed to run enterprise applications with incredible performance, reliability and speed. All resources are fully dedicated. [Order](https://vpsdime.com/premium-vps) Storage VPS High-storage servers intended for backup use that you can rely on. Allows architecting your very own backup strategy using any software desired. [Order](https://vpsdime.com/storage-vps) --- ## London Datacenter URL: https://vpsdime.com/london-vps Summary: Buy your Cheap London VPS from VPSDime Located in the financial capital of the world ### All of Our Datacenters - [Dallas, TX](https://vpsdime.com/dallas-vps) - [Seattle, WA](https://vpsdime.com/seattle-vps) - [Los Angeles, CA](https://vpsdime.com/los-angeles-vps) - [Piscataway, NJ](https://vpsdime.com/new-jersey-vps) - London, UK - [Amsterdam, NL](https://vpsdime.com/amsterdam-vps) ### London Datacenter Located in New Cut Road, Kent, United Kingdom London's Tier III data center is a prime location for financial services infrastructure. The three-story building provides abundant power, space and connectivity options so your business can grow with us as needed. A 24/7 security team ensures the utmost in safety and privacy while electric gates provide additional protection from external threats like weather or natural disasters that may impact nearby areas. As with all VPSDime data centers, services are delivered at guaranteed service levels and around-the-clock support. Our data centers have onsite expert engineers supporting our own systems and services. These dedicated technicians are available 24/7/365 to resolve any issues or concerns you may encounter during your time working in the cloud environment provided by us. #### Brief Facility Datasheet - #### Location New Cut Road, Kent, United Kingdom - #### Test IP 185.185.126.1 - #### Certifications ISO 27001 Certified - #### Size Capacity for 1000+ Racks - #### Carriers London Internet Exchange (LINX) Peering, TeliaSonera AB, and Lumen - #### Power A 100% Uptime Record with True 2N UPS Dual Path Resilience - #### Support 24/7 Critical building monitoring and management systems observed around the clock - #### Security PIN, photographic and card combination access - #### Excellent Connectivity Located near continental Europe to provide the best latency for both in the United Kingdom and Europe. #### Test our network speed with a file download 100MB [Download](https://lg.london.vpsdime.com/100MB.test) [Download](https://lg.london.vpsdime.com/1GB.test) [Download](https://lg.london.vpsdime.com/10GB.test) #### Deploy a VPS in The United Kingdom Purchase your cheap London VPS Linux VPS Run your applications without compromising on quality or support. Offers gobs of resources at a highly affordable price point. [Order](https://vpsdime.com/linux-vps) Windows VPS Powered by Microsoft Hyper-V. Convenient and easy to manage by remote desktop. Perfect for development and production. [Order](https://vpsdime.com/windows-vps) Premium VPS Designed to run enterprise applications with incredible performance, reliability and speed. All resources are fully dedicated. [Order](https://vpsdime.com/premium-vps) Storage VPS High-storage servers intended for backup use that you can rely on. Allows architecting your very own backup strategy using any software desired. [Order](https://vpsdime.com/storage-vps) --- ## Amsterdam Datacenter URL: https://vpsdime.com/amsterdam-vps Summary: Purchase your Netherlands VPS located in Amsterdam from VPSdime The Digital Gateway To Europe ### All of Our Datacenters - [Dallas, TX](https://vpsdime.com/dallas-vps) - [Seattle, WA](https://vpsdime.com/seattle-vps) - [Los Angeles, CA](https://vpsdime.com/los-angeles-vps) - [Piscataway, NJ](https://vpsdime.com/new-jersey-vps) - [London, UK](https://vpsdime.com/london-vps) - Amsterdam, NL ### Amsterdam Datacenter Located in Amsterdam, Netherlands Our Amsterdam data center is a Tier 3 design with 100% uptime track record, guaranteeing high availability for your enterprise needs. The network redundant global backbone ensures the highest available bandwidth and near-zero latency to multiple destinations including Nikhef and Iron Mountain while combined with unique indirect adiabatic cooling configuration our Amsterdam data center achieves an extremely energy efficient facility that guarantees exceptional service quality along with its unmatched density per rack unit The network is designed in a way that it never depends on a single point of failure. For example, the fiber paths are geologically separated and ensure business continuity at all times. #### Brief Facility Datasheet - #### Location Industriestraat 53, 2671 in The Netherlands - #### Test IP 185.185.127.1 - #### Certifications ISO 9001:2015 Certified - #### Size 536 data center racks - #### Carriers A blend of Tier 1 network providers and selectively chosen peering partners - #### Power 2N infrastructure design - #### Support 24/7 Critical building monitoring and management systems observed around the clock - #### Security Biometric access control, electric fences, video surveillance - #### Excellent Connectivity 10 Tbit/s network redundant global backbone ensures the highest available bandwidth and uptime guarantees for enterprise needs. #### Test our network speed with a file download 100MB [Download](https://lg.amsterdam.vpsdime.com/100MB.test) [Download](https://lg.amsterdam.vpsdime.com/1GB.test) [Download](https://lg.amsterdam.vpsdime.com/10GB.test) #### Deploy a VPS in The Netherlands Purchase your cheap Amsterdam VPS Linux VPS Run your applications without compromising on quality or support. Offers gobs of resources at a highly affordable price point. [Order](https://vpsdime.com/linux-vps) Windows VPS Powered by Microsoft Hyper-V. Convenient and easy to manage by remote desktop. Perfect for development and production. [Order](https://vpsdime.com/windows-vps) Premium VPS Designed to run enterprise applications with incredible performance, reliability and speed. All resources are fully dedicated. [Order](https://vpsdime.com/premium-vps) Storage VPS High-storage servers intended for backup use that you can rely on. Allows architecting your very own backup strategy using any software desired. [Order](https://vpsdime.com/storage-vps) --- # Policies ## Terms of Service URL: https://vpsdime.com/tos Summary: VPSDime Terms of Service Effective date: 2026-07-03 These Terms of Service ("Terms") govern your use of the VPSDime service (the "Service"). By ordering, accessing, or using the Service, you agree to be bound by these Terms. If you do not agree, do not use the Service. ### Definitions "VPSDime", "we", "us", and "our" refer to Nodisto FZE, B.C. 1305967, Ajman Free Zone, United Arab Emirates, the operator of the Service. "You" and "your" refer to the natural or legal person who orders, accesses, or uses the Service. ### The Service We provide virtual private server (VPS) hosting: virtualized compute, storage, and network resources accessible over the Internet. Specific resource allocations, software, and features for each plan are described on our website at the time of order. Except as expressly stated in the Service Level Agreement section below, we do not guarantee any specific level of uptime, performance, or availability. You are responsible for all activity that occurs on or through your service. ### Service Level Agreement We offer a 99.9% network uptime SLA and a 99.99% power uptime SLA. If we fall short of these commitments, you may claim the corresponding service credit by opening a support ticket from your authenticated client area. Service credits are your sole and exclusive remedy for any failure to meet these commitments. Beyond these commitments, no uptime, performance, or availability guarantee of any kind is made. ### Account Registration You must be at least 18 years old and able to enter into a legally binding contract. You must provide accurate and current identification information when ordering and must keep it updated. We may, at our sole discretion, verify any information you provide. We may suspend or terminate any account that we determine, in our sole discretion, is associated with false or inaccurate information, fraud, or any violation of these Terms. Accounts opened to circumvent suspension, termination, payment obligations, or these Terms may be terminated without notice. We may decline to provide service to any person or entity, at our sole discretion. Orders placed while using a VPN, proxy, or other anonymization methods to conceal your identity may be declined or terminated. We use services from MaxMind and FraudRecord to screen all new orders automatically, and orders and payments may be subject to manual review. If resolving a verification review takes multiple days, we will credit your account for the number of days it took to resolve. ### Sanctions You represent that you are not located in, organized under the laws of, or ordinarily resident in a jurisdiction subject to comprehensive sanctions under U.S., European Union, United Kingdom, United Nations, or applicable UAE sanctions regimes, and that you are not a person or entity listed on any applicable sanctions list. We may suspend or terminate any service, without notice, if we determine that your use of the Service violates or could cause us to violate any applicable sanctions law. ### Acceptable Use Your use of the Service is subject to the following rules. We may suspend or terminate any service for violation of these rules, at our sole discretion, with or without notice. These rules are supplemented by our Acceptable Use Policy at [https://vpsdime.com/aup](https://vpsdime.com/aup), which forms part of these Terms. **1. Resource fair use.** Sustained 100% CPU, IOPS, or network usage that affects other customers is not permitted. We may notify and throttle services that exceed fair use, and may suspend services that do not return to fair use after notice. Plans with dedicated resources are not subject to fair-use throttling for the resources specifically dedicated to the plan. **2. Prohibited content.** You may not use the Service to host, distribute, or transmit: sexually explicit adult content, pornography, or sex work content; child sexual abuse material (always reported to authorities); hate speech, incitement, harassment, doxxing, or defamatory content; terrorism, violent extremism, or content promoting violence against persons or groups; content infringing copyright, trademarks, or other intellectual property rights, including nulled, cracked, or otherwise pirated software; gambling, betting, lotteries, or online casinos; drugs, controlled substances, or weapons sales; counterfeit or replica goods; HYIP, Ponzi schemes, or pyramid schemes; fraud, phishing, or identity theft material. **3. Prohibited network behavior.** You may not use the Service to operate or facilitate: public proxy services, public VPN services, or residential proxy / exit-node networks; TOR relays, exits, entry guards, or bridges; open SMTP relays; outbound spam, bulk unsolicited email, or mailing-list software without verified opt-in; outbound port scanning, vulnerability scanning, or brute-force activity against third parties; outbound denial-of-service or amplification attacks; IP spoofing; forgery of email headers, packet headers, or other identifying information; use of IP addresses not assigned to your service; interception of network traffic not destined for your service; attempts to access, compromise, or subvert the security of our systems or other customers' services; phishing, malware command-and-control, or botnet infrastructure. **4. Prohibited workloads.** You may not use the Service for: cryptocurrency mining (all variants and chains); torrent clients, trackers, or seeders; web scraping that generates denial-of-service-level load on third parties or that ignores robots.txt directives; view-bot, traffic-exchange, or artificial-engagement networks; booter, stresser, or denial-of-service-for-hire services. **5. Allowed uses, subject to fair use.** The following are permitted, subject to the resource fair-use rules above: AI inference workloads; cryptocurrency staking and validator nodes; game servers; lawful streaming that does not infringe third-party rights or violate these Terms; personal or private VPN and proxy use (for the customer's own use only, not multi-tenant or sold-on services); hosting your clients' websites and applications (you remain responsible for their usage); web hosting, database hosting, and other normal application workloads. **6. Customer security obligations.** You must keep your software updated, use secure passwords and authentication, and notify us promptly if your account or service is compromised. ### Reselling Offering our servers or services as your own product (reselling or white-labelling) is not permitted. Hosting your clients' websites and applications on your services is allowed; you remain responsible at all times for all usage of your services, including usage by your clients. ### Email Policy Low-volume transactional and personal email is permitted. Bulk or unsolicited email of any kind is prohibited, as is maintaining an open, unsecured SMTP relay. Our monitoring systems may automatically block SMTP ports on services detected emitting mass mail. If an IP address assigned to your service becomes listed on an email blacklist as a result of your usage, a $250 charge per blacklist entry will be applied and you are required to handle the delisting. ### Billing When you order a service, an invoice is generated and becomes due immediately. Service does not commence until the invoice is paid. Services are provided on a subscription basis. Renewal invoices are generated automatically until you cancel the service in accordance with these Terms. Payments must be made from a payment instrument bearing the same name as the account holder, or a name reasonably similar. Requests to pay from a different name may be submitted by ticket and accepted at our sole discretion. All outstanding invoices must be paid before placing new orders. Account credit on your account may be applied automatically toward outstanding invoices. Renewal invoices are generated fourteen (14) days before their due date. A payment reminder is sent on the due date, and overdue notices are sent on each of the first three days an invoice is overdue. If a service is set to renew automatically and you also pay its invoice manually, you will not be charged twice for the same period. Prices may change at any time. We will provide at least 30 days' notice via email for any price increase affecting an existing subscription. The new price applies to renewals after the notice period. Prices listed on our website do not include any taxes, duties, or fees imposed by your jurisdiction. You are responsible for any such taxes, duties, or fees, including value-added tax (VAT), goods and services tax (GST), sales tax, withholding tax, or similar charges. A service whose invoice remains unpaid three (3) full days after its due date is suspended; that is, suspension occurs on the fourth day after the due date. We do not charge late fees, and paying the overdue invoice reactivates the service automatically, free of charge. A service whose invoice remains unpaid ten (10) full days after its due date is terminated without further notice; that is, termination occurs on the eleventh day after the due date, and the service data is permanently deleted. ### Traffic Allowance Each service includes a monthly traffic allowance that resets on the first day of each calendar month; unused allowance does not roll over. We notify you by email when your service reaches 75% and 100% of its allowance. If you do not purchase additional traffic or upgrade the service within 24 hours of reaching 100%, the service is suspended until you do so or until the allowance resets. ### Refunds No refunds are issued except as follows: the first service ordered by a customer is eligible for a refund if, within 72 hours of the time the service is provisioned and accessible to you, you (a) cancel the service through the authenticated client area and (b) request the refund by ticket from the authenticated client area. The trial refund is void if more than 90% of the service's monthly traffic allowance is used within the trial period. Only the first service ordered by a customer is eligible; no subsequent service, whether ordered by the same customer or by an account related to the customer, is eligible for a trial-period refund. Refunds due for payments made using methods that cannot be reversed (cryptocurrencies, AliPay, DOKU, Boleto, PIX) are issued as account credit. To the maximum extent permitted by applicable law, account credit balances are not refundable and are forfeited if your account is terminated by us for violation of these Terms; account credit balances otherwise never expire and are retained on your account. If we terminate your service without cause, we will refund the prorated amount of the remaining term. No other refunds are issued. ### Cancellation You may cancel your service at any time by submitting a cancellation request from your authenticated client area. We do not accept cancellation requests through other channels. Cancellation may be requested for immediate termination or for termination at the end of the current billing period, if those options are available in the client area. Immediate cancellation may result in immediate and permanent deletion of service data. ### Communications We may send you operational and account-related communications via email or through the client area, including service notices, billing notices, security alerts, and notices required by these Terms. The email address on your account is the official contact address for these communications. In addition to email, we may post operational notices in the client area. Operational and account-related communications cannot be opted out of while your account is active. You are responsible for receiving them. We are not liable for any consequences of your failure to receive them, including missed payment deadlines, suspensions, or terminations. ### Support The Service is unmanaged unless expressly stated otherwise in the applicable plan. Support requests must be submitted via ticket from the authenticated client area. Other channels (email, phone, live chat, social media, or any other means) may not receive a response. Our support covers issues with our infrastructure and services. We do not provide support for the operation, installation, configuration, or troubleshooting of customer software, applications, or operating systems running on the service. We make no commitment to any specific response time or resolution time and offer no compensation for delays. You may not request resolution by a specific staff member. Abusive behavior toward our staff may result in termination of service without refund. Complaints may be submitted by ticket from the authenticated client area; we will respond to complaints within ten (10) working days. ### Customer Data Your data is your responsibility. You are required to maintain your own off-site backups. You retain all rights to your data. Upon termination of your service for any reason, your data, including any backups stored as part of the backup service, is scheduled for permanent deletion and is not recoverable. We do not commit to any specific retention or deletion window and may delete data immediately upon termination. ### Backups We do not retain copies, snapshots, or backups of your service data unless your plan includes, or you have purchased, our Nightly Backups feature. Where Nightly Backups is active, the service is backed up once per night with a three-night retention; restores are self-service from the client area for Linux and Premium VPS services, and are performed by our team upon request by ticket for Windows VPS services. Premium VPS plans include Nightly Backups free of charge. Your data remains your responsibility at all times. We do not guarantee that backups will exist or be restorable, and we cannot be held accountable for missing or unrestorable backups. We will not restore backups to any third-party service or network, and we offer no compensation for data loss. Where Nightly Backups applies, our aggregate liability is limited to one month's subscription fee for the affected service. You are required to maintain your own off-site backups. ### Data Locations Your service operates in the datacenter location you select at the time of order. Customer account, billing, and operational data may be processed in other locations. Further details are described in our Privacy Policy. ### IP Addresses IP addresses assigned to your service are licensed for use with the Service and are not sold to you. We may change, remove, null-route, or reassign IP addresses where necessary for operational, security, abuse, legal, or network-management reasons. We do not guarantee the reputation, geolocation, blacklist status, or email deliverability of any IP address. ### DDoS Response Traffic targeting your service may be null-routed to protect our network and other customers. We may suspend or terminate service that is the target of sustained or recurring attacks. No refunds are issued for service affected by or terminated due to such attacks. ### Chargebacks Before initiating a chargeback or payment dispute, you must first attempt in good faith to resolve the matter with our support team via ticket from the authenticated client area, and must allow a reasonable opportunity for us to respond. Contacting us first is always faster and keeps your service online. If you raise a chargeback or payment dispute, or threaten to do so, the related service is suspended automatically while we work with you to resolve it; if a dispute was raised in error, we will give you the opportunity to resolve it with your bank or payment provider. We reserve the right to terminate services without refund where disputes are made in bad faith. ### Copyright Complaints We respond to notices of alleged copyright infringement under applicable copyright laws. We accept notices in the format prescribed by the U.S. Digital Millennium Copyright Act (DMCA), 17 U.S.C. § 512(c)(3), as well as equivalent formats under other applicable laws. Notices must be sent to abuse@nodisto.com and should include: (a) identification of the copyrighted work claimed to have been infringed; (b) identification of the allegedly infringing material and sufficient information to locate it; (c) your contact information; (d) a statement that you have a good-faith belief that the use is not authorized; (e) a statement that the information is accurate and that you are authorized to act on behalf of the copyright owner; and (f) your physical or electronic signature. We may forward notices to the affected customer. We maintain a repeat infringer policy and will terminate, in appropriate circumstances, the accounts of customers who are the subject of repeated substantiated copyright complaints. A customer that is the subject of two or more substantiated notices may be considered a repeat infringer at our discretion. ### Reporting Illegal Content To report content hosted on our network that you believe is illegal or violates these Terms, contact abuse@nodisto.com. Your notice should identify the content, explain the basis for the report, provide sufficient information for us to locate the content, and provide your contact information. We may acknowledge receipt of valid notices. We may, at our discretion, remove content, suspend service, or terminate accounts based on such notices. Where required by applicable law, we may provide a statement of reasons to the affected customer and an opportunity to respond. ### EU Digital Services Act Where the Digital Services Act applies, abuse@nodisto.com is our point of contact for notices concerning illegal content. Notices should include the exact electronic location of the content, the legal basis for the report, the reporter's contact information, and a good-faith statement that the information is accurate. Where required, we will provide a statement of reasons for restrictions imposed due to illegal content or Terms violations and may provide an opportunity to respond or appeal. ### Child Sexual Abuse Material We have zero tolerance for child sexual abuse material. Any service hosting such material will be terminated immediately and without notice. We will report such material to applicable authorities, which may include the National Center for Missing and Exploited Children (NCMEC) and equivalent national bodies, as required by applicable law, and we may cooperate with their investigations. ### Legal Process We may disclose customer information or content in response to a subpoena, court order, warrant, or other valid legal process; to comply with applicable law; to enforce these Terms; or to protect the rights, property, or safety of VPSDime, our customers, or others. We may preserve customer information or content where required or permitted by law. We are not obligated to notify the affected customer of such disclosures, except where required by law. Legal requests may be sent to legal@vpsdime.com. ### Privacy Our handling of personal data is described in our Privacy Policy, available at [vpsdime.com/privacy-policy](https://vpsdime.com/privacy-policy). You may exercise your data rights under applicable law by contacting us at legal@vpsdime.com. ### Customer Data Processing The Service is offered as raw infrastructure. We do not inspect, monitor, or analyze the content of files, databases, communications, or other data you store, transmit, or process using the Service, except as necessary to respond to abuse reports, investigate suspected violations of these Terms, or comply with law. In the course of operating the Service, we routinely perform technical operations on your data, including storage, replication, snapshotting, migration between physical hosts, and, where you have ordered the backup service, scheduled backups and restoration. These operations are performed automatically as part of providing the Service and do not involve inspection of the content of your data. The Service is not offered for use cases in which we would act as a "processor," "service provider," or equivalent role under the General Data Protection Regulation (GDPR), the UK GDPR, the California Consumer Privacy Act (CCPA), the Health Insurance Portability and Accountability Act (HIPAA), or similar data protection or sectoral privacy laws. We do not enter into Data Processing Agreements, Standard Contractual Clauses, Business Associate Agreements, or equivalent instruments. If your intended use of the Service requires any such agreement with your infrastructure provider, the Service is not suitable for your use case and you must not order it. You are solely responsible for compliance with all data protection and privacy laws applicable to any personal data you store, transmit, or process using the Service, including obtaining all required consents, providing all required notices, implementing all required security measures (including encryption of sensitive data at rest and in transit), and responding to data-subject requests. You will not represent to any third party that we have undertaken any role or obligation under any data protection law in respect of your data. We may suspend or terminate any service, with or without notice, if we determine that your use of the Service places us in the position of a processor or equivalent role under any data protection law. ### Disclaimer of Warranties The Service is provided "as is" and "as available" without warranties of any kind, either express or implied, including without limitation warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, reliability, or uninterrupted or error-free operation. We do not warrant that the Service will meet your requirements, be available without interruption, be secure, or be free from defects or data loss. ### Limitation of Liability To the maximum extent permitted by applicable law, we shall not be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, including without limitation loss of profits, revenue, data, goodwill, business opportunities, or third-party claims, arising from or relating to the Service, even if we have been advised of the possibility of such damages. Our aggregate liability for any claim arising from or relating to the Service shall not exceed the fees you have paid to us for the affected service in the three (3) months preceding the event giving rise to the claim. ### Indemnification You agree to indemnify, defend, and hold harmless us, our affiliates, officers, directors, employees, and agents from and against any claims, damages, losses, liabilities, costs, and expenses (including reasonable attorneys' fees) arising from or related to: (a) your use of the Service; (b) your violation of these Terms; (c) your violation of any law or any rights of a third party; or (d) any content or data you transmit, store, or process using the Service. ### Consumer Rights Nothing in these Terms limits or excludes any rights you have under mandatory consumer protection laws in your jurisdiction that cannot be waived by contract. Where any provision of these Terms is held unenforceable as applied to a consumer under such laws, the provision will be enforced to the maximum extent permitted, and the remainder of these Terms will continue in effect. ### Governing Law and Disputes These Terms, and any dispute arising out of or in connection with these Terms or the Service, are governed by the laws of the United Arab Emirates, together with the laws of the country in which your service is physically located where applicable, without regard to conflict of laws principles. Any dispute arising out of or in connection with these Terms or the Service shall be resolved exclusively by the competent courts of the United Arab Emirates. You consent to the personal jurisdiction of these courts and waive any objection based on inconvenient forum. Any dispute arising out of or in connection with these Terms or the Service must be brought solely in your individual capacity. You waive any right to bring or participate in any class, collective, or representative action. Any claim arising out of or in connection with these Terms or the Service must be brought within one (1) year of the date the claim arose. Claims not brought within this period are permanently barred. ### Force Majeure We are not liable for any failure or delay in performance caused by events beyond our reasonable control, including acts of God, war, civil disturbance, government action, labor disputes, power or telecommunications failures, network or infrastructure outages, denial-of-service attacks, or natural disasters. ### Severability If any provision of these Terms is held to be invalid, illegal, or unenforceable, the remaining provisions shall remain in full force and effect, and the invalid provision shall be modified to the minimum extent necessary to make it valid, legal, and enforceable. ### No Waiver Our failure to enforce any right or provision of these Terms shall not be deemed a waiver of that right or provision. No waiver shall be effective unless made in writing. ### Assignment You may not assign or transfer your rights or obligations under these Terms without our prior written consent. We may assign or transfer our rights and obligations under these Terms at any time without notice. Any attempted assignment by you in violation of this section is void. ### Changes to Terms We may modify these Terms at any time, with or without notice. Modified Terms are effective when posted to our website. You are responsible for reviewing the current Terms, and your continued use of the Service after the effective date constitutes acceptance of the modified Terms. ### Entire Agreement These Terms, together with any policies or documents referenced herein, constitute the entire agreement between you and us regarding the Service, and supersede any prior agreements, communications, or understandings. ### Independent Parties Nothing in these Terms creates any agency, partnership, joint venture, employment, or franchise relationship between you and us. ### Language These Terms are written in English. Any translation is provided for convenience only. In the event of any conflict between the English version and a translation, the English version controls. ### Notices Legal notices to us must be sent to legal@vpsdime.com. Notices to you may be sent to the email address on your account or posted in the client area. ### Order of Precedence If there is a conflict between these Terms, an invoice, a plan description, the Privacy Policy, or any other referenced policy, the following order controls: first, any signed written agreement; second, the invoice or order terms; third, these Terms; fourth, applicable policies; and fifth, general website descriptions, unless expressly stated otherwise. ### Survival The provisions of these Terms that by their nature should survive termination, including without limitation the Disclaimer of Warranties, Limitation of Liability, Indemnification, Disputes, Customer Data, and any payment obligations accrued prior to termination, will survive termination of these Terms or your service. ### Contact Nodisto FZE B.C. 1305967 Ajman Free Zone United Arab Emirates Support: via ticket from your authenticated client area Abuse reports: abuse@nodisto.com Legal requests: legal@vpsdime.com --- ## Acceptable Use Policy URL: https://vpsdime.com/aup Summary: VPSDime Acceptable Use Policy Revision date: 03/07/2026 ### Torrents, TOR, public proxy/VPN services, cryptocurrency mining and bulk email are not allowed. **If your service is a constant target of DDoS attacks, we may stop the service. If you expect to be attacked regularly, we recommend putting a DDoS mitigation service (such as Cloudflare) in front of your service.** As a provider of web site hosting and other Internet-related services, VPSDime offers its customer (also known as "Subscribers") and their customers and users the means to acquire and disseminate a wealth of public, private, commercial and non-commercial information. VPSDime respects that the Internet provides a forum for free and open discussion and dissemination of information. However, when there are competing interests at issue, VPSDime reserves the right to take certain preventive or corrective actions. In order to protect these competing interests, VPSDime has developed an **Acceptable Use Policy ("AUP")**, which supplements and explains certain terms of each customer's respective service agreement, and is intended as a guide to the customer's rights and obligations when using VPSDime' services. This AUP will be revised from time to time. One important aspect of the Internet is that no one party owns or controls it. This fact accounts for much of the Internet's openness and value, but it also places a high premium on the judgement and responsibility of those who use it, both in the information they acquire and in the information they disseminate to others. When subscribers obtain information through the Internet, they must keep in mind that VPSDime cannot monitor, verify, warrant or vouch for the accuracy and quality of the information they acquire. For this reason, the subscriber must exercise his or her best judgement in relying on information obtained from the Internet, and also should be aware that some material posted to the Internet may be sexually explicit or otherwise offensive. Because VPSDime cannot monitor or censor the Internet, and will not attempt to do so, VPSDime cannot accept any responsibility for injury to its subscribers resulting from inaccurate, unsuitable, offensive or illegal Internet communications. When subscribers disseminate information from the Internet, they must keep in mind that VPSDime does not review, edit, censor or take responsibility for any information its subscribers may create. When users place information on the Internet, they have the same liability as other authors for copyright infringement, defamation and other harmful speech. Also, because the information created is carried over VPSDime' network and may reach a large number of people, including both subscribers and non-subscribers of VPSDime, subscribers' postings to the Internet may affect other subscribers and may affect VPSDime' goodwill, business, reputation or operations. For these reasons, subscribers violate VPSDime policy and the Service Agreement when they, their customers, affiliates or subsidiaries engage in the following prohibited activities: **Spamming:** Sending unsolicited bulk and/or commercial information over the Internet. It is not only harmful because of its negative impact on consumer attitudes toward VPSDime, but also because it can overload VPSDime's network and disrupt service to VPSDime's subscribers. Also, maintaining an open SMTP relay is prohibited. Low-volume transactional and personal email is permitted; bulk sending of any kind is not, and our monitoring systems automatically block SMTP ports on servers detected emitting mass mail. When a complaint is received, VPSDime will investigate and suspend the account if it is found to be sending SPAM. If your IP address is blacklisted as a result of your usage, a $250 charge per blacklist entry will be applied and you are required to handle the delisting. Furthermore VPSDime reserves the right to prosecute for this violation. **BitTorrent:**: VPSDime does not allow BitTorrent, you may not run any bit torrent application/script, tracker, or client, and will suspend/terminate any offending account. **TOR - Open Proxy/VPN:** You may not run any public proxy services or any scripts that interface with TOR, including TOR relay, entry, exit and bridge nodes. TOR, public proxies and public VPN's are strictly forbidden and we reserve the right to immediately terminate any account, without warning, found to be running these services. **Digital Currency Mining** The high CPU load produced by mining digital currency negatively impacts performance for all of our customers, as such you may not mine any digital currency on our network, whichever coin or chain is involved. Cryptocurrency staking and validator nodes are permitted, subject to fair use. **CamFrog:** Due to the high frequency of DDOS attacks against CamFrog servers, it is forbidden to host Camfrog servers or other server applications that are frequent targets of Denial of Service attacks or other types of attacks. If found to be running such services your server will be immediately suspended and the server will not be reconnected to the network until such time that you agree to completely remove any and all traces of the offending service, and agree to let us have access to your server to confirm that the content has been completely removed. Any server guilty of a second violation will result in immediate account termination. **Adult Content:** Hosting, transmitting or distributing adult content on VPSDime's network is prohibited. **Obscene Speech or Materials:** Using VPSDime's network to advertise, transmit, store, post, display, or otherwise make available child pornography or obscene speech or material is prohibited. VPSDime is required by law to notify law enforcement agencies when it becomes aware of the presence of child pornography on or being transmitted through its network. **Defamatory or Abusive Language:** Using VPSDime's network as a means to transmit or post negative, defamatory, harassing, abusive or threatening language. **Forging of Headers:**Forging or misrepresenting message headers, whether in whole or in part, to mask the originator of the message. **Illegal or Unauthorized Access to Other Computers or Networks:** Accessing, illegally or without authorization, computers, accounts or networks belonging to another party, or attempting to penetrate security measures of another individual's system (often known as "hacking"). Also, any activity that may be used as a precursor to an attempted system penetration (i.e., port scan, stealth scan or other information-gathering activity). **Distribution of Internet Viruses, Worms, Trojan Horses or Other Destructive Activities**: Distributing information regarding the creation of and sending Internet viruses, worms, Trojan horses, pinging, flooding, mail bombing or denial of service attacks. Also, activities that disrupt the use of or interfere with the ability of others to effectively use the network or any connected network, system, service or equipment. **Facilitation a Violation of this AUP:** Advertising, transmitting or otherwise making available any software, program, product or service that is designed to violate this AUP, which includes the facilitation of the means to spam, initiation of pinging, flooding, mail bombing, denial of service attacks and piracy of software. **Other Illegal Activities:** Engaging in activities that are determined to be illegal, including, but not limited to, advertising, transmitting or otherwise making available ponzi schemes, pyramid schemes, fraudulently charging credit cards and pirating software. **Other Activities:** Engaging in activities, whether lawful or unlawful, that VPSDime determines to be harmful to its subscribers, operations, reputation, goodwill or customer relations. As we have pointed out, the responsibility for avoiding harmful activities just described rests primarily with the subscriber. VPSDime will not, as an ordinary practice, monitor the communications of its subscribers to ensure that the comply with VPSDime' policy or applicable law. However, when VPSDime becomes aware of harmful activities, it may take any action to stop the harmful activity, including, but not limited to, removal of information, shutting down a web site, implementing screening software designed to block offending transmissions, denying access to the Internet, or any other action deemed appropriate by VPSDime. VPSDime is also aware that many of its subscribers are themselves providers of Internet services, and that information reaching VPSDime' facilities from those subscribers may have originated from a customer of the subscriber or from another third party. VPSDime does not require its subscribers who offer Internet services to monitor or censor transmissions or web sites created by customers of its subscribers. VPSDime reserves the right to directly take action against a customer of its subscribers. Also, VPSDime may take action against the VPSDime' subscriber because of activities of a customer of the subscriber, even though the action may affect other customers of the subscriber. Similarly, VPSDime anticipates that subscribers who offer Internet services will cooperate with VPSDime in any corrective or preventive action that VPSDime deems necessary. Failure to cooperate with such corrective or preventive measures is a violation of VPSDime policy. VPSDime will not intentionally monitor private electronic mail messages sent or receive by its subscribers, unless required to do so by law, governmental authority or when public safety is at stake. VPSDime may, however, monitor its service electronically to determine that its facilities are operating satisfactorily. Also, VPSDime may disclose information, including, but not limited to, information concerning a subscriber, a transmission made using our network, or a web site, in order to comply with a court order, subpoena, summons, discovery request, warrant, statute, regulation or governmental request. VPSDime assumes not obligation to inform the subscriber that subscriber information has been provided and, in some cases, may be prohibited by law from giving such notice. Finally, VPSDime may disclose subscriber information or information transmitted over its network where necessary to protect VPSDime and others from harm, or where such disclosure is necessary to the proper operation of the system. However, VPSDime will never sell information to other services or outside companies. VPSDime expects that its subscribers who provide Internet services to others will comply fully with all applicable laws concerning the privacy of online communications. A subscriber's failure to comply with those laws will violate VPSDime policy. Finally, VPSDime wishes to emphasize that, in signing the Service Agreement, subscribers indemnify VPSDime for any violation of the Service Agreement, law or VPSDime policy resulting in loss to VPSDime or the bringing of any claim against VPSDime by any third party. This means that, if VPSDime is sued because of a subscriber's or customer of a subscriber's activity, the subscriber will be responsible for payment of any damages awarded against VPSDime, plus costs and reasonable attorney's fees. We hope this AUP is helpful in clarifying the obligations of Internet users, including VPSDime and its subscribers, as responsible members of the Internet. Any complaints about a subscriber's violation of this AUP should be sent to abuse@nodisto.com --- ## Privacy Policy URL: https://vpsdime.com/privacy-policy Summary: Privacy Policy of VPSDime This Privacy Policy describes how VPSDime ("VPSDime", "our", "us" or "we") collects, uses, and shares information gathered from your ("you", "your", "Client" or "Customer") use of our website, products and services ("Service" or "Services"). If you have any questions about our Privacy Policy, or wish to exercise your data rights, please contact legal[at]vpsdime.com. Any changes made to this Privacy Policy will be available on this page. The data controller of your personal information is Nodisto FZE (B.C. 1305967, Ajman Free Zone, United Arab Emirates), DBA VPSDime. Your privacy matters to us so please read the privacy policy thoroughly. If you have questions please contact us. ### Information We Collect VPSDime may collect information about you as follows: - By registering an account, we may collect information provided at the time of registration (name, company name, address, telephone number, and email address). - By linking our services to a third-party account, we may collect information from that account such as any authentication tokens involved in authorization. - If you contact us, we may collect data regarding your correspondence. - We may collect details of your transactions involved in the fulfillment of orders. VPSDime does not store your financial information on our systems. Your financial information is stored with our third-party payment processors. VPSDime does, however, have access to, and may retain, your information through our third-party payment processors. - When you visit our website we may capture your IP address, time of and duration of visit, and time and duration of the pages on our website that you view. We may tie this information to personally identifiable information we have about you. - When using our services, we may collect information about your utilization, such as processor, memory, storage, and network usage. ### Use of Information We will use your personally identifiable information only as follows: - For transaction processing. - To provide customer support. - To provide, maintain, improve, and expand our services. - To understand and analyze how you use our services. - For fraud checking, reporting, and other screening methods involving third-party companies in order to verify information submitted to us. - To enforce the Acceptable Use Policy ("AUP") in the detection, prevention, and resolving of abuse. - To announce special offers or provide other information from time to time via email with your consent. - To improve our service and the marketing of our service. For example, we may use the information we gather from user surveys, demographic data, and website visits to help us improve or target our website and customize your visit. ### Third-Party Sign-In (OAuth) VPSDime supports signing in to your account using third-party identity providers. The providers we currently support are Google and GitHub, with Microsoft and Facebook in the process of being added. When you choose to sign in or register using one of these providers, the provider sends us a limited set of information about your account: - Your verified email address. - Your first and last name, when available. - A stable identifier issued by the provider, used internally to recognise your account on return visits. We do not receive your password, your contacts, your messages, or any other data from the provider. We do not request offline or refresh-token access, and our connection to the provider exists only for the duration of each sign-in. We use this information to: - Match your sign-in to an existing VPSDime account, or pre-fill the registration form when you are creating a new account. - Recognise you on subsequent visits and sign you in. - Display your name in the client area as part of your account profile. If the email address returned by the provider already belongs to a VPSDime account, we send a confirmation link to that email address before any link is established. The link is only created after you click the confirmation, so a third-party sign-in cannot be attached to your account without explicit approval at the email address on file. We store, per linked provider, the provider name, the provider's stable identifier, the email address the provider returned at link time, and the date the link was created. You can view and remove any of these links at any time from the Sign-in Methods page in your client area. We also keep an internal audit log of sign-in events for security review (event type, timestamp, IP address, and outcome). Removing a linked provider only removes it from VPSDime. To revoke VPSDime's access at the provider side as well, visit the provider's own connected-apps settings (for example, Google Account → Security → Third-party apps). ### Authorised Disclosures Without prejudice to anything contained in this Privacy Policy and in the interest of full transparency, We reserve the right to disclose (and otherwise process) any relevant Personal Data relating to You which We may be processing (including in certain cases relevant IP addresses) to authorised third parties in or outside the EU/EEA if such disclosures are allowed under the Data Protection Laws (whether or not You have provided Your consent) including but not limited to: - For the purpose of preventing, detecting or suppressing fraud (for example, if You provide false or deceptive information about Yourself or attempt to pose as someone else, We may disclose any information We may have about You in Our possession so as to assist any type of investigation into Your actions); - In the event of VPSDime being involved in a merger, sale, restructure, acquisition, joint venture, assignment, transfer; - To protect and defend Our rights (including the right to property), safety, or those of Our affiliates, of Users of Our Site or even Your own; - To protect against abuse, misuse or unauthorised use of Our Site; - For any purpose that may be necessary for the performance of any agreement You may have entered into with Us (including the request for provision of services by third parties) or in order to take steps at Your request prior to entering into a contract; - To comply with any legal obligations such as may arise by way of response to any Court subpoena or order or similar official request for Personal Data; or - As may otherwise be specifically allowed or required by or under any applicable law (for example, under anti-money laundering legislation). - If you register an account through an affiliate referral link, we may share information with your referrer to let them know that you used their referral to order service. ### Internet Communications You will be aware that data sent via the Internet may be transmitted across international borders even where sender and receiver of information are located in the same country. We cannot be held responsible for anything done or omitted to be done by You or any third party in connection with any Personal Data prior to Our receiving it including but not limited to any transfers of Personal Data from You to Us via a country having a lower level of data protection than that in place in the European Union, and this, by any technological means whatsoever (for example, WhatsApp, Skype, Dropbox etc.). Moreover, We shall accept no responsibility or liability whatsoever for the security of Your data while in transit through the internet unless Our responsibility results explicitly from a law having effect in UAE. ### Accuracy of Personal Information All reasonable efforts are made to keep any Personal Data We may hold about You up-to-date and as accurate as possible. You can check the information that We hold about You at any time by accessing and updating Your account information in Your VPSDime client area to achieve accuracy, in addition you can contact us in the manner explained above. If You find any inaccuracies, We will correct them and where required, delete them as necessary. Please see below for a detailed list of Your legal rights in terms of any applicable data protection law. ### Legal Basis for Information Processing Our legal basis for collecting and processing your personal data depends on the specific data involved and the context in which we collect it. These reasons include: - When you order service from us, we need to collect personal data in order to fulfill our contractual obligation to you (account management, support, invoicing, etc.). - We are required by law to collect and process data for financial record-keeping and law enforcement compliance. - We have legitimate interests which require the collection of personal data in order to operate our business. - We may collect your data for marketing communications, etc. with your consent. You may also remove your consent at any time. ### Information About Consent Should You exercise Your right to withdraw Your consent at any time (by contacting Us as described above), We will determine whether at that stage an alternative legal basis exists for processing Your Personal Data (for example, on the basis of a legal obligation to which We are subject) where We would be legally authorised (or even obliged) to process Your Personal Data without needing Your consent and if so, notify You accordingly. When We ask for such Personal Data, You may always decline, however should You decline to provide Us with necessary data that We require to provide requested services, We may not necessarily be able to provide You with such services (especially if consent is the only legal ground that is available to Us). Just to clarify, consent is not the only ground that permits Us to process Your Personal Data. Contractual necessity, Legitimate interest, Legal obligation may also our be bases for collecting your data. ### Storage of Personal Data Our website, billing, and account systems are hosted in Canada, a country recognised by the European Commission as providing an adequate level of protection for personal data. As a general rule, Your account and billing data is therefore stored and processed in Canada. Some processing (for example by payment and fraud-screening providers) may take place in other countries, as described below. The content of Your VPS itself is stored in the datacenter location You select at the time of order. ### Transfers to Third Countries In some cases, it may be necessary for Us to transfer Your Personal Data to a non-EEA country not considered by the European Commission to offer an adequate level of protection. For example, for the implementation of Your desired transaction it can be necessary that We disclose Your Personal Data to other payment processors outside the EEA. In such cases, apart from all appropriate safeguards that We implement, in any case, to protect Your Personal Data, We have put in place additional adequate measures. For example, We have ensured that the recipient is bound by the EU Standard Contractual Clauses (the EU Model Clauses) designed to protect Your Personal Data as though it were an intra-EEA transfer. You are entitled to obtain a copy of these measures by contacting Us as explained above. ### Protection of Personal Data The personal information which We may hold (and/or transfer to any affiliates/partners/subcontractors as the case may be) will be held securely in accordance with Our internal security policy and the law. We use reasonable efforts to safeguard the confidentiality of any and/or all Personal Data that We may process relating to You and regularly review and enhance Our technical, physical and managerial procedures so as to ensure that Your Personal Data is protected from: - unauthorised access - improper use or disclosure - unauthorised modification - unlawful destruction or accidental loss. To this end We have implemented security policies, rules and technical and organisational measures to protect the Personal Data that We may have under Our control. All our members, staff and data processors (including specific subcontractors, including cloud service providers, who may have access to and are associated with the processing of Personal Data, are further obliged (under contract) to respect the confidentiality of Our Users' or clients' Personal Data as well as other obligations as imposed by the Data Protection Laws. Despite all the above, We cannot guarantee that a data transmission or a storage system can ever be 100% secure. For more information about Our security measures, please contact Us in the manner described above. Authorised third parties, and external/third party service providers, with permitted access to Your information (as explained in this Privacy Policy) are specifically required to apply appropriate technical and organisational security measures that may be necessary to safeguard the Personal Data being processed from unauthorised or accidental disclosure, loss or destruction and from any unlawful forms of processing. As stated above, the said service providers (Our data processors) are also bound by a number of other obligations in line with the Data Protection Laws (particularly, Article 28 of the GDPR). ### Data Retention We will retain Your Personal Data only for as long as is necessary (taking into consideration the purpose for which it was originally obtained). The criteria We use to determine what is 'necessary' depends on the particular Personal Data in question and the specific relationship We have with You (including its duration). Our normal practice is to determine whether there is/are any specific EU and/or UAE law(s) (for example tax or corporate laws) permitting or even obliging Us to keep certain Personal Data for a certain period of time (in which case We will keep the Personal Data for the maximum period indicated by any such law). For example, any data that can be deemed to be 'accounting records' must be kept for ten (10 years). We would also have to determine whether there are any laws and/or contractual provisions that may be invoked against Us by You and/or third parties and if so, what the prescriptive periods for such actions are (this is usually five (5) years). In the latter case, We will keep any relevant Personal Data that We may need to defend Ourselves against any claim(s), challenge(s) or other such action(s) by You and/or third parties for such time as is necessary. Where Your Personal Data is no longer required by Us, We will either securely delete or anonymise the Personal Data in question. ### Updating, Deleting, and Downloading Your Data You may update your data at any time either through the client area Account section or by submitting a support ticket. We may require proof of identification in order to change certain data fields. You may may request that VPSDime export your personal data by opening a support ticket. Customers with no active services may request that their account be closed and personal data be deleted from VPSDime's databases, with the exception of: billing system access logs, which may be stored for any duration of time at VPSDime's discretion, cases where financially fraudulent or otherwise illegal activity is deemed to have occurred (as determined by VPSDime management or law enforcement officials), in which case personal information may be retained indefinitely for purposes of ongoing investigation and prevention of fraud recurrence, or cases where a violation of the Terms of Service has resulted in termination of Customer's account, in which case personal information may be retained indefinitely for purposes of prevention of further use of VPSDime's services in the future by the offending Customer. VPSDime will not delete any data required to comply with our legal obligations and financial requirements, or any data required to resolve disputes and enforce our legal agreements and policies. ### Communication We may contact you directly or through a third-party service provider regarding products or services you have ordered from us. We may also send you marketing emails if you have opted-in through the client area. Communication methods may include: email, text (SMS) message. VPSDime does not offer phone support and will not call you directly at any time. ### Use of Non-Personally Identifiable Information We may share aggregate statistical data about our customers with third parties, such as advertisers or suppliers. This aggregate statistical data will not identify you personally. ### Cookies We may also place a "cookie" that will identify you to us as a repeat visitor or a customer when you visit our website. A cookie is an alphanumeric identifier that is unique to your browser. The cookie will identify your browser to us when you visit our website so that we may customize your visit. ### Your Rights Under GDPR If you are a resident of the EEA, you have the following data protection rights, which you may exercise by contacting us via support ticket: - Right to Access - You have the right to access your personal data and to request a data export from us. - Right to Rectification - You have the right to have any incorrect or incomplete personal data corrected. - Right to Restrict - You have the right to request the restriction of processing your personal data where there is no legitimate reason for us to do so. - Right to Object - You have the right to object to the processing of your personal data where we have no legitimate reason to do so. - Right to Erasure - You have the right to request the erasure of any personal data we have collected. However, this right does not override our financial and legal requirements to keep certain data (see above). - Right to Withdraw Consent - You have the right to withdraw consent (unsubscribe) from any marketing communications we may send you. Please note that we may ask you to verify your identity before responding to such requests. You have the right to complain to a Data Protection Authority about our collection and use of your Personal Data. For more information, please contact your local data protection authority in the EEA. ### Data Processing Agreements Our services are offered as raw infrastructure. We do not act as a "processor", "service provider", or equivalent role under the GDPR, the UK GDPR, the CCPA, HIPAA, or similar data protection laws in respect of the content you store, transmit, or process on your services, and we do not enter into Data Processing Agreements, Standard Contractual Clauses, Business Associate Agreements, or equivalent instruments. If your intended use of our services requires such an agreement with your infrastructure provider, our services are not suitable for your use case. This does not affect our obligations as the data controller of your account data, as described in this Privacy Policy. ### California Online Privacy Protection Act Compliance Because we value your privacy we have taken the necessary precautions to be in compliance with the California Online Privacy Protection Act. We therefore will not distribute your personal information to outside parties without your consent, except as described in this Privacy Policy. As part of the Online Privacy Protection Act, all users of our site may make any changes to their information at anytime by logging into their control panel and going to the 'Edit Profile' page. ### Children's Privacy Our service is not available to children under the age of 18, and we will not intentionally maintain personal information about anyone under the age of 18. Last updated: July 3, 2026 --- # Knowledge base ## Getting started with your VPS URL: https://vpsdime.com/knowledgebase/getting-started Last reviewed: 2026-07-05 Summary: The first steps after your VPS is deployed, connecting over SSH, uploading files with SFTP, pointing your domain, hosting a website with free SSL, securing the server properly, and setting up real backups. Your VPS is deployed, here's the path from "I have an IP address" to a working, secured, backed-up server. The guides read in order, but each stands alone. ### Get in and get your files up - [Your first 30 minutes on a new VPS](https://vpsdime.com/knowledgebase/getting-started/first-30-minutes). The checklist: update, sudo user, keys, firewall, backups, half of it doable on the deploy form itself. - [Managing your VPSDime VPS](https://vpsdime.com/knowledgebase/getting-started/managing-your-vpsdime-vps). The control panel tour: one login for billing and servers, and everything that's self-service. - [Connecting to your VPS (SSH)](https://vpsdime.com/knowledgebase/getting-started/connecting-to-your-vps). Username, password, your first `ssh` command, the Console fallback, and why Linux isn't RDP. - [Terminal basics](https://vpsdime.com/knowledgebase/getting-started/terminal-basics). Enough shell to run a server: tab completion, nano, systemctl, logs, and the safety habits. - [Using Claude Code on your VPS, safely](https://vpsdime.com/knowledgebase/getting-started/claude-code-on-vps). The AI agent as junior sysadmin, install, what it's good at, and the leash (CLAUDE.md rules included). - [Running a self-hosted AI agent (OpenClaw, Hermes)](https://vpsdime.com/knowledgebase/getting-started/self-hosted-ai-agents). The always-on agents with a web panel: honest RAM requirements, and why you must never expose the control panel to the internet. - [Setting up SSH keys, properly](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys). Generate on any OS, deploy via the panel or ssh-copy-id, the agent, and the config file. - [Uploading files (SFTP)](https://vpsdime.com/knowledgebase/getting-started/uploading-files-sftp). Built into SSH, nothing to install, FileZilla/WinSCP or scp/rsync. ### Put something live - [Pointing your domain](https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain). A records, Cloudflare, or our free DNS Manager, and propagation expectations. - [Hosting a website](https://vpsdime.com/knowledgebase/getting-started/hosting-a-website). One-click apps vs nginx/Caddy, and free SSL with Let's Encrypt. - [Cloudflare best practices](https://vpsdime.com/knowledgebase/getting-started/cloudflare-best-practices). Locking the origin to Cloudflare's IPs, real visitor IPs in your logs, Full (strict) SSL, and caching that actually caches HTML. - [SSL/TLS certificates: a complete guide](https://vpsdime.com/knowledgebase/getting-started/ssl-certificates). Every free ACME CA with instructions, challenge types (and why not to keep port 80 open just for renewals), wildcards done right, cipher best practices, and CA-fallback resilience. - [One-click Applications explained](https://vpsdime.com/knowledgebase/getting-started/one-click-applications). Coolify, Traccar, Immich, Code Server, picked on the deploy form, credentials emailed. - [Modern open-source control panels](https://vpsdime.com/knowledgebase/getting-started/open-source-control-panels). Coolify, Dokploy, Dokku, HestiaCP, CloudPanel, and the security rule for all of them. - [Should I host my own email?](https://vpsdime.com/knowledgebase/getting-started/self-hosting-email) The honest decision: what self-hosting costs in upkeep, when it's worth it, and the hybrid. ### Moving an existing setup here - [Migrating from shared hosting to a VPS](https://vpsdime.com/knowledgebase/getting-started/migrating-to-a-vps). The email decision, the hosts-file test, and the overlap week. - [Migrating a VPS to a new server](https://vpsdime.com/knowledgebase/getting-started/migrating-a-vps). Server-to-server rsync, database dumps, two-pass cutover, and the new-IP checklist. ### Make it durable - [Securing your VPS](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps). SSH keys, closed ports, automatic updates, acting fast on CVEs, and what to do if compromised. - [Securing publicly accessible services](https://vpsdime.com/knowledgebase/getting-started/securing-public-services). Bind databases and caches to localhost, service by service, and the scanner-report quick wins. - [Backing up your VPS](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps). The 3-2-1 rule, database dumps, restic and friends, and how the Nightly Backups add-on fits in. ### When you need us - [How to raise a support ticket](https://vpsdime.com/knowledgebase/getting-started/raising-a-support-ticket). The first-reply-fix recipe, and why you paste what the server said, never what the chatbot said. Ordering a VPS or adding another one is covered separately: [how to order](https://vpsdime.com/knowledgebase/presales/how-to-order-a-vps) and [deploying a new VPS](https://vpsdime.com/knowledgebase/client-area/deploy/deploying-a-new-vps). --- Still need a person? You can [open a support ticket](https://vpsdime.com/open-ticket/) any time. --- ## Your first 30 minutes on a new VPS URL: https://vpsdime.com/knowledgebase/getting-started/first-30-minutes Last reviewed: 2026-07-02 Summary: The setup checklist between "provisioned" and "ready to build", update everything, create a sudo user, switch to SSH keys and lock password login, set hostname and timezone, add your own firewall layer, and turn on backups. Half of it can be done on the deploy or reinstall form itself; each step shows both the form way and the manual way. ### What this is The short list that turns a freshly provisioned VPS into a server you can trust, in roughly the order that pays off fastest. One thing to know before starting: **our [deploy](https://vpsdime.com/knowledgebase/client-area/deploy/deploying-a-new-vps) and [reinstall](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os) forms front-load several of these steps**, SSH keys, login mode, even creating your user, so if you set them there, some steps below are already done. Each step notes both routes. ### Minute 0: get in `ssh root@YOUR.VPS.IP` with the password shown at deploy (or your key, if you set one on the form). First-time prompts and fallbacks are in [Connecting to your VPS](https://vpsdime.com/knowledgebase/getting-started/connecting-to-your-vps). ### 1. Update everything The image is fresh, but the world moved since it was built: ``` apt update && apt upgrade -y # Debian/Ubuntu dnf upgrade -y # AlmaLinux/Rocky ``` Reboot if a kernel update landed (`reboot`, it takes seconds now and gets awkward later). Then put security patches on autopilot, `unattended-upgrades` / `dnf-automatic`, the two-minute version is in [Securing your VPS](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps). ### 2. Create your everyday user Working as root full-time means every typo runs with full power. Give yourself a normal account with sudo: - **The form way:** the deploy and reinstall forms have a **user** section, name, password, its own SSH key and login mode, and the account is created with the OS. - **The manual way:** ``` adduser deploy usermod -aG sudo deploy # Debian/Ubuntu (RHEL-family: -aG wheel) ``` Log in as that user for daily work; `sudo` when you need power, root when you truly need root. ### 3. Switch to SSH keys, then close the password door The single biggest security upgrade of the half hour: - **The form way:** at deploy or reinstall, pick a saved key (or paste one, or **import straight from GitHub/GitLab**) and set the login mode to **Login with SSH Key Only**, done before the server even exists, and it keeps you clear of the [port-22 brute-force firewall](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall) forever. - **The manual way:** add your public key to `~/.ssh/authorized_keys`, confirm key login works **in a second terminal**, then set `PasswordAuthentication no` in `/etc/ssh/sshd_config` and restart SSH. Generation and details: [Securing your VPS](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps), and save the key on the [SSH Keys page](https://vpsdime.com/knowledgebase/client-area/services/ssh-keys) so every future deploy is one click. Either way, keep the root password stored safely, the browser [Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) still uses it, and it's your no-lockout guarantee. ### 4. Name and clock Cosmetic, but done once and never again: ``` hostnamectl set-hostname myserver timedatectl set-timezone UTC ``` (The hostname may already be what you typed at deploy. UTC is the sane server default, logs from every machine line up, and cron doesn't jump around with DST; set a local zone only if your applications genuinely need it.) ### 5. Add your own firewall layer Your Linux VPS already sits behind our [managed edge firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall) for the riskiest app ports; add the general-purpose layer inside, **allow before enable**: ``` ufw allow 22/tcp ufw default deny incoming ufw enable ``` Open more only as you serve more (80/443 when the [website](https://vpsdime.com/knowledgebase/getting-started/hosting-a-website) arrives). The order matters, [here's why](https://vpsdime.com/knowledgebase/troubleshooting/allow-ssh-in-common-firewalls). ### 6. Turn on backups today The step everyone defers and someone always regrets: enable [Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/enable-nightly-backups) ($5/month, tonight becomes your first restore point, included free on Premium), and once there's real data, add the [off-site routine](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps). Doing this *before* the server matters is what makes every future mistake boring. ### Done. Where to next? That's a patched, keyed, firewalled, backed-up server, from here it branches: - Put something live: [host a website](https://vpsdime.com/knowledgebase/getting-started/hosting-a-website), or pick a [control panel](https://vpsdime.com/knowledgebase/getting-started/open-source-control-panels) if you want point-and-click. - Bringing an existing setup? [From shared hosting](https://vpsdime.com/knowledgebase/getting-started/migrating-to-a-vps) or [from another server](https://vpsdime.com/knowledgebase/getting-started/migrating-a-vps). - The deeper hardening pass when you're ready: [Securing your VPS](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps) and [Securing publicly accessible services](https://vpsdime.com/knowledgebase/getting-started/securing-public-services). And if any step above fought back, paste the exact error into an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management), this checklist is territory they know cold. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which step fought back, with the exact command and its output. ### Related questions - "What should I do first on a new VPS?" - "How do I create a sudo user on my VPS?" - "Should I disable root password login, and how?" - "What timezone should my server use?" - "How do I set up a firewall on a fresh VPS?" - "Can I set up my SSH key and user before the VPS is created?" --- ## Managing your VPSDime VPS, the control panel tour URL: https://vpsdime.com/knowledgebase/getting-started/managing-your-vpsdime-vps Last reviewed: 2026-07-02 Summary: One login covers everything, billing and server management in the same account, through a proprietary panel built in-house. The tour of what's self-service: power and Console, password resets, reinstalls and one-click apps, the firewall, upgrades and add-ons, graphs and the audit log, plus the account-wide tools (SSH keys, free DNS, backups, the troubleshooter), each linked to its full guide. ### What this is The map of what you can do **without opening a ticket**, which is nearly everything. Two things make our setup a little different from what you may be used to elsewhere: - **One login for everything.** Billing and server management live in the **same account**: the login that pays the invoice is the login that reboots the server, no separate panel URL, no second set of credentials to save and track, no "which password was the VPS control panel one" moments. (Which also means that one login is worth protecting well, [2FA is already on for every account](https://vpsdime.com/knowledgebase/client-area/account/two-factor-overview), and an authenticator app upgrades it.) - **The panel is proprietary, built in-house.** It isn't an off-the-shelf panel bolted next to a billing system, it's our own, built for our platform, which is why the pieces interlock: the deploy form sets your SSH keys and users, the troubleshooter can actually *fix* things, the backup panel restores without tickets. Everything below is a one-paragraph summary with the full guide linked. ### Home base: Manage VPS **My Services → Manage** opens [the Service Management page](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps), status, live usage bars, your IP and specs, billing facts, and the button strip: - **Power controls, from outside the OS**: soft restart/shutdown for normal use, hard reset/power-off for a frozen VPS, [the guide explains which to use when](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps), it matters. - **Console**, the out-of-band screen that works with no SSH, RDP, or functioning network. The tool for "I locked myself out", and the reason a firewall mistake is never fatal here. - **Password reset**, set a new root (or any user's) password on a *running* VPS; Admin password on Windows. - **Hostname** changes, and **Migrate to Another Location** (your IP changes with a move, so it's a deliberate decision). ### The tabs, each with its own guide - **[Network](https://vpsdime.com/knowledgebase/client-area/services/network)**: your IPv4/IPv6 addresses, netmask and gateway, and **self-service reverse DNS**, the thing mail senders need. - **[Firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall)** (Linux VPS): the managed edge firewall that blocks the riskiest app ports by default, with per-app whitelists. - **[Reinstall OS](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os)**: fresh distro or a [one-click application](https://vpsdime.com/knowledgebase/getting-started/one-click-applications), with SSH keys, login mode, and users configured on the form, done in minutes. - **Boot From ISO** ([Premium VPS](https://vpsdime.com/knowledgebase/client-area/services/boot-from-iso)): boot a rescue image to fix an unbootable system without wiping it. - **[Upgrade/Downgrade](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade)**: plan changes, live and instant on Linux VPS with the same IP. - **[Extra Features](https://vpsdime.com/knowledgebase/client-area/services/extra-features)**: add backups, vCPU, storage, traffic, or IPs one at a time, prorated. - **[Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs)**: CPU, memory, disk, and traffic over time, your first stop for "[is my plan the right size](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps)". - **[Tasks](https://vpsdime.com/knowledgebase/client-area/services/tasks)**: the audit log, every action ever taken on the VPS, when, whether it worked, and **who did it** (you, with the IP you acted from, or our staff). Underrated for troubleshooting: "did something change right before this broke?" - **[Cancellation](https://vpsdime.com/knowledgebase/client-area/services/cancellation)**: self-service, immediate or end-of-period, revocable until it runs. ### Account-wide tools - **[SSH Keys](https://vpsdime.com/knowledgebase/client-area/services/ssh-keys)**: store your public keys once (paste, or import from GitHub/GitLab), pick them at every deploy and reinstall. [The keys guide](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys) covers generating them. - **[DNS Manager](https://vpsdime.com/knowledgebase/client-area/services/dns)**: free DNS hosting, point your domain's nameservers at dns1/dns2.vpsdime.com and manage records in the panel. - **[Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview)** (with the add-on, included on Premium): self-service full restores, per-file recovery through a web file browser, and full disk-image downloads. - **[My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter)**: the automated troubleshooter that checks your VPS and **fixes** common causes on the spot, banned IPs, disabled password login, and escalates with diagnostics attached when it can't. Windows has [its own](https://vpsdime.com/knowledgebase/windows-vps/windows-troubleshooter). - **Billing, same login**: [invoices, payment methods, auto-renewals, credit, billing cycles](https://vpsdime.com/knowledgebase/client-area/billing), plus prepaying months ahead, picking your billing day, and syncing several services onto one renewal date, all next to the server controls rather than in some other portal. ### What isn't in the panel The inside of your server, that's [yours over SSH or RDP](https://vpsdime.com/knowledgebase/getting-started/connecting-to-your-vps), and this knowledge base plus [an AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) covers that side. The split is the [self-managed deal](https://vpsdime.com/knowledgebase/support-coverage/what-support-covers): the panel gives you full control of the machine's lifecycle; the OS and software on it are your domain. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which panel feature you were using and what happened (a screenshot helps if it looks odd). ### Related questions - "What can I do myself in the VPSDime panel?" - "Is there a separate login for the VPS control panel?" - "How do I reboot / reinstall / resize my VPS from the panel?" - "Where do I see what actions were taken on my VPS?" - "What control panel does VPSDime use?" --- ## Connecting to your VPS (SSH) URL: https://vpsdime.com/knowledgebase/getting-started/connecting-to-your-vps Last reviewed: 2026-07-02 Summary: How to make your first connection to a Linux or Premium VPS over SSH, the username is root, where your password comes from, connecting from Windows, macOS, or Linux, the host-key prompt, the Console fallback, and why Remote Desktop doesn't apply to Linux. ### What this is Your first connection to a **Linux VPS or Premium VPS**. You manage these over **SSH**, a secure remote terminal. A **Windows VPS** is different, you connect to a full desktop over Remote Desktop instead; see [how to connect using RDP](https://vpsdime.com/knowledgebase/windows-vps/connect-rdp). ### Your credentials - **Username:** `root`. That's the administrator account on your VPS, and the default login for every fresh deployment. - **Password:** generated when you deploy and shown once with a Copy button (it's also in your welcome email). Change it after your first login with the `passwd` command. - **Lost it?** Reset the root password any time from [Manage VPS](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps). ### Connect Windows 10+, macOS, and Linux all have SSH built into their terminal (PowerShell or Terminal on Windows). One command: ``` ssh root@YOUR.VPS.IP ``` Your VPS's IP is on its [Manage VPS](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) page and in your welcome email. Two first-time things to expect: - **A host-key prompt** ("The authenticity of host ... can't be established"). This is normal on the first connection to any new server: type `yes`. If you ever see a loud *"REMOTE HOST IDENTIFICATION HAS CHANGED"* warning later, that's usually because you reinstalled the VPS (new OS, new key), remove the old line with `ssh-keygen -R YOUR.VPS.IP` and connect again ([the full story on that warning](https://vpsdime.com/knowledgebase/troubleshooting/host-identification-changed)). - **The password doesn't show as you type.** No dots, no stars, nothing. That's how terminals do passwords; type it and press Enter. Prefer a graphical client on Windows? **PuTTY** still works fine, put the IP in Host Name and open, but the built-in `ssh` command has been standard on Windows for years and is one less thing to install. ### Two things worth doing next - **Set up SSH keys.** Passwordless, far more secure, and it makes the next point moot. Save a key on the [SSH Keys](https://vpsdime.com/knowledgebase/client-area/services/ssh-keys) page for future deploys, and see [Securing your VPS](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps) for the full setup. - **Don't brute-force yourself.** Our network [bans IPs](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall) that rack up failed password attempts on port 22. If you're retrying passwords from memory, three wrong guesses is the time to reset the password from the panel instead. ### If SSH won't connect at all The **[Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps)** in your client area connects straight to your VPS's screen in the browser, no SSH, no networking needed. It always works, even when the firewall or network config on the VPS is broken, which makes it the tool for "I locked myself out." For a guided diagnosis of any connection problem, run [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter). ### Linux and Remote Desktop Microsoft's Remote Desktop (RDP) does not connect to a Linux VPS. Linux servers don't come with a desktop at all, everything happens in the terminal, which is exactly what makes a VPS light and fast. - If you want a **graphical desktop on Linux**, it's possible and self-setup: install a desktop environment (XFCE is the light classic) plus xRDP, VNC, or X2Go, the full guide with the options compared is [Installing a desktop environment on your VPS](https://vpsdime.com/knowledgebase/technical-questions/install-desktop-environment). - If what you actually want is a **point-and-click Windows machine**, that's our [Windows VPS](https://vpsdime.com/knowledgebase/presales/windows-vps) product, a full Windows Server desktop over RDP with the license included. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what happens when you try to connect (timeout, refused, wrong password), copied exactly. ### Related questions - "How do I connect to my VPS?" - "What is my SSH username and password?" - "Why doesn't my password show when I type it?" - "What is the host key / authenticity prompt?" - "Can I use Remote Desktop with a Linux VPS?" - "How do I get a desktop (GUI) on my Linux VPS?" - "I locked myself out of SSH, what now?" --- ## Terminal basics for your first VPS URL: https://vpsdime.com/knowledgebase/getting-started/terminal-basics Last reviewed: 2026-07-02 Summary: Enough command line to operate a server confidently, moving around, tab completion (the one habit that changes everything), reading and editing files with less and nano, driving services with systemctl, reading logs with journalctl and tail, sudo vs root, escaping vim, and the safety habits that prevent self-inflicted outages. ### What this is Enough shell to run your server, not a Linux course. Every guide in this knowledge base hands you commands; this page is what makes them feel routine instead of risky. Twenty minutes here pays for itself the first week. ### Orientation You're [connected](https://vpsdime.com/knowledgebase/getting-started/connecting-to-your-vps) and staring at a prompt like `root@myserver:~#`, that's *who* you are, *which machine*, and *where* (`~` is your home directory; `#` means root, `$` means a normal user). - `pwd` prints where you are; `ls` lists what's here (`ls -la` shows everything, with permissions and owners, output you'll learn to read in the [403 guide](https://vpsdime.com/knowledgebase/troubleshooting/403-forbidden)). - `cd /var/www` moves; `cd ..` goes up one; plain `cd` goes home. - **Tab completion is the single habit to build first**: type a few characters of any command, path, or filename and hit **Tab**, the shell finishes it or shows the options. It's faster than typing *and* it can't typo a path. If Tab won't complete it, the thing probably doesn't exist, which is diagnostic gold. - **Up-arrow** replays previous commands (edit and re-run); `Ctrl+R` searches your history; `Ctrl+C` cancels the current command; `Ctrl+L` clears the screen. ### Reading and editing files - `cat file` prints a short file; `less file` pages through a long one (arrows/PageDown to move, `/word` to search, **`q` to quit**, the keystroke every beginner needs told once). - `nano file` edits: type normally, **Ctrl+O** then Enter saves, **Ctrl+X** exits. The shortcut legend is right there at the bottom of the screen. Every edit-this-config instruction in this KB assumes nano. - Land in **vim** by accident (some systems default to it)? Press `Esc`, type `:q!`, Enter, you're out, nothing saved. Now you know the joke. ### Driving services The single most useful command family on a server, systemd runs everything: ``` systemctl status nginx # is it running, and its last log lines systemctl restart nginx # stop + start systemctl enable nginx # start at boot (started ≠ enabled!) ``` That third distinction has [its own cautionary tale](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot). And when a service won't start, its own words are in the journal: ``` journalctl -u nginx -n 50 # last 50 log lines for that service ``` ### Reading logs - `tail -20 /var/log/nginx/error.log` shows the end of a log; `tail -f` **follows** it live, start it, reproduce your problem in another window, and watch the error appear in real time. - `grep something file` finds lines containing it; `grep -r something /etc/nginx/` searches a whole directory. Half of troubleshooting is these two commands pointed at the right file. ### Power: sudo vs root Day-to-day, work as [your normal user](https://vpsdime.com/knowledgebase/getting-started/first-30-minutes) and prefix commands that need power with `sudo`. The prompt asking for *your* password (not root's) is normal. Full root shells are for when you genuinely need them, mistakes as root have no seatbelt. ### Safety habits (learned here, not the hard way) - **`rm` has no undo and no trash.** Before any `rm` with a wildcard, run the same pattern with `ls` first and look at what matched, [recovery after the fact is grim](https://vpsdime.com/knowledgebase/troubleshooting/recover-deleted-files). - **Never `chmod 777`** to "fix permissions", [here's what to do instead](https://vpsdime.com/knowledgebase/troubleshooting/403-forbidden). - **Editing SSH or firewall config? Keep your current session open** and test from a second terminal, the [lockout guide](https://vpsdime.com/knowledgebase/troubleshooting/restore-ssh-access) exists because people don't. - **Copy exact error messages**, into a search engine, into [an AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) (genuinely excellent at exactly this), or into a ticket. "It says permission denied for /var/www/html/index.php" is solvable; "it doesn't work" is not. - `man command` or `command --help` when you wonder what a flag does, reading two lines of manual beats pasting mystery commands. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the command you ran and its exact output. ### Related questions - "What basic commands do I need to manage a VPS?" - "How do I edit a file on my VPS?" - "How do I quit less or vim?" - "How do I check if a service is running and see its logs?" - "What's the difference between sudo and root?" - "How do I safely delete files in the terminal?" --- ## Using Claude Code on your VPS, safely URL: https://vpsdime.com/knowledgebase/getting-started/claude-code-on-vps Last reviewed: 2026-07-02 Summary: Installing Claude Code (Anthropic's terminal AI agent) on a VPS and letting it help run the server, what it's genuinely good at, and the control rules that matter on a live system: never skip permission prompts, review and understand every command before approving, run it as your everyday user, and give it standing safety orders in CLAUDE.md. ### What this is [Claude Code](https://claude.com/claude-code) is Anthropic's AI agent that lives in a terminal: you tell it what you want in plain language, and it proposes and runs the commands, reads the output, and iterates, with **you approving each action**. On a VPS that makes it something like a junior sysadmin who never sleeps: excellent at diagnosis and legwork, and in need of exactly the supervision the title promises. This page covers both halves, the setup and the leash. The general "AI as server helper" picture (chatbots included) is in [our support scope guide](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management); this is the hands-on version for the agent tier. For the *always-on* kind of agent, OpenClaw, Hermes, and the like, that runs as a background service with its own web panel, see [Running a self-hosted AI agent](https://vpsdime.com/knowledgebase/getting-started/self-hosted-ai-agents) (and heed its warning about never exposing the panel). ### Installing it on the VPS Run it as your [everyday sudo user, not root](https://vpsdime.com/knowledgebase/getting-started/first-30-minutes), that's the first safety decision, made before anything else (an approved command then runs with your user's power, and escalates through `sudo` only when genuinely needed and visible): ``` curl -fsSL https://claude.ai/install.sh | bash ``` (Alternative, if you prefer npm and have Node installed: `npm install -g @anthropic-ai/claude-code`.) Then start it with `claude` and sign in when prompted, you'll need an Anthropic account (a paid plan, or an API key). Two practical notes for server use: launch it inside **tmux** so a dropped SSH connection doesn't kill a session mid-task, and start it in a sensible working directory (your project or `/etc` service configs it should see), it works relative to where you launch it. ### What it's genuinely good at on a server - **Diagnosis without the copy-paste loop**: ask "why is the site slow?" and it runs the [checks](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps) itself, `htop`, `ss`, `df`, the logs, and interprets the results in context. - **Configuration legwork**: writing an nginx vhost, a [systemd unit or timer](https://vpsdime.com/knowledgebase/technical-questions/systemd-timers), a [restic backup script](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps), a fail2ban jail, and explaining each line if you ask. - **Walking a multi-step job**: a [migration](https://vpsdime.com/knowledgebase/getting-started/migrating-a-vps), a [certificate mess](https://vpsdime.com/knowledgebase/troubleshooting/ssl-certificate-errors), a permissions cleanup, work where the value is doing twenty small steps in the right order without losing the thread. ### The control rules This is the part that matters. An agent on a live server is power steering, not autopilot: 1. **Never give it unlimited power.** Claude Code asks permission before each action by default, that prompt is the entire safety model, so **keep it**. It has a flag to skip permissions entirely; that flag has no business on a live server, full stop. 2. **Review every command before approving, and understand it.** If you don't recognize a command or a flag, ask it to **explain what it does and what could go wrong** before you approve, it answers honestly and in detail, and the thirty seconds is the whole discipline. 3. **Be doubly suspicious of anything destructive**: `rm`, `dd`, `mkfs`, `DROP`, `truncate`, package removals, anything touching `/var/lib/mysql` or other data directories, or edits to SSH and firewall config (the [lockout classics](https://vpsdime.com/knowledgebase/troubleshooting/allow-ssh-in-common-firewalls)). Approve those only when you'd have been willing to type them yourself. 4. **[Backups](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps) current before big sessions.** The same rule as for any tool with write access, agents make mistakes confidently, and a restore point converts a disaster into an anecdote. 5. **Stay present.** One task per session, watch it work, and don't leave it grinding unattended on a machine that matters. 6. **Mind the secrets.** It reads files to do its job, and config files contain credentials; that's usually fine, but it's a thing to be conscious of, not surprised by. ### Give it standing orders: CLAUDE.md Claude Code reads a `CLAUDE.md` file in the working directory (and `~/.claude/CLAUDE.md` globally) as persistent instructions, so write the safety rules down **once** and every future session starts with them. Run `/init` inside a session to scaffold it, then make sure it contains something like: ```markdown # Server rules - This is a LIVE PRODUCTION server. Real users depend on it. - NEVER run destructive commands (rm, dd, mkfs, DROP/TRUNCATE, package removal, overwriting configs) without explicitly asking first and receiving my confirmation, even if the task seems to require it. - Explain what a command does and its risks BEFORE proposing to run it. - Prefer read-only diagnostics first; change things only after diagnosis. - Never modify SSH or firewall configuration without warning me that lockout is possible and telling me the recovery path. - Never touch database data directories directly; databases are dumped, not file-copied. - Before any risky change, check that a current backup exists and say so. ``` Adapt it to your setup (name your critical paths and services), the point is that "this machine is live and you ask before breaking things" is written policy, not something you re-explain every session. ### When not to use it Two situations where the right tool is this knowledge base and your own hands: a **database that won't start** (the [safe order of operations](https://vpsdime.com/knowledgebase/troubleshooting/mysql-wont-start) forbids experimentation, and an eager agent loves to experiment), and a **[compromised server](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery)**, where the box itself can't be trusted, agent included, and the answer is the rebuild routine, not cleverness. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - where the setup stops (install, sign-in, or the first session), with the exact message. ### Related questions - "Can I install Claude Code on my VPS?" - "Is it safe to let an AI agent manage my server?" - "How do I stop an AI agent from running dangerous commands?" - "What should I put in CLAUDE.md for a production server?" - "Should the agent run as root?" - "What is Claude Code good at on a Linux server?" --- ## Running a self-hosted AI agent (OpenClaw, Hermes) on your VPS URL: https://vpsdime.com/knowledgebase/getting-started/self-hosted-ai-agents Last reviewed: 2026-07-04 Summary: A VPS is a natural home for a persistent, self-hosted AI agent like OpenClaw or Hermes Agent, an always-on assistant with its own memory and a web control panel, reachable from Telegram, Discord, and the like. This covers what they are, honest resource requirements (the agent itself is light; a local model is the RAM-heavy part), how to install them as a non-root user, and the one thing that has compromised tens of thousands of these deployments: exposing the control panel to the internet. Keep it bound to localhost and reach it over an SSH tunnel. ### What this is A new class of tool arrived in 2026: the **persistent, self-hosted AI agent**. Unlike a chatbot you visit, or [Claude Code](https://vpsdime.com/knowledgebase/getting-started/claude-code-on-vps) which lives in your terminal for the length of a session, these run as an **always-on background service**. They keep their own memory across sessions, write and reuse their own "skills", and you reach them through a **web control panel** and messaging apps (Telegram, Discord, Slack, and others). A VPS is the natural home for one, it's online 24/7, it's yours, and your data stays on it rather than on someone else's cloud. The two most prominent open-source examples as of mid-2026: - **OpenClaw** ([openclaw/openclaw](https://github.com/openclaw/openclaw), previously known as Clawdbot and Moltbot). A personal assistant with a browser control UI and a broad plugin ecosystem. - **Hermes Agent** ([Nous Research](https://github.com/nousresearch/hermes-agent)). Built around persistent memory and self-authored skills that follow an open `agentskills.io` standard, with a single gateway process fronting the messaging integrations. Both are open source and free to run; you supply the intelligence behind them (see below). This guide is product-neutral, the setup shape and, crucially, the security posture are the same for these and the agents that will follow them. ### Before anything else: the security reality This is the most important section on the page, so it comes first. These agents run a **control panel as a network service** (OpenClaw's, for instance, listens on port **18789**), and that panel can do anything the agent can do: run commands, spend your API credits, read the credentials it has stored. In 2026, security firms found **tens of thousands of these control panels exposed directly to the public internet** with authentication left off, many of them trivially takeoverable, and multiple remote-code-execution vulnerabilities have been published against exposed instances. Infostealer malware now specifically hunts for these agents' files, because their configuration, memory, and chat logs routinely store **API keys and passwords in plain text**. None of that is a reason to avoid them. It's a reason to run one correctly, which is genuinely easy: - **Keep the control panel bound to `localhost` (`127.0.0.1`).** This is the default on current versions, don't change it to `0.0.0.0` (all interfaces) for convenience. A panel bound to localhost cannot be reached from the internet at all, which removes essentially the entire attack surface above. - **Reach it over an SSH tunnel, not an open port.** To use the panel from your laptop, forward it through SSH: `ssh -L 18789:localhost:18789 you@YOUR.VPS.IP`, then open `http://localhost:18789` in your **local** browser. Traffic rides your existing encrypted SSH connection; nothing new is exposed. This is the recommended pattern and it needs no firewall changes. - **Never open the panel's port in a firewall or publish it.** If you find yourself running `ufw allow 18789` or putting the panel behind a bare public IP, stop, that's the exact mistake behind the mass compromises. If you genuinely need browserless remote access for a team, put it behind a reverse proxy with **HTTPS and a strong gateway token** (`openssl rand -hex 64`), never the raw port. - **Treat the machine's secrets as exposed if the agent is.** Because keys are stored in cleartext, an agent compromise is a credential compromise. Use scoped, revocable API keys, and rotate them if anything looks off. The rest of this page assumes you're following the localhost-plus-SSH-tunnel pattern. ### Resource requirements: two very different answers The honest answer depends entirely on **where the model runs**, and this is where people over- or under-buy: - **The agent software itself is light.** It's a Node.js process (these need **Node 22 LTS or newer**) plus its memory store. Figure a **2-core, 4 GB** VPS with room for the OS, comfortable on any current entry Linux plan, and perhaps **50 to 100 GB of disk** if it accumulates a lot of files or logs. - **If you point it at a cloud model API** (Anthropic, OpenAI, OpenRouter, and similar), that's all you need. The heavy lifting happens on the provider's servers; your VPS just orchestrates. This is what the projects themselves recommend starting with, and it's the right default. - **If you run the model locally** (via [Ollama](https://vpsdime.com/knowledgebase/getting-started/one-click-applications) or similar, for zero per-token cost or full privacy), the model's RAM becomes the dominant requirement, and it's large. As a rule of thumb, with the common Q4 quantization: a **7-8B** model (Qwen, Mistral Small, and the like) wants **~8 GB RAM** all to itself; a **30B+** model wants **16 GB and up**. A CPU-only VPS runs these, just slowly; responsiveness improves dramatically with more RAM and, if available, a GPU. Size the plan for the model, not the agent. In short: **cloud API → an entry plan is plenty. Local model → buy RAM for the model.** Don't provision a large VPS "for the AI" if the AI is actually running in Anthropic's datacenter. ### Installing (as a non-root user) The same safety rule as [Claude Code](https://vpsdime.com/knowledgebase/getting-started/claude-code-on-vps) applies: run the agent as your **[everyday sudo user, not root](https://vpsdime.com/knowledgebase/getting-started/first-30-minutes)**, so a mistake or a compromise is contained to that user rather than owning the box. Both projects install with a one-line script that fetches Node and their dependencies: ``` # OpenClaw curl -fsSL https://openclaw.ai/install.sh | bash # Hermes Agent curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash ``` A note on `curl … | bash`: piping a script straight into a shell means running whatever that URL serves, sight unseen. It's the projects' official method, but the careful habit is to fetch the script first, read it, then run it (`curl -fsSL -o install.sh; less install.sh; bash install.sh`), especially on a server that holds anything you care about. (OpenClaw also publishes an npm package and Docker images if you prefer those.) After install, start the gateway/agent per the project's docs, connect your **model provider** (API key or local Ollama endpoint), and open the control panel **through your SSH tunnel** to finish setup, linking messaging accounts, granting the permissions you actually want it to have, and no more. ### Keeping it healthy on a server - **Run it under a process manager** so it survives reboots and dropped sessions, a **systemd** service is the clean way; `tmux` works for a quick trial. Don't leave it tied to an interactive SSH session that dies when you disconnect. - **Give it least privilege.** Grant the agent only the integrations and permissions it needs for what you actually use it for. An agent with your email, your shell, and your cloud keys is a large blast radius if it misbehaves or is breached. - **Watch the resources.** An agent looping on a task, or a local model, can saturate CPU or RAM; the [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) tab shows it, and a runaway local model is the classic cause of a small plan going unresponsive. - **Keep it updated.** These projects move fast and patch security issues often; update on the project's cadence, the published vulnerabilities above were all against out-of-date, exposed instances. ### Still need help? Running these is self-managed software, so the specifics live in each project's own documentation, but if the **VPS itself** is unreachable or misbehaving, [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what you installed and how you're reaching its panel (SSH tunnel, or, we hope not, an open port), - what the [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) show if it's a resource problem. ### Related questions - "Can I run OpenClaw or Hermes Agent on my VPS?" - "How much RAM do I need for a self-hosted AI agent?" - "How do I access the AI agent's control panel safely?" - "Is it safe to expose port 18789 to the internet?" (No.) - "Do I need a big VPS to run an AI agent?" - "Should I run the AI model locally or use an API?" - "How do I keep my AI agent's API keys from being stolen?" --- ## Setting up SSH keys, properly, on any OS URL: https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys Last reviewed: 2026-07-04 Summary: Generate an ed25519 key pair with the same command on Windows, macOS, and Linux, understand which file stays secret, get the key onto your VPS (the saved-keys page and GitHub import at deploy, or ssh-copy-id on a running server), then the agent, the ~/.ssh/config quality-of-life file, multiple devices, and the classic failure modes. ### What this is The full path from "no key" to "logging in everywhere with keys": generate, deploy, and the quality-of-life pieces most guides skip. Why bother is covered elsewhere in one line, no password to guess, brute force pointless, [no more banned IPs](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall), this page is the how. One concept before the commands: a key is a **pair of files**. The **private key** stays on your device, is never uploaded anywhere, and is the thing to protect. The **public key** (the `.pub` file) is what you hand out, to your VPS, to GitHub, to anyone, it's called public because it is. ### Generate the pair (same command everywhere) Windows 10/11 (PowerShell), macOS (Terminal), and Linux all ship the same OpenSSH tooling now, no PuTTYgen required: ``` ssh-keygen -t ed25519 ``` - Accept the default location (`~/.ssh/id_ed25519` and `id_ed25519.pub`; on Windows, `C:\Users\you\.ssh\`). - **Set a passphrase.** It encrypts the private key on disk, so a stolen laptop doesn't equal stolen server access, and the agent (below) means you type it rarely. - `ed25519` is the modern default: small, fast, strong. (Only fall back to `-t rsa -b 4096` for ancient systems that don't speak it.) Print the public half whenever you need to paste it: `cat ~/.ssh/id_ed25519.pub`, one line starting `ssh-ed25519 ...`. ### Get it onto your VPS - **Before the VPS exists (the best way):** save the public key on the [SSH Keys page](https://vpsdime.com/knowledgebase/client-area/services/ssh-keys), or import it **straight from your GitHub/GitLab account**, then select it on the [deploy](https://vpsdime.com/knowledgebase/client-area/deploy/deploying-a-new-vps) or [reinstall](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os) form. The server is born trusting your key, and with **key-only login mode** there was never a password to attack. - **On a running server:** from your machine, ``` ssh-copy-id root@YOUR.VPS.IP ``` does everything (appends the key to `~/.ssh/authorized_keys` with correct permissions). Doing it by hand instead: append the `.pub` line to `~/.ssh/authorized_keys` on the server, and make sure permissions are strict, `700` on `~/.ssh`, `600` on the file, SSH refuses keys in sloppy directories. The same strictness extends one level up: a **home directory writable by group or others** also gets the key silently ignored (SSH keeps asking for a password with no error), `chmod 755 ~` fixes it, and `sshd`'s log names the rejected path if you're unsure which level is at fault. Then test (`ssh root@YOUR.VPS.IP` should log in without a password) and, once it works, [turn off password login](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps). ### The agent: type the passphrase once The ssh-agent holds your unlocked key for the session, so the passphrase costs you one entry, not one per connection: ``` ssh-add ``` macOS remembers across reboots via the keychain; on Windows, enable the **OpenSSH Authentication Agent** service once (Services app, set to Automatic) and `ssh-add` works the same way. ### The `~/.ssh/config` file: stop typing IPs The most underrated file in the toolchain, define your servers once: ``` Host web HostName 203.0.113.5 User deploy IdentityFile ~/.ssh/id_ed25519 Port 22 ``` From then on, `ssh web`, and every tool that speaks SSH (`scp`, `rsync`, [SFTP clients](https://vpsdime.com/knowledgebase/getting-started/uploading-files-sftp), IDEs) understands the alias too. Changed your [SSH port](https://vpsdime.com/knowledgebase/technical-questions/change-ssh-port)? Update it here once instead of in every command. ### Multiple devices, revocation, and clients - **One key per device** (laptop, desktop, work machine), not one key copied everywhere. Add each public key to the server; `authorized_keys` happily holds many lines. - **Revoking a device** is deleting its line from `authorized_keys`. That granularity is the payoff of per-device keys. - **FileZilla and WinSCP** use the same key for [SFTP](https://vpsdime.com/knowledgebase/getting-started/uploading-files-sftp), point them at the key file. WinSCP and PuTTY historically wanted their own `.ppk` format; both convert OpenSSH keys, though if you're starting fresh, the built-in `ssh` client makes PuTTY optional entirely. - **New computer, or reinstalling your OS? The key doesn't come along by itself.** Your **private key exists only on your machine**, a fresh computer or a wiped OS has no idea about it, and the server can't help, it only ever saw the public half. Before you retire the old machine, either **copy the key pair across** (both files, `id_ed25519` and `id_ed25519.pub`, into the new machine's `~/.ssh/`, then `chmod 600 ~/.ssh/id_ed25519` on Linux/macOS), or, cleaner, **generate a new pair on the new machine** and add its public key to the server while the old machine still works. The classic mistake is wiping the old computer first and discovering the only key that could log you in went with it, at that point you're recovering via the [Console or SSH-access guide](https://vpsdime.com/knowledgebase/troubleshooting/restore-ssh-access) instead of a two-minute copy. ### When it doesn't work - **Still asked for a password:** the server didn't accept the key, wrong username (the key went to `root` but you're connecting as `deploy`?), key not in that user's `authorized_keys`, or permissions too loose (check `ls -la ~/.ssh` on the server). `ssh -v web` prints which keys were offered and what the server said, and that verbose output is dense, pasting it whole into an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) gets it decoded line by line. - **"WARNING: UNPROTECTED PRIVATE KEY FILE"** on your machine: your private key's permissions are too open, `chmod 600 ~/.ssh/id_ed25519`. - **Locked out after enabling key-only:** the [Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) doesn't use SSH, get in there and fix `authorized_keys` or re-enable password auth. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - your OS, and where it fails (generating, deploying, or logging in), - the `ssh -v` output for a failing login. ### Related questions - "How do I generate an SSH key on Windows / Mac / Linux?" - "What's the difference between the private and public key?" - "How do I add my SSH key to my VPS?" - "How do I use the same key with FileZilla or WinSCP?" - "How do I set up the ssh config file with an alias?" - "How do I remove a device's access to my server?" --- ## Uploading files to your VPS (SFTP) URL: https://vpsdime.com/knowledgebase/getting-started/uploading-files-sftp Last reviewed: 2026-07-02 Summary: How to move files to and from your VPS with SFTP, which is built into SSH with nothing to install, using FileZilla or WinSCP with your root credentials, why you shouldn't install plain FTP, and command-line options (scp, rsync). ### What this is Moving files between your computer and your VPS. The answer is **SFTP**, and the pleasant surprise is that it's **already set up**: SFTP is part of SSH, so if you can [connect over SSH](https://vpsdime.com/knowledgebase/getting-started/connecting-to-your-vps), you can transfer files right now with nothing to install on the server. ### Don't install FTP Skip plain FTP entirely. It sends your password and files unencrypted, it needs an extra server (attack surface) installed and configured, and SFTP does the same job securely with zero setup. Any client that "wants FTP details" almost certainly speaks SFTP too. ### With FileZilla (or WinSCP) [FileZilla](https://filezilla-project.org/) (Windows/macOS/Linux) and [WinSCP](https://winscp.net/) (Windows) both speak SFTP out of the box. In FileZilla's Quickconnect bar: 1. **Host:** `sftp://YOUR.VPS.IP` (the `sftp://` prefix picks the right protocol) 2. **Username:** `root` 3. **Password:** your root password 4. **Port:** 22 (or blank) 5. Click **Quickconnect**, and accept the host-key prompt the first time, same as SSH. You'll see your computer on the left, the VPS on the right; drag and drop either way. WinSCP is the same idea with an explorer-style layout. ### From the command line - Copy a file up: `scp mysite.zip root@YOUR.VPS.IP:/var/www/` - Sync a whole folder (repeatable, only transfers changes): `rsync -av ./site/ root@YOUR.VPS.IP:/var/www/mysite/` `rsync` is the tool to reach for when you'll be updating the same files repeatedly. ### Things worth knowing - **Where website files go:** by convention under `/var/www/`, but it's wherever your web server is configured to look. See [Hosting a website](https://vpsdime.com/knowledgebase/getting-started/hosting-a-website). - **Use keys here too.** SFTP authenticates exactly like SSH, so once you set up [SSH keys](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys), FileZilla and WinSCP can use the key instead of a password. - **A separate upload user** is a good idea when someone other than you needs file access: `adduser deploy`, give it ownership of the site folder, and hand out that login instead of root. - **Wrong passwords count.** Failed SFTP logins are failed SSH logins, so hammering a wrong password can get your IP [banned on port 22](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall), the same as SSH. ### Troubleshooting - **"Connection refused" or it tries port 21:** your client is in FTP mode. Make sure the host starts with `sftp://` or the protocol dropdown says SFTP, and the port is 22. - **Login works in SSH but not SFTP:** almost always a typo'd password or the client stuck in FTP mode; the credentials are identical by definition. - **Permission denied when uploading:** the folder belongs to another user (web files often belong to `www-data`). Upload as root, or change the folder's ownership to your upload user. Unsure of the right ownership? Tell an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) which user uploads and which folder it is, and it hands you the exact `chown`. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the client you're using (FileZilla, WinSCP, scp) and the exact error. ### Related questions - "How do I upload files to my VPS?" - "Do you support FTP?" - "How do I use FileZilla with my VPS?" - "What are my SFTP login details?" - "How do I copy files from the command line?" --- ## Pointing your domain at your VPS URL: https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain Last reviewed: 2026-07-02 Summary: How to connect a domain name to your VPS, create an A record at your registrar's DNS, use Cloudflare (which also hides your IP), or use VPSDime's free DNS Manager with nameservers dns1/dns2.vpsdime.com, plus www vs apex, propagation, and mail notes. ### What this is Making `yourdomain.com` reach your VPS. DNS does one job here: an **A record** maps your domain name to your VPS's IPv4 address (an **AAAA record** does the same for IPv6). Create that record wherever your domain's DNS is hosted, and you're pointed. Your VPS's IP is on its [Manage VPS](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) page and in your welcome email. ### Pick where your DNS lives (any of these works) **Option A: your registrar's DNS (simplest).** Nearly every registrar (Namecheap, GoDaddy, Porkbun, and the rest) includes free DNS. In its DNS or "manage records" panel, add: - **A record**, host `@` (the bare domain), value = your VPS IP - **A record**, host `www`, value = your VPS IP (or a CNAME from `www` to `@`) **Option B: Cloudflare (free, with extras).** Point your domain's nameservers at Cloudflare and manage records there. With the proxy enabled you also get your **VPS IP hidden** and attack traffic absorbed at their edge, exactly what we recommend if you [expect DDoS attention](https://vpsdime.com/knowledgebase/acceptable-use/ddos-policy), plus edge caching and certificates. Going this route? Do it properly, locked origin, real visitor IPs, working cache, with [Cloudflare best practices](https://vpsdime.com/knowledgebase/getting-started/cloudflare-best-practices). **Option C: our free DNS Manager.** We host DNS for your domains at no charge. Set your domain's nameservers to **dns1.vpsdime.com** and **dns2.vpsdime.com** at the registrar, then manage your records in the client area. Full guide: [DNS Manager](https://vpsdime.com/knowledgebase/client-area/services/dns). ### Propagation: give it a little time DNS changes aren't instant. New records typically work within minutes, but nameserver changes and edits to existing records can take a few hours (worst case a day or two) to reach every network, because resolvers cache answers. Check progress with `dig yourdomain.com` or an online checker like whatsmydns.net, and resist the urge to keep changing things while a previous change is still propagating. ### If you'll run mail Two extra records matter: an **MX record** pointing at your mail server's hostname, and **reverse DNS (PTR)** on your VPS IP matching that hostname, set rDNS yourself from the [Network](https://vpsdime.com/knowledgebase/client-area/services/network) tab. Also read the [email policy](https://vpsdime.com/knowledgebase/acceptable-use/email-policy) first, low-volume mail is fine, bulk is not. ### Troubleshooting - **The domain doesn't resolve at all.** The record hasn't propagated yet, or there's a typo in the IP, `dig +short yourdomain.com` should print your VPS IP. If you changed nameservers, confirm the change actually saved at the registrar. - **It resolves but no site loads.** DNS has done its job; the VPS isn't answering on port 80/443. That's a web-server matter, see [Hosting a website](https://vpsdime.com/knowledgebase/getting-started/hosting-a-website). - **`www` works but the bare domain doesn't (or the reverse).** You created one record and not the other, add the missing `@` or `www` record. Records refusing to make sense? Paste your `dig` output and what you *expected* into an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management), DNS confusion unravels fast with a second pair of eyes on the actual records. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the domain and the VPS (hostname or IP), - where the domain's DNS is hosted (registrar, Cloudflare, or our DNS Manager), - what `dig yourdomain.com` (or an online DNS checker) currently shows. ### Related questions - "How do I point my domain at my VPS?" - "What nameservers should I use?" - "Do you offer free DNS hosting?" - "How long does DNS take to propagate?" - "Why does www work but not my bare domain?" - "What records do I need for email?" --- ## Hosting a website on your VPS URL: https://vpsdime.com/knowledgebase/getting-started/hosting-a-website Last reviewed: 2026-07-02 Summary: From fresh VPS to a live site, choosing between a one-click app and a manual web server (nginx, Apache, or Caddy), pointing the domain, getting free SSL with Let's Encrypt certbot (or Caddy's automatic HTTPS), and what to check when the site won't load. ### What this is The path from a fresh VPS to a live website: pick how you'll serve it, point the domain, and put HTTPS on it. This is the map with the key commands, each step has endless deeper tutorials (and an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) walks through any of them patiently). ### Choose your route - **One-click Applications (least work).** When you deploy or [reinstall](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os), you can pick an Application instead of a bare OS ([how one-clicks work](https://vpsdime.com/knowledgebase/getting-started/one-click-applications)). **Coolify** in particular is a self-hosted platform that deploys sites and apps from a git repository and handles the web server and HTTPS for you, a lot of "how do I host X" ends right there. - **A classic web server (most control).** Install **nginx** or **Apache** on a clean OS, the standard for a reason, with certbot for SSL (below). Or use **Caddy**, which is friendlier: it configures HTTPS **automatically** with no extra steps. For a typical stack, e.g. WordPress, the recipe is web server + PHP + MariaDB, and every distro has a well-worn guide for exactly that. Update the OS first (`apt update && apt upgrade`), install the stack, and put your site files where the server expects them (conventionally under `/var/www/`, uploaded [over SFTP](https://vpsdime.com/knowledgebase/getting-started/uploading-files-sftp)). ### Point the domain Create the A record for your domain and give it a few minutes to propagate, see [Pointing your domain](https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain). Do this before requesting SSL: Let's Encrypt validates your domain by reaching your server, so DNS has to resolve first. ### Free SSL (HTTPS) with Let's Encrypt There's no reason to pay for a standard certificate, and no reason to skip HTTPS. With nginx or Apache, **certbot** does the whole thing: ``` apt install certbot python3-certbot-nginx # or python3-certbot-apache certbot --nginx -d example.com -d www.example.com ``` It obtains the certificate, rewires your config for HTTPS, and sets up **automatic renewal** (certificates last 90 days; the installed timer renews them, verify with `certbot renew --dry-run`). If a certificate error ever shows up later, expiry, name mismatch, Cloudflare mode trouble, the fixes are in [Fixing SSL certificate errors](https://vpsdime.com/knowledgebase/troubleshooting/ssl-certificate-errors). And when you outgrow the quick start, other free CAs, wildcard certificates, challenge types, cipher tuning, it's all in [the complete certificate guide](https://vpsdime.com/knowledgebase/getting-started/ssl-certificates). - **Using Caddy?** Nothing to do, it provisions and renews certificates automatically for the domains in its config. - **Behind Cloudflare's proxy?** Your visitors get HTTPS at the edge; still put a certificate on the VPS so the Cloudflare-to-origin leg is encrypted too (certbot as above works, or Cloudflare's origin certificates). The rest of a proper Cloudflare setup, locked origin, real visitor IPs, caching, is in [Cloudflare best practices](https://vpsdime.com/knowledgebase/getting-started/cloudflare-best-practices). ### When the site won't load Work down this list, it catches nearly every case: 1. **DNS:** does `dig +short yourdomain.com` print your VPS IP? If not, [DNS](https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain) first. 2. **Is the server listening?** On the VPS: `ss -tulnp | grep -E ':80|:443'`. No listener means the web server isn't running (`systemctl status nginx`) or your app is bound to `127.0.0.1` with no reverse proxy in front. 3. **Your own firewall:** if you set up ufw and forgot the web ports, `ufw allow 80` and `ufw allow 443`. (Our [managed firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall) never blocks web ports, so it's not the cause.) 4. **HTTPS works, HTTP doesn't (or vice versa):** one of the two server blocks/vhosts is missing or not redirecting, check the config certbot wrote. 5. **It worked until now and "nothing changed":** check the disk, a [full disk](https://vpsdime.com/knowledgebase/troubleshooting/disk-full) silently takes down databases and apps, and it's a ten-second `df -h` to rule out. 6. **Seeing a 502, 503, or 504 instead of nothing?** That's your web server reporting that the app behind it didn't answer, a different diagnosis with [its own guide](https://vpsdime.com/knowledgebase/troubleshooting/502-503-errors). ### After it's live Two habits make the site durable: [secure the VPS](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps) (the site's admin panel and database included) and [back it up](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps), a nightly database dump plus off-site copies, so a bad update or a compromise is an inconvenience rather than a disaster. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS and the domain, - what you're serving it with (nginx, Apache, Caddy, Coolify), - what exactly fails (DNS, connection, certificate error), with the message. ### Related questions - "How do I host a website on my VPS?" - "How do I get a free SSL certificate?" - "How do I set up HTTPS with Let's Encrypt?" - "Why isn't my website loading?" - "Can I run WordPress on my VPS?" - "Do your one-click apps include a website platform?" --- ## Cloudflare best practices for your VPS URL: https://vpsdime.com/knowledgebase/getting-started/cloudflare-best-practices Last reviewed: 2026-07-05 Summary: Putting Cloudflare's free tier in front of a website on your VPS, done properly. Moving the domain over and what must stay unproxied, locking your web ports to Cloudflare's IP ranges so the hidden origin is actually hidden, restoring real visitor IPs in nginx, Caddy, and Apache (and why fail2ban needs rethinking behind a proxy), the right SSL mode, and caching that actually caches, including why Cloudflare never caches HTML or PHP output by default and how to change that with origin headers and Cache Rules. Plus the free-tier security switches and the classic gotchas (521, 524, the 100 MB upload cap). ### What this is Putting Cloudflare in front of a website on your VPS, and configuring it so it actually delivers what people install it for. The free tier gives you a hidden origin IP, absorbed attack traffic, edge caching, and bot filtering, but only the DNS move happens automatically. The rest is configuration on your side, and a half-done setup quietly delivers none of it: the "hidden" IP still answers to anyone who scans it, logs fill with Cloudflare's IPs instead of your visitors', and the cache never caches the pages that cost you CPU. This guide is the whole path: the move, then the four practices that separate a proper setup from a decorative one. ### The mental model (read this first) With Cloudflare's proxy enabled, visitors never connect to your VPS. They connect to Cloudflare's edge, and Cloudflare connects to your VPS on their behalf: ``` visitor ⇄ Cloudflare edge ⇄ your VPS (the "origin") ``` In the DNS records, the **orange cloud** means proxied (the name resolves to Cloudflare's IPs, and your real IP stays out of public DNS) and the **grey cloud** means DNS only (the name resolves straight to your VPS, no Cloudflare involvement). One consequence drives half of this article: **the proxy only handles HTTP and HTTPS**. Mail, SSH, game servers, and anything else non-web must stay grey-clouded, or it silently stops working the moment you flip the switch. ### Moving a site to Cloudflare The DNS mechanics are covered in [Pointing your domain](https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain); the Cloudflare-specific care points: 1. **Add the site** in the Cloudflare dashboard. It scans and imports your existing DNS records, and this import is the step people regret rushing: it can miss records, subdomains especially. Compare the imported list against your current zone before going further. 2. **Change the nameservers** at your registrar to the pair Cloudflare assigns. Propagation takes minutes to hours. 3. **Orange-cloud the web records only** (`@` and `www`, plus any subdomain serving a website). Keep **grey**: the hostname your MX record points at, anything you SSH to by name, and any non-HTTP service. If in doubt, grey is the safe default, it just means "works exactly as before". One honest caveat about secrecy: proxying hides your IP **from now on**, but if the domain pointed straight at the VPS before, that old A record lives on in DNS-history databases attackers know to check. The orange cloud alone is not what hides your origin. The firewall is, which brings us to the first best practice. ### Best practice 1: allow only Cloudflare to reach your web ports If ports 80 and 443 answer to the whole internet, anyone who learns your IP (from DNS history, a mail header, a verbose error page) can bypass Cloudflare and hit your server directly, attacks, scrapers, and all. The fix is to accept web traffic **only from Cloudflare's published IP ranges** (https://www.cloudflare.com/ips/), in your VPS's own firewall. (Our [managed edge firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall) is a separate layer that never blocks web ports; this lockdown is yours to do, with ufw or nftables inside the VPS.) With ufw already set up the standard way (default deny incoming, SSH allowed): ``` for net in $(curl -s https://www.cloudflare.com/ips-v4) $(curl -s https://www.cloudflare.com/ips-v6); do ufw allow proto tcp from $net to any port 80,443 comment 'Cloudflare' done ``` Then make sure no broad rule undoes it: `ufw status numbered` should show 80/443 allowed *only* from the Cloudflare ranges, so delete any general `80/tcp ALLOW Anywhere` rule left over from before. Prove it worked from any machine that isn't your VPS: ``` curl -m 5 http://YOUR.VPS.IP/ ``` A timeout is success: the origin no longer talks to strangers. Three warnings that keep this safe: - **Never apply this thinking to SSH.** Cloudflare doesn't proxy SSH, so restricting port 22 to Cloudflare ranges locks *you* out, not attackers. Leave SSH rules alone, and keep your current session open while changing firewall rules (the [Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) is the recovery path if something goes wrong). - **The ranges change, rarely but really.** A stale list eventually surfaces as intermittent **521 errors** (Cloudflare says the origin refused the connection). If 521s appear months after setup, refreshing these rules is the first suspect: delete the Cloudflare-commented rules and re-run the loop. - **Mind the other leaks.** Sending email directly from the VPS stamps its IP into the mail headers, and hosting your mail on the same VPS makes the IP public by necessity (MX can't be proxied). If origin secrecy genuinely matters, send mail through a relay and keep mail off the web VPS; otherwise, know the trade-off you're accepting. ### Best practice 2: restore real visitor IPs Once traffic arrives via the proxy, your web server's peer is Cloudflare, so access logs, rate limits, and applications all see Cloudflare's IPs. The real visitor address travels in the `CF-Connecting-IP` request header, and each web server has a module to swap it in, trusting the header **only when the connection comes from Cloudflare's ranges**, so it can't be spoofed. **nginx** (the realip module is built in). Generate the config and reload: ``` (for net in $(curl -s https://www.cloudflare.com/ips-v4) $(curl -s https://www.cloudflare.com/ips-v6); do echo "set_real_ip_from $net;" done echo "real_ip_header CF-Connecting-IP;") > /etc/nginx/conf.d/cloudflare-realip.conf nginx -t && systemctl reload nginx ``` **Caddy**, in the global options at the top of your Caddyfile (paste the current ranges from cloudflare.com/ips in place of the two shown): ``` { servers { trusted_proxies static 173.245.48.0/20 103.21.244.0/22 # ...the rest of the ranges trusted_proxies_strict client_ip_headers CF-Connecting-IP } } ``` **Apache**, with mod_remoteip: ``` a2enmod remoteip ``` Then in a config file (one `RemoteIPTrustedProxy` line per Cloudflare range): ``` RemoteIPHeader CF-Connecting-IP RemoteIPTrustedProxy 173.245.48.0/20 RemoteIPTrustedProxy 103.21.244.0/22 # ...the rest of the ranges ``` One Apache extra: the stock combined log format logs `%h` (the connection peer, still Cloudflare), so switch it to `%a` in your `LogFormat` to log the restored client IP. Verify by tailing your access log: entries should show real, varied visitor IPs again, not addresses from the Cloudflare ranges. **The fail2ban consequence almost everyone misses:** behind Cloudflare, banning a visitor's IP in your local firewall does nothing, because the packets reaching your VPS come from Cloudflare's addresses, not the visitor's. Log-parsing still works (the log now shows real IPs), but the *enforcement* has to move to Cloudflare: fail2ban ships a `cloudflare` action that issues the ban through Cloudflare's API instead of iptables, and for simpler cases a WAF custom rule or an IP Access rule in the dashboard does the same by hand. ### Best practice 3: the SSL mode that can't loop Set **SSL/TLS → Full (strict)** and give the origin a valid certificate. That's the whole rule, and the full reasoning (why Flexible causes the infamous redirect loop, what each mode actually does) lives in [Fixing SSL certificate errors](https://vpsdime.com/knowledgebase/troubleshooting/ssl-certificate-errors). The practical notes for a VPS behind the proxy: - The lazy-and-correct option for an always-proxied site is a free **Cloudflare Origin CA certificate** (dashboard → SSL/TLS → Origin Server): valid up to 15 years, no renewals to babysit, trusted only by Cloudflare, which is exactly who connects to your origin now. - Your existing **certbot** certificate keeps working too: Let's Encrypt's HTTP validation passes through the proxy, so renewals survive the firewall lockdown from practice 1. If you want renewals that don't depend on HTTP at all, the `certbot-dns-cloudflare` plugin validates via a DNS record using a Cloudflare API token. - Error decoder while you're here: **526** means Full (strict) rejected the origin's certificate, **525** means the TLS handshake itself failed, both point at the origin certificate, not at Cloudflare. ### Best practice 4: make the cache actually cache Here's the disappointment this section prevents: you add Cloudflare, re-test your site, and the response times barely move. That's expected, because **by default Cloudflare only caches static files, decided by file extension** (images, CSS, JS, fonts, and similar). **HTML, and therefore everything your PHP or app server renders, is never cached by default.** Every page view still hits your VPS. The diagnostic tool is one header: ``` curl -sI https://example.com/ | grep -i cf-cache-status ``` - **DYNAMIC**: not eligible for caching (the default verdict for HTML), Cloudflare didn't even consider storing it. - **MISS**: eligible, fetched from origin this time, stored for next time. Run the same command again and a **HIT** confirms the cache works. - **BYPASS**: eligible by rule, but the response talked Cloudflare out of it, a `Set-Cookie`, or `Cache-Control: private` / `no-store` from the origin. #### Caching HTML, the right way Two pieces, and you want both: 1. **The origin declares cacheability.** Send proper `Cache-Control` headers from the pages you want cached. In PHP: ```php header('Cache-Control: public, max-age=0, s-maxage=600'); ``` `s-maxage` is for shared caches like Cloudflare (here, 10 minutes at the edge), `max-age` for browsers (here, always revalidate, so you keep control). A detail that explains a lot of mystery BYPASSes: the moment a PHP script calls `session_start()`, PHP emits `Cache-Control: no-store, no-cache` and a session cookie on its own, marking the page uncacheable. That's the correct default for pages with any per-user content, and it means you add caching headers only to pages that are genuinely the same for everyone. 2. **A Cache Rule makes HTML eligible.** Dashboard → Caching → **Cache Rules** (the free plan includes 10; these replaced the old Page Rules): create a rule matching your site or the paths you want cached, with **Eligible for cache**, leaving Edge TTL on "respect origin headers" so the `s-maxage` you set above stays in charge. #### The safety rule: never cache a logged-in page A cached page is served identically to everyone, so caching a personalized page is how one user sees another's account. Protect against it explicitly with a **bypass rule ordered before the caching rule**: match your application's session cookie and bypass cache. For WordPress, the expression `http.cookie contains "wordpress_logged_in"` (plus bypassing `/wp-admin`) is the standard pattern; other apps have an equivalent session cookie. Cloudflare's refusal to cache `Set-Cookie` responses is your backstop, but be deliberate anyway. #### Why this is worth the effort here specifically Every edge cache hit is a request your VPS never sees: no PHP executed, no bytes from your [monthly traffic allowance](https://vpsdime.com/knowledgebase/acceptable-use/bandwidth-overage). On a busy or bot-hammered site, good edge caching is the cheapest capacity upgrade available, it's free. Two operational habits: use **Development Mode** (dashboard, temporarily disables caching) while actively working on the site instead of fighting the cache, and purge by URL rather than "purge everything" when you can, so you don't dump the whole cache to fix one page. ### The free-tier switches worth flipping - **WAF custom rules** (5 on the free plan): put a **managed challenge** on your login endpoints, e.g. expression `http.request.uri.path eq "/wp-login.php"`, and block `/xmlrpc.php` outright if nothing uses it. Scanners fail the challenge; you barely notice it. - **Rate limiting**: the free plan includes basic rate limiting rules, useful for an API path or login endpoint that shouldn't see bursts. - **Bot Fight Mode and the AI-crawler controls**: one-toggle filtering for the scraper flood, covered properly in [Handling bot traffic](https://vpsdime.com/knowledgebase/troubleshooting/bot-traffic). - **Under Attack mode**: the panic switch that challenges every visitor. Flip it during an active attack, not permanently, and see [our DDoS policy](https://vpsdime.com/knowledgebase/acceptable-use/ddos-policy) for how attacks are handled on our side. ### Gotchas that generate tickets - **Uploads over 100 MB fail with a 413.** That's the free plan's request-body cap at the edge, not your server. Workarounds: chunked uploads in the app, or a grey-clouded subdomain (`uploads.example.com`) that skips the proxy for uploads, remembering that subdomain reveals the IP and needs its own certificate thinking. - **Long requests die at about two minutes with a 524.** Cloudflare's proxy read timeout (currently 120 seconds, not raisable on the free plan) cuts off slow admin exports, reports, and one-shot migration scripts. Move long work into background jobs, or run it on a grey-clouded hostname or via SSH. - **521 means "origin refused the connection"**: your web server is down, or the practice-1 firewall is blocking a Cloudflare range it should allow (the stale-list symptom). **522** is a connect timeout, usually the same family of causes. - **Old tutorials will mislead you.** Auto Minify no longer exists (removed August 2024), Page Rules gave way to Cache Rules, and Rocket Loader is a "test it, don't trust it" toggle that can break JavaScript-heavy sites. - **Non-standard ports aren't proxied.** Cloudflare handles 80/443 and a short list of alternates (8080, 8443, and a few others). A panel on port 3000 behind an orange-clouded name won't work; put it behind a reverse proxy on 443 or grey-cloud it. And if what you're protecting is a **game server or another non-web service**, Cloudflare's proxy isn't the tool at all, the options that are (game proxies, Spectrum, protected tunnels) are in [our DDoS policy](https://vpsdime.com/knowledgebase/acceptable-use/ddos-policy). ### The five-minute verification After setup, this list proves each layer did its job: 1. `dig +short example.com` returns Cloudflare IPs, not your VPS's. 2. `curl -m 5 http://YOUR.VPS.IP/` from another machine times out (origin locked). 3. `curl -sI https://example.com/style.css | grep -i cf-cache-status` shows MISS then HIT on the second run. 4. Your access log shows real visitor IPs (realip working). 5. SSL/TLS mode reads **Full (strict)** and the site loads with no redirect loop. 6. A test email to the domain arrives (MX still grey-clouded and working). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the domain and the VPS behind it, - what the browser or `curl -I` shows (any `cf-cache-status`, any 52x error code), - whether the record is orange- or grey-clouded, and your SSL/TLS mode. Bear in mind that Cloudflare's dashboard and plans are theirs, not ours, we can help with everything on the VPS side, and their [community](https://community.cloudflare.com/) covers the rest. ### Related questions - "How do I put my website behind Cloudflare?" - "How do I hide my VPS's IP address?" - "How do I allow only Cloudflare IPs to my web server?" - "Why do my logs show Cloudflare IPs instead of visitors?" - "How do I get real visitor IPs in nginx / Caddy / Apache behind Cloudflare?" - "Does fail2ban work behind Cloudflare?" - "Why isn't Cloudflare caching my HTML or PHP pages?" - "What does cf-cache-status DYNAMIC mean?" - "How do I cache HTML on Cloudflare's free plan?" - "Which Cloudflare SSL mode should I use?" - "Why do large uploads fail behind Cloudflare?" - "What causes Cloudflare error 521 or 524?" --- ## SSL/TLS certificates: a complete guide URL: https://vpsdime.com/knowledgebase/getting-started/ssl-certificates Last reviewed: 2026-07-05 Summary: Everything that matters about certificates for a self-managed server, in one place. Why free DV certificates are the correct choice, every free ACME certificate authority (Let's Encrypt, ZeroSSL, Google Trust Services, SSL.com, Actalis) with issuance instructions for each, the three challenge types and why HTTP-01 shouldn't be the reason port 80 stays open, wildcards explained properly (one label, no apex, DNS-01 only), TLS protocol and cipher best practices with SSL Labs as the report card, and the high-availability habits: CA fallback, rate limits, renewal monitoring, and CAA records. ### What this is A working understanding of TLS certificates for someone running their own server: what a certificate actually proves, where to get one for free (there are five current sources, not one), how validation challenges differ and which to prefer, what a wildcard does and doesn't cover, and the configuration and reliability practices that separate a setup that survives years from one that fails on day 91. The [hosting guide](https://vpsdime.com/knowledgebase/getting-started/hosting-a-website) has the two-command quick start; this page is the full picture behind it. ### What a certificate actually is A TLS certificate binds a **domain name to a public key**, signed by a **certificate authority (CA)** whose root certificate browsers and operating systems already trust. The standard web certificate is **domain-validated (DV)**: the CA verified, at issuance time, that whoever requested it controls the domain. That is the entire claim. Encryption strength has nothing to do with what you paid; a free DV certificate and a $200 one produce byte-identical TLS. Paid tiers exist, **OV** and **EV** embed a verified organization name, but browsers stopped displaying any special UI for them years ago, and for a typical website they buy nothing visible. The defensible reasons to pay for a certificate today are narrow compliance requirements, not security. **ACME** is the protocol that made all of this automatic: your client proves domain control (a "challenge"), the CA issues, and the same client renews on a timer without you. Every CA and tool on this page speaks it. ### Why automation is the whole game Free certificates are short-lived on purpose: **90 days** is the norm, and the industry has formally committed to much shorter. Under the CA/Browser Forum's adopted schedule, the maximum certificate lifetime drops to **200 days in 2026, 100 days in 2027, and 47 days by 2029**, for every CA, paid or free. The era of installing a certificate by hand once a year is ending by design. The practical doctrine follows directly: a certificate setup is correct only if it **renews unattended and you've watched it do so** (every client has a dry-run or staging mode for exactly this). Anything manual is a scheduled future outage. ### The free ACME certificate authorities All of these issue browser-trusted DV certificates over standard ACME, so the same client works with any of them. The differences are registration friction and small policy details. One entry for the obituary column first: **Buypass**, long the standard "Let's Encrypt alternative" in tutorials, stopped issuing in October 2025 and shut down its ACME service in April 2026. If a guide recommends Buypass Go SSL, it's out of date. #### Let's Encrypt The default, and its structural advantage is real: **no account, no sign-up, no EAB credentials**, every ACME client works with it out of the box, it runs a **staging environment** for safe testing, and it has the longest operational track record. Certificates are 90 days, wildcards supported via DNS-01. ``` # certbot (installs the cert into nginx and sets up renewal) certbot --nginx -d example.com -d www.example.com # acme.sh acme.sh --issue --server letsencrypt -d example.com -w /var/www/html ``` #### ZeroSSL Free 90-day certificates, unlimited, wildcards included, over ACME. Requires **EAB** (External Account Binding) credentials from a free account, which is less friction than it sounds: ZeroSSL is **acme.sh's default CA**, and acme.sh obtains the EAB for you from just an email address: ``` acme.sh --register-account -m you@example.com acme.sh --issue -d example.com -w /var/www/html ``` With certbot, generate EAB credentials in the ZeroSSL dashboard (Developer section), then: ``` certbot --server https://acme.zerossl.com/v2/DV90 \ --eab-kid YOUR_KID --eab-hmac-key YOUR_KEY \ --nginx -d example.com ``` #### Google Trust Services Free ACME issuance on Google's roots, whose selling point is **very broad device trust**, including old Android versions that distrust some other chains. EAB keys come from a Google Cloud account: ``` gcloud publicca external-account-keys create ``` Then use the returned key ID and HMAC with any client against `https://dv.acme-v02.api.pki.goog/directory` (certbot's `--eab-kid`/`--eab-hmac-key` as above; acme.sh has a built-in `--server google` shortcut). #### SSL.com A commercial CA with a free 90-day DV tier over ACME. Create a free account; the dashboard shows your ACME credentials, and acme.sh has a built-in `--server sslcom` shortcut. #### Actalis An Italian CA offering a free ACME plan with unlimited issuance, the notable choice if you specifically want a **European** CA. Register at [actalis.com](https://www.actalis.com/), generate EAB credentials in their portal, and point any ACME client at the directory URL they provide. ### Clients: pick by your stack, not by fashion - **Caddy or Traefik:** you're done, ACME is built in, certificates appear and renew with zero configuration, and Caddy even **falls back to a second CA automatically** (Let's Encrypt, then ZeroSSL) if issuance fails. This is the strongest reliability story on the page, for free. - **nginx or Apache:** pick one of the two standalone clients. **certbot** is the distro-packaged, most-documented choice. **acme.sh** is a lighter shell script with more CA shortcuts, automatic EAB handling, and TLS-ALPN support, which certbot lacks. Both install renewal timers. - **Go/infrastructure tooling:** **lego** is the library-grade client the above ecosystems build on. - **Windows/IIS:** **win-acme** does the same job as a scheduled task. ### Challenge types: prove control the right way The challenge is how the CA verifies you control the domain, and the choice matters more than most guides admit. - **DNS-01** proves control by publishing a TXT record. Nothing inbound touches your server at all: **no open port required**, it works behind CDNs, proxies, and closed firewalls, and it is **the only challenge that can issue wildcards**. The cost is automation: your ACME client needs API access to your DNS (both certbot and acme.sh have plugins for all the major providers). Where it's available, this is the strongest option. - **TLS-ALPN-01** proves control during a TLS handshake **on port 443 only**. No port 80, no HTTP involved. **Caddy and Traefik do it natively** (it's how they renew without any HTTP plumbing), and acme.sh supports it (`--alpn`); certbot does not support it at all. With a standalone client it needs to answer on 443 itself, so it fits best where the web server *is* the ACME client, or on hosts without one. - **HTTP-01** proves control by serving a file at `http://yourdomain/.well-known/acme-challenge/`, which is why it demands **port 80 open to the world** and a carve-out from your HTTPS redirect. It's the ubiquitous default and there's nothing wrong with it **when port 80 is open anyway** to redirect visitors to HTTPS. What it should never be is the *reason* port 80 stays open: if your service is HTTPS-only, don't keep an extra listening port and a redirect exemption alive purely so a renewal can happen over plaintext HTTP, use DNS-01 (or TLS-ALPN-01 where your stack supports it) and close 80 entirely. The decision in one breath: **Caddy/Traefik → TLS-ALPN, already done. Wildcard or HTTPS-only or behind a CDN → DNS-01. Port 80 open anyway for redirects → HTTP-01 is fine.** ### Wildcards, understood properly A wildcard certificate (`*.example.com`) is the most misunderstood object in this topic, and the rules are exact: - **It covers one label, one level deep.** `*.example.com` matches `app.example.com` and `mail.example.com`. It does **not** match `a.b.example.com` (two levels), which needs `*.b.example.com`. - **It does not cover the apex.** `example.com` itself is not matched by `*.example.com`. This is why the standard wildcard certificate carries **both names**: the apex and the wildcard, in one cert. - **It requires DNS-01.** All CAs require the DNS challenge for wildcards, deliberately: a certificate valid for every present and future subdomain warrants proof of DNS-level control, not just control of one web server. Issuance, both names together: ``` # acme.sh with, e.g., Cloudflare-hosted DNS export CF_Token="your-scoped-api-token" acme.sh --issue --dns dns_cf -d example.com -d '*.example.com' # certbot with the matching DNS plugin certbot certonly --dns-cloudflare \ --dns-cloudflare-credentials /root/.secrets/cloudflare.ini \ -d example.com -d '*.example.com' ``` Every DNS provider with an API has an equivalent plugin; use a **scoped token** (zone-edit for the one zone, not a global account key), because that credential lives on the server for renewals. And the counterweight: if you have three known subdomains, a plain **multi-SAN certificate** (`-d example.com -d www.example.com -d api.example.com`) is simpler, requires no DNS API on the server, and exposes less if the host is compromised. Wildcards earn their place when subdomains are numerous or created dynamically. ### Protocols and ciphers: strong by configuration, not by luck The certificate is only half of TLS; the server's protocol and cipher configuration is the other half, and defaults on older distros can be poor. - **Enable TLS 1.2 and 1.3 only.** TLS 1.0 and 1.1 have been formally deprecated for years, and nothing legitimate still needs them. In nginx: `ssl_protocols TLSv1.2 TLSv1.3;` - **Don't hand-roll cipher lists**, and especially don't paste one from a 2015 blog post. Generate the configuration from the **[Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org/)**: pick your server and version, take the **Intermediate** profile (the right default; "Modern" only if you can drop older clients), and use it verbatim. TLS 1.3's cipher suites aren't configurable through the classic directives anyway, leave them alone. - **Prefer ECDSA keys.** Modern clients negotiate them universally, handshakes are faster, and keys are smaller; certbot and acme.sh both issue ECDSA by default now. Add an RSA fallback only if you must serve genuinely ancient clients. - **HSTS, once everything works.** `Strict-Transport-Security` tells browsers to refuse plain HTTP for your domain, an excellent hardening step *and* a commitment: turn it on only after HTTPS is fully working everywhere, start with a modest `max-age`, and treat the `preload` flag as close to irreversible. - **Caddy note:** its TLS defaults already match current best practice; the tuning above is for nginx and Apache, whose shipped defaults trail behind. **Then measure instead of assuming:** run **[SSL Labs' server test](https://www.ssllabs.com/ssltest/)**, the industry-standard report card for exactly this, certificate, chain, protocols, ciphers, known weaknesses, graded A+ to F with each finding explained. An **A** is the pass mark; the Mozilla intermediate profile plus a valid chain gets you there. For the same audit from a terminal (or for servers you'd rather not submit to a public tool), **[testssl.sh](https://testssl.sh/)** performs the equivalent checks locally. ### High availability: certificates that survive bad days The failure mode to design against isn't a bad certificate, it's issuance being unavailable the week you need it: a CA outage, a rate limit, a broken renewal nobody noticed. - **Don't depend on a single CA.** Everything on this page speaks the same protocol, so a second CA is a configuration line, not a migration. Caddy does the fallback automatically; with acme.sh it's one command when needed (`acme.sh --set-default-ca --server zerossl`, or `--server` per issue); with certbot, keep the ZeroSSL EAB pattern from above in your notes. This is also the answer to **Let's Encrypt rate limits**, which are the usual self-inflicted emergency: a looping misconfiguration burns the duplicate-certificate allowance, and the fastest way out is issuing the same names from a different CA while the loop gets fixed. - **Test against staging, not production.** Let's Encrypt's staging endpoint exists so experiments don't consume rate limits: `certbot --test-cert` / `acme.sh --staging`, and `certbot renew --dry-run` for verifying renewal health any time. - **Let the timers do the timing.** Clients renew at roughly a third of lifetime remaining (certbot at 30 days before expiry) with daily checks; the practice worth adding is *watching* it: after setup, confirm the timer exists (`systemctl list-timers`) and the dry run passes. - **Monitor expiry from outside the server.** The server whose renewal is broken is the wrong place to run the alert. Any uptime monitor with certificate checks (Uptime Kuma if you self-host one) watching for "expires in under 14 days" turns every possible renewal failure, whatever the cause, into an email two weeks ahead instead of a red padlock at 3 AM. **[crt.sh](https://crt.sh/)** complements this with the public issuance log: every certificate ever issued for your domain, useful both to confirm a renewal happened and to spot certificates you didn't request. - **CAA records, with the fallback in mind.** A `CAA` DNS record whitelists which CAs may issue for your domain, cheap hardening. Just remember it must list **every** CA you use, including your fallback, or the fallback fails precisely when you reach for it. ### When something breaks Browser errors, expired certificates, name mismatches, chain problems, and the Cloudflare SSL modes each have a specific fix, all collected in [Fixing SSL certificate errors](https://vpsdime.com/knowledgebase/troubleshooting/ssl-certificate-errors). If your site sits behind Cloudflare's proxy, the certificate visitors see is Cloudflare's edge certificate, and the origin-side rules are in [Cloudflare best practices](https://vpsdime.com/knowledgebase/getting-started/cloudflare-best-practices). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the domain, and which CA and client you're using, - the challenge type (HTTP-01, DNS-01, or TLS-ALPN-01), - the exact error from the client's log or dry run. ### Related questions - "Where can I get a free SSL certificate besides Let's Encrypt?" - "Do paid SSL certificates encrypt better than free ones?" - "What's the difference between HTTP-01, DNS-01, and TLS-ALPN-01 challenges?" - "Can I renew certificates without keeping port 80 open?" - "How do wildcard certificates work, and why do they need a DNS challenge?" - "Does *.example.com cover example.com or sub.sub.example.com?" - "What happens when I hit Let's Encrypt's rate limit?" - "Which TLS versions and ciphers should my server allow?" - "How do I test my SSL configuration strength?" - "How short are certificate lifetimes going to get?" --- ## One-click Applications explained URL: https://vpsdime.com/knowledgebase/getting-started/one-click-applications Last reviewed: 2026-07-02 Summary: The Applications tab on the deploy and reinstall forms installs a ready-made app (Coolify, Traccar, Immich, Code Server) instead of a bare OS, you enter the app's admin credentials on the form, provisioning installs everything, and the completion email tells you where to log in. What you get, what stays your job, and how to switch. ### What this is When you [deploy a VPS](https://vpsdime.com/knowledgebase/client-area/deploy/deploying-a-new-vps) or [reinstall one](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os), the install picker has two tabs: **Operating Systems** (a bare distro, you build from there) and **Applications**, which installs a complete, configured app on top of the OS for you. "One-click" is literal: you select the app, fill in its couple of fields on the same form, and the VPS comes up with the application installed and ready, no SSH session required to get it running. ### The current lineup - **[Coolify](https://coolify.io/)**, a self-hosted deploy platform (the open-source alternative to Vercel/Heroku/Netlify): websites, databases, and 280+ one-click services of its own, deployed to your VPS from git. The most popular pick, and the broadest, [a whole hosting workflow](https://vpsdime.com/knowledgebase/getting-started/open-source-control-panels) in one install. - **[Traccar](https://www.traccar.org/)**, GPS tracking server for vehicles and devices. - **[Immich](https://immich.app/)**, self-hosted photo and video library, the Google Photos replacement. - **[Code Server](https://github.com/coder/code-server)**, VS Code in your browser, running on your VPS. More get added over time, the tab shows what's currently available (availability can vary by plan size, some apps need more memory than the smallest plans offer). ### How it works 1. On the deploy or reinstall form, switch to the **Applications** tab and select the app. 2. Fill in the app's fields right on the form, typically an **admin email and admin password** (the form validates the app's requirements, e.g. password length and complexity, so what you enter is what works on first login). 3. Continue the deploy or reinstall as normal. Provisioning installs and configures the app automatically. 4. **Watch your inbox**: the completion email contains the details, where to log in and with what. You use the credentials you set on the form. That's the whole procedure. The admin password you choose is about to be an **internet-facing login**, so give it the same respect as any other: unique and from a password manager. ### What you get, and what stays yours Underneath the app is a **normal VPS**: full root over [SSH](https://vpsdime.com/knowledgebase/getting-started/connecting-to-your-vps), our [managed firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall), the same panel controls. The one-click saves you the installation, not the ownership, the app's configuration, its updates, and its data are yours to run, using the app's own documentation plus an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) when stuck, these are popular projects the models know deeply, and Coolify or Immich questions get excellent answers ([self-managed](https://vpsdime.com/knowledgebase/support-coverage/what-support-covers), as ever). Two habits worth keeping from day one: - **Update the app** on its own schedule, an internet-facing application is [attack surface](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps) like any other (Coolify and Immich ship updates frequently and make them easy). - **[Back it up](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps).** The one-click installed it; only backups can reinstall your *data*. The [first-30-minutes checklist](https://vpsdime.com/knowledgebase/getting-started/first-30-minutes) still applies to the server underneath, one-click doesn't change that. ### Switching, or starting over Want a different app, or back to a bare OS? [Reinstall](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os) and pick again, remembering a reinstall **wipes everything**, app data included, so export or back up first. ### Troubleshooting - **No completion email?** Check spam, and the VPS's Tasks log in the panel. Provisioning an app takes a few minutes longer than a bare OS. - **The app's page doesn't load right after the email.** Give it a couple of minutes on first boot, then check from another network ([the usual scoping](https://vpsdime.com/knowledgebase/troubleshooting/network-problems)). Still down? [Ticket us](https://vpsdime.com/open-ticket/) with the VPS and the app. - **Forgot the admin password you set on the form?** Password recovery is the app's own mechanism from here (or reinstall and set fresh credentials, at the cost of the data). ### Related questions - "What are the one-click Applications and how do they work?" - "How do I deploy Coolify / Immich / Traccar / Code Server?" - "Where do I get the login details for my one-click app?" - "Can I still SSH into a VPS deployed with an application?" - "Who updates the app, you or me?" - "How do I switch my VPS to a different app?" --- ## Modern open-source control panels for your VPS URL: https://vpsdime.com/knowledgebase/getting-started/open-source-control-panels Last reviewed: 2026-07-02 Summary: The genuinely good, actively developed, open-source panels for hosting websites on a VPS, Coolify, Dokploy, and Dokku on the deploy-platform side, HestiaCP and CloudPanel on the classic hosting-panel side, what each is for, honest caveats, and the security rule every panel install must follow. ### What this is If you want point-and-click hosting on your VPS without paying license rent to the cPanel/Plesk generation, the open-source world has you covered, and the current crop is genuinely good. This list is deliberately short: only panels that are **open source, actively developed, built for the Docker/Let's Encrypt era**, and pleasant to actually use. They split into two families, pick by which question you're asking. ### Family 1: deploy platforms ("host my apps and sites") These treat your VPS like your own private Heroku/Netlify: connect a git repository or pick an app, and the platform builds, deploys, reverse-proxies, and handles HTTPS automatically. The right family for developers and self-hosters. - **[Coolify](https://coolify.io/)**, the standout. Deploys apps from git, one-click installs for hundreds of open-source services, databases as first-class citizens, automatic SSL, backups, webhooks. Big, friendly UI and a very active project. It's also one of our **one-click Applications**, so you can [deploy a VPS with Coolify preinstalled](https://vpsdime.com/knowledgebase/getting-started/one-click-applications) and skip the setup entirely. Give it room: a 6 GB plan runs it comfortably alongside real workloads. - **[Dokploy](https://dokploy.com/)**, the newer, leaner take on the same idea (Docker + Traefik under the hood): git deploys, compose support, databases, automatic HTTPS, with a tighter footprint than Coolify. Worth a look if Coolify feels like more platform than you need. - **[Dokku](https://dokku.com/)**, the minimalist elder that aged beautifully: `git push` deploys via buildpacks or Dockerfiles, driven from the command line rather than a web UI. Tiny footprint, rock-solid, perfect if you live in the terminal and want the platform to disappear. (Honorable mention with an asterisk: EasyPanel is slick and popular but **not open source**, and on our Linux VPS its Swarm services need [the dnsrr adjustment](https://vpsdime.com/knowledgebase/technical-questions/docker-swarm).) ### Family 2: classic hosting panels ("host my PHP sites, mail, and domains") These are the true replacement for what shared hosting's panel did: sites, PHP versions, databases, DNS, mailboxes, in one web UI. - **[HestiaCP](https://hestiacp.com/)**, the most complete free cPanel replacement: nginx/Apache sites, per-site PHP versions, MariaDB, **full mail hosting** (with DKIM), DNS, Let's Encrypt, user accounts, and quotas. Actively maintained, clean UI, runs light. If you're [migrating off shared hosting](https://vpsdime.com/knowledgebase/getting-started/migrating-to-a-vps) and want the same mental model, this is the one. (Mail hosting on a VPS remains a commitment, [deliverability](https://vpsdime.com/knowledgebase/troubleshooting/emails-going-to-spam) and [our email policy](https://vpsdime.com/knowledgebase/acceptable-use/email-policy) apply regardless of panel.) - **[CloudPanel](https://www.cloudpanel.io/)**, focused and fast: PHP sites on nginx with per-site versions, MySQL/MariaDB, Let's Encrypt, cloud-friendly and genuinely quick. **No mail hosting**, which is a feature if you took [the hosted-mail advice](https://vpsdime.com/knowledgebase/getting-started/migrating-to-a-vps), one less thing the panel can get wrong. Installation, for any of these, is a single documented script from the project's site, and an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) walks the distro-specific quirks with you if the script hits one. ### The rule that applies to every panel A control panel is, by definition, a **root-powered web application listening on the internet**, which makes it the juiciest target on your server, and several popular panels (not the ones above) have suffered mass-exploited remote holes in recent years. Whatever you install: - **Update the panel with the same urgency as the OS**, panel CVEs get weaponized within days. - **Restrict access to it**: IP-allowlist the panel's port in your firewall, or reach it only over a VPN/SSH tunnel, the same logic as any [admin surface](https://vpsdime.com/knowledgebase/getting-started/securing-public-services). - Strong unique password and 2FA where the panel offers it. ### Do you need a panel at all? Honest question worth a beat: for one or two sites, [Caddy or nginx + certbot](https://vpsdime.com/knowledgebase/getting-started/hosting-a-website) is arguably *less* total complexity than a panel, and there's nothing extra to secure or update. Panels earn their keep when you manage **many** sites, hand access to **other people**, or genuinely miss the shared-hosting workflow. And choose deliberately: panels take over the server's configuration, so switching later is effectively a [migration](https://vpsdime.com/knowledgebase/getting-started/migrating-a-vps). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which panel you're installing, and where its install script stopped, with the output. ### Related questions - "What's a good free alternative to cPanel for my VPS?" - "Coolify or a traditional hosting panel, which do I want?" - "Which open-source panel can host mail too?" - "Is EasyPanel open source?" - "Do I even need a control panel on a VPS?" - "How do I secure a control panel installation?" --- ## Should I host my own email on a VPS? URL: https://vpsdime.com/knowledgebase/getting-started/self-hosting-email Last reviewed: 2026-07-02 Summary: The honest decision guide, what self-hosted email actually costs in ongoing work (deliverability, reputation, blocklist watch, uptime, spam filtering), when hosted mail is the right answer, when self-hosting is genuinely worth it, the hybrid setup most people should land on, and the policy boundaries either way. ### What this is Not the how, the **whether**. Email is the one workload where the honest advice for most people is "don't", and the same honest advice makes self-hosting great for the right person. This page is the decision; the how-tos are linked at the end. ### What self-hosting actually involves Running a mail server isn't the hard part, Mailcow installs in an afternoon. The commitment is everything after: - **Deliverability is a discipline, not a setting.** rDNS, SPF, DKIM, and DMARC get you to the starting line; large receivers then judge your **IP and domain reputation** continuously. A fresh server earns trust over weeks of consistent, low-volume, legitimate sending, and one compromised WordPress form on the same box can spend that trust overnight. - **You become the blocklist watcher.** Listings happen even to clean senders; noticing and delisting is on you ([the tools](https://vpsdime.com/knowledgebase/troubleshooting/emails-going-to-spam)), and [our policy](https://vpsdime.com/knowledgebase/acceptable-use/email-policy) puts blacklist cleanup on the customer, with a charge per listing, precisely because it's real work. - **Uptime carries a different weight.** A down website loses visitors; a down mail server *eventually loses mail*, senders retry for a few days, then bounce. Vacations count. - **Inbound is its own job**: spam filtering, storage growth, and [mailbox backups](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps), mail is often the least replaceable data a person has. None of this is exotic, but it's **forever**: a mail server is a pet, not a cattle. ### When hosted mail is the right answer For most people and almost every business: mailboxes at a dedicated mail provider (or your registrar's mail service), your domain's MX pointing there, and your VPS doing everything *except* mailboxes. You get teams of people whose whole job is deliverability and uptime, for a few dollars a mailbox, and your VPS migration/reinstall/experiments [never endanger mail](https://vpsdime.com/knowledgebase/getting-started/migrating-to-a-vps). If email failing for a day would genuinely hurt you, this is your answer, and there's no shame in it. ### When self-hosting is worth it - **You want ownership**: your mail on your hardware, no third party reading, mining, or locking you out. For many self-hosters this is the entire point, and it's a good one. - **You'll actually enjoy the craft**: deliverability is a skill, and running clean mail infrastructure teaches more about the internet than almost any other service. - **The stakes fit**: personal domains, project mail, a tinkerer's setup, places where a rough week hurts pride, not payroll. If that's you: [Mailcow](https://vpsdime.com/knowledgebase/technical-questions/mailcow-on-linux-vps) on a **6 GB plan or larger**, rDNS set first, the [outbound](https://vpsdime.com/knowledgebase/troubleshooting/emails-going-to-spam) and [inbound](https://vpsdime.com/knowledgebase/troubleshooting/cannot-receive-email) checklists as your setup guides, and the [email policy](https://vpsdime.com/knowledgebase/acceptable-use/email-policy) as the boundary (personal and transactional volume, never bulk). ### The hybrid most setups should land on These aren't all-or-nothing: - **Mailboxes hosted, VPS sends transactional**: human mail lives at a provider; your apps send their password resets either through the VPS directly (fine at low volume with the records set right) or through a relay like Amazon SES/Mailgun, which also keeps app mail off your personal reputation. - **Self-host inbound-light**: some self-hosters run Mailcow for mailboxes but route all *outbound* through a relay, keeping the hardest problem (sending reputation) outsourced while owning their data. ### The one-paragraph verdict Host your own email if you *want to run a mail server*, as a project, a principle, or a craft. If you just want **email that works**, host the mailboxes elsewhere, point MX there, and let your VPS be great at everything else. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - what you're weighing (self-hosting, hosted mailboxes, or the hybrid), - roughly the volume and kind of mail involved. ### Related questions - "Is it worth hosting my own email on a VPS?" - "What's the ongoing work of running a mail server?" - "Should my business self-host email?" - "Can I keep mailboxes at a provider and still send from my VPS?" - "What does the hybrid email setup look like?" --- ## Migrating from shared hosting to a VPS URL: https://vpsdime.com/knowledgebase/getting-started/migrating-to-a-vps Last reviewed: 2026-07-02 Summary: The complete move from cPanel-style shared hosting to your own VPS, what changes (you own the server now), the email decision to make before touching DNS, inventory, building the destination first, the hosts-file trick to test before cutover, lowering TTL, and the overlap week before cancelling the old plan. ### What this is Moving your sites off shared hosting (cPanel, Plesk, and friends) onto your own VPS. Done in the right order, the visitors never notice; this page is that order. (Moving from *another VPS* instead? That's [its own guide](https://vpsdime.com/knowledgebase/getting-started/migrating-a-vps).) First, the honest framing of what changes. Shared hosting sold you a managed **environment**: PHP preconfigured, a control panel, mailboxes bundled in, backups quietly handled. A VPS gives you the whole **server**: root access, your choice of everything, real performance, no neighbor caps, and in exchange, setup, updates, [security](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps), and [backups](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps) become yours. The migration is also the moment you take over those jobs, plan for that, not just for the file copy. ### Step 0: decide about email first The single most common migration casualty is mail, because shared hosting bundled your mailboxes and the VPS doesn't. Decide **before touching DNS**: - **Keep mail at a mail provider** (the sane default): a hosted mail service (or your registrar's mail offering) hosts the mailboxes; your domain's MX records point there, and the VPS only serves the website. Nothing about the site move touches your mail. - **Self-host mail on the VPS** (hard mode): possible, [Mailcow](https://vpsdime.com/knowledgebase/technical-questions/mailcow-on-linux-vps) is the good tooling, but deliverability and upkeep are a real ongoing job, and [our email policy](https://vpsdime.com/knowledgebase/acceptable-use/email-policy) applies. Choose this deliberately, not by default, the full decision guide is [Should I host my own email?](https://vpsdime.com/knowledgebase/getting-started/self-hosting-email) Either way, list every mailbox and forwarder that exists on the shared plan **now**, they vanish when that plan closes. ### Step 1: inventory From the old panel, write down: the sites and their PHP versions, every database, cron jobs (easy to forget, invisible until something stops happening), the full **DNS zone** (export or screenshot it, especially MX and TXT/SPF records), and which domains have SSL. ### Step 2: build the destination first Deploy the VPS and set up the stack **before** anything moves: web server + PHP (matching the version the site ran on) + database, or a [one-click application](https://vpsdime.com/knowledgebase/getting-started/hosting-a-website) if it fits. Get a placeholder page serving on the VPS's IP so you know the plumbing works. The old site stays live and untouched throughout. **Missing cPanel already?** You don't have to go without a panel, and you don't have to pay for one either. The modern open-source generation is genuinely good: **HestiaCP** gives you the full shared-hosting mental model (sites, PHP versions, DNS, even mailboxes), **CloudPanel** does fast PHP hosting without the mail baggage, and **Coolify** turns the VPS into your own deploy platform. The full rundown with honest caveats: [Modern open-source control panels](https://vpsdime.com/knowledgebase/getting-started/open-source-control-panels). ### Step 3: move files and databases - **Files:** download a full backup from the old panel (cPanel: Backup → Download a Full Website Backup) or pull the document root over [SFTP](https://vpsdime.com/knowledgebase/getting-started/uploading-files-sftp), then place it under your web root on the VPS. - **Databases:** export from the old side (phpMyAdmin → Export, or the panel's backup), import on the VPS (`mysql newdb < dump.sql`). - **Reconnect:** update the app's config for the new DB name/user/password and any changed paths (`wp-config.php` for WordPress). Watch for hardcoded old-server paths like `/home/cpaneluser/...`. ### Step 4: test before DNS moves, the hosts-file trick You can browse the site **on the new server** while the whole world still sees the old one: add a line to your own computer's hosts file (`/etc/hosts`, or `C:\Windows\System32\drivers\etc\hosts` on Windows): ``` YOUR.VPS.IP yourdomain.com www.yourdomain.com ``` Your machine now resolves the domain to the VPS. Click through everything, pages, logins, forms, uploads, and fix what's broken with zero pressure, because nothing is live yet. Remove the line when done testing. ### Step 5: cutover 1. **A day ahead**, lower the TTL on the domain's A records (to 300s) so the switch propagates fast. 2. **Switch the A records** to the VPS IP ([pointing your domain](https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain)), leaving MX and mail-related records exactly as your Step-0 decision requires. 3. **Issue SSL on the VPS** as soon as DNS resolves there ([certbot](https://vpsdime.com/knowledgebase/getting-started/hosting-a-website)). 4. **Keep the old hosting alive for a week.** Cached DNS sends stragglers to the old server for a while, and the overlap is your safety net if something surfaces late. ### Step 6: take over the landlord's jobs Shared hosting did these silently; now they're yours, and day one is the right day: the [security checklist](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps), a [real backup routine](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps) (the old panel's nightly backups are gone with it), and re-creating the **cron jobs** from your inventory ([timers are the better home](https://vpsdime.com/knowledgebase/technical-questions/systemd-timers)). Then, and only then, cancel the old plan. The work itself is yours (the service is [self-managed](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management)), but none of it is exotic, and an AI chatbot walks any single step in this page with you patiently. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP and the site being moved, - which step you're on (inventory, copy, hosts-file test, cutover), and where it got stuck. ### Related questions - "How do I move my website from shared hosting to a VPS?" - "What happens to my email when I leave shared hosting?" - "How do I test my site on the new server before changing DNS?" - "How do I migrate a WordPress site to a VPS?" - "When can I safely cancel my old hosting?" --- ## Migrating a VPS to a new server URL: https://vpsdime.com/knowledgebase/getting-started/migrating-a-vps Last reviewed: 2026-07-02 Summary: Moving from one VPS to another, from another provider, between product lines, or as a rebuild, done the clean way: rebuild services, move data server-to-server with rsync over SSH, dump databases rather than copying files, the two-pass rsync for minutes of downtime, and the new-IP checklist (DNS, SPF, rDNS, SSL, allowlists) that prevents the post-move surprises. ### What this is Moving everything from one VPS to another: coming from another provider, replacing a server, rebuilding after [a compromise](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery), or switching product lines here (there's no automatic Linux VPS → Premium VPS conversion, this guide is the path). One boundary: this is a **Linux-to-Linux** guide, between Linux and Windows there's no migration in this sense, applications get reinstalled on the new OS and you copy data files across, then cancel the old service. One carve-out first: if you only want the **same VPS in a different location**, don't migrate at all, we offer a [location migration](https://vpsdime.com/knowledgebase/client-area/services/migrate-location) for a $4 fee, ordered from your client area and carried out by our team, and if you don't need the data at all, we'll re-provision the VPS in the new location for free (your IP changes either way, so the checklist below still applies). And if you're coming from *shared hosting*, that's [the other guide](https://vpsdime.com/knowledgebase/getting-started/migrating-to-a-vps). ### Don't copy the disk, move the workload The instinct is to image the old disk onto the new server; resist it. Different platforms differ in kernel, network configuration, and boot plumbing, and a transplanted disk drags along every accumulated quirk (and, if you're rebuilding for security reasons, the compromise itself). The clean method mirrors the [backup doctrine](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps): the OS and services are **rebuildable**, the data is **irreplaceable**, so install fresh and move only the data. 1. Deploy the new VPS and set up the stack (web server, runtime, database, [the site plumbing](https://vpsdime.com/knowledgebase/getting-started/hosting-a-website)), old server untouched and live. 2. Move data (below). 3. Test, cut over, run in parallel, decommission. ### Move files server-to-server Both machines are servers on fast links, so transfer **directly between them** over SSH, never down to your home connection and back up: ``` rsync -avz --progress root@OLD.SERVER.IP:/var/www/ /var/www/ ``` Run it from the new server (pulling), inside `tmux` so a dropped SSH session doesn't kill a long transfer. rsync is restartable by nature, re-running continues where it left off. ### Databases move by dump, not by file copy Copying `/var/lib/mysql` between servers invites version and consistency trouble; a dump restores cleanly across versions. Pipe it straight over SSH, no intermediate file: ``` ssh root@OLD.SERVER.IP "mysqldump --single-transaction --all-databases" | mysql ``` (`--single-transaction` gives a consistent snapshot of InnoDB databases without locking the live site. PostgreSQL: the same pattern with `pg_dumpall`.) ### The two-pass trick: minutes of downtime at any size Big sites don't need long outages, split the copy: 1. **Pass one, live:** run the full rsync and DB import while the old server keeps serving. Takes as long as it takes; nobody notices. 2. **Freeze:** at cutover time, stop writes on the old server (put the app in maintenance mode or stop its services). 3. **Pass two, delta:** re-run the same rsync (it now transfers only what changed since pass one, seconds to minutes) and re-import the database dump. 4. Switch DNS. Total write-downtime: the delta pass, not the migration. ### The new-IP checklist The server moved; its **IP address didn't come along**. This list is what prevents the week-two surprises: - **DNS**: A and AAAA records to the new IP ([lower TTL a day ahead](https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain), and test first with the [hosts-file trick](https://vpsdime.com/knowledgebase/getting-started/migrating-to-a-vps)). - **SPF**: if the server sends mail, your SPF TXT record names the **old IP**, mail keeps flowing but starts [landing in spam](https://vpsdime.com/knowledgebase/troubleshooting/emails-going-to-spam), silently. Update `ip4:` to the new address. - **rDNS**: set the new IP's PTR to your hostname from the [Network](https://vpsdime.com/knowledgebase/client-area/services/network) tab (mail servers especially). - **SSL**: issue fresh certificates on the new server with certbot once DNS points there, cleaner than hauling the old keys across. - **Hardcoded IPs**: grep your app configs, firewalls elsewhere, and monitoring for the old address. - **Third-party allowlists**: payment gateways, external APIs, and remote databases that allowlisted your old IP need the new one, this is the one that always gets forgotten until something 403s. ### Cut over, overlap, decommission Switch DNS, then **run both servers in parallel** for a few days: watch the old server's access log, real traffic still arriving there means cached DNS or a record you missed. When the old log goes quiet: take one last data snapshot for your [off-site backups](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps), then decommission the old server, and if the old one is with us, [cancellation](https://vpsdime.com/knowledgebase/client-area/services/cancellation) deletes it and its data permanently, so the snapshot comes first. As always: the hands-on work is yours on a [self-managed service](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management), and every command above is safe to ask an AI chatbot to adapt to your exact stack. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, and where you're migrating from, - which step you're on (copy, database, DNS cutover), with the exact error. ### Related questions - "How do I migrate my VPS from another provider?" - "How do I move from Linux VPS to Premium VPS?" - "How do I transfer a large site with minimal downtime?" - "Should I copy the whole disk or reinstall and move data?" - "What breaks when my server's IP changes?" - "When is it safe to cancel the old server?" --- ## Securing your VPS URL: https://vpsdime.com/knowledgebase/getting-started/securing-your-vps Last reviewed: 2026-07-02 Summary: A practical, layered security checklist for a self-managed VPS, SSH keys and strong passwords, never exposing database and app ports to the internet, staying updated and reacting fast to CVEs, application hygiene, monitoring, backups, and what to do if you're compromised. ### What this is A practical security checklist for your VPS. The service is self-managed, so this part is yours, but none of it is hard, and the payoff is huge: almost every compromised VPS we see was taken by an **automated scanner** exploiting one of a handful of basics, an exposed database port, a weak password, or software left unpatched. Cover the layers below and you're ahead of virtually all of it. ### 1. Lock down how you get in - **Use SSH keys instead of passwords.** This is the single best upgrade. With key authentication there's no password to guess, brute-forcing becomes pointless, and you'll never get your own IP banned for typos (see [the SSH firewall](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall)). Save your key on the [SSH Keys](https://vpsdime.com/knowledgebase/client-area/services/ssh-keys) page and select it when you deploy or reinstall, or add it to `~/.ssh/authorized_keys` on a running VPS, the full generate-and-deploy walkthrough is [Setting up SSH keys, properly](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys). - **Then disable password login.** Once you've confirmed key login works, set `PasswordAuthentication no` in `/etc/ssh/sshd_config` and restart SSH. Test the key login in a second terminal **before** closing your working session. - **Keep the root password strong anyway.** You'll still need it for the [Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps). Long beats clever: several random words together (`HolyConcreteThrone` style) is both strong and typeable. Use a password manager, or our [password generator](https://vpsdime.com/passwordgen.php). Skip the classics that crackers try first: dictionary words with `@123` bolted on, keyboard walks like `qwerty`, names, and "clever" substitutions like `D00R8377`. - **Never reuse passwords** between your VPS, your client account, and anything else. - **Want a second factor on SSH itself?** Authenticator-app codes at login are a real option, most valuable if you keep password auth, belt-and-braces on top of keys, [the TOTP setup guide](https://vpsdime.com/knowledgebase/technical-questions/ssh-2fa-totp) covers it, lockout-safe. - **Your VPSDime account already has [two-factor authentication](https://vpsdime.com/knowledgebase/client-area/account/two-factor-overview) on**, every account does, with email login codes by default. Upgrading to an [authenticator app](https://vpsdime.com/knowledgebase/client-area/account/authenticator-app-setup) makes the second factor independent of your mailbox. Whoever controls the account controls the server. ### 2. Don't expose services to the internet The most common VPS compromise isn't SSH at all. It's an **application port accidentally open to the whole internet**: a database with a weak password, Redis without auth, a Docker API on tcp/2375, an admin panel bound to `0.0.0.0`. Scanners find these within hours. - **Bind internal services to `127.0.0.1`.** If only the VPS itself needs your database or cache, it should listen on localhost, then nothing outside can reach it no matter what. - **Keep our managed firewall on.** Linux VPS include a [network-edge firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall) that blocks the most-attacked app ports by default and lets you whitelist just the sources that need access. It exists precisely for this failure mode. Leave it on. - **Run your own firewall inside the VPS too.** Default-deny inbound with only what you serve open (`ufw default deny incoming`, then allow 22, 80, 443 and whatever you actually run). Two independent layers means one mistake isn't fatal. - **Audit what's listening** now and then: `ss -tulnp` shows every port. Anything LISTENing on `0.0.0.0` or a public address should be something you deliberately serve to the world. Service-by-service bind instructions (MySQL, PostgreSQL, Redis, MongoDB, Elasticsearch, Memcached, Docker's port-publishing trap) live in their own guide: [Securing publicly accessible services](https://vpsdime.com/knowledgebase/getting-started/securing-public-services). ### 3. Stay updated, and move fast on CVEs Unpatched software is the other big door in. - **Update the OS regularly**, and put security patches on autopilot: `unattended-upgrades` on Debian/Ubuntu, `dnf-automatic` on RHEL-family. A VPS that patches itself at 4am beats one waiting for you to remember. - **The application layer counts just as much.** CMSes and their plugins (WordPress especially), panels, Docker images, and app dependencies are attacked more than the OS. Update them on a schedule, and delete plugins and software you don't use, every installed package is attack surface. - **Follow security news for the stack you run.** Subscribe to your distro's security announcements, watch the GitHub releases of the software you depend on, and skim a feed like CISA's Known Exploited Vulnerabilities list. The point is speed: when a critical CVE lands in something internet-facing that you run, patching **the same day** is what separates a non-event from a rebuild. When a scary CVE headline does land, asking an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) what it means for *your* stack, and whether your configuration is even exposed, gets you a clear answer in minutes instead of an afternoon of advisory-parsing. ### 4. Application hygiene - **Don't live as root.** Create a regular user with `sudo` for day-to-day work; use root only when needed. - **Strong, unique credentials for every service**, including ones bound to localhost. A leaked app config shouldn't hand out a password that works elsewhere. - **Protect admin panels.** Anything with a login page facing the internet deserves a strong password at minimum, and ideally an IP allowlist or a VPN in front. - **fail2ban** is worth installing for exposed login surfaces beyond SSH (mail, panels, WordPress logins). Our network already stops SSH brute-force on port 22, [network-wide, and better than a local tool could](https://vpsdime.com/knowledgebase/technical-questions/ssh-bruteforce-firewall), but defense in depth is the theme here. ### 5. Notice trouble early - Glance at your [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs): CPU or traffic that's suddenly pinned when you changed nothing is the classic symptom of a compromise or abuse. - Check auth logs occasionally (`journalctl -u ssh`, `lastb`), and be suspicious of processes you don't recognize. ### 6. Backups are a security control Ransomware, a wiped disk, or a rootkit you can't trust your way out of, all of them end the same way: you restore. Have real, off-site, tested backups. See [Backing up your VPS](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps). ### If you're compromised anyway We [suspend compromised VPSes](https://vpsdime.com/knowledgebase/acceptable-use/whats-allowed) to protect the network, and then you decide: clean it or rebuild it. Our honest advice is **rebuild**: once a box is rooted you can't fully trust it. Recover data from backups, [reinstall](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os), patch whatever let them in, and **rotate every credential** that lived on the server. The full procedure, including why modern attack bots make in-place cleanup a losing game, is in [My VPS was hacked. Recovery, step by step](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what you're trying to secure or what you think happened. ### Related questions - "How do I secure my VPS?" - "How do I set up SSH keys and disable password login?" - "How do I choose a strong root password?" - "Should my database port be open to the internet?" - "How do I keep my VPS updated automatically?" - "How do I find out about security vulnerabilities in my software?" - "What should I do if my VPS was hacked?" --- ## Securing publicly accessible services on your VPS URL: https://vpsdime.com/knowledgebase/getting-started/securing-public-services Last reviewed: 2026-07-02 Summary: Service-by-service instructions for closing accidentally exposed services, bind MySQL/MariaDB, PostgreSQL, MongoDB, Redis, Elasticsearch, and Memcached to localhost, handle Docker's port publishing, give remote access safely (whitelists, SSH tunnels), and fix the quick wins vulnerability scanners flag (version disclosure, old TLS). ### What this is A service that listens on **all interfaces** (`0.0.0.0`) is reachable by the entire internet, and internet scanners find it within hours, not days. An exposed database, cache, or API with a weak (or missing) password is the single most common way a VPS gets compromised. This guide closes those doors service by service. It's also the fix-list for when a **vulnerability scanner** has flagged your server. The general rule behind every section: **if only the VPS itself needs a service, it should listen on `127.0.0.1`.** Localhost can't be reached from outside, no matter what. ### First, see what's actually exposed On the VPS: ``` ss -tulnp ``` Read the **Local Address** column: entries on `127.0.0.1` are safe by construction; entries on `0.0.0.0` or `[::]` are offered to the whole internet and should each have a reason. For the outside view, scan yourself from home: `nmap -Pn YOUR.VPS.IP` shows what the world actually sees. If the `ss` output is a wall of mystery, paste it whole into an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) and ask it to identify each listener and flag any that look unintentional, genuinely one of the best uses of the tool. ### Layer 1: what our firewall already covers Linux VPS sit behind our [managed network firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall), which blocks internet access to the most-attacked service ports by default, PostgreSQL, MongoDB, Redis, Elasticsearch, Memcached, RabbitMQ, the Docker API, and more (the full port table is in that guide). So a mistakenly exposed Redis on a Linux VPS is shielded even before you fix it. Two important gaps in that safety net: - **MySQL/MariaDB (port 3306) is deliberately not blocked**, too many customers need it reachable, so securing MySQL is entirely on you (next section). - **Premium and Windows VPS** don't have this firewall, everything below is on you there. The firewall is a net, not a substitute: fix the binds anyway, then a mistake in either layer is covered by the other. ### Layer 2: bind services to localhost For each service you run, apply the change, then restart it (`systemctl restart `) and re-check with `ss -tulnp`. **MySQL / MariaDB**, the one our firewall doesn't cover: ``` # /etc/mysql/mariadb.conf.d/50-server.cnf (MariaDB) # /etc/mysql/mysql.conf.d/mysqld.cnf (MySQL) bind-address = 127.0.0.1 ``` **PostgreSQL** (`/etc/postgresql/*/main/postgresql.conf`): ``` listen_addresses = 'localhost' ``` **MongoDB** (`/etc/mongod.conf`): ``` net: bindIp: 127.0.0.1 ``` **Redis** (`/etc/redis/redis.conf`), bind it *and* keep protected mode: ``` bind 127.0.0.1 protected-mode yes ``` Set `requirepass` too, an unauthenticated Redis is a remote-code-execution kit even semi-exposed. **Elasticsearch** (`/etc/elasticsearch/elasticsearch.yml`): ``` network.host: 127.0.0.1 ``` **Memcached** (`/etc/memcached.conf`): ``` -l 127.0.0.1 ``` **Docker deserves special attention:** publishing a port with `-p 5432:5432` exposes it to the internet **bypassing ufw/iptables rules on the VPS**, Docker manages its own firewall chains. Publish to localhost when only the VPS needs it: ``` docker run -p 127.0.0.1:5432:5432 ... ``` (and the same `127.0.0.1:` prefix in compose `ports:`). Our edge firewall still shields the [blocked-list ports](https://vpsdime.com/knowledgebase/client-area/services/firewall) even when Docker sidesteps your local rules, one more reason to keep it on. ### When something must be reachable from outside Don't fall back to `0.0.0.0` and hope. In order of preference: 1. **SSH tunnel**, zero exposure, great for admin access: `ssh -L 3306:127.0.0.1:3306 root@YOUR.VPS.IP` on your machine, then connect your client to `localhost:3306`. The service stays bound to localhost. 2. **A private overlay** (WireGuard or Tailscale) between your machines, then bind services to the overlay interface, our recommendation for server-to-server traffic generally. 3. **IP allowlists.** For services on our [blocked list](https://vpsdime.com/knowledgebase/client-area/services/firewall), use its **Per-Application Whitelist**. For MySQL and anything custom, allowlist in your own firewall (`ufw allow from YOUR.OFFICE.IP to any port 3306`), never a blanket `ufw allow 3306`. ### Layer 3: credentials still matter A correct bind plus a default password is one config regression away from disaster: - Strong, unique passwords for **every** service, including localhost-only ones, and no default accounts left enabled. - Lock down secrets files: `find /var/www -name ".env"`, then `chmod 600` them, a readable `.env` through a misconfigured web server leaks every credential it holds. - Admin panels that must face the internet get a strong password plus an IP allowlist. The broader checklist is in [Securing your VPS](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps). ### Scanner quick wins (version disclosure and old TLS) If a scan report is what brought you here, two findings appear on nearly every fresh web server and take a minute each: - **Hide version info.** nginx: `server_tokens off;` in the `http` block. Apache: `ServerTokens Prod` and `ServerSignature Off` in `conf-available/security.conf`, plus `Options -Indexes` on your web root to kill directory listings. - **Modern TLS only.** nginx: `ssl_protocols TLSv1.2 TLSv1.3;`. Apache: `SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1`. That retires the POODLE/FREAK-era findings in one line. (Certificates themselves: [free with Let's Encrypt](https://vpsdime.com/knowledgebase/getting-started/hosting-a-website).) Restart the web server after either change. ### Verify, and re-verify Finish the way you started: `ss -tulnp` on the VPS, `nmap -Pn YOUR.VPS.IP` from outside. Everything still listed public should be something you deliberately serve to the world, with authentication in front of it. Re-run the pair after big installs, new software loves binding to `0.0.0.0` by default. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the service you're locking down and its `ss -tulnp` line, - the scanner finding you're chasing, if there is one. ### Related questions - "A vulnerability scanner flagged services on my VPS, how do I fix them?" - "How do I stop MySQL/PostgreSQL/Redis accepting connections from any IP?" - "Is my database port open to the internet?" - "Why is my Docker container's port public even though I have ufw?" - "How do I access my database remotely without exposing it?" - "How do I hide my web server version and disable old TLS?" --- ## Backing up your VPS URL: https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps Last reviewed: 2026-07-02 Summary: Honest backup advice for a VPS, why backups (not RAID) are what save you, the 3-2-1 rule, dumping databases properly, tools that work well (restic, borg, rclone, rsync), off-site destinations, testing restores, and how our Nightly Backups add-on fits in as an extra layer, not a replacement. ### What this is How to actually keep your data safe on a VPS. Your data is your responsibility with any self-managed host, and the good news is that a genuinely solid backup setup takes an evening to build and then runs itself. First, a distinction that bites people: **redundancy is not backup.** Our nodes run RAID10 and redundant everything, which protects against a dead disk, but it faithfully replicates your mistakes too. Most real-world data loss is a deleted file, a botched upgrade, a bad migration, ransomware, or a compromise, and against all of those, only a backup helps. ### What to back up Split your VPS mentally into two piles: - **Irreplaceable:** your databases, uploaded files, application data, configs you've sweated over, TLS keys and certs. This is what backups are for. - **Rebuildable:** the OS and installed packages. You can reinstall those in minutes, so most people don't image the whole OS themselves, they keep a note (or script) of how the server was set up, plus the data. If you can answer "how would I get from a fresh [reinstall](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os) back to a working server?", you know exactly what belongs in the backup. ### The 3-2-1 rule The classic standard, and it maps neatly onto a VPS: - **3 copies** of your data (the live one counts as one), - on **2 different systems**, - with **1 off-site**, away from the VPS and ideally away from any single provider. A copy that lives only on the VPS itself is not a backup: whatever takes out the server (compromise, deletion, a mistake with `rm`) takes the "backup" with it. ### Databases need dumps, not file copies Copying a running database's files produces backups that may not restore. Dump instead, on a schedule: - MySQL/MariaDB: `mysqldump --single-transaction dbname > backup.sql` - PostgreSQL: `pg_dump dbname > backup.sql` Run it nightly from cron to a folder like `/var/backups/`, then let your backup tool ship that folder off-site. Bonus: a nightly dump inside the VPS also makes our [Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview) image cleanly restorable, since the dump is a consistent copy sitting in the image. ### Tools that work well Any of these, automated with cron or better, a [systemd timer](https://vpsdime.com/knowledgebase/technical-questions/systemd-timers) (logged runs, catch-up after downtime, no overlaps), is a real setup: - **restic** (our default recommendation): encrypted, deduplicated, incremental, works with any S3-compatible storage or SFTP, and retention is one flag (`restic forget --keep-daily 7 --keep-weekly 4 --keep-monthly 6 --prune`). One tool does the whole job. - **BorgBackup:** the same virtues, best when your destination is another Linux box you control. - **rclone:** syncs directories to almost any cloud storage; great for shipping a backups folder off-site. - **rsync** to another server: simple and battle-tested, though it's a mirror rather than versioned history unless you add snapshots. - Even a **tar + cron** job shipped off-site beats nothing, start simple rather than not at all. ### Where to send them (off-site) - **Object storage** is the sweet spot for price and durability: Backblaze B2, Cloudflare R2, Wasabi, or any S3-compatible bucket. Pennies per month for typical site data. - **Another server you control**, with a different provider or at home (a NAS), also works well. - The principle: at least one copy should survive the total loss of this VPS **and** be independent of any single company, including us. ### Test your restores An untested backup is a hope, not a backup. Twice a year, actually restore something: pull a file back from restic, load a database dump into a scratch database, and confirm it's all there. And make failure noisy, check that your backup job alerts you when it stops working (a cron email, or a dead-man's-switch ping service), because backup jobs love to die silently the month before you need them. ### Where our Nightly Backups add-on fits [Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview) images your **whole VPS** once a night with 3-night retention, with self-service full restore, per-file recovery, and disk-image download. It's $5/month on Linux and Windows VPS ([enable it here](https://vpsdime.com/knowledgebase/client-area/nightly-backups/enable-nightly-backups)) and included free on Premium VPS. Use it **in addition to** your own backups, not instead of them. The two cover different failures: - **Nightly Backups** is the fastest way back from "I broke the server last night", a whole-server rollback or a quick file recovery, no setup required. - **Your own off-site backups** give you long retention, history beyond three nights, and a copy that exists outside our platform entirely. Together that's a genuinely robust setup. Either alone has a gap. ### A solid starter recipe 1. Enable **Nightly Backups** on the VPS. 2. Add a nightly **database dump** to `/var/backups/` via cron. 3. Run **restic** daily to an off-site bucket (site files + `/var/backups/` + configs), with `--keep-daily 7 --keep-weekly 4 --keep-monthly 6`. 4. Put a **restore test** in your calendar twice a year. (Steps 2 and 3 are a script and a schedule, exactly the kind of thing an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) drafts correctly from your paths and bucket details, you review the retention flags and paste it in.) An evening of setup, and every failure mode short of "the internet ends" is covered. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what data you're trying to protect, and what you've set up so far. ### Related questions - "How should I back up my VPS?" - "Do you back up my VPS for me?" - "How do I back up my database properly?" - "What backup tool should I use on a VPS?" - "Where should I store my backups?" - "Is the Nightly Backups add-on enough on its own?" - "How do I know my backups actually work?" --- ## How to raise a support ticket (and get it solved fast) URL: https://vpsdime.com/knowledgebase/getting-started/raising-a-support-ticket Last reviewed: 2026-07-02 Summary: The beginner's guide to asking for help well, what to try first, how to write a ticket that gets fixed on the first reply (exact errors, timeline, what you tried), why you should paste what the server said but never what an AI chatbot said, and how the conversation works after you submit. ### What this is How to ask for help in a way that gets your problem **solved on the first reply**. Our support is [staffed 24/7 and typically answers within minutes](https://vpsdime.com/knowledgebase/support-coverage/response-times-and-priorities), so the variable you control is how solvable your ticket is when it lands. This page is that craft, plus one rule about AI output that saves everyone time. ### Before you ticket: the faster paths Not gatekeeping, just speed. Three things regularly beat even a minutes-fast reply: - **VPS down or unreachable?** [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) checks it and *fixes* several causes on the spot (banned IP, disabled password login), and if it can't, it escalates into a ticket with diagnostics already attached, the best of both. - **Search this knowledge base**, the most common problems have step-by-step fixes here. - **Your software misbehaving?** Remember [the scope](https://vpsdime.com/knowledgebase/support-coverage/what-support-covers): the platform is on us, software on your VPS is yours with our best-effort help. An [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) is genuinely excellent at your-software problems, and often faster than any human could be. ### Opening the ticket [Open a ticket](https://vpsdime.com/open-ticket/) any time from your account. Pick **Sales/Billing** or **Support** as the department, set the **Related Service** to the VPS it's about, and choose the priority honestly, High is for down-and-urgent, and [it isn't a queue-jump button](https://vpsdime.com/knowledgebase/support-coverage/response-times-and-priorities). The full form mechanics are in [Getting help](https://vpsdime.com/knowledgebase/client-area/support/getting-help). ### Writing a ticket that gets solved in one reply The recipe, in the order our team reads it: 1. **One problem per ticket.** Two problems in one thread get solved slower than two tickets. 2. **What you expected, and what happened instead.** "I'm trying to reach my site over HTTPS; browsers show ERR_CONNECTION_REFUSED" beats "site broken" by a full day of back-and-forth. 3. **The exact error, copied verbatim.** Machine output is gold: the browser's error code, the command and its output, the log line. "SSH says `Permission denied (publickey)`" and "SSH times out" are different problems with different fixes, precision here *is* the diagnosis. 4. **When it started, and what changed just before**, a reinstall, an update, a config edit, a new firewall. "Right after I enabled ufw" solves the ticket in the subject line. 5. **What you already tried**, so nothing gets suggested back to you. 6. **Attachments where they help**: screenshots of errors, log files. (Never full card numbers, and no passwords unless we ask.) ### The AI rule: paste what the server said, never what the chatbot said We genuinely recommend [AI chatbots](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) for working problems yourself, they'll walk you to a fix or at least point the right direction. But when a ticket is where you've landed, **write it in your own words and do not paste the chatbot's output into it.** Here's why this matters. Our support staff are **all L3-level admins**, they diagnose from real symptoms: your description, the exact errors, the actual command output. A pasted AI conversation is the opposite of that: paragraphs of generic possibilities, speculation about causes that don't apply to our platform, and suggested fixes for problems you don't have. It buries the two lines of signal in a page of noise, and a human now has to *read all of it* to find out what's actually wrong, which makes your fix slower, not faster. The clean division of labor: - **Paste freely:** what the *server* said, error messages, log lines, command output. That's evidence. - **Summarize in your own words:** what you did, what you saw, what the AI helped you try and what happened when you tried it ("an AI suggested checking the bind-address; it was already 127.0.0.1"). That's *useful* history, one line of it. - **Never paste:** the chatbot transcript, its bullet-point essays, or its guesses. If the AI had solved it, you wouldn't be writing the ticket, give the humans the raw material instead, they're good. ### After you submit - **Answered** status means it's your turn; reply in the same thread (or just reply to the email, same thing). - **Don't open a second ticket for the same issue** or bump every few minutes, it fragments the thread and slows the fix. - **Solved it yourself in the meantime? Say so**, a one-line "fixed, it was X" closes the loop and helps the next person too. ### Related questions - "How do I open a support ticket?" - "What should I include in a support ticket?" - "Why shouldn't I paste ChatGPT/Claude output into my ticket?" - "How do I get my problem fixed on the first reply?" - "Should I open a new ticket or reply to the old one?" --- ## Account & sign-in help URL: https://vpsdime.com/knowledgebase/client-area/account Last reviewed: 2026-07-02 Summary: Help articles for signing in, two-factor authentication, linked sign-in providers, and creating an account at VPSDime. Guides for getting into your VPSDime account and managing how you sign in. ### Signing in & creating an account - [Signing in](https://vpsdime.com/knowledgebase/client-area/account/signing-in). Email and password, "verify you're human", forgotten passwords. - [Reset a forgotten password](https://vpsdime.com/knowledgebase/client-area/account/reset-password). Use the "Forgot password?" link to get a reset email and set a new one. - [Sign in with Google or GitHub](https://vpsdime.com/knowledgebase/client-area/account/sign-in-with-google-or-github). One-click sign-in, the confirmation email, "no password needed". - [Creating an account](https://vpsdime.com/knowledgebase/client-area/account/creating-an-account). Signing up on the site or during checkout. ### Two-factor authentication & security - [Two-factor authentication: overview](https://vpsdime.com/knowledgebase/client-area/account/two-factor-overview). How 2FA works here, email codes vs an authenticator app. - [Set up an authenticator app](https://vpsdime.com/knowledgebase/client-area/account/authenticator-app-setup). Switch to fast, offline 6-digit codes. - [Email login codes](https://vpsdime.com/knowledgebase/client-area/account/email-login-codes). The default codes we email you, and what to do if one doesn't arrive. - [Backup codes](https://vpsdime.com/knowledgebase/client-area/account/backup-codes). Your fallback when you lose your authenticator. - [Keeping your account secure](https://vpsdime.com/knowledgebase/client-area/account/keeping-your-account-secure). A short checklist, and spotting suspicious activity. ### Managing your account - [Account details](https://vpsdime.com/knowledgebase/client-area/account/account-details). Update your name, email, address, billing contact, and marketing preferences. - [Change password](https://vpsdime.com/knowledgebase/client-area/account/change-password). Change your password when you know your current one. - [Sign-in Methods](https://vpsdime.com/knowledgebase/client-area/account/manage-sign-in-methods). Link or disconnect Google/GitHub, and set a password. - [Contacts & sub-accounts](https://vpsdime.com/knowledgebase/client-area/account/contacts-and-sub-accounts). Add people as email contacts, or as sub-accounts with their own limited login. - [Email history](https://vpsdime.com/knowledgebase/client-area/account/email-history). Read the emails we've sent to your account. - [Transferring a service](https://vpsdime.com/knowledgebase/client-area/account/transfer-a-service). Move a VPS to another person's account. ### Stuck? - [I can't sign in](https://vpsdime.com/knowledgebase/client-area/account/cant-sign-in). Work through the common causes, and how to reach us. - [Account closed](https://vpsdime.com/knowledgebase/client-area/account/account-closed). Why an account may be closed, and how to ask us to review it. - [Deleting your account & data](https://vpsdime.com/knowledgebase/client-area/account/delete-your-account). Request permanent deletion of your account and personal data. --- Still need a person? You can [open a support ticket](https://vpsdime.com/open-ticket/) any time. --- ## Signing in URL: https://vpsdime.com/knowledgebase/client-area/account/signing-in Last reviewed: 2026-07-02 Summary: How to sign in to your VPSDime account with your email and password, including the "verify you're human" check and forgotten passwords. ### What this is How to get into your account from the VPSDime sign-in page. Sign in at https://vpsdime.com/clientarea. ### Steps 1. Open the sign-in page (the **Sign In** / client area link on vpsdime.com). 2. Enter the **email address** and **password** for your account and submit. 3. If two-factor authentication is on (it is, for every account), you'll be asked for a verification code next. See [Two-factor authentication](https://vpsdime.com/knowledgebase/client-area/account/two-factor-overview). You can also skip the password entirely with [Sign in with Google or GitHub](https://vpsdime.com/knowledgebase/client-area/account/sign-in-with-google-or-github). ### What you'll see ![The VPSDime sign-in form, headed "Welcome Back", with email and password fields, a Remember Me checkbox, a Forgot Password? link, and Google / GitHub sign-in buttons](https://vpsdime.com/knowledgebase/client-area/account/images/cropped/signing-in-form.png) - The sign-in screen is headed **"Welcome Back"** with **email** and **password** fields, plus **Sign in with Google / GitHub** buttons. - Sometimes a **"verify you're human"** check (a small Cloudflare box) appears above the button. This only shows up after a few failed attempts. Tick it and sign in as normal. - A wrong email or password shows an **"incorrect"** error; your details aren't changed, you can just try again. ### Staying signed in Tick **Remember me** on the sign-in page to stay signed in on that device, so you don't have to enter your details (and a code) every visit. Leave it **unticked on shared or public computers**. Signing out, or changing your password, ends "remember me" everywhere. ### Troubleshooting - **"Login incorrect" / wrong password.** Re-enter carefully (watch for caps lock). If you've forgotten it, reset it from the **Forgot password?** link on the sign-in page and we'll email you a reset link. See [Reset a forgotten password](https://vpsdime.com/knowledgebase/client-area/account/reset-password). If you originally signed up with Google or GitHub and never set a password, you may not have one yet: use [Sign in with Google or GitHub](https://vpsdime.com/knowledgebase/client-area/account/sign-in-with-google-or-github), or set a password from [Sign-in Methods](https://vpsdime.com/knowledgebase/client-area/account/manage-sign-in-methods). - **The "verify you're human" box appears (or won't complete).** It's a safety check that shows after repeated attempts. Complete the check and sign in. If it won't load, try a different browser, or turn off a VPN/ad-blocker that may be blocking it, then retry. - **It asks for a code after my password.** That's normal. It's your second step. See [Email login codes](https://vpsdime.com/knowledgebase/client-area/account/email-login-codes) or [Set up an authenticator app](https://vpsdime.com/knowledgebase/client-area/account/authenticator-app-setup). - **I don't remember which email my account uses.** Open a ticket (below) and we'll help you locate it. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address you're trying to sign in with, - whether it's the **password** or a **verification code** that's being rejected, - a screenshot of the screen and any error message. ### Related questions - "I can't log in to my account." - "I forgot my password." - "Why does it ask me to verify I'm human?" - "Where do I sign in?" --- ## Reset a forgotten password URL: https://vpsdime.com/knowledgebase/client-area/account/reset-password Last reviewed: 2026-07-02 Summary: Reset your password when you can't remember it, using the "Forgot password?" link and the emailed reset link, including what to do if the link expires or you signed up with Google or GitHub. ### What this is If you can't remember your password, you can reset it yourself from the sign-in page. We email you a link, and you set a new one. This is different from [changing your password](https://vpsdime.com/knowledgebase/client-area/account/change-password) while you're already signed in: that needs your current password, this doesn't. Reset it at https://vpsdime.com/pwreset. ### Steps 1. On the sign-in page, click **Forgot password?**. This opens the **Lost Password Reset** page. 2. Enter the **email address** on your account and click **Submit**. 3. We email you instructions with a reset link. Open your inbox and click the link. 4. On the page the link opens, enter your **New Password**, confirm it, and click **Save Changes**. 5. You'll see **"Password Updated!"**. Click **Sign In to Your Account** and sign in with the new password. ### What you'll see - **The request page ("Lost Password Reset"):** a short note, *"If you have forgotten your password, you can reset it here. When you fill in your registered email address, you will be sent instructions on how to reset your password."*, an **Email Address** field, and a **Submit** button. ![The Lost Password Reset request page with an Email Address field and a Submit button](https://vpsdime.com/knowledgebase/client-area/account/images/cropped/reset-password-request.png) - **After you submit:** a **"Validation Email Sent"** confirmation, *"The password reset process has now been started. Please check your email for instructions on what to do next,"* and a **Back to Login** button. - **The reset link page:** **New Password** and **Confirm New Password** fields with a **Password Strength** meter, and a **Save Changes** button. ![The page the reset link opens: New Password and Confirm New Password fields, a Password Strength meter, and a Save Changes button](https://vpsdime.com/knowledgebase/client-area/account/images/cropped/reset-password-new-password.png) - **On success:** a **"Password Updated!"** screen (*"Password Reset Successful"*) with a **Sign In to Your Account** button. - **If the link is bad:** an **"Invalid Link"** page (*"Link Invalid or Expired"*) with a **Request New Reset Link** button. ### Things worth knowing - **The reset link is time-limited and single-use.** If you land on the **Invalid Link** page, the link has expired or already been used. Click **Request New Reset Link** and start again. - **Two-factor still applies.** Resetting your password doesn't turn off two-factor authentication. After you sign in with the new password, you'll still be asked for your code (email or authenticator). See [Two-factor authentication](https://vpsdime.com/knowledgebase/client-area/account/two-factor-overview). - **Signed up with Google or GitHub?** If you never set a password, there may be nothing to reset. Just [sign in with Google or GitHub](https://vpsdime.com/knowledgebase/client-area/account/sign-in-with-google-or-github), or set a password from [Sign-in Methods](https://vpsdime.com/knowledgebase/client-area/account/manage-sign-in-methods). - **If your account has a security question,** you'll be asked it after entering your email, before the reset email is sent. - **Know your current password and just want to change it?** Use [Change password](https://vpsdime.com/knowledgebase/client-area/account/change-password) instead. ### Troubleshooting - **The reset email didn't arrive.** Give it a minute, then check your **spam/junk** folder. Make sure you used the exact email address on your account. Still nothing? Request the reset again. - **"Link Invalid or Expired."** Reset links don't last forever and work only once. Click **Request New Reset Link** for a fresh one, and use the newest email. - **I don't have a password to reset (I use Google/GitHub).** Sign in with your provider, or set a password from [Sign-in Methods](https://vpsdime.com/knowledgebase/client-area/account/manage-sign-in-methods). - **My new password is rejected.** Choose a stronger one: longer, with a mix of letters, numbers, and symbols. - **I no longer have access to the account's email.** You can't receive the reset link without it. Contact us (below) so we can help you recover access. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address on your account, - whether you're stuck on the request page, the email, or the new-password page, - a screenshot of any error. **Never put your password in a ticket.** We don't need it and will never ask for it. ### Related questions - "I forgot my password, how do I reset it?" - "Where's the forgot password link?" - "I didn't get the password reset email." - "My reset link says it's invalid or expired." - "I signed up with Google, how do I get a password?" --- ## Sign in with Google or GitHub URL: https://vpsdime.com/knowledgebase/client-area/account/sign-in-with-google-or-github Last reviewed: 2026-07-02 Summary: Use one-click Google or GitHub sign-in, including the first-time confirmation email and signing in with no password. ### What this is Instead of an email and password, you can sign in with your **Google** or **GitHub** account in one click. It works on the sign-in page, the sign-up page, and during checkout. There's no password to remember. Manage it at https://vpsdime.com/manageoauth. ### Steps ![The sign-in form with Google and GitHub buttons below the email and password fields, under "or continue with"](https://vpsdime.com/knowledgebase/client-area/account/images/cropped/signing-in-form.png) 1. On the sign-in (or sign-up) screen, click **Sign in with Google** or **Sign in with GitHub**. 2. Approve the request on Google's / GitHub's page. 3. You'll be brought back and signed in. The first time, see *What you'll see* below. There may be a quick one-time confirmation. ### What you'll see - **First time, if you already have a VPSDime account with that email:** for your security we email you a confirmation link. Open it and you'll land on a **"Confirm your sign-in"** page, then click the button there to link the provider and continue. (We do this so only the real account owner can attach Google/GitHub.) - **First time, with a new email (no account yet):** you'll be taken to finish creating your account, pre-filled from your Google/GitHub profile, with **"no password needed."** - **Every time after that:** one click signs you straight in. If you also use an [authenticator app](https://vpsdime.com/knowledgebase/client-area/account/authenticator-app-setup), you'll still be asked for that 6-digit code. ### Troubleshooting - **"Your … email address is not verified."** We only accept providers that have verified your email. Verify your email with Google/GitHub first, then try again. - **"Sign-in was cancelled or rejected by the provider."** You closed or declined the approval screen. Click the button again and approve it. - **I didn't get the confirmation email.** Check your spam folder. The link is valid for 30 minutes and opens a page with a **Confirm** button (clicking the link alone won't complete it, so press the button). If it expired, just start the sign-in again to get a fresh one. - **"This … account is already linked to a different account."** That Google/GitHub identity is connected to another VPSDime account. Sign in to that one, or contact us if you've lost access. - **The email belongs to a different VPSDime account.** You can't link a provider whose email is registered to someone else's account. Sign in to the correct account, or reach out below. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address on your Google/GitHub account, - which provider you're using (Google or GitHub), - the exact message you see (a screenshot is ideal). ### Related questions - "How do I sign in with Google / GitHub?" - "I clicked the confirmation email but it didn't work." - "Can I log in without a password?" - "It says my account is already linked somewhere else." --- ## Creating an account URL: https://vpsdime.com/knowledgebase/client-area/account/creating-an-account Last reviewed: 2026-07-02 Summary: How to sign up for VPSDime, either from the sign-up page or while checking out, with email/password or with Google/GitHub. ### What this is How to create a VPSDime account, either up front on the sign-up page or as part of placing your first order. Create one at https://vpsdime.com/register. ### Steps **On the sign-up page** 1. Open the **Register / Sign Up** page. 2. Either click **Sign in with Google / GitHub** to create your account from that profile (no password to set), or fill in your details and choose a password. 3. Accept the Terms of Service and complete the **"verify you're human"** check, then submit. **During checkout (in the cart)** 1. At checkout you'll see a **New client** / **Existing client** toggle. 2. Choose **New client** and either use **Sign in with Google / GitHub** or fill in your details, then continue your order. 3. Choose **Existing client** instead if you already have an account, and sign in. ### What you'll see ![The Register form with Google and GitHub buttons at the top, Personal Information and Billing Address fields, a Terms of Service checkbox, and a Register button](https://vpsdime.com/knowledgebase/client-area/account/images/cropped/register-form.png) - **On the sign-up page:** Google and GitHub buttons at the top, then **Personal Information** (first and last name, optional company, email, and a password with a strength meter) and a **Billing Address** (street, city, state/region, postcode, country, phone). At the bottom, a **"verify you're human"** check (a small Cloudflare box that usually clears itself), the **Terms of Service** checkbox, and a **Register** button. - If you start with Google/GitHub, the form pre-fills and shows **"Continuing as you@example.com. Verified via Google. No password needed."** A small ✕ on that banner lets you switch back to using a password instead. - In the cart, the **New client / Existing client** toggle sits above the form so you can flip between signing up and signing in. ### Troubleshooting - **"A user already exists with that email address."** You already have an account. Head to [Signing in](https://vpsdime.com/knowledgebase/client-area/account/signing-in) (or use [Google/GitHub](https://vpsdime.com/knowledgebase/client-area/account/sign-in-with-google-or-github)) instead of creating a new one. Forgotten the password? Reset it from the sign-in page. - **"This email address is registered as a sign-in contact on another customer's account."** That email is set up as a login contact under a different account. Sign in with your existing credentials, or contact us if you've lost access. - **The "verify you're human" check won't complete.** Try a different browser, or disable a VPN/ad-blocker that may be blocking it, then submit again. - **It won't accept my password.** Choose a stronger one (longer, mixed characters). Very weak passwords are rejected at sign-up. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address you're trying to register, - the exact message you're seeing (for example "already exists"), - a screenshot of the screen. ### Related questions - "How do I create an account?" - "How do I sign up during checkout?" - "It says my email already exists when I try to register." - "Can I sign up with Google instead of a password?" --- ## Two-factor authentication (overview) URL: https://vpsdime.com/knowledgebase/client-area/account/two-factor-overview Last reviewed: 2026-07-02 Summary: How two-factor authentication works at VPSDime, with email login codes by default and the option to switch to an authenticator app. ### What this is Two-factor authentication (2FA) adds a second step after your password, so a leaked password alone can't get into your account. **Every VPSDime account has 2FA on.** You can't turn it off, but you choose *how* you receive the second step: Manage it at https://vpsdime.com/2fa. - **Email login codes (default).** At each sign-in we email you a 6-digit code to enter. Nothing to set up. - **Authenticator app (optional upgrade).** An app on your phone (Google Authenticator, Authy, 1Password, …) generates the code instantly, even with no internet, and no waiting on email. You can switch from email codes to an app, and back, at any time. ### Steps - To see or change your method, go to **My Account → Two-Factor Authentication**. - To switch to an app, follow [Set up an authenticator app](https://vpsdime.com/knowledgebase/client-area/account/authenticator-app-setup). - To go back to email codes, open the same page and choose **Remove authenticator app**. Your account falls back to email codes automatically. ### What you'll see On **My Account → Two-Factor Authentication** there's a status card that reads either: - **"Email login codes are on"** with a **Set up an authenticator app** button, or ![The Two-Factor Authentication status card reading "Email login codes are on" with a Set up an authenticator app button](https://vpsdime.com/knowledgebase/client-area/account/images/cropped/2fa-status-email.png) - **"Authenticator app is on"** with **Regenerate backup code** and **Remove authenticator app** buttons. ![The Two-Factor Authentication status card reading "Authenticator app is on" with Regenerate backup code and Remove authenticator app buttons](https://vpsdime.com/knowledgebase/client-area/account/images/cropped/2fa-status-app.png) ### Troubleshooting - **Can I turn 2FA off completely?** No. For account safety it's always on. You can switch between email codes and an app, but one of them is always active. - **I'm not getting my email codes.** See [Email login codes](https://vpsdime.com/knowledgebase/client-area/account/email-login-codes), or switch to an [authenticator app](https://vpsdime.com/knowledgebase/client-area/account/authenticator-app-setup) so codes don't depend on email. - **I lost my authenticator app.** Use a [backup code](https://vpsdime.com/knowledgebase/client-area/account/backup-codes) to get in, then reset your method. No backup code either? See [I can't sign in](https://vpsdime.com/knowledgebase/client-area/account/cant-sign-in). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address you sign in with, - whether you're on email codes or an authenticator app, - what you're seeing (a screenshot helps). ### Related questions - "How does two-factor authentication work here?" - "Can I disable 2FA?" - "What's the difference between email codes and an authenticator app?" - "How do I change my 2FA method?" --- ## Set up an authenticator app URL: https://vpsdime.com/knowledgebase/client-area/account/authenticator-app-setup Last reviewed: 2026-07-02 Summary: Turn on app-based two-factor codes (TOTP) so you sign in with a 6-digit code from an app instead of waiting for an email. ### What this is Your account is always protected by two-factor authentication. By default we email you a one-time code at each sign-in. You can replace those emails with an **authenticator app** (like Google Authenticator) that generates a 6-digit code on your phone. App codes are faster, work offline, and don't depend on email delivery. Set it up at https://vpsdime.com/2fa. You only need to set this up once. ### Before you start - You'll need to be signed in to your account. - Install an authenticator app on your phone if you don't have one: **Google Authenticator**, **Authy**, **1Password**, or any other TOTP app. ### Steps 1. Go to **My Account → Two-Factor Authentication**. 2. You'll see **"Email login codes are on."** Click **Set up an authenticator app**. 3. The **"Set up your authenticator app"** panel opens with a QR code. 4. In your authenticator app, add a new account and **scan the QR code**. (Can't scan? Under the QR there's a **"Can't scan? Enter this key manually:"** line with a key you can type into the app instead.) 5. Your app now shows a 6-digit code that changes every 30 seconds. Type the current code into the **6-digit code** box and click **Verify & enable**. 6. We'll show you a **backup code**. Write it down and keep it safe (see *What you'll see* below). Click **I've saved it** when done. That's it. From now on, signing in will ask for the code from your app instead of emailing you one. ### What you'll see - **Status card:** before setup it reads *"Email login codes are on."* After setup it reads *"Authenticator app is on,"* with **Regenerate backup code** and **Remove authenticator app** buttons. - **Setup panel:** a QR code, a manual entry key beneath it, and a **Verify & enable** button (plus **Cancel**). ![The "Set up your authenticator app" panel with a QR code, a manual entry key below it, a 6-digit code box, and a Verify & enable button](https://vpsdime.com/knowledgebase/client-area/account/images/cropped/2fa-setup-panel.png) - **Backup code panel ("Save your backup code"):** a single one-time code shown **once**. The page warns: *"Store it somewhere safe. It won't be shown again."* This code lets you sign in if you ever lose your phone. Save it before clicking **I've saved it**. ![The "Save your backup code" panel showing a one-time backup code and an "I've saved it" button](https://vpsdime.com/knowledgebase/client-area/account/images/cropped/2fa-backup-code-panel.png) ### Troubleshooting - **"That code did not match" / the code isn't accepted.** Authenticator codes are time-based, so this is almost always your phone's clock being slightly off. Turn on automatic date & time on your phone, then try the current code again. Also make sure you're typing the latest code (it changes every 30 seconds) with no spaces. - **You can't scan the QR code.** Use the **"Enter this key manually"** key shown under the QR, then add the account in your app by typing that key instead. - **It says an authenticator app is already active.** You've already set one up. To switch to a new phone or app, first click **Remove authenticator app**, then set it up again. - **You set up the app but lost or replaced your phone.** Sign in using the **backup code** you saved during setup, then go to **My Account → Two-Factor Authentication** and remove or re-set the authenticator. If you don't have your backup code either, see [I can't sign in](https://vpsdime.com/knowledgebase/client-area/account/cant-sign-in). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address you sign in with, - which authenticator app you're using (Google Authenticator, Authy, etc.), - what happens and the exact message you see (a screenshot of the screen is ideal). ### Related questions - "How do I turn on two-factor authentication?" - "How do I set up Google Authenticator / Authy / 1Password?" - "How do I use an app for my login codes instead of email?" - "Where do I add 2FA to my account?" - "My authenticator code isn't working." --- ## Email login codes URL: https://vpsdime.com/knowledgebase/client-area/account/email-login-codes Last reviewed: 2026-07-04 Summary: The 6-digit codes VPSDime emails you at sign-in by default, and what to do if one doesn't arrive. ### What this is Unless you've set up an authenticator app, this is your second sign-in step: after your password (or a Google/GitHub sign-in), we email a **6-digit code** to your account address. Enter it to finish signing in. Sign in at https://vpsdime.com/clientarea. ### Steps 1. Sign in as usual. You'll land on a **"Verify It's You"** screen. 2. Check your email for a message titled **"Confirm your login request"** containing a 6-digit code. 3. Type the code into the box and continue. The code is good for **5 minutes**. Prefer not to wait for emails? [Set up an authenticator app](https://vpsdime.com/knowledgebase/client-area/account/authenticator-app-setup) for instant codes that work offline. ### What you'll see ![The "Verify It's You" screen telling you a code was sent to your email, with a 6-digit code box and a Verify Code button](https://vpsdime.com/knowledgebase/client-area/account/images/cropped/email-code-verify-form.png) - The verification screen tells you a code was sent to your email and gives you a box to enter it. - The email comes from VPSDime with the subject **"Confirm your login request"** and shows the code plus the IP address the sign-in came from. ### Troubleshooting - **The code didn't arrive.** Give it a minute, then check your **spam/junk** folder. Make sure you're checking the inbox for the exact email address on your account. Still nothing? Start the sign-in again to send a fresh code. - **The code says it's wrong or expired.** Codes expire after 5 minutes and each new sign-in sends a new one, so always use the most recent email and ignore older codes. - **I never receive codes (every time).** Email may not be reaching you reliably. The best fix is to [set up an authenticator app](https://vpsdime.com/knowledgebase/client-area/account/authenticator-app-setup), which doesn't depend on email. If you can't, contact us below. - **My account email is hosted on my own VPS, and that VPS is suspended or down.** The code can't be delivered because the mail server it goes to is the thing that's offline. See the section below, we can verify you and temporarily lift the email code so you can get back in. - **Wrong email address on the account.** If codes go to an old address you no longer control, open a ticket and we'll help you recover access and update it. ### My email runs on my VPS, and the VPS is suspended A special case worth naming: you host your own mail server **on your VPSDime VPS**, an invoice went overdue, the VPS got suspended, and now the login code can't reach you because the mail server it would be delivered to is the thing that's down. You can't sign in to pay the invoice, and paying the invoice is what would bring your email back. Here's how we break that loop: 1. **Contact us from any email address you have access to**, a personal Gmail is fine: [open a ticket](https://vpsdime.com/open-ticket/). 2. In the message, tell us **the email address of your VPSDime account**, and confirm **one** of the following so we can verify the account is yours: - one of your **VPS IP addresses**, or - an **invoice number** from your account, or - the **address on file** for the account. 3. Once verified, we **temporarily disable the email login code** on your account so you can sign in with just your password. 4. Sign in and settle the invoice. **The email code protection re-enables automatically** after you're back in, there's nothing to switch back on. To make sure this never happens again, set up a sign-in method that doesn't depend on your email being reachable: - **[Set up an authenticator app](https://vpsdime.com/knowledgebase/client-area/account/authenticator-app-setup)**, codes are generated on your phone, offline, no email involved, or - **[Connect your Google or GitHub account](https://vpsdime.com/knowledgebase/client-area/account/sign-in-with-google-or-github)** and sign in through them. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address you sign in with, - whether you checked spam and roughly when you requested the code, - a screenshot of the verification screen. ### Related questions - "I didn't get my login code." - "My verification code isn't working." - "Where is my 2FA email?" - "Can I stop waiting for email codes?" - "My mail server is on my VPS and it's suspended, how do I log in?" - "I can't receive the login code because my email is down." - "Can you disable the email code so I can sign in and pay my invoice?" --- ## Backup codes URL: https://vpsdime.com/knowledgebase/client-area/account/backup-codes Last reviewed: 2026-07-02 Summary: What your two-factor backup code is, how to sign in with it if you lose your authenticator app, and how to get a new one. ### What this is A **backup code** is a one-time code that lets you sign in if you ever lose access to your authenticator app. You're shown one when you set up the app, and a fresh one each time you use it. Keep it somewhere safe and separate from your phone. Manage it at https://vpsdime.com/2fa. Backup codes apply when you're using an **authenticator app**. (On email login codes, your recovery is simply your email inbox.) ### Steps **Using a backup code to sign in** 1. Sign in with your password (or Google/GitHub). On the **"Verify It's You"** screen, choose the option to sign in **with a backup code** instead of the app. 2. Enter your saved backup code. 3. You're signed in. We immediately **replace** the used code and show you a new one on a **"Save your new backup code"** screen, so write it down before continuing. ![The "Verify It's You" screen with a Backup Code field and a Login button](https://vpsdime.com/knowledgebase/client-area/account/images/cropped/backup-code-login-form.png) **Getting a fresh code any time** - Go to **My Account → Two-Factor Authentication** and click **Regenerate backup code**. You'll confirm your password, and we'll show the new code once. ### What you'll see - During app setup, a **"Save your backup code"** box: *"Store it somewhere safe. It won't be shown again."* - After using one to sign in, a **"Save your new backup code"** screen with the replacement and an **I've saved it, continue** button. - A backup code is four short groups, e.g. `abcd 1234 ef56 7890`. ### Troubleshooting - **My backup code didn't work.** Backup codes are single-use. If you've already used it, the old one no longer works, so use the newest one we showed you afterward. Spaces don't matter, but make sure you're using the most recent code. - **I lost both my phone and my backup code.** You'll need our help to safely restore access. See [I can't sign in](https://vpsdime.com/knowledgebase/client-area/account/cant-sign-in) and open a ticket below. - **I want a fresh code but don't remember setting one up.** If you're on email login codes (not an app), there are no backup codes; your recovery is your email. See [Two-factor authentication](https://vpsdime.com/knowledgebase/client-area/account/two-factor-overview). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address on your account, - whether you still have your authenticator app or have lost it, - a screenshot of the screen you're stuck on. ### Related questions - "How do I use a backup code?" - "I lost my phone, how do I get in?" - "How do I get a new backup code?" - "My backup code isn't working." --- ## Keeping your account secure URL: https://vpsdime.com/knowledgebase/client-area/account/keeping-your-account-secure Last reviewed: 2026-07-02 Summary: Simple steps to keep your VPSDime account safe, and what to do if you notice something suspicious. ### What this is A short checklist for keeping your account safe. Most of it takes a couple of minutes. ### The essentials - **Use a strong, unique password.** Don't reuse a password from another site. You can change it any time on [Change password](https://vpsdime.com/knowledgebase/client-area/account/change-password). - **Switch to an authenticator app.** App codes are stronger and faster than emailed ones. See [Set up an authenticator app](https://vpsdime.com/knowledgebase/client-area/account/authenticator-app-setup). Two-factor is always on either way. - **Save your backup code.** If you use an authenticator app, keep your [backup code](https://vpsdime.com/knowledgebase/client-area/account/backup-codes) somewhere safe and separate from your phone, so a lost device doesn't lock you out. - **Consider Google/GitHub sign-in.** Linking a provider on [Sign-in Methods](https://vpsdime.com/knowledgebase/client-area/account/manage-sign-in-methods) means one less password to manage. - **On shared or public computers,** don't tick "Remember me," and sign out when you're done. ### Spotting something wrong - **We email a login code with the IP address** the sign-in came from. If you receive a code you didn't request, someone may have your password, so **change it right away** and turn on an authenticator app. - **We will never ask for your password.** Not by email, not in a support ticket, never. Anyone who does is not us. - Only ever enter your password on our own sign-in page. ### If you think your account was accessed Change your password immediately (this signs out other devices), and [open a ticket](https://vpsdime.com/open-ticket/) so we can help you review it. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address on your account, - what you noticed (an unexpected login code, an email you didn't expect, etc.), - a screenshot if you have one. We'll never ask for your password. ### Related questions - "How do I keep my account secure?" - "I got a login code I didn't request." - "I think someone accessed my account." - "Is this email really from you?" --- ## Account details URL: https://vpsdime.com/knowledgebase/client-area/account/account-details Last reviewed: 2026-07-05 Summary: View and update your profile, including name, company, email, address, phone, billing contact, and marketing email preferences. ### What this is Your profile: the name, email, address, and phone on file, plus a couple of account preferences. Update it at **My Account → Account Details** (https://vpsdime.com/accountdetails). ### Steps 1. Go to **My Account → Account Details**. 2. Change any field you need. 3. Click **Save Changes** at the bottom. ### What you'll see ![The Account Details page with contact fields, Default Billing Contact selector, Newsletter Opt-out checkbox, GST/VAT number fields, and a Save Changes button](https://vpsdime.com/knowledgebase/client-area/account/images/account-details.png) - The usual contact fields: first/last name, company, **email**, address, city, state, postcode, phone. - **Default Billing Contact**: pick which contact (if you've added any) receives invoices and billing emails. See [Contacts & sub-accounts](https://vpsdime.com/knowledgebase/client-area/account/contacts-and-sub-accounts). - **Newsletter Opt-out**: a checkbox to stop marketing/announcement emails. You'll still receive essential account, billing, and service emails. - **Product Listing - Show Active Only**: a checkbox that hides cancelled and terminated services from your [My Services](https://vpsdime.com/knowledgebase/client-area/services/my-services) list. It's the same setting as the **Hide Cancelled Services** button on that page, changing either one updates both. - Some fields may appear **greyed out / locked**. These are set on our side and can't be self-edited. - **GST Number** and **VAT Number** at the bottom, both optional. Enter either one and it will be shown on your invoices. ### Things worth knowing - **Your email is also where your login codes go.** If you change it here, future verification codes and all account emails go to the new address, so make sure it's an inbox you control. See [Email login codes](https://vpsdime.com/knowledgebase/client-area/account/email-login-codes). - **Address changes don't update past invoices.** A new billing address or company name applies to **future invoices only**; invoices already generated or paid keep the details they were issued with, they're records of what was billed at the time, not living documents. If you need an existing invoice **reissued with corrected details** (a company name for your accounting, a missing address line), [open a ticket](https://vpsdime.com/open-ticket/) with the invoice number and what should change. The same goes for a VAT/GST number added after the fact, it appears on invoices from now on, not retroactively. - **Using a Default Billing Contact? Invoices carry the contact's details.** When a billing contact is selected, invoices are issued with **that contact's name, company, and address**, not your main profile's. So if new invoices show details that look wrong or outdated, and editing this page changes nothing, the details live on the contact: edit them at [Contacts / Sub-Accounts](https://vpsdime.com/knowledgebase/client-area/account/contacts-and-sub-accounts), or set Default Billing Contact back to None to use your main profile again. - **Tax IDs on invoices.** Adding your **GST Number** or **VAT Number** here makes it show on your future invoices, which is handy for business and tax records. Both are optional. (To have tax removed from a payment, you also enter the number on the payment form at checkout, see [Taxes](https://vpsdime.com/knowledgebase/billing/taxes).) - Changing your **password** is a separate page. See [Change password](https://vpsdime.com/knowledgebase/client-area/account/change-password). ### Troubleshooting - **A field is greyed out and I can't edit it.** That field is locked on our side. Open a ticket and we'll update it for you. - **"A user already exists with that email address" when I change my email.** That email is already on another account. Use a different address, or contact us if you think it's a mistake. - **I changed my email to the wrong address and now I'm not getting codes/emails.** Contact us (below) and we'll help you correct it and regain access. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address on your account, - which detail you're trying to change, - a screenshot of the screen or any error. ### Related questions - "How do I update my account details?" - "How do I change my email address?" - "How do I stop marketing emails?" - "What is a billing contact?" - "How do I add my VAT or GST number to my invoices?" - "I updated my address, why do old invoices still show the previous one?" - "I changed my details but new invoices still show different information." - "Can you reissue an invoice with my correct company details?" --- ## Change password URL: https://vpsdime.com/knowledgebase/client-area/account/change-password Last reviewed: 2026-07-02 Summary: Change your account password from the client area, when you know your current one. ### What this is Change the password on your account when you're signed in and know your current one. Find it at **My Account → Change Password** (https://vpsdime.com/changepassword). ### Steps 1. Go to **My Account → Change Password**. 2. Enter your **current password**, then your **new password** twice. 3. Click **Save Changes**. ### What you'll see ![The Change Password page with Existing Password, New Password, and Confirm New Password fields, a password-strength indicator, and a Save Changes button](https://vpsdime.com/knowledgebase/client-area/account/images/change-password.png) - Three fields (**Existing Password**, **New Password**, **Confirm New Password**) and a password-strength indicator. Choose something strong; very weak passwords are rejected. ### Things worth knowing - This page needs your **current** password. If you've **forgotten** it, use the **Forgot password?** link on the sign-in page instead. See [Reset a forgotten password](https://vpsdime.com/knowledgebase/client-area/account/reset-password). - If you **signed up with Google or GitHub** and never set a password, you won't have a current one to enter. Set one from [Sign-in Methods](https://vpsdime.com/knowledgebase/client-area/account/manage-sign-in-methods) (the **Set a Password** option). You'll be sent there automatically if you land on this page without a password. - **Changing your password signs you out on your other devices.** You stay signed in here; anywhere else will need the new password next time. ### Troubleshooting - **"Existing password incorrect."** Re-enter your current password carefully. If you can't recall it, reset it from the sign-in page's **Forgot password?** link. See [Reset a forgotten password](https://vpsdime.com/knowledgebase/client-area/account/reset-password). - **My new password is rejected.** Pick a stronger one: longer, with a mix of characters. - **There's no current password to enter (I use Google/GitHub).** Go to [Sign-in Methods](https://vpsdime.com/knowledgebase/client-area/account/manage-sign-in-methods) and use **Set a Password** instead. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address on your account, - whether it's your **current** or **new** password being rejected, - a screenshot of the error. **Never put your password in a ticket.** We don't need it and will never ask for it. ### Related questions - "How do I change my password?" - "It says my existing password is incorrect." - "I signed up with Google, how do I set a password?" - "How do I reset a password I've forgotten?" --- ## Sign-in Methods URL: https://vpsdime.com/knowledgebase/client-area/account/manage-sign-in-methods Last reviewed: 2026-07-02 Summary: Manage how you sign in, link or disconnect Google/GitHub, and set a password on an account created with a provider. ### What this is The **Sign-in Methods** page (https://vpsdime.com/manageoauth) lets you control how you get into your account: which sign-in providers (Google, GitHub) are linked, and whether you have a password. Find it at **My Account → Sign-in Methods**. ### Steps **Link another provider** 1. Go to **My Account → Sign-in Methods**. 2. Under **Link Another Provider**, click the provider you want. 3. Approve it with the provider; you'll return with it linked. **Disconnect a provider** 1. On the same page, find it under **Linked Providers** and click **Disconnect**. **Set a password** (if you signed up with Google/GitHub and never had one) 1. On the same page, use the **Set a Password** card to choose a password. 2. After that you can also sign in with your email and password as a backup. ### What you'll see ![The Sign-in Methods page with a Google account under Linked Providers (with a Disconnect button), a Link Another Provider section offering GitHub, and Recent Activity below](https://vpsdime.com/knowledgebase/client-area/account/images/signin-methods-linked.png) - **Linked Providers**: a list of your connected providers with when each was linked and last used, and a **Disconnect** button. - **Link Another Provider**: buttons for providers you haven't linked yet. - **Set a Password**: only shown if your account was created with a provider and has no password yet. - **Recent Activity**: a short history of your sign-in events. ### Troubleshooting - **The Disconnect button is greyed out / "This is your only sign-in method."** You can't remove your last way in. **Set a password first** (on the same page), then you can disconnect the provider safely. - **I can't link a provider: "email is registered to a different account."** That provider's email belongs to another VPSDime account. Sign in to that account instead, or contact us if you've lost access. - **I don't see a "Set a Password" option.** That section only appears for accounts created via Google/GitHub that don't have a password yet. If you already have one, use [Change password](https://vpsdime.com/knowledgebase/client-area/account/change-password) instead. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address on your account, - which provider you're trying to link or disconnect, - the exact message you see (a screenshot is ideal). ### Related questions - "How do I connect / disconnect Google or GitHub?" - "How do I set a password if I signed up with Google?" - "Why can't I remove my linked account?" - "Where do I manage my sign-in methods?" --- ## Contacts & sub-accounts URL: https://vpsdime.com/knowledgebase/client-area/account/contacts-and-sub-accounts Last reviewed: 2026-07-05 Summary: Add other people to your account, as contacts who receive certain emails, and/or as sub-accounts who can sign in with their own login and limited access. ### What this is A way to bring other people (a colleague, an accountant, a developer) onto your account. There are two levels, and they're set in the same place, at **My Account → Contacts / Sub-Accounts**: Find it at https://vpsdime.com/contacts. - **Contact**: a person on your account who receives the **email types you choose** (billing, support, etc.). A contact has **no login**. - **Sub-account**: a contact you've also given **client-area access**, with their own email and password, limited to the **permissions you select**. You can have as many as you need, and you choose exactly what each one can see or do. ### Add a contact (and optionally make it a sub-account) ![The Contacts / Sub-Accounts page: a "Choose Contact" list of existing contact cards and an Add New Contact button](https://vpsdime.com/knowledgebase/client-area/account/images/cropped/contacts-choose-contact.png) 1. Go to **My Account → Contacts / Sub-Accounts** and click **Add New Contact**. 2. Fill in their name and details. 3. Choose their **Email Preferences** (which emails they should receive, see below). 4. To let them sign in too, tick **Activate Sub-Account**: *"Tick to configure as a sub-account with client area access."* That reveals a **password** field and the **Sub-Account Permissions** list. Set a password and pick what they may access. 5. Click **Add Contact**. To **edit** or **delete** one later, return to the same page, pick the contact from the list, and change or remove it. ### Email preferences ![The Email Preferences checkboxes on the contact form: General, Product, Domain, Invoice, and Support emails](https://vpsdime.com/knowledgebase/client-area/account/images/cropped/contacts-email-preferences.png) For any contact, tick the categories they should receive: - **General Emails**: general announcements & password reminders - **Product Emails**: order details, welcome emails, etc. - **Domain Emails**: renewal notices, registration confirmations, etc. - **Invoice Emails**: invoices & billing reminders - **Support Emails**: lets this person open tickets on your account ### Sub-account permissions ![The Activate Sub-Account panel with password fields and the Sub-Account Permissions checkboxes](https://vpsdime.com/knowledgebase/client-area/account/images/cropped/contacts-subaccount-panel.png) When **Activate Sub-Account** is ticked, choose what they can do once signed in: - **Modify Master Account Profile**: edit the main account's details - **View & Manage Contacts**: add/edit other contacts and sub-accounts - **View Services**: see your services - **Manage Services**: change services (upgrades, cancellations, etc.) - **View & Pay Invoices**: see and pay invoices - **View & Open Support Tickets**: see and open tickets - **View & Manage Affiliate Account**: access the affiliate area - **View Emails**: see the account's email history - **Place New Orders/Upgrades/Cancellations**: order new services A sub-account only sees the areas you've ticked; anything else shows a "no permission" message. ### How a sub-account signs in They go to the normal [sign-in page](https://vpsdime.com/knowledgebase/client-area/account/signing-in) and use **their own email address and the password you set**, not yours. Their view is limited to the permissions you granted. ### Billing contact If you'd like a specific contact (say, your accounts team) to receive invoices, set them as your **Billing Contact** on [Account Details](https://vpsdime.com/knowledgebase/client-area/account/account-details). One consequence to know: with a billing contact selected, **invoices are issued with the contact's details**, their name, company, and address appear on the invoice instead of your main account's. Keep the contact's details current, since that's what your accounting records will carry, and remember that editing your main profile won't change what invoices show while a billing contact is set. ### Troubleshooting - **"A user already exists with that email address" when adding a sub-account.** That email is already used on an account somewhere. Sub-account logins need their own unique email, so use a different one. - **My sub-account can't see or do something.** They're missing that permission. Edit the contact and tick the relevant box (for example **Manage Services** or **View & Pay Invoices**). - **My sub-account forgot their password.** Edit the contact and set a new password in the sub-account section, then share it with them. - **I don't want a person to log in anymore.** Either untick **Activate Sub-Account** (keeps them as an email contact) or delete the contact entirely. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address on your **main** account, - the contact/sub-account email involved, - what access or email issue you're seeing (a screenshot helps). ### Related questions - "How do I add someone to my account?" - "What's the difference between a contact and a sub-account?" - "How do I give a colleague access without sharing my password?" - "How do I control which emails a contact gets?" - "How do I remove a sub-account?" - "Why do my invoices show my billing contact's details instead of mine?" --- ## Email history URL: https://vpsdime.com/knowledgebase/client-area/account/email-history Last reviewed: 2026-07-02 Summary: View a log of the emails we've sent to your account (invoices, notices, welcome emails and more), and read any of them. ### What this is A record of the emails we've sent to your account: order/welcome emails, invoices and billing reminders, renewal and service notices, and so on. Even if one didn't reach your inbox, you can read it here. Find it at **My Account → Email History** (https://vpsdime.com/emailhistory). ### Steps 1. Go to **My Account → Email History**. 2. Browse the list (newest first; use the column headers to sort by **Date Sent** or **Message Subject**, and the pager for older pages). 3. Click **View Message** on any row to read the full email. ### What you'll see ![The Email History page: a table of Date Sent and Message Subject rows, each with a View Message button, plus a record count and page navigation](https://vpsdime.com/knowledgebase/client-area/account/images/email-history.png) - A table of **Date Sent** and **Message Subject**, with a **View Message** button that opens the email in a popup. - A count of how many emails are on record, with page navigation. ### Things worth knowing - This is a log of what **we sent**. It's handy if you didn't receive something in your own inbox (also check your spam folder). - It's a read-only history; there's no "resend" here. If you need a copy actioned (for example a fresh invoice), ask us via a ticket. - Want to change **which** emails you receive? Marketing emails are controlled on [Account Details](https://vpsdime.com/knowledgebase/client-area/account/account-details); per-person email types are set under [Contacts & sub-accounts](https://vpsdime.com/knowledgebase/client-area/account/contacts-and-sub-accounts). ### Troubleshooting - **An email isn't in my inbox.** Open it here to read it, and check your spam/junk folder. If important emails consistently don't arrive, contact us so we can check delivery to your address. - **The list is empty.** We haven't sent anything to this account yet, or you're viewing a sub-account without the **View Emails** permission. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address on your account, - the **subject and date** of the email you're asking about, - a screenshot of what you're seeing. ### Related questions - "Where can I see the emails you sent me?" - "I didn't get your email, can I read it somewhere?" - "How do I view a past invoice email?" - "Why is my email history empty?" --- ## Transferring a service to someone else URL: https://vpsdime.com/knowledgebase/client-area/account/transfer-a-service Last reviewed: 2026-07-05 Summary: How to move a VPS to another person's VPSDime account. Transfers are free and cause no downtime, the VPS keeps running untouched with the same IP and data, only billing ownership changes. Covers the open-invoice requirement and the tickets both parties open to confirm the transfer. ### What this is You can transfer a VPS to another person's VPSDime account. It's a deliberate, two-sided process, so a service only moves when both people confirm it. ### Before you start - **Pay any open invoices** on the service first. A service with outstanding invoices can't be transferred until they're settled. - **The new owner needs an account.** If they don't already have one, they can create one at the [sign-up page](https://vpsdime.com/register). See [Creating an account](https://vpsdime.com/knowledgebase/client-area/account/creating-an-account). ### How to transfer Both people open a support ticket so we can confirm the move from each side: 1. **You (current owner):** [open a ticket](https://vpsdime.com/open-ticket/) naming the service and the **email address of the account it should move to**. 2. **The new owner:** opens a ticket from their account naming the same service and **your account's email address**. Once both tickets line up, we'll move the service to the new account. ### Things worth knowing - **Transfers are free.** There's no fee for moving a service between accounts. - **Nothing happens to the VPS itself.** A transfer is an ownership change in our billing system, not a technical operation: the server keeps running throughout, with **no downtime, no reboot**, and the same IP, data, and configuration. Whatever it's hosting won't notice the handover. - We need confirmation from **both** parties before moving a service. - After the transfer, billing and management of the service move to the new owner's account. If the old passwords weren't handed over, the new owner can set fresh ones from the [manage page](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) (root password on Linux, Admin password on Windows). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the service (hostname or IP) being transferred, - the email addresses of both the current and new accounts. ### Related questions - "How do I transfer my VPS to someone else?" - "Can I move a service to a different account?" - "How do I change the owner of my VPS?" - "Can I move my VPS from my account to my customer's account?" - "I sold my VPS, how do I hand it over?" - "Does transferring a VPS cause downtime or change anything on it?" - "Is there a fee to transfer a service to another account?" --- ## I can't sign in URL: https://vpsdime.com/knowledgebase/client-area/account/cant-sign-in Last reviewed: 2026-07-05 Summary: Work through the common reasons you can't get into your VPSDime account, and how to reach support when you need a person. ### What this is A quick map of the usual reasons sign-in fails, with the fastest fix for each. Find your situation below. Sign in at https://vpsdime.com/clientarea. ### Find your situation - **Wrong email or password.** Reset it with the **Forgot password?** link on the sign-in page (see [Reset a forgotten password](https://vpsdime.com/knowledgebase/client-area/account/reset-password)). If you originally used Google/GitHub and never set a password, sign in that way instead, or set one from [Sign-in Methods](https://vpsdime.com/knowledgebase/client-area/account/manage-sign-in-methods). More: [Signing in](https://vpsdime.com/knowledgebase/client-area/account/signing-in). - **My password works but I'm stuck on the code screen.** - On email codes and not receiving them → [Email login codes](https://vpsdime.com/knowledgebase/client-area/account/email-login-codes) (check spam, request a fresh one). - Using an app and the code is rejected → it's usually your phone's clock; see [Set up an authenticator app](https://vpsdime.com/knowledgebase/client-area/account/authenticator-app-setup). - **My account email runs on my own VPS, and that VPS is suspended or down.** The login code can't reach you because the mail server it's sent to is offline, often because the VPS was suspended over the very invoice you're trying to pay. Contact us from any email you have access to, tell us your account email, and confirm a VPS IP, an invoice number, or your account address; we'll verify you and temporarily lift the email code so you can sign in. The full steps are in [Email login codes](https://vpsdime.com/knowledgebase/client-area/account/email-login-codes). - **I lost my phone / authenticator app.** Sign in with a [backup code](https://vpsdime.com/knowledgebase/client-area/account/backup-codes), then reset your method. - **I lost my phone *and* my backup code.** You'll need us to verify you and restore access, so open a ticket below. - **Sign in with Google/GitHub isn't working.** See [Sign in with Google or GitHub](https://vpsdime.com/knowledgebase/client-area/account/sign-in-with-google-or-github) (verify your provider email, click the **Confirm** button on the confirmation page). - **The "verify you're human" check is blocking me.** It appears after repeated attempts. Complete it, or try another browser / turn off a VPN or ad-blocker, then retry. - **Your account has been closed.** When you sign in with the correct details (or via Google/GitHub), you'll see an **"Account Closed"** message; password reset won't work for a closed account either. See [Account closed](https://vpsdime.com/knowledgebase/client-area/account/account-closed) for why this happens and how to ask us to review it. - **"IP banned", or the site refuses to load with an IP-blocked notice.** Your **IP address** has been blocked by our security systems, usually after repeated failed login attempts or activity that looked suspicious from that address. Two things to know: the block is on the **IP, not your account** (the site works fine from another connection), and it **can't be removed from your side**. Switch to a different network, a phone on **mobile data** is the quickest, then [contact us](https://vpsdime.com/open-ticket/) from there (or reply to any email you've received from us) with the banned IP, and our team will review and unblock it. (Blocked from your own **VPS** rather than from our website? That's a different system, see [My IP is blocked from my server](https://vpsdime.com/knowledgebase/troubleshooting/ip-blocked).) ### Still need help? If none of the above gets you in, [open a support ticket](https://vpsdime.com/open-ticket/) and we'll help you get back into your account. We help a lot of customers, so a few specifics get you a faster, first-reply answer. Please include whatever applies: - the **email address** on your account, - if that email itself is unreachable, contact us from one you can use, and confirm a **VPS IP**, an **invoice number**, or your **account address** so we can verify you, - **what you've already tried** and where it stops (password screen, code screen, the provider page), - the **exact message** you see, with a **screenshot** if you can, - for lost-device cases, whether you still have a **backup code**. We'll never ask for your password in a ticket. ### Related questions - "I'm locked out of my account." - "I lost my phone and can't get my 2FA code." - "I lost my authenticator and my backup code." - "Help, I can't log in at all." - "My email is hosted on my suspended VPS and I can't get the login code." - "It says my IP is banned when I try to open the client area." - "Your website won't load for me but works for everyone else." --- ## Account closed URL: https://vpsdime.com/knowledgebase/client-area/account/account-closed Last reviewed: 2026-07-02 Summary: Why an account may be closed by our risk checks, how to ask us to review it if it's a mistake, and what happens to any payment. ### What this is If you're told your account is **closed** when you try to sign in, this explains why that can happen and how to get it sorted if it's not right. ### Why might my account be closed? To protect our platform and our customers, orders go through automated and manual **risk checks**. If an order is flagged as high-risk, we may close the account as a precaution. These checks aren't perfect, and legitimate customers are occasionally caught by them. ### I think this was a mistake That does happen, and we're glad to look into it. [Open a ticket](https://vpsdime.com/open-ticket/) and let us know. We review these individually and reinstate genuine customers. Including a few details that confirm the order is really yours helps us sort it out quickly. ### Was I charged? If a flagged order was paid, the charge is **refunded**, and you'll receive a **refund confirmation email**. There's nothing further you need to do for the refund itself. ### Still need help? [Open a support ticket](https://vpsdime.com/open-ticket/). So we can review it on the first reply, it's worth including: - the email address (and order number, if you have it) on the account, - anything that helps confirm the order is genuinely yours, - a screenshot of the "Account Closed" message you're seeing. We'll never ask for your password in a ticket. ### Related questions - "Why is my account closed?" - "My account was closed by mistake, how do I get it back?" - "Was my order flagged as fraud?" - "Will I get a refund if my account was closed?" - "How do I reopen my account?" --- ## Deleting your account & data URL: https://vpsdime.com/knowledgebase/client-area/account/delete-your-account Last reviewed: 2026-07-02 Summary: How to request permanent deletion of your account and personal data, your privacy rights, and how it differs from an account that's simply closed. ### What this is If you'd like us to **permanently delete your account and personal data**, we can do that on request. This is different from an account being *closed* (see below). ### Before you request So we can delete your account cleanly, it needs to be wound down first: - **No unpaid invoices.** Any outstanding bills must be settled. - **No active or suspended services.** Submit a **cancellation request** for each active or suspended service first (from your Services area). Once everything is cancelled and there's nothing outstanding, we can proceed. ### How to request it There's no self-service button for this. It's deliberate, since deletion can't be undone. **Sign in to your account first**, then [open a support ticket](https://vpsdime.com/open-ticket/) and ask us to delete your account and data. Being signed in confirms the request is really coming from you; we'll then confirm and take care of it. If you can't sign in, see [I can't sign in](https://vpsdime.com/knowledgebase/client-area/account/cant-sign-in) to regain access first, or open a ticket anyway and we'll verify your identity another way before deleting anything. ### What deletion does - It's **permanent and irreversible**. Your personal data is removed, not just hidden. - We can only delete an account that's already wound down, with **no unpaid invoices and no active or suspended services** (see *Before you request* above). ### Deleted vs closed - **Closed:** the account can no longer sign in, but your records are retained (for example after a risk review; see [Account closed](https://vpsdime.com/knowledgebase/client-area/account/account-closed)). It can potentially be reopened. - **Deleted:** your data is erased and the account can't be restored. ### Your privacy rights Depending on where you live, privacy laws such as the EU/UK **GDPR** or California's **CCPA/CPRA** give you the right to request deletion of your personal data. We honor these requests; just open a ticket as above and let us know. ### Still need help? Sign in and [open a support ticket](https://vpsdime.com/open-ticket/). So we can action it on the first reply, it's worth mentioning: - that you're requesting account/data **deletion** (and that you understand it's permanent), - confirmation that your services are cancelled and there are no unpaid invoices. (If signing in isn't possible, open a ticket anyway and we'll verify your identity before deleting anything.) We'll never ask for your password. ### Related questions - "How do I delete my account?" - "How do I get my personal data removed (GDPR / CCPA)?" - "Is deleting my account the same as closing it?" - "Can a deleted account be restored?" - "What do I need to do before you can delete my account?" --- ## Billing & payments help URL: https://vpsdime.com/knowledgebase/client-area/billing Last reviewed: 2026-07-05 Summary: Help articles for paying invoices, payment methods, account credit, automatic renewals, saved cards, changing your billing cycle, and managing renewal dates at VPSDime. Guides for paying for your VPSDime services and managing how you're billed. ### Paying - [Viewing and paying an invoice](https://vpsdime.com/knowledgebase/client-area/billing/invoices). Find invoices, pay an unpaid one, download a PDF, and what the statuses mean. - [Payment methods we accept](https://vpsdime.com/knowledgebase/billing/payment-methods). Cards, wallets (PayPal, Apple Pay, Google Pay and more), bank and local methods, and crypto. - [Add funds (account credit)](https://vpsdime.com/knowledgebase/client-area/billing/add-funds). Prepay a balance and let invoices draw from it. ### Renewals & cards - [Automatic renewals (subscriptions)](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions). Saved card vs Paddle vs Fastspring, and turning auto-renewal on or off. - [Saved cards](https://vpsdime.com/knowledgebase/client-area/billing/saved-cards). Add or remove a card on file for renewals. - [Change your billing cycle](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-cycle). Switch a service between billing cycles yourself. ### Renewal dates - [Pay for your service in advance](https://vpsdime.com/knowledgebase/client-area/billing/pay-in-advance). Prepay 1 to 24 months so the renewal date moves forward. - [Sync your renewal dates](https://vpsdime.com/knowledgebase/client-area/billing/sync-due-dates). Align several services on one renewal date with a single invoice. - [Change your billing day](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-day). Move your renewal to a day of the month that suits you. ### Billing schedule & policies - [When invoices are due, and what happens if you don't pay](https://vpsdime.com/knowledgebase/billing/billing-timeline). The schedule, and suspension vs termination. - [Refunds and credits](https://vpsdime.com/knowledgebase/billing/refunds). The 72-hour money-back guarantee, and what isn't refundable. - [Taxes (VAT and sales tax)](https://vpsdime.com/knowledgebase/billing/taxes). How tax is added, and your VAT/GST number on invoices. - [Billing questions](https://vpsdime.com/knowledgebase/billing/billing-questions). A billing FAQ: pausing a service, late payment and fees, proration, saved cards, chargebacks, transfers, and querying a charge. --- Still need a person? You can [open a support ticket](https://vpsdime.com/open-ticket/) any time. --- ## Viewing and paying an invoice URL: https://vpsdime.com/knowledgebase/client-area/billing/invoices Last reviewed: 2026-07-05 Summary: How to find your invoices, open one, pay an unpaid invoice (choosing a payment method and applying account credit), download a PDF, and what the invoice statuses mean. ### What this is Your invoices and how to pay them. Find them at **Billing, My Invoices** (https://vpsdime.com/invoices). ### The invoices list **Billing, My Invoices** shows your full invoice history in a table: **Invoice #**, **Invoice Date**, **Due Date**, **Total**, **Balance**, and **Status**. Each row has a **View Invoice** button. ![The My Invoices page: a table of invoices with status badges and View Invoice buttons, plus a Pay All Unpaid Invoices button](https://vpsdime.com/knowledgebase/client-area/billing/images/invoices-list.png) - Click a column header to sort, and use the per-page selector for longer histories. - To clear more than one unpaid invoice at once, tick the ones you want and click **Pay Selected Invoices**, or click **Pay All Unpaid Invoices**. **Before you use those two buttons, know that they merge invoices.** Paying several invoices together combines them into a **single invoice and one transaction**, and once merged, they can't be separated from your side, there's no unmerge button. That's usually exactly what you want (one payment, one line on your statement), but if your bookkeeping needs each invoice as its own document, pay them **individually** instead. Merged something you needed split? [Open a ticket](https://vpsdime.com/open-ticket/) with the invoice numbers and we'll sort it out. And if you find yourself merging invoices **every month**, there's a cleaner fix: [sync your renewal dates](https://vpsdime.com/knowledgebase/client-area/billing/sync-due-dates) once, and your services renew together on a single combined invoice from then on, no button-clicking required. ### Opening an invoice Click **View Invoice** (or the invoice number) to open it. You'll see: - A header with the **status** (Paid, Unpaid, and so on). If it's paid, the payment method and date. - **Billing Information:** who the invoice is billed to, and who it's paid to. - **Invoice Items:** each line (for example a VPS for its billing period, with its IP), then **Subtotal**, any **Credit** applied, and the **Total**. - **Transactions:** payments recorded against the invoice, and the remaining **Balance**. - A **Download as PDF** button at the bottom. ![A paid invoice: the PAID header with invoice number and dates, Billing Information, Invoice Items with credit applied and a $0.00 total, Transactions, and a Download as PDF button](https://vpsdime.com/knowledgebase/client-area/billing/images/cropped/invoice-paid-view.png) ### Paying an unpaid invoice Open the unpaid invoice and, under **Payment Method**, choose how you want to pay. For the full list see [Payment methods](https://vpsdime.com/knowledgebase/billing/payment-methods). Then use the payment button to complete it. ![The Payment Method selector on an unpaid invoice, with options like PayPal / Card, Mastercard / Visa, Alternative PayPal, Bitcoin, USDT, and Alipay, above a Pay Now button](https://vpsdime.com/knowledgebase/client-area/billing/images/cropped/invoice-payment-method.png) - **Pay Once vs Subscribe (PayPal / Card):** when you pay with PayPal / Card you can choose **Pay Once** (a single payment) or **Subscribe** (saves your details so the service renews automatically). See [Automatic renewals](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions). - **Apply account credit:** if you have a credit balance, you'll see an option to apply some or all of it to the invoice before paying the rest. See [Add funds](https://vpsdime.com/knowledgebase/client-area/billing/add-funds). ### Invoice statuses - **Paid:** fully paid, nothing to do. - **Unpaid:** awaiting payment. - **Pending:** your payment is processing and the invoice will flip to Paid shortly. **Please don't pay again.** - **Security Review:** your card payment went through and is being checked by our processor's anti-fraud step, usually cleared within 6 to 8 hours. **Please don't pay again.** - **Refunded** / **Cancelled:** the invoice was refunded or cancelled. ### Things worth knowing - **Download a copy any time** with **Download as PDF**, handy for expense records. - **Auto-renewing services still generate an invoice.** If a service is set to renew automatically and you pay its invoice yourself, we won't charge again for that same period. See [Automatic renewals](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions). - **A paid invoice can show a $0.00 total** when it was covered by account credit. The credit line shows what was applied. ### Troubleshooting - **I paid but the invoice isn't marked Paid.** If it shows **Pending** or **Security Review**, the payment is being processed (a security review by the card processor can take 6 to 8 hours); don't pay again, it clears to **Paid** on its own. See [Pending or Security Review after paying](https://vpsdime.com/knowledgebase/billing/invoice-pending-after-paying). If it stays **Unpaid**, the payment didn't go through, so try again or use another option. Still stuck? [Open a ticket](https://vpsdime.com/open-ticket/) with the invoice number. - **My payment failed.** Try another method, for example PayPal or a different card. See [Payment methods](https://vpsdime.com/knowledgebase/billing/payment-methods). - **The method I want isn't shown.** Not every method is offered for every invoice. Choose from the options shown, or contact us. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the **invoice number**, - its current **status** and the method you tried, - a screenshot of any error. ### Related questions - "How do I pay my invoice?" - "Where do I find my past invoices?" - "How do I download an invoice as a PDF?" - "I paid but the invoice still shows unpaid, why?" - "What does Pending or Security Review mean on my invoice?" - "Why did my invoices get combined into one after using Pay All?" - "Can I split invoices that were merged by Pay All Unpaid Invoices?" --- ## Add funds (account credit) URL: https://vpsdime.com/knowledgebase/client-area/billing/add-funds Last reviewed: 2026-07-05 Summary: How to add prepaid credit to your account, the deposit limits, that deposits are non-refundable, and how credit is applied to invoices. ### What this is You can prepay a **credit balance** on your account and let invoices draw from it automatically. It saves making lots of small payments. Find it at **Billing, Add Funds** (https://vpsdime.com/addfunds). (Two kinds of "prepay" exist, so pick the right one: Add Funds loads a **general balance** that pays whatever comes due. To prepay a **specific service** so its renewal date itself moves 1 to 24 months forward, use [Pay for your service in advance](https://vpsdime.com/knowledgebase/client-area/billing/pay-in-advance) instead, and you can pay that invoice *with* your credit balance, so the two combine nicely.) ### Steps 1. Go to **Billing, Add Funds**. 2. Enter an **Amount to Add** (within the limits below). 3. Click **Add Funds** and complete the payment with any [payment method](https://vpsdime.com/knowledgebase/billing/payment-methods). ### What you'll see ![The Add Funds page with Minimum Deposit, Maximum Deposit, and Maximum Balance tiles, an Amount to Add field, a non-refundable warning, and an Add Funds button](https://vpsdime.com/knowledgebase/client-area/billing/images/add-funds.png) - The deposit limits: - **Minimum deposit:** $50.00 USD - **Maximum deposit:** $10,000.00 USD - **Maximum balance:** $20,000.00 USD - An **Amount to Add** field, a note that **deposits are non-refundable**, and an **Add Funds** button. ### Things worth knowing - **Deposits are strictly non-refundable.** Only add what you expect to spend on services. - **Credit never expires.** Your balance stays on the account until it's spent. The one exception: if we terminate your account for a Terms of Service violation, any remaining credit is forfeited. - **Credit applies automatically.** Your balance is applied to your invoices for you, both to new renewal invoices as they're generated and to any open (unpaid) invoices already on your account, so there's usually nothing to do. You can also apply it by hand when paying an invoice. See [Viewing and paying an invoice](https://vpsdime.com/knowledgebase/client-area/billing/invoices). - **An invoice covered by credit** shows the credit applied and a $0.00 total. ### Changed your mind before paying? If you started an Add Funds deposit and then decided against it, you don't have to do anything, but you can tidy it up. An unpaid Add Funds invoice shows an **Add Funds Payment Pending** notice on your [dashboard](https://vpsdime.com/clientarea) with **Pay Now** and **Cancel** buttons. Click **Cancel** to drop the invoice, nothing is charged and no credit is added. If you leave it, our system **cancels an unpaid Add Funds invoice automatically after 24 hours**. ### Troubleshooting - **It won't accept my amount.** Check it's at least the minimum ($50), within the maximum, and that it won't push you over the maximum balance. - **My payment for the credit failed.** Try another [payment method](https://vpsdime.com/knowledgebase/billing/payment-methods). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the amount you tried to add, - the payment method you used and any error, - what you plan to use the credit for. ### Related questions - "How do I add credit to my account?" - "Is account credit refundable?" - "What's the minimum I can deposit?" - "How does my credit balance get used?" - "Does my account credit expire?" - "How do I cancel an Add Funds invoice I don't want to pay?" - "I started adding funds by mistake, what happens if I don't pay?" --- ## Automatic renewals (subscriptions) URL: https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions Last reviewed: 2026-07-02 Summary: How automatic renewals work at VPSDime, the difference between a saved card, a Paddle subscription, and a Fastspring subscription, how to turn auto-renewal on or off, and how to change or update your payment method. ### What this is By default your services renew **manually**: we email you an invoice each cycle and you pay it. If you'd prefer not to pay each invoice by hand, you can set a service to **renew automatically**. You manage this at **Billing, Manage Subscriptions**. Find it at https://vpsdime.com/managesubscriptions. ### The three ways a service can auto-renew Automatic renewal runs through one of three separate systems, each set up in a different place: - **Card on file:** a card you save with us. Set up and managed under [Saved cards](https://vpsdime.com/knowledgebase/client-area/billing/saved-cards). On the subscriptions page it shows as **Saved Card**. - **Paddle subscription:** created when you pay an invoice with **PayPal / Card** and choose **Subscribe**, or when you click **Make Automatic** with no saved card. Shows as **Paddle PayPal** or **Paddle Card**. - **Fastspring subscription:** created when you pay with **Alternative PayPal** (Fastspring) as a subscription. Shows as **Fastspring PayPal** or **Fastspring Card**. A service uses **one** of these at a time. The saved card is managed on the [Saved cards](https://vpsdime.com/knowledgebase/client-area/billing/saved-cards) page; Paddle and Fastspring subscriptions are managed here. ### What you'll see On **Billing, Manage Subscriptions**: ![The Manage Subscriptions page: the Renewal Methods Explained key above a Subscription Management table with Renewal Method badges and Make Automatic / Cancel VPS buttons](https://vpsdime.com/knowledgebase/client-area/billing/images/manage-subscriptions.png) - A **Renewal Methods Explained** key: - **Manual:** automatic renewals are off for this service - **Saved Card:** renews with your card on file - **Paddle PayPal** / **Paddle Card:** renews via your Paddle subscription - **Fastspring PayPal** / **Fastspring Card:** renews via your Fastspring subscription - A table of your services with **VPS**, **Price / Cycle**, **Renewal Date**, and **Renewal Method**. - The buttons on each row depend on the current method: - **Manual:** **Make Automatic** and **Cancel VPS** - **Saved Card** or **Paddle:** **Manage**, **Make Manual**, and **Cancel VPS** - **Fastspring:** **Make Manual** and **Cancel VPS** ### Turning auto-renewal on - Click **Make Automatic** on a manual service. With no saved card, this sets up a **Paddle** subscription where you pick card or PayPal on the Paddle checkout page. With a saved card, it takes you to assign that card to the service. ![The "Set your VPS to renew automatically" dialog with Make Automatic and Close buttons](https://vpsdime.com/knowledgebase/client-area/billing/images/cropped/make-automatic-dialog.png) ![The Set up automatic renewal page: an authorization-only notice, the renewal amount with tax, a PayPal button, card fields, and a Subscribe now button](https://vpsdime.com/knowledgebase/client-area/billing/images/paddle-subscribe.png) - Or, when you **pay an invoice** with PayPal / Card, choose **Subscribe** instead of **Pay Once**. See [Viewing and paying an invoice](https://vpsdime.com/knowledgebase/client-area/billing/invoices). - To renew with a **saved card**, add one under [Saved cards](https://vpsdime.com/knowledgebase/client-area/billing/saved-cards). ### Changing or updating your payment method Use the **Manage** button next to a service. What you can change depends on the method: - **Paddle subscription:** Manage opens Paddle's management window. - On **Paddle Card**, you can **update your card details** or **switch to PayPal**. - On **Paddle PayPal**, you can **switch to a credit card**. ![The subscription management window opened by Manage: a PayPal button, card number, name, expiry, and CVV fields, and an Update card details button](https://vpsdime.com/knowledgebase/client-area/billing/images/cropped/paddle-manage-window.png) - **Saved card:** Manage takes you to [Saved cards](https://vpsdime.com/knowledgebase/client-area/billing/saved-cards), where you add, remove, or reassign a card. - **Fastspring** subscriptions don't have an in-page Manage option. To change one, set the service to **Manual** and set up auto-renewal again with the method you want, or [open a ticket](https://vpsdime.com/open-ticket/). ### Turning auto-renewal off - Click **Make Manual** on the service. We stop charging automatically, and you pay each invoice yourself when it's due. The service keeps running. - If your auto-renewal is a **saved card**, you can also remove or unassign the card under [Saved cards](https://vpsdime.com/knowledgebase/client-area/billing/saved-cards). ### Things worth knowing - **When the charge happens:** automatic renewals are charged on the service's **renewal date** (the date in the Renewal Date column), not days in advance, whichever renewal method is in use. - **Turning off auto-renewal is not the same as cancelling.** Make Manual keeps the service running (you just pay invoices yourself). **Cancel VPS** ends the service. Use Cancel VPS only if you actually want the VPS gone. - **Paying early won't double-charge.** If a service is set to auto-renew and you pay its invoice manually before the renewal date, we won't charge again for that same period. - **Switching systems** (for example from a saved card to a Paddle subscription) means setting the current one to Manual or removing the saved card first, then setting up the new one. - **Cancelling a VPS stops its automatic charges by itself.** We only charge for **active** services, so a cancelled service (or one with a cancellation request in) isn't charged again. You don't need to set it to Manual or cancel anything on PayPal's side first. ### Troubleshooting - **My service renewed on a card or PayPal I didn't expect.** Check the **Renewal Method** column to see which system is active. Saved-card renewals are managed under [Saved cards](https://vpsdime.com/knowledgebase/client-area/billing/saved-cards); Paddle and Fastspring under Manage Subscriptions. - **I want to switch my Paddle subscription from card to PayPal (or back).** Use **Manage** on that service and follow the Paddle window. - **I turned off auto-renew but still got an invoice.** That's normal. Manual means we invoice you and you pay it; the invoice itself isn't an automatic charge. - **I want to stop renewals but keep my VPS.** Use **Make Manual**, not Cancel VPS. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS (hostname or IP) you mean, - whether you want to turn auto-renewal on or off, or change the payment method, - the renewal method currently shown for it. ### Related questions - "How do I make my VPS renew automatically?" - "How do I stop automatic renewal without cancelling my VPS?" - "How do I change my payment method or switch from card to PayPal?" - "What's the difference between a saved card and a subscription?" - "Why did my service renew through Paddle or Fastspring?" - "When will my card or PayPal be charged for renewal?" --- ## Saved cards URL: https://vpsdime.com/knowledgebase/client-area/billing/saved-cards Last reviewed: 2026-07-02 Summary: How to add or remove a saved payment card for automatic renewals, choose which services a card renews, and how card priority works. ### What this is A saved card is a card you store with us so a service can **renew automatically** from it. You manage saved cards at **Billing, Saved Cards**. This is one of the three auto-renewal options. See [Automatic renewals](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions) for how it compares to Paddle and Fastspring subscriptions. Find it at https://vpsdime.com/managecards. ### What you'll see On **Billing, Saved Cards**: ![The Saved Cards page: the Card Usage Priority notice, a Saved Payment Cards table with Manage Services and Delete buttons per card, and an Add New Card button](https://vpsdime.com/knowledgebase/client-area/billing/images/saved-cards.png) - An **Add New Card** button. - A table of your saved cards: **Card Owner**, **Card Number** (masked), **Date Added**, and **Used For Services**. - If you haven't saved any, an empty state: *"No saved card found. Click here to add one."* ### Adding a card Click **Add New Card** on the Saved Cards page to open the form. It has two parts: - **Billing Information:** your name, address, and phone number (pre-filled from your account). - **Card Details:** card type, card number, expiry date, and CVV. ![The Add New Card form: Billing Information and Card Details panels, the Use Card For Auto Renewal selector, and Save Card / Cancel buttons](https://vpsdime.com/knowledgebase/client-area/billing/images/cropped/add-card-form-panels.png) Then set **Use Card For Auto Renewal**: - **Renew all of my services** with this card. - **Renew some services** (you pick which ones from the list that appears). - **Save it for manual payments only** (the card is stored for convenience but won't auto-renew anything). Click **Save Card** when you're done. ### Choosing which services a card renews The **Used For Services** column shows what each card covers. A card can renew **all** your services, **specific** ones, or be saved **for manual payments only** (no auto-renewal). - **Card priority:** if you have one card saved for specific services and another saved for all services, the specific-service card is used for those services, and the all-services card covers the rest. ### Removing a card Remove a card from the same page to stop it being used for renewals. If that card was the only thing auto-renewing a service, that service goes back to **manual** renewal and you'll pay its invoices yourself. See [Automatic renewals](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions). ### If a saved-card charge fails Your saved card is charged **on the invoice's due date**, never before it. If that charge is declined, we retry **once a day** on the following days. If you have several unpaid invoices, we attempt **one** of them per day; the others wait for the next day's run. After **three failed days in a row**, we **disable the card** for automatic renewals and email you. To get back on track, pay any open invoice manually (see [Viewing and paying an invoice](https://vpsdime.com/knowledgebase/client-area/billing/invoices)) and check, update, or re-add your card. ### Things worth knowing - **Saved cards are separate from Paddle and Fastspring subscriptions.** A saved card here renews through our card processor and shows as **Saved Card** on the subscriptions page. Paddle and Fastspring subscriptions are set up while paying an invoice and are managed under [Automatic renewals](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions). - **Removing a card doesn't cancel the service.** It just stops auto-renewal. The service keeps running until its next due date. ### Troubleshooting - **My card was declined when I tried to save it.** Try again or use a different card. If it keeps failing, your bank may be blocking it. Contact them, or use another auto-renewal method. - **A renewal didn't go through on my saved card.** Pay the open invoice manually (see [Viewing and paying an invoice](https://vpsdime.com/knowledgebase/client-area/billing/invoices)), and check the card is still valid and assigned to that service. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - which service the card should renew, - whether you're adding, removing, or reassigning a card, - any error you saw. **Never put full card details in a ticket.** Add or update cards only on the Saved Cards page. ### Related questions - "How do I save a card for automatic renewal?" - "How do I remove a saved card?" - "Can I use different cards for different services?" - "Which card will be used to renew my VPS?" - "Does removing my card cancel my service?" - "What happens if my saved card keeps failing?" - "Why was my saved card disabled?" --- ## Change your billing cycle URL: https://vpsdime.com/knowledgebase/client-area/billing/change-billing-cycle Last reviewed: 2026-07-05 Summary: How to switch a service between billing cycles yourself (for example monthly to annual), and how outstanding invoices and pricing are handled. ### What this is You can change how often a service is billed (for example from **monthly** to a longer cycle) yourself, without opening a ticket. Find it at **Billing, Change Billing Cycle** (https://vpsdime.com/changebillingcycle). ### Steps 1. Go to **Billing, Change Billing Cycle**. 2. Find the service in **Your Active Services** and click **Change Cycle**. 3. Choose the billing cycle you want from the options shown and confirm. If the service has an unpaid invoice, it's updated to the new cycle and price automatically. ### What you'll see - A **Your Active Services** table: **Hostname / IP Address**, **Product**, **Current Billing Cycle**, **Amount**, **Next Due Date**, and **Status**, with a **Change Cycle** button per service. ![The Change Billing Cycle page with a Your Active Services table and a Change Cycle button per service](https://vpsdime.com/knowledgebase/client-area/billing/images/change-billing-cycle.png) - After clicking **Change Cycle**, the available cycles and their prices for that service. ![The cycle selection screen: the service's current cycle, price, and next due date, above Monthly, Quarterly, Semi-Annually, and Annually options](https://vpsdime.com/knowledgebase/client-area/billing/images/cropped/change-cycle-options.png) ### Things worth knowing - **A longer cycle means fewer invoices.** You pay for more time up front and get billed less often. Check the price shown for each cycle before you confirm. - **When it takes effect:** an unpaid invoice on the service is updated to the new cycle straight away; otherwise the change shows on your next renewal invoice. - **Changing the cycle is not the same as changing your renewal method.** To control automatic renewal, see [Automatic renewals](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions). - **Want the same price, just paid ahead or on a different day?** To prepay months at your current cycle, see [Pay for your service in advance](https://vpsdime.com/knowledgebase/client-area/billing/pay-in-advance); to move which day of the month you're billed, see [Change your billing day](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-day); and to line several services up on one renewal date, see [Sync your renewal dates](https://vpsdime.com/knowledgebase/client-area/billing/sync-due-dates). ### Troubleshooting - **My service isn't listed.** Only active services can have their cycle changed here. If a service is pending or suspended, [open a ticket](https://vpsdime.com/open-ticket/). - **I'm not sure what I'll be charged.** The options screen shows the price for each cycle before you confirm. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the service (hostname or IP), - the cycle you want to switch to, - anything unexpected about the pricing or invoices. ### Related questions - "How do I change my billing cycle?" - "Can I switch from monthly to annual?" - "Will changing my cycle change my price?" - "How do I pay yearly instead of monthly?" --- ## Pay for your service in advance URL: https://vpsdime.com/knowledgebase/client-area/billing/pay-in-advance Last reviewed: 2026-07-05 Summary: How to prepay a VPS for 1 to 24 extra months so the renewal date moves forward, what it costs, and what happens if you don't pay the invoice. ### What this is You can pay now to move a service's renewal date **1 to 24 months** forward, without changing its price or billing cycle. You get a one-time invoice for exactly the time you add; once it's paid, renewal invoices simply start arriving that much later. Find it at **Billing, Pay In Advance** (https://vpsdime.com/payinadvance). This is useful when you want to spend account credit ahead of time, cover a long absence, or lock in service time before a card expires. If what you actually want is to be billed less often (for example monthly to annual), use [Change your billing cycle](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-cycle) instead; it changes the recurring price schedule rather than prepaying at your current one. ### Steps 1. Go to **Billing, Pay In Advance**. 2. Find the service in **Your Services** and click **Pay In Advance**. 3. Pick how many months to add. Each option shows the exact price and your new renewal date before you commit. 4. Click **Create Invoice & Continue to Payment** and pay the invoice with any payment method, including account credit. The renewal date moves the moment the invoice is paid. Nothing changes until then. ### What you'll see - A **Your Services** table with each service's current cycle, price, and next due date, and a **Pay In Advance** button per service. Services that can't be adjusted right now (for example, with an unpaid renewal invoice) show the reason and a **View Invoice** button instead. ![The Pay In Advance page with a Your Services table and a Pay In Advance button per service](https://vpsdime.com/knowledgebase/client-area/billing/images/pay-in-advance.png) - After choosing a service, a grid of 1 to 24 month options, each with the new renewal date and its exact price. ![The month picker: cards for 1 to 24 months, each showing the new renewal date, days added, and price](https://vpsdime.com/knowledgebase/client-area/billing/images/pay-in-advance-options.png) ### Things worth knowing - **The price is prorated from your plan price.** Each month added costs your plan's monthly-equivalent price, calculated per day. What's shown on the option card is exactly what's invoiced. - **The invoice is not charged automatically.** Saved cards and PayPal subscriptions never auto-pay a prepayment invoice; pay it from the invoice page yourself (account credit works too). - **The offer expires if unpaid.** An unpaid prepayment invoice cancels itself automatically after a few days (shown next to the pending entry). If it expires or you cancel it, nothing changes and normal renewal billing continues. Nothing is ever charged without the invoice being paid. - **One pending adjustment per service.** A pending prepayment blocks creating a [due-date sync](https://vpsdime.com/knowledgebase/client-area/billing/sync-due-dates) or [billing-day change](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-day) for the same service until you pay or cancel it. Any of the three pages shows your pending adjustments with **Pay** and **Cancel** buttons. - **Changed your mind before paying?** Cancel the pending entry, or just submit a different number of months; a new submission replaces the pending one. Applied account credit is returned on cancel. ### Troubleshooting - **The button says View Invoice instead of Pay In Advance.** The service has an unpaid or overdue renewal invoice. Pay that first, then come back. - **My service isn't listed.** Only Active, Pending, or Suspended services with a recurring billing cycle can be prepaid. Free and one-time services have no renewal date to move. - **"Your renewal is due very soon."** When the renewal is a day away or less, pay the upcoming renewal invoice instead; you can prepay right after. - **I paid but want to undo it.** Once paid and applied, the date change is permanent. [Open a ticket](https://vpsdime.com/open-ticket/) and we'll take a look. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the service (hostname or IP), - how far ahead you want to pay, - the invoice number if one was created. ### Related questions - "How do I manually renew my VPS?" - "Can I pay for my VPS a year in advance?" - "How do I prepay my server?" - "Can I pay early without changing my billing cycle?" - "Will my saved card be charged if I create a prepayment invoice?" --- ## Sync your renewal dates URL: https://vpsdime.com/knowledgebase/client-area/billing/sync-due-dates Last reviewed: 2026-07-05 Summary: How to align two or more services to renew on the same date with a single one-time invoice, so you get one combined renewal instead of several scattered ones. ### What this is If you have several services renewing on different days, you can pay a one-time invoice to advance them all to a single renewal date. From then on they renew together, so you deal with one renewal instead of several scattered through the month. Find it at **Billing, Sync Due Dates** (https://vpsdime.com/syncduedates). Renewal dates only ever move **forward**. Each selected service is charged for exactly the days added to reach the target date, at its own daily rate, all on one invoice. ### Steps 1. Go to **Billing, Sync Due Dates**. 2. Click the services you want to sync (at least two). The date picker unlocks once two are selected. 3. Pick the target renewal date. The calendar only offers valid dates: from the day after the latest renewal among your selected services, up to 24 months out. The earliest possible date for your selection is shown under the field. 4. Click **Create Invoice & Continue to Payment** and pay the invoice with any payment method, including account credit. All selected services move to the target date the moment the invoice is paid. Nothing changes until then. ### What you'll see - A card per service showing its hostname, IP, current renewal date, cycle, and price. Services that can't be synced right now (an unpaid renewal invoice, or a pending adjustment) are greyed out with the reason. ![The Sync Due Dates page: selectable service cards, a locked date field, and a hint to select at least two services](https://vpsdime.com/knowledgebase/client-area/billing/images/sync-due-dates.png) - With two or more services selected, the calendar opens with the invalid earlier days disabled and the earliest possible date shown. ![Two services selected and the calendar open: days before the earliest valid date are greyed out](https://vpsdime.com/knowledgebase/client-area/billing/images/sync-due-dates-selected.png) ### Things worth knowing - **The cost is per service: daily rate times days added.** A service 5 days short of the target costs 5 days of its price; one already close costs almost nothing. Each service is an itemized line on the invoice. - **Pick the date with the calendar.** Dates that would move any selected service backward simply can't be chosen. If one service renews much later than the others, the earliest possible sync date is right after it; leave it out of the selection if that's further ahead than you want to pay for. - **The invoice is not charged automatically.** Saved cards and PayPal subscriptions never auto-pay a sync invoice; pay it from the invoice page yourself. - **The offer expires if unpaid.** An unpaid sync invoice cancels itself automatically after a few days (shown next to the pending entry). If it expires or you cancel, no dates change and normal renewal billing continues for every service. - **A pending adjustment blocks the service.** Each service can have one pending adjustment across [Pay In Advance](https://vpsdime.com/knowledgebase/client-area/billing/pay-in-advance), Sync Due Dates, and [Change Billing Day](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-day). Pay or cancel the pending one first; cancelling a sync releases all of its services at once. - **After the sync, renewals arrive together.** Services due on the same date with the same payment method are normally combined on a single renewal invoice going forward. ### Troubleshooting - **The date field is locked.** Select at least two services first; the picker unlocks and shows the earliest valid date for that selection. - **A service is greyed out.** It either has an unpaid renewal invoice (a **View Invoice** button is shown; pay it first) or a pending billing adjustment (pay or cancel it first). - **I can't pick the date I want.** The target must be after every selected service's current renewal date and at most 24 months from today. Deselect the service whose renewal is past your preferred date, or pick a later date. - **I paid but one service's date looks wrong.** [Open a ticket](https://vpsdime.com/open-ticket/) with the invoice number and we'll check it. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - which services you're trying to sync, - the target date you picked, - the invoice number if one was created. ### Related questions - "How do I make all my servers renew on the same day?" - "Can I combine my invoices into one?" - "How do I align the due dates of my services?" - "Why can't I pick an earlier date when syncing?" --- ## Change your billing day URL: https://vpsdime.com/knowledgebase/client-area/billing/change-billing-day Last reviewed: 2026-07-05 Summary: How to move a service's renewal to a different day of the month (for example the 1st) with a small one-time payment for the days added. ### What this is You can move a service's renewal to the day of the month that suits you, for example the 1st, or just after payday. You pay a small one-time invoice for the days added (the renewal always moves forward, never backward), and every future renewal stays on the new day. Find it at **Billing, Change Billing Day** (https://vpsdime.com/changebillingday). This changes **which day** you're billed. To change **how often** you're billed (monthly, quarterly, annual), use [Change your billing cycle](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-cycle) instead. ### Steps 1. Go to **Billing, Change Billing Day**. 2. Find the service in **Your Services** and click **Change Day**. 3. Pick the new day of the month. Each option shows the new renewal date, the days added, and the exact price. 4. Click **Create Invoice & Continue to Payment** and pay the invoice with any payment method, including account credit. The renewal day changes the moment the invoice is paid. Nothing changes until then. ### What you'll see - A **Your Services** table with each service's cycle, price, and next due date, and a **Change Day** button per service. ![The Change Billing Day page with a Your Services table and a Change Day button per service](https://vpsdime.com/knowledgebase/client-area/billing/images/change-billing-day.png) - After choosing a service, a grid of days 1 to 28. Your current billing day is marked and the rest show the new renewal date and cost. ![The day picker: cards for days 1 to 28, the current day marked, each other day showing its new renewal date and price](https://vpsdime.com/knowledgebase/client-area/billing/images/change-billing-day-options.png) ### Things worth knowing - **Days 29 to 31 aren't offered** so your renewal day also exists in February. Pick the 28th or the 1st if you want end-of-month or start-of-month billing. - **The change always moves forward.** Choosing a day earlier in the month than your current one lands on that day in the **next** month; you pay for the extra days in between, at your plan's daily rate. The exact price is on each option card. - **The invoice is not charged automatically.** Saved cards and PayPal subscriptions never auto-pay a billing-day invoice; pay it from the invoice page yourself. - **The offer expires if unpaid.** An unpaid invoice cancels itself automatically after a few days (shown next to the pending entry). If it expires or you cancel, your renewal day stays as it is. - **One pending adjustment per service.** A pending billing-day change blocks creating a [prepayment](https://vpsdime.com/knowledgebase/client-area/billing/pay-in-advance) or [due-date sync](https://vpsdime.com/knowledgebase/client-area/billing/sync-due-dates) for the same service until you pay or cancel it. Submitting a different day replaces the pending one. - **Several services to move to the same day?** [Sync your renewal dates](https://vpsdime.com/knowledgebase/client-area/billing/sync-due-dates) does them all on one invoice. ### Troubleshooting - **The button says View Invoice instead of Change Day.** The service has an unpaid or overdue renewal invoice. Pay that first, then come back. - **My current day is not clickable.** You're already billed on that day; there's nothing to change (and nothing to charge). - **My service isn't listed.** Only Active, Pending, or Suspended services with a recurring billing cycle are shown. Free and one-time services have no renewal date to move. - **"Your renewal is due very soon."** When the renewal is a day away or less, pay the upcoming renewal invoice first; you can change the day right after. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the service (hostname or IP), - the day of the month you want, - the invoice number if one was created. ### Related questions - "How do I get billed on the 1st of the month?" - "Can I change my renewal day?" - "How do I move my due date to after payday?" - "Why can't I pick the 31st as my billing day?" --- ## Deploying a VPS URL: https://vpsdime.com/knowledgebase/client-area/deploy Last reviewed: 2026-07-05 Summary: How to add a new VPS to your account from the Deploy page, choosing a plan, location, and OS, adding extras, and setting up how you'll log in. Covers Linux, Premium, and Windows VPS. Spinning up another server on your account. - [Deploying a new VPS](https://vpsdime.com/knowledgebase/client-area/deploy/deploying-a-new-vps). Pick a plan, choose a location and OS, add any extras (backups, storage, bandwidth, IP), set up your SSH key or Administrator password, and pick a billing cycle. Covers Linux, Premium, and Windows VPS. - [Cloning a VPS into a new VPS](https://vpsdime.com/knowledgebase/client-area/deploy/cloning-a-vps). Deploy a new VPS as an exact copy of one you already have, requested by ticket. Free on systemd 232+ distros, $25 on older ones, and how long the source is powered off. --- Still need a person? You can [open a support ticket](https://vpsdime.com/open-ticket/) any time. --- ## Deploying a new VPS URL: https://vpsdime.com/knowledgebase/client-area/deploy/deploying-a-new-vps Last reviewed: 2026-07-02 Summary: How to add another VPS to your account from the Deploy page, choosing a plan, location, and OS, deciding which extras to add now versus later, setting up SSH keys or your Administrator password, and picking a billing cycle. Covers Linux, Premium, and Windows VPS. ### What this is Adding another VPS to your account from **Deploy** in the client area (https://vpsdime.com/deployvps). You pick a plan, choose where it runs and what OS it starts with, add anything extra you want, set up how you'll log in, and it's live within a few minutes, billed on your existing account. The flow is the same for **Linux VPS**, **Premium VPS**, and **Windows VPS**; the few places they differ are called out below. You don't have to get every choice perfect. Almost everything here can be changed after the fact (resize the plan, reinstall a different OS, add resources, set an SSH key), so pick sensible defaults and move on. ### 1. Pick a plan Open **Deploy**, choose the product group at the top (Linux, Premium, or Windows), and pick a plan. Each card lists what you get: vCPU, dedicated memory, SSD storage, monthly traffic, an IP, and the uplink. ![The Deploy a New VPS page: Linux, Premium, and Windows product tabs above plan cards, each listing specs with a Deploy Now button](https://vpsdime.com/knowledgebase/client-area/deploy/images/cropped/deploy-plans-top.png) - **Don't overthink the size on Linux or Windows VPS.** Start with what fits your workload now: you can move up or down later, and on Linux VPS a plan change is live and instant with no downtime and the same IP. On **Premium VPS**, size deliberately, it's **upgrade-only**, so you can grow but not move to a smaller plan later. See [Upgrading or downgrading](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade). - **Which product group?** **Linux VPS** is the general-purpose choice. **Premium VPS** gives fully dedicated resources. **Windows VPS** runs Windows Server and you connect over RDP. The "Most Popular" tag is just a hint, not a recommendation for your case. Clicking **Deploy Now** on a plan takes you to its configuration page. ### 2. Name it and note the password - **Hostname** (Linux and Premium) or **Label** (Windows) is optional. Leave it blank and we'll pick one for you; a hostname can be a short name (`myserver`) or a full domain. The label on Windows is just a friendly name for the service, it doesn't name Windows itself. - A temporary **Root password** (Linux and Premium) or **Administrator password** (Windows) is generated and shown once, with a **Copy** button. Save it somewhere safe and **change it the first time you log in**. If you set up an SSH key (below), you may not need this password at all. ![The Configure VPS card with a hostname field and the generated root password with its Copy button](https://vpsdime.com/knowledgebase/client-area/deploy/images/cropped/deploy-configure-vps.png) ### 3. Choose a location and an OS - **Location** is where the VPS physically runs, and it sets the region of your IP address. **Pick the datacenter nearest your users** for the lowest latency, and if you're not sure which that is, our [Looking Glass](https://vpsdime.com/looking-glass) lets you ping and download from each location before you decide. Your IP belongs to the location, so changing location later means [a migration](https://vpsdime.com/knowledgebase/client-area/services/migrate-location) that changes the IP, worth choosing deliberately now. (That said, a wrong pick isn't costly to undo: if you realize right after deploying and haven't used the VPS yet, [contact us](https://vpsdime.com/open-ticket/) and we'll re-provision it in the right location for free; the $4 migration fee only applies once you have data you want moved.) We run six datacenters, Dallas, Seattle, Los Angeles, New Jersey, London, and Amsterdam, and the form lists the ones currently in stock for your product; an out-of-stock location returns as soon as we add capacity. - **Operating system:** - **Linux and Premium:** pick a distribution. A current **LTS** release (Ubuntu LTS, Debian, AlmaLinux, or Rocky) is the safe default for most people. Linux also has an **Applications (beta)** tab if you'd rather deploy a common app stack pre-installed than a bare OS. - **Windows:** choose Windows Server 2025, 2022, or 2019. ![The Windows VPS configuration: a Label field and Administrator password instead of a hostname and root password, Windows Server 2025/2022/2019 options, and only Nightly Backups and Extra Bandwidth as extras](https://vpsdime.com/knowledgebase/client-area/deploy/images/cropped/deploy-configure-windows-cards.png) - Not sure, or want to switch later? You can [reinstall](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os) to a different OS any time (it wipes the VPS, so it's cleanest to get close now). ![The Configurable Options card: location buttons per datacenter, then the operating system grid with an Applications (beta) tab](https://vpsdime.com/knowledgebase/client-area/deploy/images/cropped/deploy-location-os.png) ### 4. Add resources now, or later The configuration page offers optional extras. Which ones appear depends on the product: - **Linux VPS:** Nightly Backups, Additional vCPU, Additional Storage, Extra Bandwidth, and Extra IP. - **Premium VPS:** Extra Bandwidth and Extra IP (backups are included free, and CPU and storage are fixed to the plan). - **Windows VPS:** Nightly Backups and Extra Bandwidth. ![The optional extras on a Linux VPS: Nightly Backups, Additional vCPU, Additional Storage, Extra Bandwidth, and Extra IP Address, each with its price](https://vpsdime.com/knowledgebase/client-area/deploy/images/cropped/deploy-extras.png) **You don't have to decide all of this now.** Most extras can also be added later from the VPS's [Extra Features](https://vpsdime.com/knowledgebase/client-area/services/extra-features) tab, and Linux upgrades are live, so add only what you know you need up front. The one worth turning on from the start if your data matters is [Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview). ### 5. Set up how you'll log in **Linux and Premium** have an **Optional Configuration** section for SSH: - **Root public SSH key:** pick one of your saved keys, paste one, or import from GitHub/GitLab. See [SSH Keys](https://vpsdime.com/knowledgebase/client-area/services/ssh-keys). - **Root SSH login mode:** *Login Using Password* (also allows a key), *Login with SSH Key Only*, or *Disable Root Login*. Key-only is more secure, but choose it **only if you've actually set a key**, or you'll lock yourself out. - Optionally create a **user** with its own password, key, and login mode. ![The Optional Configuration card: root public SSH key (with GitHub/GitLab import), root SSH login mode, and optional user fields](https://vpsdime.com/knowledgebase/client-area/deploy/images/cropped/deploy-optional-config.png) **Recommended:** add an SSH key and use **key-only** login. It's the strongest protection, and because there's no password to get wrong, it keeps you clear of the [SSH firewall](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall) that blocks brute-force password attempts. **Windows VPS** has no SSH section. After deploy you connect over **RDP** using the Administrator password from step 2. ### 6. Pick a billing cycle and deploy The **Configuration Summary** on the right shows your choices, the setup fee ($0), and the total. ![The Configuration Summary sidebar: billing cycle prices, the plan's location, OS and extras, Total Due Today, the recurring amount, and the Deploy Now button](https://vpsdime.com/knowledgebase/client-area/deploy/images/cropped/deploy-summary.png) - **Billing cycle:** Monthly, Quarterly, Semi-Annually, or Annually. A longer cycle simply pays for more months up front, and you can change your cycle later. Pick Monthly if you're unsure. - Click **Deploy Now** to go to checkout and pay the invoice (with a saved card or your credit balance, if you have one). Your VPS is usually **provisioned within a few minutes**, and you'll get the connection details by email. ![The Please Confirm dialog reminding you of the auto-picked hostname and that the root password won't be shown again after checkout](https://vpsdime.com/knowledgebase/client-area/deploy/images/cropped/deploy-confirm-dialog.png) ![The checkout page: your information, a payment method selector (Credit Card, PayPal, Google Pay, Bitcoin, USDT, Alipay), and the order summary with a Complete Order button](https://vpsdime.com/knowledgebase/client-area/deploy/images/deploy-checkout.png) ### After it's deployed The new VPS appears under **My Services**. Open [Manage VPS](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) to control it, and connect over **SSH** (Linux and Premium) with your key or root password, or **RDP** (Windows) with the Administrator password. Then walk [your first 30 minutes on a new VPS](https://vpsdime.com/knowledgebase/getting-started/first-30-minutes), updates, a sudo user, and backups, before the real work starts. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - which plan and location you're ordering, - the operating system you chose, - and any message you saw at checkout. ### Related questions - "How do I add another VPS to my account?" - "What plan size should I pick, and can I change it later?" - "Which datacenter should I choose, and can I move it later?" - "Which operating systems can I choose when deploying?" - "Should I add backups, extra storage, or an IP now or later?" - "How do I set up my SSH key when deploying?" - "What's the difference between the billing cycles?" - "How long until my VPS is ready after I order?" - "How do I connect to my VPS once it's deployed?" --- ## Cloning a VPS into a new VPS URL: https://vpsdime.com/knowledgebase/client-area/deploy/cloning-a-vps Last reviewed: 2026-07-05 Summary: How to deploy a new VPS that's an exact copy of one you already have. Cloning is done by our team on request, free when the source VPS runs systemd 232 or newer (Ubuntu 18.04+, Debian 9+, CentOS/Alma/Rocky 8+), or for a $25 fee on older distributions where the process is manual. Covers how to check your distro and systemd version, what to put in the ticket, and how long the source VPS is powered off during the transfer. ### What this is Deploying a new VPS that starts as an **exact copy of one you already have**: same operating system, same configuration, same installed software, same data. It's the fastest way to spin up a second server that matches one you've already set up, and our team does the cloning for you, you just request it in a [support ticket](https://vpsdime.com/open-ticket/). The clone is a full copy of the source's disk. The new VPS keeps its own IP address and the hostname you give it, so anything on the source that's configured around its old IP will want updating on the copy. ### Free or $25, depending on the source's distribution Whether the clone is free comes down to the **systemd version** on the source VPS: - **Free:** the source runs **systemd 232 or newer**, which means our automated cloning handles it. In practice that's **Ubuntu 18.04 or newer, Debian 9 or newer, and CentOS/AlmaLinux/Rocky 8 or 9**. - **$25 fee:** anything older, **Ubuntu 16.04, Debian 8, CentOS 7, and earlier**. These don't support cgroups v2, so the clone is a manual job for our team, and it carries a **$25 fee**. #### Check what you're running Two commands work on every distribution: ``` cat /etc/os-release systemctl --version | head -n 1 ``` The first prints your distribution and release (look at the `PRETTY_NAME` line), the second prints the systemd version as the first number, for example `systemd 237`. If you prefer the distro-specific commands: `lsb_release -d` on Ubuntu and Debian, `cat /etc/redhat-release` on CentOS, AlmaLinux, and Rocky. #### On an older distro? You have two options - **Upgrade the OS first, then clone for free.** Moving to a qualifying release (Ubuntu 18.04+, Debian 9+, EL8+) makes the clone free, and it's worth doing for its own sake, the releases below the line stopped receiving security updates long ago. - **Clone as-is for $25.** If upgrading isn't practical for your setup, we'll do the manual clone once the fee is paid. ### How to request a clone [Open a ticket](https://vpsdime.com/open-ticket/) with the following: - **Source VPS:** its hostname and IP. - **Target VPS:** if you've already purchased the new VPS, its hostname and IP. If you haven't ordered it yet, tell us the **hostname you'll use** for it, then [deploy the new VPS](https://vpsdime.com/knowledgebase/client-area/deploy/deploying-a-new-vps), and we'll clone onto it once it's active. - **Confirmation that the target can be wiped.** Cloning naturally **erases everything on the target VPS's disk**, it becomes a copy of the source. If there's anything important on the target, back it up before we start. What happens next: - **If your source qualifies for free cloning**, we proceed and let you know in the ticket when it's done. - **If it's a manual clone**, we add a **$25 invoice** to your account. Pay it and reply to the ticket, and we'll proceed. ### Downtime during the clone To copy a **consistent filesystem**, the source VPS is stopped for the transfer, a snapshot of a running disk would risk half-written files, so a clean power-off sync is how it's done properly. The source is powered off **only for the data transfer itself**, and powered back on as soon as it finishes. The transfer runs over our **10 Gbps network** at around **2 Gbps** of real throughput, so the power-off window depends on how much disk your source actually **uses** (not the plan's disk size). That works out to roughly **4 seconds per GB used**, and the whole job adds about **5 to 10 minutes** of preparation and finalization around the transfer: | Disk used on source | Source powered off for | Whole clone, roughly | |---|---|---| | 20 GB | ~2 minutes | ~10 minutes | | 100 GB | ~7 minutes | ~15 minutes | | 250 GB | ~17 minutes | ~25 minutes | | 500 GB | ~35 minutes | ~40-45 minutes | If the downtime window matters, `df -h /` on the source shows your current usage, and trimming what you don't need (old logs, caches, leftover archives) before the clone shrinks the window directly. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the source VPS's hostname and IP, - the target VPS (or the hostname you'll order it with), - your source's distro and systemd version if you've checked them. ### Related questions - "Can I clone a server to spin up more identical ones?" - "Can I deploy a new VPS using an existing VPS as a base?" - "Is cloning my VPS free?" - "Why does cloning cost $25 on my distro?" - "How do I check my systemd or distro version?" - "How long will my VPS be powered off during cloning?" - "Will cloning erase the data on the target VPS?" - "How do I request a clone?" --- ## Managing your services URL: https://vpsdime.com/knowledgebase/client-area/services Last reviewed: 2026-07-02 Summary: Guides for running a VPS from the Service Management page, power and console, graphs and history, network and DNS, the firewall, reinstalling or rescuing the OS, SSH keys, plan changes and add-ons, and cancellation. Everything you can do to a VPS from the client area. Start with the management page, then jump to the tab you need. Details differ by product (Linux, Storage, Premium, Windows VPS); each guide calls out where they matter. ### Day to day - [My Services (your services list)](https://vpsdime.com/knowledgebase/client-area/services/my-services). Every service at a glance, renewal method, status, next due date, and the toggle that hides cancelled services. - [Managing your VPS](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps). Home base: check health, power on/off and restart, open the Console, reset the root or Admin password, change the hostname, and move between datacenters. - [Reading your VPS graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs). CPU, memory, disk, and network over time, how to tell if your plan fits, and why to run an in-VPS monitoring agent for the detail. - [The Tasks log](https://vpsdime.com/knowledgebase/client-area/services/tasks). A history of every action on your VPS and who did it, for troubleshooting and a quick security check. ### Network and DNS - [Network and IP addresses](https://vpsdime.com/knowledgebase/client-area/services/network). Your IPv4/IPv6, netmask and gateway, and reverse DNS (rDNS/PTR) for mail deliverability. - [DNS Manager](https://vpsdime.com/knowledgebase/client-area/services/dns). Free DNS hosting: point a domain at your VPS and manage A, AAAA, CNAME, NS, MX, and TXT records. - [The VPS firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall). The managed firewall (Linux and Storage VPS) that blocks risky app ports by default, and how to whitelist the sources that need in. ### Access and the OS - [SSH Keys](https://vpsdime.com/knowledgebase/client-area/services/ssh-keys). Save your public keys and pick them when deploying or reinstalling (Linux and Premium VPS). - [Reinstalling your OS](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os). Wipe and install a fresh OS or one-click app, with your key and login mode set up front. Destructive, so back up first. - [Boot from ISO](https://vpsdime.com/knowledgebase/client-area/services/boot-from-iso). Premium VPS: boot a rescue or installer ISO without touching your disk, to fix an unbootable system. ### Plan changes and billing - [Upgrading or downgrading](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade). Move to a bigger or smaller plan. On Linux VPS it's live and instant, no downtime, same IP. Premium VPS is upgrade-only. - [Moving your VPS to another location](https://vpsdime.com/knowledgebase/client-area/services/migrate-location). The $4 datacenter move with your data, the free re-provision when you don't need it, and the new-IP homework that comes with either. - [Extra Features (add-ons)](https://vpsdime.com/knowledgebase/client-area/services/extra-features). Add nightly backups, storage, vCPU, traffic, or IPs one at a time without changing your base plan. - [Cancelling a VPS](https://vpsdime.com/knowledgebase/client-area/services/cancellation). Request cancellation immediately or at the end of your billing period, and revoke it if you change your mind. --- Still need a person? You can [open a support ticket](https://vpsdime.com/open-ticket/) any time. --- ## My Services (your services list) URL: https://vpsdime.com/knowledgebase/client-area/services/my-services Last reviewed: 2026-07-04 Summary: The My Services page lists every service on your account with its IP, plan, price, billing cycle, next due date, renewal method, and status, and is the front door to managing each VPS. Also how to hide cancelled and terminated services from the list, a saved preference that doubles as the Product Listing - Show Active Only checkbox on Account Details. ### What this is **My Services** (https://vpsdime.com/myservices) lists every service on your account in one table and is the front door to everything per-VPS: click a service to open its [Service Management page](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps), jump straight to a billing-cycle change, or pay the invoice a pending service is waiting on. ![The My Services list](https://vpsdime.com/knowledgebase/client-area/services/images/my-services.png) ### Reading the list Each row is one service: - **Hostname** and **IP Address** both click through to the service's management page (for services that are running or suspended; a cancelled service isn't clickable). - **Plan**: the product line and plan, for example Linux VPS - Linux6GB. - **Price** and **Billing Cycle**: what you pay and how often. The small calendar button next to the cycle takes you straight to [changing the billing cycle](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-cycle) for that service. - **Next Due Date**: when the service renews next. Renewal invoices are generated 14 days ahead, see [when invoices are due](https://vpsdime.com/knowledgebase/billing/billing-timeline). The date itself is adjustable: [prepay months](https://vpsdime.com/knowledgebase/client-area/billing/pay-in-advance), [move it to a day that suits you](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-day), or [line several services up to renew together](https://vpsdime.com/knowledgebase/client-area/billing/sync-due-dates). - **Renewal**: how the service renews. **Manual** means you pay each invoice yourself; **Saved Card**, **Paddle PayPal / Paddle Card**, and **Fastspring PayPal / Fastspring Card** are the automatic options. The **Renewal Methods Explained** note at the top of the page is the key for these labels, clicking a label takes you to [Automatic renewals](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions) (or [Saved cards](https://vpsdime.com/knowledgebase/client-area/billing/saved-cards)) to change it. - **Status**: Active, Pending, Suspended, Cancelled, or Terminated. A service you've asked to cancel at the end of its billing period shows **Pending Cancellation** while it keeps running, see [Cancelling a VPS](https://vpsdime.com/knowledgebase/client-area/services/cancellation), including how to revoke it. ### The action button The last column depends on the service's state: - **Manage**, for a running service, opens [Manage VPS](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps). A **suspended** service shows a warning-styled Manage button, the usual cause is an unpaid invoice, and paying it reactivates the service automatically. - **Pending Payment**, for a new order whose invoice isn't paid yet, links straight to that invoice. If you placed the order by mistake, a **Cancel** button appears next to it: this abandons the whole order and cancels its unpaid invoice, so use it only if you don't want the service (it's available only while the order is still pending, unpaid, and nothing on it has been provisioned). If you do nothing, our system **cancels an unpaid pending order automatically after 3 days**. - **Pending Activation**, paid and being provisioned; you'll get an email when it's ready. - Cancelled and terminated services have no actions. ### Finding and sorting With more than a few services, the tools at the top earn their keep: the **search box** filters by hostname, the **Hostname, Price, Billing Cycle, Next Due Date, and Status** column headers sort the list, and **Results Per Page** at the bottom raises the page size. ### Hiding cancelled and terminated services Old cancelled and terminated services stay in the list by default, which gets noisy after a few years. To hide them, click **Hide Cancelled Services** at the top of the list: the list then shows only your pending, active, and suspended services, and the button becomes **Show All Services** for whenever you want the history back. The choice is **saved to your account**, so it sticks across visits and devices. It's the same preference as the **Product Listing - Show Active Only** checkbox on [Account Details](https://vpsdime.com/knowledgebase/client-area/account/account-details), ticking the box there and clicking the button here flip the same switch, so you can change it from either place. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the service (hostname or IP) the question is about, - what looks wrong on the list (a screenshot helps). ### Related questions - "Where do I see all my services?" - "How do I hide cancelled or terminated services from My Services?" - "What does the Renewal column on My Services mean?" - "Why does my service say Pending Cancellation?" - "What does Pending Payment or Pending Activation mean?" - "How do I search or sort my services list?" --- ## Managing your VPS URL: https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps Last reviewed: 2026-07-05 Summary: The Service Management page is home base for a VPS, checking its health, powering it on and off, getting in when you can't connect, resetting the root or Admin password, and reaching every other tool through the tabs. What to use when, and the gotchas. ### What this is The **Service Management** page is home base for a single VPS. From here you check its health, power it on and off, get in when you can't reach it, reset the login password, and reach everything else through the tabs across the top ([Network](https://vpsdime.com/knowledgebase/client-area/services/network), [Firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall), [Reinstall OS](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os), [Upgrade/Downgrade](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade), [Extra Features](https://vpsdime.com/knowledgebase/client-area/services/extra-features), [Cancellation](https://vpsdime.com/knowledgebase/client-area/services/cancellation), [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs), [Tasks](https://vpsdime.com/knowledgebase/client-area/services/tasks), each with its own guide). New to VPS hosting? Think of this page as the dashboard for your server. Almost anything you'd want to do to it is here or one tab away. Open it from [My Services](https://vpsdime.com/knowledgebase/client-area/services/my-services) (https://vpsdime.com/myservices), then **Manage** on the VPS. The page looks a little different per product: Linux VPS and Storage VPS have a **Firewall** tab, Premium VPS has a **Boot From ISO** tab, and Windows VPS shows a **Label** and connects over RDP. Differences are noted where they matter. ### Checking your VPS at a glance ![The Service Management page's Information tab: location, hostname, and IP, status and uptime, the button strip, specs and billing facts, and live usage bars](https://vpsdime.com/knowledgebase/client-area/services/images/manage-information.png) The **Information** tab is a quick health-and-facts summary. The parts worth knowing: - **Status and Uptime**, is it running, and for how long. If it isn't running and you didn't stop it, go to [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter). - **Live usage bars** (CPU, Memory, Storage, Traffic), a snapshot of how loaded it is right now. For trends over time and deciding whether to size up, use the [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) tab. - **Your specs and OS** (vCPU, RAM, storage, traffic, uplink), each with a shortcut to change it (order more storage or traffic, reinstall, upgrade/downgrade). - **Billing facts** (plan, service status, billing cycle, next due date, recurring amount), so you can see what you pay and when it renews. - **IP address, hostname, and location/node.** Nothing here needs memorizing, it's the place to grab a fact fast: your IP, when the VPS renews, or how much disk is left. ### Powering on, off, and restarting The button strip controls power from **outside** the operating system. That matters most when the VPS is unresponsive and you can't do it from inside. ![The button strip on a Linux VPS: Power On, Restart, Shutdown, Hostname, Root Password, and Console](https://vpsdime.com/knowledgebase/client-area/services/images/cropped/manage-power-buttons.png) - **Power On**, start a VPS that's off. - **Restart** is a soft reboot (the OS shuts down cleanly first). **Reset** is a hard reboot, the equivalent of pulling the power cord and plugging it back in. - **Shutdown** is a clean power-off (you then Power On yourself). **Power Off** cuts power immediately. **Rule of thumb:** reboot from inside the OS when you can (`reboot` on Linux, Restart on Windows). Use the panel's soft option (Restart/Shutdown) next, and the hard option (Reset/Power Off) only when the VPS is frozen, a hard cut can leave the filesystem needing a check on the next boot. Which buttons you get depends on the product: | Product | Buttons | |---|---| | Linux VPS | Power On, Restart, Shutdown, Hostname, Root Password, Console | | Storage VPS | Power On, Reset, Power Off, Root Password, Reinstall OS, Console | | Premium VPS | Power On, Reset, Shutdown, Power Off, Root Pass, Console | | Windows VPS | Power On, Reset, Power Off, Admin Pass, Reinstall OS, Console | (**Reinstall OS** here is just a shortcut to the Reinstall OS tab.) ### Getting in when you can't connect When your normal way in fails, SSH on Linux, RDP on Windows, two tools get you back: - **Console** opens an out-of-band console straight to the VPS's screen, no SSH, RDP, or working network required. It's the tool for a firewall rule that locked you out, a broken network config, or a VPS that won't boot: get in, fix it, get out. It isn't meant for everyday use, connect over SSH or RDP normally. On a **Windows VPS**, the Console signs you into the [VPSDime Support Account](https://vpsdime.com/knowledgebase/windows-vps/vpsdime-support-account)'s session, so expect a different desktop than your own; sign out and log in as `Administrator` if you need your own session. ![The out-of-band Console: a terminal view of the VPS's screen, here logged in at a root shell](https://vpsdime.com/knowledgebase/client-area/services/images/manage-console.png) - **Root Password** (Linux, Storage, Premium) or **Admin Pass** (Windows) sets a new login password on the VPS, even while it's running. Use it if you're locked out or forgot the password. On Linux you can reset **root or another user** (choose "Other user" and enter the name). Generate a strong password or type your own. Better yet, set up [SSH keys](https://vpsdime.com/knowledgebase/client-area/services/ssh-keys) so a forgotten or guessed password can't lock you out at all. And if repeated wrong passwords got your IP blocked, see the [SSH firewall](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall). ### Naming and moving your VPS - **Hostname** (Linux and Storage VPS) sets the server's hostname from the Information tab. The same change can be made from inside the VPS with `hostnamectl set-hostname newname`, no reboot needed, which is also the way on **Premium VPS**, where the panel only sets the hostname when you reinstall. **Label** (Windows VPS) is just a friendly name for the service in your account, it doesn't rename Windows itself. Renaming is a low-risk change. Websites answer to their **domains** (your web server's vhost or `server_name` config), not to the machine's name, so a hostname change doesn't directly affect the sites you host, unless something on the server was deliberately tied to the old name. Worth a quick check after renaming: the `/etc/hosts` line that maps the old name (update it, or `sudo` and some services get slow resolving the machine's own name), a mail server's `myhostname` (Postfix) if the VPS sends mail, and any script, backup job, or monitoring agent that reads the hostname. And it's instantly reversible: if anything misbehaves after the change, set the old name back the same way and regroup. - **Migrate to Another Location** starts a move of your VPS to a different datacenter, for example to sit closer to your users. You pay a **$4 fee**, a ticket opens with our team after payment, and we perform the move. The fee is for migrating your data with the VPS; if you don't need the data, ordered the wrong location and haven't used the VPS yet, or were going to reinstall anyway, [open a ticket](https://vpsdime.com/open-ticket/) instead and we'll **re-provision it in the location you want for free**. Because IP addresses belong to a location, **your IP changes when you move**. The decision guide and the post-move checklist (DNS, SPF, rDNS, allowlists) are in [Moving your VPS to another location](https://vpsdime.com/knowledgebase/client-area/services/migrate-location). ### Everything else (the tabs) Each tab has its own guide: [Network](https://vpsdime.com/knowledgebase/client-area/services/network) (your IPs and reverse DNS), [Firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall) (the managed firewall, on Linux and Storage VPS), [Reinstall OS](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os), [Boot From ISO](https://vpsdime.com/knowledgebase/client-area/services/boot-from-iso) (Premium VPS), [Upgrade/Downgrade](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade), [Extra Features](https://vpsdime.com/knowledgebase/client-area/services/extra-features) (add-ons like nightly backups, extra storage, vCPU, traffic, and IPs), [Cancellation](https://vpsdime.com/knowledgebase/client-area/services/cancellation), plus [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) and [Tasks](https://vpsdime.com/knowledgebase/client-area/services/tasks). ### Product differences at a glance - **Linux VPS and Storage VPS** include the **Firewall** tab and connect over SSH. - **Premium VPS** adds a **Boot From ISO** tab (boot a rescue image) and has hard power controls. - **Windows VPS** connects over **RDP**, shows a **Label** and an **OS Status**, and uses **Admin Pass** instead of Root Password. ### Troubleshooting - **The buttons are greyed out.** They enable once the live status has loaded. Give the page a moment or reload it. - **My VPS won't respond to anything.** Try the **Console** to see its screen and get in without the network. If that fails too, run [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter), then open a ticket. - **I'm locked out / forgot my password.** Reset it with **Root Password** / **Admin Pass** above. To avoid it in future, switch to [SSH keys](https://vpsdime.com/knowledgebase/client-area/services/ssh-keys). - **I did a hard Reset/Power Off and the VPS is slow to boot or checking the disk.** That's the filesystem recovering from the abrupt stop; let it finish, and prefer soft reboots next time. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what you were trying to do and what happened, - any error, and whether the Console works. ### Related questions - "How do I manage my VPS?" - "How do I restart or shut down my VPS the right way?" - "What's the difference between Restart and Reset, or Shutdown and Power Off?" - "My VPS is frozen, how do I force a restart?" - "How do I reset my root or Administrator password if I'm locked out?" - "How do I get into my VPS when SSH or RDP won't connect?" - "How do I change my VPS hostname?" - "Can I move my VPS to another datacenter, and will my IP change?" --- ## Reading your VPS graphs URL: https://vpsdime.com/knowledgebase/client-area/services/graphs Last reviewed: 2026-07-02 Summary: The Graphs tab plots CPU, memory, disk, and network usage over time. Use it to check whether your plan fits your workload, decide when to upgrade, and troubleshoot slowdowns. The graphs are measured from the host, so run an in-VPS agent for precise monitoring. ### What this is for The **Graphs** tab (in Manage VPS, https://vpsdime.com/myservices) plots how hard your VPS is working over time. It's the fastest way to answer three questions: **is my plan the right size for what I'm running, is a slowdown caused by CPU, memory, disk, or network, and how much bandwidth am I using.** Pick a time range with the buttons: **Today**, **Yesterday**, **This Week**, **Last Week**, **This Month**, **Last Month**. ![The top of the Graphs tab: time-range buttons (Today through Last Month) above the CPU Usage and Memory Usage percentage graphs; disk and network graphs follow below](https://vpsdime.com/knowledgebase/client-area/services/images/cropped/manage-graphs-top.png) ### Important: these are host-side graphs These graphs are measured from the **host** (the hypervisor your VPS runs on), not from inside your VPS. That makes them great for trends and a quick health check without installing anything, but they can differ slightly from what tools inside the VPS report, and short spikes between samples may not show. **For accurate, detailed monitoring, run a monitoring agent inside the VPS.** An agent sees per-process usage, real (non-cache) memory, application metrics, and can alert you. Easy options include [Netdata](https://www.netdata.cloud/) (one-line install, live dashboard), or Prometheus `node_exporter` with Grafana if you already run that stack. Use the host graphs for the big picture and an in-VPS agent for the detail. ### What each graph means, and what to do about it - **CPU Usage Percentage.** How much of your vCPU allocation is in use. Short spikes are normal. **Sustained CPU near 100%** means your workload is CPU-bound: either a runaway/misbehaving process, or your plan is too small for the load. Find the process with the in-VPS agent (or `top`/`htop`); if it's legitimate and constant, upgrade. - **Memory Usage Percentage** and **Memory Usage (Used / Available).** RAM in use versus your limit. **Consistently near the limit is the clearest sign you need more RAM**, and running out risks the kernel killing your processes (OOM). One caveat: Linux uses spare RAM as disk cache, so host-side "used" can look higher than what your app strictly needs. The in-VPS agent separates cache from real usage, so check there before concluding you're short on RAM. - **Disk IOPS (Read / Write)** and **Disk Throughput (Read / Write, MB/sec).** How hard your storage is being hit. **High sustained IOPS or throughput** points to a disk-bound workload (databases, search indexes, heavy logging) and can explain slowness even when CPU and RAM look fine. If this is your bottleneck, more CPU or RAM won't help, you likely need a storage-optimized plan or to reduce disk churn. - **Network Used Data / Traffic (Download / Upload).** Bandwidth consumed over the period. Use **This Month** to see how fast you're burning through your monthly traffic allowance. - **Network Packets per Second (In / Out)** and **Network Throughput (In / Out, Mbps).** Your live network rate. Useful for spotting a traffic spike, a busy service, or a possible attack. ### Deciding whether to upgrade Look at CPU, Memory, and Disk over **This Week** or **This Month**, not just this moment: - **Low most of the time** means you have headroom (you may even be paying for more than you use). - **CPU or RAM repeatedly sitting near the limit during normal use** means it's time to size up. On a Linux VPS this is painless: upgrades are live and instant with no downtime, no data loss, and your IP stays the same. See [Upgrade/Downgrade](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade). - **Only disk is high** (IOPS/throughput or you're low on space): add storage rather than CPU/RAM, or move to a storage plan. - **Only bandwidth is high:** buy [extra traffic](https://vpsdime.com/knowledgebase/client-area/services/extra-features) or upgrade rather than resizing CPU/RAM. ### Troubleshooting a slowdown or a spike 1. Switch to **Today** or **Yesterday** and line up the time the problem happened with the graphs. 2. See which resource is pinned: - **CPU maxed** → a runaway process or an under-sized plan. - **Memory maxed** → memory pressure and swapping; expect sluggishness and possible OOM kills. - **Disk IOPS/throughput maxed** → an I/O bottleneck; everything waits on the disk. - **Network maxed** → a traffic flood, a busy service, or a possible attack. 3. Confirm the cause inside the VPS with your monitoring agent and logs, then act (fix the process, add resources, or open a ticket with the timestamp and which graph was pinned). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which graph looks wrong and roughly when (a screenshot of the Graphs tab helps), - what you were running at the time. ### Related questions - "Where do I see my VPS CPU, memory, disk, and bandwidth usage?" - "How do I know if I need to upgrade my VPS?" - "My VPS is slow, how do I find the bottleneck?" - "Are the graphs measured inside my VPS or on the host?" - "How do I get accurate, per-process resource monitoring?" - "How much bandwidth have I used this month?" - "My memory graph is always high, do I need more RAM?" --- ## The Tasks log URL: https://vpsdime.com/knowledgebase/client-area/services/tasks Last reviewed: 2026-07-02 Summary: The Tasks tab is a history of every action taken on your VPS (power, password, reinstall, firewall, network) and who did it, you or our staff. Use it to confirm what happened and to troubleshoot changes. ### What this is for The **Tasks** tab (in Manage VPS, https://vpsdime.com/myservices) is the history of actions taken on your VPS. Whenever something is done through the panel, a reboot, a password reset, a reinstall, a firewall change, it's recorded here with when it ran, whether it worked, and who started it. It's the place to answer two questions well: **what happened to my VPS, and when?** and **did a change cause this problem?** ### What's in it ![The Tasks tab: a table of actions with start and end times, a success or error status, and who initiated each (client IP or staff)](https://vpsdime.com/knowledgebase/client-area/services/images/manage-tasks.png) Each entry shows: - **Action**, what was done (for example Restart, Shutdown, Change Pass, Unlock SSH, Reinstall, Fix Network, Flush Firewall). - **Start** and **End**, when it ran. - **Status**, whether it finished or failed. A failed action is worth noticing, it can explain why something you tried didn't take effect. - **Initiated By**, either **you** (shown with the IP address you acted from) or our **Staff**. The newest actions are at the top, with older ones on the following pages. ### How to use it - **Troubleshooting.** If the VPS started misbehaving, check whether an action ran just before it: a reinstall, a network fix, a firewall change. Lining up the timestamps often points straight at the cause. - **Confirming a support action.** If you asked us to do something, or we did it proactively, it shows here marked **Staff**, with the time, so you can confirm it happened. - **A quick security check.** Since your own actions are logged with the IP you ran them from, an action from an IP you don't recognize is a red flag. If you see one, secure your account, see [Keeping your account secure](https://vpsdime.com/knowledgebase/client-area/account/keeping-your-account-secure). ### Good to know - Only actions relevant to you appear here. Routine internal operations we run across the fleet aren't listed. - An action that isn't marked finished is usually still running, give it a moment and refresh. If one stays failed, retry it, and if it keeps failing, open a ticket with the action name and time. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, mention the **action** and the **time** you see in the log, and the VPS hostname or IP. ### Related questions - "What has been done to my VPS?" - "Who restarted or reinstalled my VPS?" - "Did support make a change to my server?" - "Why did an action on my VPS fail?" - "How do I see the history of actions on my VPS?" - "I see an action from an IP I don't recognize, what do I do?" --- ## Network and IP addresses URL: https://vpsdime.com/knowledgebase/client-area/services/network Last reviewed: 2026-07-02 Summary: The Network tab lists your VPS's IPv4 and IPv6 addresses with their netmask and gateway, and lets you set reverse DNS (PTR). Set rDNS for mail deliverability, use the netmask and gateway for manual network config, and request IPv6 or extra IPs when you need them. ### What this is for The **Network** tab (in Manage VPS, https://vpsdime.com/myservices) shows the IP addresses assigned to your VPS and their network settings, and lets you set **reverse DNS**. You'll come here to look up your netmask and gateway (for manual network configuration), to set a PTR record for an IP (important if you send email), and to see your IPv6 allocation. ### Your IPv4 addresses ![The Network tab: the IPv4 address with its netmask, gateway, and rDNS edit icon, and the IPv6 section below with a link to request an allocation](https://vpsdime.com/knowledgebase/client-area/services/images/manage-network.png) Each IP is listed with its **Netmask** and **Gateway**, and your **main IP** is marked with a star. - The **netmask and gateway** are what you'd enter if you configure the network **statically inside the VPS**. Most setups get this automatically, so you rarely need to touch it, but it's here for when you do (for example when adding a second IP or troubleshooting connectivity from inside the OS). - To add more IPv4 addresses, order them under [Extra Features](https://vpsdime.com/knowledgebase/client-area/services/extra-features) (there's an "Order More IPs" shortcut on the Information tab). Additional IPs can require a short justification. ### Reverse DNS (rDNS / PTR) Reverse DNS maps your IP back to a hostname. It matters most if you **send email** from your VPS: many mail servers reject or spam-folder mail from an IP whose PTR doesn't resolve, and ideally the PTR should match your sending hostname. Set it in the **rDNS** column with the edit icon, entering the hostname the IP should resolve to. - Point the PTR at your mail server's hostname (for example `mail.example.com`), and make sure that hostname also has a matching **A record** pointing back to the same IP. If we host your DNS, do that in the [DNS Manager](https://vpsdime.com/knowledgebase/client-area/services/dns). - rDNS changes can take a little while to take effect. ### IPv6 If your VPS has an IPv6 allocation, you'll see your **IPv6 block** (a /64) and address here. A /64 is a huge range you can assign from inside the VPS. If you don't have IPv6 yet, there's a link to **request one by ticket**. ### Troubleshooting - **My static network config broke connectivity.** Check that the netmask and gateway you set inside the VPS match what's shown here, and prefer the VPS's default automatic (cloud-init/DHCP) config unless you specifically need static. If you've locked yourself out, fix it from the [Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps). - **My outgoing mail is rejected or lands in spam.** Set rDNS here to your sending hostname (with a matching A record), and set up SPF, DKIM, and DMARC in your [DNS](https://vpsdime.com/knowledgebase/client-area/services/dns). rDNS alone isn't enough, but missing rDNS is a common cause. - **I need more IPv4 addresses or an IPv6.** Order IPv4 under Extra Features; request IPv6 by ticket from this tab. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what you're trying to do (set rDNS, configure a static IP, add an IP, or get IPv6), - the exact values you used and any error. ### Related questions - "What are my VPS's IP address, netmask, and gateway?" - "How do I set reverse DNS (rDNS/PTR) for my IP?" - "Why is my outgoing email rejected or going to spam?" - "How do I get an IPv6 address?" - "How do I add another IP to my VPS?" - "How do I configure a static IP inside my VPS?" --- ## DNS Manager URL: https://vpsdime.com/knowledgebase/client-area/services/dns Last reviewed: 2026-07-05 Summary: VPSDime's free DNS hosting, add a domain, point your registrar's nameservers to dns1/dns2.vpsdime.com, and manage A, AAAA, CNAME, NS, MX, TXT, SRV, and CAA records. ### What this is The **DNS Manager** is free DNS hosting for your domains, so you can [point a domain at your VPSDime VPS](https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain) without a separate DNS provider. You add your domain, set your registrar's nameservers to ours, and manage the records here. It's free and provided for convenience, with no uptime guarantees. Open it from **DNS** in the client area sidebar (https://vpsdime.com/dnsmanager). To use it you need a domain (registered with any registrar) and a VPSDime VPS to point it at. Our nameservers are: - **dns1.vpsdime.com** - **dns2.vpsdime.com** ### Add a domain ![The DNS Manager: a How to Point Your Domain notice, the domains list with nameservers, and Manage / Delete buttons plus Add New Domain](https://vpsdime.com/knowledgebase/client-area/services/images/dns-zones.png) 1. Go to **DNS** and click **Add New Domain**. 2. Enter your **domain**. Use the root domain (for example `example.com`), not a subdomain. You can't add a subdomain as its own domain here. Add the root domain, then create records for subdomains inside it. 3. Choose the **VPS IP** to point it at, from the list of your services. 4. Click **Submit**. ![The Add New Domain dialog: a Domain field and a VPS IP selector](https://vpsdime.com/knowledgebase/client-area/services/images/cropped/dns-add-domain-dialog.png) This creates the zone with **NS** records (dns1/dns2.vpsdime.com) and an **A** record pointing your domain at the VPS IP you chose. ### Point your domain's nameservers Adding the domain here doesn't make it live on its own. At **your registrar** (where you bought the domain), set the domain's nameservers to: - **dns1.vpsdime.com** - **dns2.vpsdime.com** Until you do this, your records here won't take effect. Nameserver changes at a registrar can take up to 24 to 48 hours to propagate worldwide. ### Manage records Click **Manage** on a domain to open its records. Each record shows its **Type**, **Name**, **Value**, **TTL**, and dates, with **Edit** and **Delete** buttons. Use **Add New Record** to create one. ![A domain's records: the NS and A records created with the zone, each with Edit and Delete buttons, and an Add New Record button](https://vpsdime.com/knowledgebase/client-area/services/images/dns-records.png) A record has four fields: - **Type:** the kind of record (see below). - **Name:** `@` means the domain itself (the root). For a subdomain, enter just the label, for example `www` or `blog`. - **Value:** the record's target, which depends on the type. - **TTL:** how long resolvers cache the record before checking again. Options are 5 Minutes, 1 Hour, 2 Hours, 6 Hours, 12 Hours, and 1 Day. A shorter TTL makes changes take effect sooner but is queried more often. ![The Add New Record dialog: Type, Name, Value, and TTL fields; the Type selector explains each record type](https://vpsdime.com/knowledgebase/client-area/services/images/cropped/dns-add-record-dialog.png) #### Record types - **A** routes a name to an **IPv4** address. Example value: `192.0.2.235`. - **AAAA** routes a name to an **IPv6** address. Example value: `2001:0db8::8a2e:0370:bab5`. - **CNAME** points one name at another name (an alias). Example: Name `www`, Value `example.com`. - **NS** sets the nameservers for the zone. Example value: `dns1.vpsdime.com`. - **MX** sets your mail servers. The value is a **priority** then the mail server, for example `10 mail.example.com.` (a lower priority number is tried first). - **TXT** holds text values, used for things like SPF, DKIM, DMARC, and domain verification. Example value: `"v=DMARC1;p=quarantine;pct=100"`. - **SRV** points a service to the server that provides it (used by SIP, XMPP, and some game servers). The Name is `_service._protocol`, for example `_sip._tcp`, and the value is **priority weight port target**, for example `10 5 5060 sip.example.com`. - **CAA** controls which certificate authorities are allowed to issue certificates for your domain. The value is **flags tag value**, for example `0 issue letsencrypt.org` (use tag `issue`, or `issuewild` for wildcard certs). Record changes within a zone take effect within the record's **TTL**, since resolvers may have the old value cached until then. #### Email authentication (SPF, DKIM, DMARC) Email records are all **TXT** records. A few notes so they work first time: - **SPF** goes on the root (`@`) as a single TXT value, for example `v=spf1 include:_spf.example.com ~all`. - **DKIM** goes on the selector name your mail provider gives you, for example Name `s1._domainkey` (enter the selector exactly as provided). Paste the whole key value your provider shows, including long 2048-bit keys, we store and serve it as one value. If your provider hands you the key already split into `"..." "..."` quoted parts, you can paste it that way too. - **DMARC** goes on Name `_dmarc`, for example `v=DMARC1; p=quarantine; pct=100`. ### Delete a domain **Delete** on the zones list removes the domain and all its records from our DNS. If your registrar's nameservers still point to dns1/dns2.vpsdime.com after that, the domain will stop resolving, so only delete it once you've moved DNS elsewhere or no longer need the domain to resolve. ### Troubleshooting - **My domain isn't resolving.** Check that your registrar's nameservers are set to **dns1.vpsdime.com** and **dns2.vpsdime.com**, and that you've added the right records here. After a nameserver change, allow up to 24 to 48 hours. - **"This domain name already exists."** The domain is already in our DNS system (it may have been added before, or on another account). [Open a ticket](https://vpsdime.com/open-ticket/) if you believe it shouldn't be. - **My record was rejected.** Check the value matches the type: an **A** record needs a valid IPv4 address, an **AAAA** record a valid IPv6 address, an **MX** record needs a numeric priority before the mail server (for example `10 mail.example.com.`), an **SRV** record needs a `_service._protocol` name and a `priority weight port target` value, and a **CAA** record needs a `flags tag value` (for example `0 issue letsencrypt.org`). - **My DKIM record isn't working.** Enter the selector exactly as your mail provider gives it in the **Name** field (for example `s1._domainkey`), and paste the full key in the **Value** field. Give the record its TTL to propagate, then re-check with your provider. - **I changed a record but still see the old value.** DNS is cached by TTL. Wait for the record's TTL to pass, and note your own network or resolver may cache longer. - **Is the DNS service guaranteed?** No. It's free and provided for convenience, without an uptime guarantee. For critical setups you may prefer a dedicated DNS provider. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the domain involved, - what you're trying to do (add a domain, point it to a VPS, or fix a record), - the record type and value if it's about a specific record, - any error you saw. ### Related questions - "How do I point my domain to my VPS?" - "What nameservers do I use for VPSDime DNS?" - "How do I add a domain to the DNS Manager?" - "How do I add an A, MX, or TXT record?" - "What's the format for an MX record?" - "How do I add a DKIM, SPF, or DMARC record?" - "How do I add an SRV or CAA record?" - "Why isn't my domain resolving yet?" - "How long do DNS changes take to apply?" - "Is the free DNS service guaranteed?" --- ## The VPS firewall URL: https://vpsdime.com/knowledgebase/client-area/services/firewall Last reviewed: 2026-07-05 Summary: Linux and Storage VPS come with a managed firewall that blocks the internet from reaching risky app ports (databases, caches, panels) by default, while leaving SSH and web open. Whitelist the sources that need access per-app, or globally for a trusted IP. ### What this is, and why it exists Linux VPS and Storage VPS come with a **managed firewall** (in Manage VPS, https://vpsdime.com/myservices) at our network edge. By default it **blocks the internet from reaching the application ports most often attacked**: databases and datastores (PostgreSQL, MSSQL, MongoDB, Redis, Memcached), search and messaging (Elasticsearch, Apache Solr, RabbitMQ), and a handful of other commonly exposed services (Docker API, Ollama, ZooKeeper, Erlang/epmd, Selenium Grid). It does **not** touch the ports you normally need open, SSH (22) and web (80/443). The Firewall tab lists every blocked app with its exact ports. The point is to stop the single most common way VPSes get compromised: a database or cache left listening to the whole internet with a weak or default password. With this on, those services are reachable only from sources you explicitly allow. This is the network firewall, found on Linux and Storage VPS. It's separate from the [SSH firewall](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall) that blocks brute-force logins on port 22. Premium and Windows VPS don't have this tab. ### Exactly what's blocked | Application | Ports | |---|---| | MongoDB | tcp/27017, tcp/27018, tcp/27019 | | MSSQL | tcp/1433 | | PostgreSQL | tcp/5432, tcp/5433, tcp/5434, tcp/5435 | | Redis | tcp/6379 | | Elasticsearch | tcp/9200, tcp/9300 | | Apache Solr | tcp/8983 | | Memcached | tcp/11211, udp/11211 | | RabbitMQ | tcp/5672, tcp/15672, tcp/25672 | | ZooKeeper | tcp/2181, tcp/2888, tcp/3888 | | Docker API (plain HTTP) | tcp/2375 | | Selenium Grid | tcp/4442, tcp/4443, tcp/4444 | | Ollama | tcp/11434 | | Erlang Port Mapper (epmd) | tcp/4369 | Everything else is untouched: SSH (22), HTTP/HTTPS (80/443), mail, DNS, game servers, VPN tunnels, and any custom application port. If your workload doesn't use anything in the table, the firewall is already doing the right thing for you with no action needed. ### The thing you'll most often use it for **"I can't connect to my database (or Redis, etc.) from my app or laptop."** That's the firewall doing its job, the port is blocked by default. To allow it, add the IP that needs access to that app's row in the **Per-Application Whitelist** and save. Access opens immediately. ### Two ways to allow access - **Per-Application Whitelist (recommended).** Open one blocked app to specific sources, for example allow your web server's IP to reach the database port, and nothing else. This is the safe choice: you open only what you need, to only who needs it. ![The Per-Application Whitelist: one row per blocked app (with its ports), each with a box for the sources allowed to reach it](https://vpsdime.com/knowledgebase/client-area/services/images/cropped/firewall-per-app.png) - **Global Whitelist.** Trust an IP or subnet across **all** apps on this VPS, bypassing every per-app block. Handy for a fixed admin IP like your office, but broad, so use it sparingly. Your own VPSes with us **already trust each other automatically**, so traffic between your servers needs no whitelisting. ### What to enter One entry per line, in any of these forms: - Single IPv4: `203.0.113.5` - IPv4 subnet (up to /16): `203.0.113.0/24` - Single IPv6: `2001:db8::1` - IPv6 subnet (up to /48): `2001:db8::/64` Limits: up to **64 entries** per list, and a catch-all (`0.0.0.0/0` or `::/0`) isn't allowed, whitelisting the whole internet would defeat the purpose. Changes **apply immediately, no reboot**. ### Turning protection on or off ![The Firewall Protection status (PROTECTION: ON with a turn-off button) and the Global Whitelist box with its Save Whitelist button](https://vpsdime.com/knowledgebase/client-area/services/images/cropped/firewall-status-global.png) The **Status** shows whether the firewall is actively blocking. You can turn it off if you'd rather run your **own** firewall inside the VPS (ufw, firewalld, iptables, CSF), but then locking those ports down is entirely on you. Our advice: **keep it on** unless you already run a properly configured firewall yourself. It's a free safety net. Your whitelists aren't deleted when you turn protection off. They stay saved, and become active again the moment you turn it back on. ### Good to know, and troubleshooting - **A port I whitelisted still won't connect.** Check three things: the source IP is exactly right (your real **public** IP from a "what is my IP" site, not a LAN address); you added it to the correct app (or to Global); and the **service inside the VPS is actually listening** on that port and bound to a public address, not just `127.0.0.1`. Check from inside the VPS with `ss -tulnp | grep :`, you want a LISTEN line on `0.0.0.0` or a public address. - **It works from one location but not another.** You whitelisted a single IP, add the other source too, or use a subnet if it's a range. - **I can't reach MySQL/MariaDB (port 3306).** MySQL isn't in the default-blocked list, so this firewall isn't the cause. Check that the service is listening on a public address (not just `127.0.0.1`) and any firewall running inside the VPS. - **I opened SSH or HTTP and nothing changed.** Those aren't blocked by this firewall to begin with. If you can't reach SSH, see [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) and the [SSH firewall](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall). - **My VPS can't connect *out* to something.** Not this firewall, and not us: everything here filters **inbound** traffic only, and we don't filter or block any **outbound** connectivity at the network level. If your VPS can't reach a remote service, an API, a mail server, a payment endpoint, the block is either a firewall you run **inside** the VPS or, most often, **the remote side** refusing the connection (their firewall, rate limiting, or blocklists, some services block datacenter IP ranges wholesale). "Works from my home connection but not from the VPS" is the signature of remote-side filtering, and the fix lives with that service, not with a setting here. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which app/port you're trying to reach and from which source IP, - whether the service is listening inside the VPS. ### Related questions - "Why can't I connect to my PostgreSQL/MongoDB/Redis from outside?" - "How do I open a port on my VPS?" - "How do I whitelist my IP for a blocked service?" - "What ports does the VPS firewall block by default?" - "What's the difference between the per-app and global whitelist?" - "Can I turn the firewall off and manage my own?" - "Do you block or filter outgoing connections from my VPS?" - "Why can't my VPS connect to a remote API or service?" --- ## SSH Keys URL: https://vpsdime.com/knowledgebase/client-area/services/ssh-keys Last reviewed: 2026-07-02 Summary: Save your SSH public keys to your account and select them when deploying a new VPS or reinstalling, on Linux and Premium VPS. ### What this is The **SSH Keys** page stores your SSH **public** keys on your account, so you can pick a key from a dropdown when you deploy a new VPS or reinstall one, instead of pasting it each time. Open it from **SSH Keys** in the client area sidebar (https://vpsdime.com/sshkeys). - You always add the **public** key (the `.pub` file). Never paste your private key anywhere. - Saved keys are account-wide and work across your servers, on **Linux VPS** and **Premium VPS**. Windows VPS doesn't use this. If you don't have a key yet, create one on your own computer, for example: ``` ssh-keygen -t ed25519 ``` That makes a private key and a public key (`~/.ssh/id_ed25519.pub`). You add the **public** one here. ### Add a key On the SSH Keys page, under **Add SSH Key**, there are two tabs. ![The SSH Keys page: the Add SSH Key card on its Paste Key tab (Key Name and Public Key fields), with the Saved Keys list below showing name, type, fingerprint, and source](https://vpsdime.com/knowledgebase/client-area/services/images/ssh-keys.png) #### Paste a key 1. Open the **Paste Key** tab. 2. **Key Name:** a label so you recognise it later, for example "Work Laptop". 3. **Public Key:** paste the full contents of your public key file. It starts with `ssh-ed25519`, `ssh-rsa`, or `ecdsa-sha2-…` and is a single line. 4. Click **Save Key**. #### Import from GitHub or GitLab 1. Open the **Import from GitHub / GitLab** tab. 2. Choose the **Provider** (GitHub or GitLab) and enter your **Username**, then click **Fetch Keys**. This reads the public keys published on your GitHub or GitLab profile. 3. Select the keys you want and import them. Keys already on your account are flagged so you don't add duplicates. ![The Import from GitHub / GitLab tab: a Provider dropdown, a Username field, and a Fetch Keys button](https://vpsdime.com/knowledgebase/client-area/services/images/cropped/ssh-keys-import-tab.png) ### Your saved keys The **Saved Keys** list shows each key's **Name**, **Type** (RSA, ED25519, ECDSA-256/384/521, or DSA), **Fingerprint** (a SHA256 fingerprint), **Source** (manual, github, or gitlab), and when it was added. You can copy or delete a key from here. Adding the same key twice is blocked (matched by fingerprint). ### Use a key on a VPS You choose a saved key when you create a server or reinstall its OS. In both places there's a **"-- Select a saved key or paste below --"** dropdown, plus **Manage Keys** and **Import from GitHub / GitLab** buttons and a paste box if you'd rather not use a saved key. #### When deploying a new VPS On the configure page (**Deploy**, then a plan), open **Optional Configuration**. Pick your key under **Root Public SSH Key** (and a user key if you're creating a user). The key is added to the new server during setup. #### When reinstalling In **Manage VPS**, open the **Reinstall OS** tab. Under **Public SSH Key for root** (and **for User**), select a saved key, or paste one. If you paste a new key, a **Save this key** link lets you store it to your account at the same time. #### Login mode Both flows let you set an **SSH Login Mode** for root and for the user: - **Login Using Password** also allows logging in with your SSH key. - **Login with SSH Key Only** turns off password login, so you must use your key. - **Disable Login** turns off login for that account. If you choose **Login with SSH Key Only**, make sure you've actually set a valid key for that account first, otherwise you can lock yourself out. ### Connecting Once the VPS is built with your key, connect using the matching **private** key from your computer: ``` ssh root@your-server-ip ``` ### Troubleshooting - **"Invalid SSH public key format."** The key must start with `ssh-rsa`, `ssh-ed25519`, `ecdsa-sha2`, and so on. Paste the **public** key (the `.pub` file), as a single line, not your private key. - **"This key is already saved."** That exact key (by fingerprint) is already on your account, possibly under a different name. - **Import found no keys.** Check the GitHub or GitLab username, and that the account has public keys listed on its profile. - **I can't log in with my key.** Confirm you selected the right key when deploying or reinstalling, that you're connecting with the **matching private key**, and that you didn't pick a Login Mode that disables the login you're trying to use. If you chose key-only and no key took effect, [open a ticket](https://vpsdime.com/open-ticket/). - **I have a Windows VPS.** SSH keys aren't used for Windows VPS. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP (if it's about a specific server), - whether it's about saving a key, deploying, reinstalling, or logging in, - the key type, and any error you saw. **Never share your private key or your password in a ticket.** We only ever need your **public** key. ### Related questions - "How do I add an SSH key to my account?" - "How do I deploy or reinstall a VPS with my SSH key?" - "Can I import my keys from GitHub or GitLab?" - "What SSH key types are supported?" - "What's the difference between the SSH login modes?" - "How do I log in with SSH key only?" - "Why won't my SSH key let me log in?" - "Do Windows VPS support SSH keys?" --- ## Reinstalling your OS URL: https://vpsdime.com/knowledgebase/client-area/services/reinstall-os Last reviewed: 2026-07-06 Summary: The Reinstall OS tab wipes your VPS and installs a fresh operating system (or a one-click application), with your SSH key, login mode, and passwords for both root and an optional user set up front. It erases everything, so back up first, and prefer rescue over reinstall when your data matters. ### What this is for **Reinstall OS** (in Manage VPS, https://vpsdime.com/myservices) wipes your VPS and lays down a clean operating system. Use it to start fresh, switch to a different distribution, or recover from a system that's too broken to fix. It usually takes about 3 to 5 minutes, and you get an email when it's done. ### Read this first: it erases everything Reinstalling **deletes all data on the VPS**, files, databases, configuration, everything. There's no undo. Before you reinstall: - **Back up anything you need.** If you have [Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview), make sure a recent backup exists (or download what matters). Otherwise copy your data off first. - If the goal is to **fix** a broken system rather than start over, don't reinstall, use the [Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) or, on Premium VPS, [Boot from ISO](https://vpsdime.com/knowledgebase/client-area/services/boot-from-iso) to repair it and keep your data. ### Choosing what to install ![The Reinstall OS tab: the data-loss warning above the Operating Systems grid, with an Applications (beta) tab alongside](https://vpsdime.com/knowledgebase/client-area/services/images/cropped/reinstall-warning-os.png) - **Operating System.** Pick a distribution from the list (Ubuntu, Debian, AlmaLinux, Rocky, Arch, CentOS, Fedora, openSUSE, Alpine, and more). Choose a version you'll get updates for, current LTS releases are the safe default for most people. - **Applications (beta).** Instead of a bare OS, you can pick a one-click application to have a common stack installed and pre-configured for you. Handy if you just want the app running without setting it up by hand. ### Set up access before you reinstall The form sets up your logins up front so you can get straight in when the reinstall finishes. It configures two accounts: **root** (always), and optionally a **regular user** you create at the same time. Each has the same three fields, a password, an SSH key, and a login mode, set independently. #### Recommended: create a user, don't rely on root For everyday use, log in as a regular user and run `sudo` for admin tasks instead of logging in directly as **root**. Root can change anything on the system, so a slip or a compromised root login does far more damage. A safer, common setup: - Enter a **Username** to have a sudo-capable user created, give it your SSH key, and use it to log in. - Lock down **root**: set its login mode to **Login with SSH Key Only** (or **Disable Login**) so root can't be brute-forced over SSH. You can skip the user and just use root if you prefer, both are fully supported. Using an [SSH key](https://vpsdime.com/knowledgebase/client-area/services/ssh-keys) rather than a password is the recommended way in either way. #### Root account - **Root password.** Generated for you with a strength meter, keep it or set your own. - **Public SSH Key for root.** Pick a saved key, paste one, or import from GitHub/GitLab. - **Root SSH Login Mode**, how root may sign in over SSH: - **Login Using Password (will allow login with SSH Key as well)**, accepts either the password or a key. - **Login with SSH Key Only**, turns off password login for root. More secure, but only choose it if you've actually set a key above, or you'll be locked out of root. - **Disable Login**, switches off SSH login for root entirely (no password, no key). Only choose this if you've created a user to log in with, otherwise you'll have no way in over SSH. ![The root access fields on the reinstall form: a generated root password with strength meter, the Public SSH Key for root selector with GitHub/GitLab import, and the Root SSH Login Mode dropdown](https://vpsdime.com/knowledgebase/client-area/services/images/cropped/reinstall-access.png) #### User account (optional) Leave **Username** blank to skip this. Fill it in to have a regular user created during the reinstall, with the same options as root, applied to that user: - **Username.** The login name for the new user. Leaving it empty means no user is created. - **User Password.** Generated or your own. - **Public SSH Key for User.** A saved, pasted, or imported key for this user. - **User SSH Login Mode.** The same three choices as root (password and key, key only, or disabled), applied to the user account. ![The optional user fields on the reinstall form: Username, User Password, the Public SSH Key for User selector, and the User SSH Login Mode dropdown](https://vpsdime.com/knowledgebase/client-area/services/images/cropped/reinstall-user.png) On a **Windows VPS**, reinstalling reinstalls Windows and you connect over RDP with the Administrator password. ### Do it Once you've chosen the OS (or app) and set your access, start the reinstall and wait for the completion email. Then connect with your key or password. ### Good to know, and troubleshooting - **I can't log in after reinstalling.** Check you're using the right username, `root`, or the user you created, and the key or password you set for that account. If you set **root** to key-only or **Disable Login**, log in as your user instead (then use `sudo`). If a key didn't take effect or you're locked out of every account, reset the password from the [Console / management page](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps). - **My IP got blocked right after reinstalling.** Repeated wrong-password attempts can trip the [SSH firewall](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall), whitelist your IP there. - **SSH warns "REMOTE HOST IDENTIFICATION HAS CHANGED".** Normal after a reinstall, the fresh OS has a new host key. [The one-line fix](https://vpsdime.com/knowledgebase/troubleshooting/host-identification-changed). - **The reinstall seems stuck.** It's usually done within a few minutes; check the Tasks log and your email. If it's much longer, open a ticket. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the OS or app you reinstalled, - what happens when you try to connect. ### Related questions - "How do I reinstall my VPS?" - "Will reinstalling delete my data?" - "How do I switch my VPS to a different Linux distro?" - "How do I install an app when I reinstall?" - "How do I set up my SSH key during reinstall?" - "I reinstalled and now I can't log in, what do I do?" --- ## Boot from ISO (Premium VPS) URL: https://vpsdime.com/knowledgebase/client-area/services/boot-from-iso Last reviewed: 2026-07-02 Summary: Premium VPS can boot from a rescue ISO (System Rescue CD) instead of their disk, to rescue an unbootable system. Your disk stays intact, so you can mount and repair it from the rescue environment. Access it through the Console. ### What this is for **Boot From ISO** (on **Premium VPS**) starts your VPS from a rescue ISO instead of from its own disk. Use it to **rescue a system that won't boot**, a bad kernel, a broken `/etc/fstab`, a botched update, or a filesystem that needs checking. You boot into the rescue environment, then mount your disk from it to fix the problem without wiping anything. The image on offer is **System Rescue CD**, a general-purpose Linux rescue system. If you need to boot a different ISO, [open a ticket](https://vpsdime.com/open-ticket/) and ask. The important part: **your disk isn't touched by booting an ISO.** It's a non-destructive way in when the installed system is broken, unlike a [reinstall](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os), which erases everything. ### How to use it ![The Boot From ISO tab on a Premium VPS: the System Rescue CD image selected under "ISO To Boot From", with the Boot From ISO button below](https://vpsdime.com/knowledgebase/client-area/services/images/manage-boot-from-iso.png) 1. Open **Manage VPS** (via https://vpsdime.com/myservices), then **Boot From ISO**. 2. Select **System Rescue CD** and click **Boot From ISO**. 3. Open the **[Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps)** to see the booted ISO, the rescue environment has no SSH, so the Console is how you work in it. 4. From the rescue shell, mount your disk (it's a separate device from the ISO), fix what's wrong, unmount, and reboot. 5. When you're finished, reboot the VPS to boot back into your installed system. If it stays on the rescue ISO, open a ticket and we'll switch it back. ### A typical rescue If your VPS won't boot after a change: 1. Boot System Rescue CD and open the Console. 2. Mount your root partition (for example `mount /dev/vda1 /mnt`). 3. Fix the cause, revert a bad `/etc/fstab` line, reinstall a working kernel with `chroot`, run a filesystem check (`fsck`), or copy off data you need. 4. Unmount and boot from disk again. If you're not comfortable doing this, open a ticket, tell us what changed and the exact error, and we can help. ### Boot from ISO vs Reinstall - **Boot from ISO** keeps your data, use it to **fix** a broken system or recover files. - **[Reinstall OS](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os)** wipes the VPS and lays down a fresh OS, use it to **start over**. Try the rescue route first if the data on the VPS matters. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what happened before it stopped booting (the change you made, the exact error on screen), - whether you can reach the Console. ### Related questions - "My VPS won't boot, how do I rescue it?" - "How do I boot into rescue mode?" - "How do I recover data from a VPS that won't start?" - "How do I fix a broken fstab or bootloader?" - "Can I install my own OS from an ISO?" - "What's the difference between booting an ISO and reinstalling?" --- ## Upgrading or downgrading your VPS URL: https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade Last reviewed: 2026-07-04 Summary: The Upgrade/Downgrade tab switches your VPS to a bigger or smaller plan. On Linux VPS it's live and instant, no downtime, no data loss, same IP, and downgrades need enough free disk. Premium VPS is upgrade-only. You pay the prorated difference. ### What this is for The **Upgrade/Downgrade** tab moves your VPS to a different plan, more (or less) CPU, RAM, storage, and traffic. Reach for it when the [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) show you're consistently hitting a limit (upgrade), or paying for more than you use (downgrade). ### What to expect (Linux VPS) On a **Linux VPS**, changing plan is **live and instant**: - **No downtime**, the VPS keeps running through it. - **No data loss**, everything on the disk stays put. - **Your IP stays the same.** - Running services keep serving. The change applies as soon as you pay the upgrade invoice. On **Premium VPS** and **Windows VPS**, applying new resources can involve a short reboot. If the timing matters to you on those, ask us first. ### How to do it 1. Open **Manage VPS** (via https://vpsdime.com/myservices), then **Upgrade/Downgrade**. 2. You'll see the available plans with their CPU, Memory, Storage, Traffic, price, and a **Prorated Due Now**, the amount for the rest of your current billing term. Your current plan is marked. ![The Upgrade/Downgrade tab: every plan with its specs, monthly price, and Prorated Due Now amount, the current plan marked, and a Select button per row](https://vpsdime.com/knowledgebase/client-area/services/images/manage-upgrade.png) 3. Click **Select** on the plan you want and pay the prorated invoice. The new plan applies (instantly on Linux VPS). From then on you're billed at the new plan's rate on your normal cycle. ### Downgrading **Switching product lines (say Linux VPS to Premium VPS) isn't a resize.** The Upgrade/Downgrade tab moves you between plans **within your product line**; there's no in-place conversion from one line to another. The path is ordering the new VPS and moving your data across, the whole procedure, including the two-pass rsync and the new-IP checklist, is in [Migrating a VPS to a new server](https://vpsdime.com/knowledgebase/getting-started/migrating-a-vps). **Linux to Windows (or Windows to Linux) can't be migrated at all.** They're different operating systems: applications are installed differently, services are configured differently, and a Linux disk means nothing to Windows. If you want to switch, order the new [Windows VPS](https://vpsdime.com/windows-vps) (or Linux VPS), reinstall your applications there, copy over the data files you need (over SFTP), and then [cancel](https://vpsdime.com/knowledgebase/client-area/services/cancellation) the old service. **Premium VPS is upgrade-only.** You can move a Premium VPS up to a bigger plan, but not back down to a smaller one, so pick a Premium size you won't need to shrink. On **Linux VPS** and **Windows VPS**, downgrading works the same way as upgrading, with one catch: the smaller plan must have **room for your data**. If your disk usage is close to (or above) the smaller plan's disk size, some downgrades are blocked until you **free up space**, you need a couple of GB free after the downgrade. Delete or move data first, then try again. Downgrades don't come with a refund or credit for the difference, you're simply billed less from the next cycle. ### Plan change vs add-ons - Use **Upgrade/Downgrade** to move between whole plans. - Use [Extra Features](https://vpsdime.com/knowledgebase/client-area/services/extra-features) to add resources one at a time (extra storage, vCPU, traffic, or IPs) without changing your base plan. If you only need, say, more disk, adding storage in Extra Features is often simpler than jumping to a bigger plan. ### Good to know, and troubleshooting - **The options are missing, or I see "Upgrade Unavailable."** You usually have a **pending order** on the VPS (for example an add-on you started but haven't paid). Finish or cancel it and the plan options come back. The tab is also unavailable while a service is pending provisioning, cancelled, or terminated. - **A smaller plan I want is greyed out.** On Linux VPS, your disk usage is too high for it, free up space and retry. On Premium VPS, smaller plans aren't offered at all, Premium is upgrade-only. - **Will upgrading interrupt my sites?** On Linux VPS, no, it's live and your IP doesn't change, so nothing needs reconfiguring. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the plan you want to move to, - whether you're upgrading or downgrading, and any message you saw. ### Related questions - "How do I upgrade or downgrade my VPS?" - "Will upgrading my VPS cause downtime or change my IP?" - "Will I lose my data when I resize?" - "How much does an upgrade cost right now (proration)?" - "Why can't I downgrade to a smaller plan?" - "Can I downgrade my Premium VPS?" - "Can I convert my Linux VPS to a Premium VPS?" - "Can I switch my Linux VPS to a Windows VPS?" - "Should I upgrade the plan or just add storage/CPU?" --- ## Moving your VPS to another location URL: https://vpsdime.com/knowledgebase/client-area/services/migrate-location Last reviewed: 2026-07-05 Summary: Your VPS can be moved to a different datacenter. The $4 migration fee applies when your data moves with it, ordered from the manage page, with a ticket opening after payment. If you don't need the data, ordered the wrong location and haven't used the VPS yet, or were going to reinstall anyway, we re-provision it in the location you want for free. Your IP address changes with the location either way, so the move comes with homework: DNS, SPF, rDNS, SSL, and anything pinned to the old IP. ### What this is Your VPS lives in one of our datacenters, and sometimes the right one changes: your users turned out to be mostly in Europe, latency matters to a trading setup, or you simply picked a location on day one that no longer fits. You order the move from your VPS's [manage page](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) for a **$4 fee**; after payment, a **ticket opens with our team** and we carry out the migration. Everything on the VPS moves with it, the OS, your applications, your data. For other products, [ask us](https://vpsdime.com/open-ticket/) and we'll see what's possible for your case. ### Don't need the data? The move is free The **$4 fee applies when you want your data migrated** with the VPS. If there's nothing on it you need to keep, there's nothing to migrate, and we'll simply **re-provision the VPS in the location you want, for free**. That covers two common cases: - **You just ordered and picked the wrong location.** If you haven't used the VPS yet, [contact us](https://vpsdime.com/open-ticket/) and we'll re-provision it where you meant to deploy it, no migration fee. - **You were going to reinstall anyway**, or the data on it doesn't matter. Same deal: open a ticket, tell us the location you want, and we'll re-provision it there fresh. Re-provisioning means the VPS starts clean in the new location, so anything on the disk is gone, and the IP changes either way (see below). ### The one big consequence: your IP changes IP addresses belong to a location, so **a move always means a new IP**, we don't offer floating or portable IPs that follow a VPS between datacenters. That's not a footnote, it's the part that needs planning: - **DNS**: update the A/AAAA records for every domain pointing at the VPS, and lower the TTL ahead of the move if you want the switch to propagate quickly. - **Mail**: if the VPS sends email, update **SPF** records that name the old IP, and set the **reverse DNS (PTR)** for the new IP on the [Network tab](https://vpsdime.com/knowledgebase/client-area/services/network) again, rDNS does not follow you. - **Anything pinned to the old IP**: firewall allowlists at third parties, API access lists, monitoring, hardcoded IPs in configs or client software. - **SSL** certificates keyed to domains are fine once DNS points at the new IP; certificates or validations tied to the IP itself need redoing. This is the same checklist as any server move, the [migration guide](https://vpsdime.com/knowledgebase/getting-started/migrating-a-vps) covers it in depth. ### Deciding whether the move is worth it The honest test is measurement, not intuition: check the latency your actual users get to your current location versus the candidate (our [Looking Glass](https://vpsdime.com/looking-glass) lets you ping and download from each location before committing). A 20 ms improvement matters to a game server or trading bot; for a typical website behind a CDN it often doesn't. If you're unsure whether a move buys you anything, [open a ticket](https://vpsdime.com/open-ticket/) and describe the situation first. ### How to start it For a move **with your data** (the $4 migration): 1. Open your VPS's [manage page](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) (https://vpsdime.com/myservices). 2. Use **Migrate to Another Location** and choose the destination. 3. Pay the **$4 fee**. A **support ticket opens automatically**, and our team performs the move, follow that ticket for timing and updates. 4. When the move completes, work through the IP checklist above, DNS first. For a free re-provision **without the data**, skip the button: just [open a ticket](https://vpsdime.com/open-ticket/) with the VPS and the location you want. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP and the destination location you have in mind, - whether latency, compliance, or something else is driving the move, - whether your setup has IP-sensitive pieces (mail, allowlists) we should know about. ### Related questions - "Can I move my VPS to a different datacenter?" - "How much does a location migration cost?" - "I just ordered in the wrong location, can you fix it for free?" - "Can I change location without paying if I don't need my data?" - "Does my IP address change if I move my VPS?" - "How do I move my VPS closer to my users?" - "What do I need to update after moving my VPS?" --- ## Extra Features (add-ons) URL: https://vpsdime.com/knowledgebase/client-area/services/extra-features Last reviewed: 2026-07-02 Summary: The Extra Features tab lets you add resources to a VPS without changing its base plan, Nightly Backups, extra storage, extra vCPU, extra traffic, and extra IP addresses. Each is billed prorated now and on renewals; removing an add-on isn't refunded. ### What this is for The **Extra Features** tab (in Manage VPS, https://vpsdime.com/myservices) adds resources to your VPS **one at a time**, without moving to a whole new plan. If you only need more of one thing (disk, CPU, bandwidth, or an IP), this is usually simpler than a full [upgrade](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade). Add-ons stack on top of your plan and appear on your regular invoice going forward. ### How adding and removing works - **Add:** click **Buy Now** (or pick a quantity) on the feature. **Due Now** is prorated, you pay only for the days left in your current billing term. Then **Pay Invoice**, and it's applied. Going forward it's included on your renewal at its normal rate. - **Remove:** click **Remove** to drop an add-on. Per the **Downgrade Policy** shown on the tab, removed features aren't refunded or credited, you're simply billed less from the next cycle. So add what you need, but don't expect money back for removing it mid-term. - **Cancel a pending add-on:** if you clicked Buy Now but haven't paid, you can **Cancel** the pending order (its invoice is cancelled too), and re-order any time. ### The add-ons, and when to use each ![The Extra Features tab: the Downgrade Policy notice above rows for Nightly Backups, Additional Storage, Additional vCPU, Additional Traffic, and Additional IP Address, each with its price and a Submit / Remove button](https://vpsdime.com/knowledgebase/client-area/services/images/manage-extra-features.png) Use the [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) to decide which (if any) you actually need, add the one that's constrained, not more plan than you'll use. - **Nightly Backups.** A nightly off-server backup of your whole VPS with self-service restore. Highly recommended if the data on the VPS matters. It's an add-on on Linux VPS and included free on Premium VPS. Full details in [Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview), and [how to turn it on](https://vpsdime.com/knowledgebase/client-area/nightly-backups/enable-nightly-backups). - **Additional Storage.** More disk space. Add this when you're running low on storage but CPU and RAM are fine, cheaper and simpler than jumping to a bigger plan just for disk. **Removing it shrinks your disk**, so, just like a plan [downgrade](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade), your data has to fit in the reduced space: if your usage is close to (or above) what's left after removal, the removal is blocked until you **free up space** (you need a couple of GB free afterward). Delete or move data off first, then remove the add-on. - **Additional vCPU.** More CPU cores. Add this when your CPU graph is consistently pinned during normal use and you don't need more of anything else. - **Additional Traffic.** More monthly bandwidth. Add this if you're heading over your traffic allowance, or your VPS was suspended for a traffic overage, rather than upgrading the whole plan. - **Additional IP Address.** Extra IPv4 addresses at **$2/month** each, for example to run multiple sites with their own IP/SSL, or separate services. Extra IPs are subject to a short **justification** (we may ask what you need it for). To set reverse DNS on a new IP, use the [Network](https://vpsdime.com/knowledgebase/client-area/services/network) tab. ### Add-on vs upgrading the plan - Add-ons are best when **one** resource is tight. - If several are tight at once (CPU and RAM and disk), a plan [upgrade](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade) is usually better value and less fiddly. ### Good to know, and troubleshooting - **It asked me to pay an invoice.** That's expected, the add-on activates once the prorated invoice is paid. See [Viewing and paying an invoice](https://vpsdime.com/knowledgebase/client-area/billing/invoices). - **I don't want to be charged again, will removing refund me?** No, removing stops future charges but doesn't refund the current term. - **My extra IP request is asking for justification.** That's normal for IPv4, tell us briefly what it's for and we'll sort it. - **I only need more disk but the plan upgrade adds CPU/RAM too.** Use Additional Storage here instead. - **I can't remove Additional Storage, or it's blocked.** Removing it reduces your disk, and your data still has to fit. Free up space so there's a couple of GB clear after the removal, then try again, the same rule as a plan [downgrade](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which add-on you want (and how much), - any invoice number involved. ### Related questions - "How do I add more storage / CPU / bandwidth to my VPS?" - "How do I get an extra IP address?" - "How much does adding storage/vCPU/traffic cost, and is it prorated?" - "If I remove an add-on, do I get a refund?" - "Can I remove extra storage if my disk is nearly full?" - "Should I add resources or upgrade my plan?" - "How do I enable nightly backups?" --- ## Cancelling a VPS URL: https://vpsdime.com/knowledgebase/client-area/services/cancellation Last reviewed: 2026-07-05 Summary: The Cancellation tab requests cancellation of a VPS, immediately or at the end of your billing period. Cancelling deletes the VPS and its data, so back up first. You can revoke a pending cancellation before it takes effect. ### What this is for The **Cancellation** tab requests cancellation of a VPS: it stops renewing, and the server is shut down and removed. Use it when you're done with a server. This cancels **one VPS**, not your whole account, for that see [Deleting your account](https://vpsdime.com/knowledgebase/client-area/account/delete-your-account). **Placed an order by mistake and never paid it?** That's a different, simpler thing, not this tab. An unpaid order that hasn't been provisioned is cancelled from [My Services](https://vpsdime.com/knowledgebase/client-area/services/my-services) with the **Cancel** button next to its Pending Payment status (or it auto-cancels after 3 days). This page is for a service you actually have. ### Read this first: cancelling deletes your data Cancelling a VPS **permanently deletes it and everything on it**, and there's no undo once it's processed. Before you cancel, **download or back up anything you want to keep**. If you have [Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview), note that those go away with the service too, so grab what you need first. ### Immediate vs End of Billing Period When you request cancellation you choose **when** it happens: - **End of Billing Period** (usually the better choice). The VPS keeps running until the end of the term you've already paid for, then cancels automatically. Since unused time isn't refunded, you may as well use what you've paid for. - **Immediate.** The VPS is cancelled and its data deleted **shortly after you submit** (within about 12 hours), with no undo. Choose this only if you want it gone now and have your data off it. Either way, cancelling on its own doesn't refund the remaining time. If you're within the 72-hour money-back window of a new order, see [Refunds](https://vpsdime.com/knowledgebase/billing/refunds). ### How to cancel ![The Cancellation tab: the refund-policy notice, a reason dropdown and optional comments, the "end of billing period" vs "Immediately" choice, and the Submit Cancellation Request button](https://vpsdime.com/knowledgebase/client-area/services/images/manage-cancellation.png) 1. Open **Manage VPS** (via https://vpsdime.com/myservices), then the **Cancellation** tab. 2. Pick a **reason** from the dropdown (and add any **comments** if you like, they're optional). 3. Choose **At the end of my billing period** or **Immediately**, then click **Submit Cancellation Request**. ### Changed your mind? Revoke it If a VPS is set to cancel, you'll see a banner with the date. You can **revoke** the cancellation from the same **Cancellation** tab any time before it takes effect, and the VPS carries on as normal. ### Switching between Immediate and End of Billing Period Picked the wrong timing? There's no edit button, but the same two steps get you there: **revoke** the existing request on the Cancellation tab, then **submit a new one** with the timing you meant, for example, revoke an Immediate request and resubmit choosing **At the end of my billing period**. Works in either direction. One urgency note: an **Immediate** request is processed within about 12 hours of submission, and once it's processed, the VPS and its data are gone, there's nothing left to switch. If you submitted Immediate by mistake, do the revoke-and-resubmit **now**, not later today. ### Suspended for non-payment? The tab still works A service that's been **suspended for an unpaid invoice** can still be cancelled: the **Cancellation tab stays available** on its manage page, suspension takes the VPS offline, not your ability to end the service. And submitting an **Immediate** cancellation there also **cancels the unpaid invoice** for that service, so nothing remains to pay and no further charges follow. If you've decided you're done with a suspended VPS, this is the clean exit: cancel it rather than letting it sit until termination with an invoice hanging over it. One caution before you do: a suspended VPS still **has** its data until it's cancelled or terminated, and an Immediate cancellation deletes it. If there's anything on it you want, [ask us for a 24-hour unsuspension to back up](https://vpsdime.com/knowledgebase/billing/data-from-suspended-vps) first, then cancel. ### Good to know - **Cancelling vs not paying.** Cancelling is you choosing to end the service cleanly. If you just stop paying instead, the VPS is suspended and then terminated on our [billing schedule](https://vpsdime.com/knowledgebase/billing/billing-timeline), so cancelling on End of Billing Period is the tidy way to stop. - **No need to cancel anything on the payment side.** Our system only charges for **active** services, so once a VPS is cancelled (or has a cancellation request in), its [automatic renewal](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions) stops with it. You don't have to cancel a PayPal billing agreement, subscription, or saved card yourself, and you won't be charged for the cancelled service again. - **Cancelled or terminated means gone for good.** Once a VPS is cancelled or terminated, **its data cannot be restored**, not from our side either. There is no grace copy behind the scenes; deletion is deletion. - **Backups go too.** Restores rely on the service existing; once it's cancelled, its backups are gone. - **Data first.** The most common regret is choosing Immediate before copying data off. When in doubt, pick End of Billing Period and get your data. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - whether you want it cancelled immediately or at the end of the period, - and if it's about a refund, when you ordered it. ### Related questions - "How do I cancel my VPS?" - "What's the difference between immediate and end-of-billing-period cancellation?" - "Will I get a refund if I cancel?" - "Will cancelling delete my data?" - "I set my VPS to cancel by mistake, how do I undo it?" - "Does cancelling one VPS close my whole account?" - "Do I need to cancel my PayPal subscription when I cancel my VPS?" - "Will I still be charged after cancelling my service?" - "My VPS shows as Terminated or Cancelled, is my data gone?" - "Can you restore my cancelled VPS's data?" - "Can I cancel a VPS that's suspended for non-payment?" - "If I cancel a suspended service, do I still owe the unpaid invoice?" - "I chose Immediate cancellation but meant end of billing period, how do I change it?" --- ## Nightly Backups help URL: https://vpsdime.com/knowledgebase/client-area/nightly-backups Last reviewed: 2026-07-02 Summary: Help articles for VPSDime Nightly Backups, turning the add-on on, viewing backups, restoring your VPS, recovering individual files, and downloading a full disk image. Guides for backing up your VPS and getting your data back when you need it. ### Getting started - [Nightly Backups overview](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview). What it is, who has it (Linux VPS add-on vs Premium VPS included), the once-a-night schedule, and 3-day retention. - [Turn on Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/enable-nightly-backups). Add the $5/month add-on from the Extra Features tab, confirm it's active, and remove it. ### Your backups - [Viewing your backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/viewing-your-backups). Find your backups, read the list, and understand the Full and Incremental labels. ### Restoring and recovering - [Restore your VPS from a backup](https://vpsdime.com/knowledgebase/client-area/nightly-backups/restore-your-vps). The full restore: shut down first, Complete vs Undo, and the 7-day deadline. - [Recover individual files](https://vpsdime.com/knowledgebase/client-area/nightly-backups/recover-individual-files). Browse a backup to download specific files or copy them back to your VPS. - [Download a full disk image](https://vpsdime.com/knowledgebase/client-area/nightly-backups/download-full-disk-image). Get a complete copy of your VPS to keep, mount, or migrate. ### Help - [Backup problems and fixes](https://vpsdime.com/knowledgebase/client-area/nightly-backups/backup-troubleshooting). Quick answers to the most common backup questions. --- Still need a person? You can [open a support ticket](https://vpsdime.com/open-ticket/) any time. --- ## Nightly Backups (overview) URL: https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview Last reviewed: 2026-07-02 Summary: Nightly Backups automatically backs up your whole VPS once a night with a 3-day retention, included free on Premium VPS and available as a $5/month add-on on Linux and Windows VPS. ### What this is Nightly Backups is an automated backup of your entire VPS, taken once a night and stored separately from your server. If something goes wrong, you can restore your whole VPS to a previous night, recover individual files from a backup, or download a full copy of the disk. Your backups are at https://vpsdime.com/backups. Who has it: - **Linux VPS:** Nightly Backups is an optional add-on, **$5/month**. It's off by default. Once it's on, you manage and restore your backups yourself from the **Backups** page. See [Turn on Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/enable-nightly-backups). - **Premium VPS:** Nightly Backups is **included free**, already part of your plan. There's nothing to turn on, and you manage your backups yourself from the **Backups** page. - **Windows VPS:** the same add-on is available for **$5/month** and backs up your VPS nightly, but Windows VPS isn't managed from the self-service **Backups** page. To restore or recover files, [open a support ticket](https://vpsdime.com/open-ticket/) and we'll handle it for you. ### How it works - **One backup per night.** Our system backs up your VPS automatically each night. You don't need to start it. - **3-day retention.** We keep your three most recent nightly backups. As each new backup is taken, the oldest one is removed. - **Whole-server backup.** Each backup covers your full VPS disk, so a restore brings the entire server back to how it was that night. - **Full or Incremental label.** In the panel each backup is tagged **Full** or **Incremental**. This is just information about how the backup was stored. It doesn't change how you restore or what you can recover. ### What you can do with a backup ![The VPS Backups page: Your VPS Services with Backups listing each VPS with its last backup, transferred data, and duration, plus Backups and Restores buttons](https://vpsdime.com/knowledgebase/client-area/nightly-backups/images/vps-list.png) From **Backups** in your client area, open a service and choose a backup to: - **Restore your VPS** to that night. See [Restore your VPS from a backup](https://vpsdime.com/knowledgebase/client-area/nightly-backups/restore-your-vps). - **Browse Files** to recover individual files without a full restore. See [Recover individual files](https://vpsdime.com/knowledgebase/client-area/nightly-backups/recover-individual-files). - **Download Full Disk** to save a complete copy of the disk image. See [Download a full disk image](https://vpsdime.com/knowledgebase/client-area/nightly-backups/download-full-disk-image). ### Things worth knowing - **Keep your own backups too.** Nightly Backups is a safety net, but your data is your responsibility. We recommend keeping your own copies of anything important as well. - **Export your databases inside the VPS.** Backups are taken while your VPS is running, so a restored database is crash-consistent, the same as after a sudden power loss. Most databases recover from this on their own, but for a copy you can fully rely on, set up a regular export (a database dump) to a file on the server. The nightly backup then includes that export, so you always have a clean, consistent copy to restore. - **One backup action at a time.** You can run one restore, file browser, or disk download at a time per VPS. Start another only after the first finishes or is stopped. ### Troubleshooting - **I don't see any backups.** A backup appears after the first nightly run completes. If you just enabled Nightly Backups, check back after the next night. On a Linux VPS, confirm the add-on is enabled (see [Turn on Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/enable-nightly-backups)). - **How far back can I go?** Retention is three days, so you can restore any of your three most recent nightly backups, up to about three nights ago. - **I have a Windows VPS and want a restore.** The self-service panel doesn't cover Windows VPS. [Open a ticket](https://vpsdime.com/open-ticket/) and we'll restore it for you. - **Can you restore my VPS if I never had Nightly Backups?** No. Without Nightly Backups (or a Premium VPS, which includes them), we don't keep snapshots, disk images, or any other recoverable copy of your VPS on our side, so there's nothing we can restore from. Enabling the add-on starts backups going forward only, the first backup runs the night after it's turned on, so it can't recover anything from before it was enabled. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP the question is about, - whether you're on a Linux VPS add-on or a Premium VPS, - what you're trying to do (restore, recover a file, or download the disk). ### Related questions - "What is Nightly Backups?" - "How often is my VPS backed up?" - "How long do you keep my backups?" - "Does my plan include backups?" - "How much do backups cost?" - "Can I get my Windows VPS restored from a backup?" - "What's the difference between a Full and an Incremental backup?" - "Are my databases safely backed up?" - "Do you keep snapshots of my VPS if I don't have the backup add-on?" - "Can I recover data from before I enabled backups?" - "If I buy the backup add-on now, can you restore yesterday's data?" --- ## Turn on Nightly Backups URL: https://vpsdime.com/knowledgebase/client-area/nightly-backups/enable-nightly-backups Last reviewed: 2026-07-02 Summary: How to add the Nightly Backups add-on to a Linux or Windows VPS from the Extra Features tab for $5/month, confirm it's active, and remove it. Windows restores are handled by our team. ### What this is Nightly Backups is an optional add-on for Linux and Windows VPS, **$5/month**, that backs up your whole VPS each night. This page covers adding it, confirming it's active, and removing it. Add it from **Extra Features** in Manage VPS (https://vpsdime.com/myservices). - On a **Premium VPS** it's already included, so there's nothing to turn on. - A **Windows VPS** adds it the same way, from the Extra Features tab. Restores are handled by our team rather than the self-service Backups page (a Windows VPS doesn't appear there), see the [overview](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview). ### Turn it on 1. Go to **My Services** and open the VPS you want to back up. This opens its **Service Management** page. 2. Open the **Extra Features** tab. 3. Find the **Nightly Backups** row. The **Price** column shows **$5.00 USD** for your billing cycle, and **Due Now** shows the prorated amount for the rest of your current term. 4. Click **Buy Now**. We create an invoice for the Due Now amount. 5. Click **Pay Invoice** and pay it. (If you change your mind before paying, click **Cancel**.) 6. After payment, the row shows *"Please wait while we process the order"* while we set it up. Once it's active, your first backup runs that night. ![The Nightly Backups row on the Extra Features tab, showing the description and $5.00 USD Monthly price. On this VPS the add-on is already active, so the button reads Remove; before purchase it reads Buy Now](https://vpsdime.com/knowledgebase/client-area/nightly-backups/images/cropped/extra-features-nightly-backups-row.png) ### Check that it's on - On the VPS's **Information** tab, the **Backups** line shows **ENABLED**. - After the first nightly run, the VPS appears on the **Backups** page with its backups listed. See [Viewing your backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/viewing-your-backups). ### Cost and billing - Nightly Backups is **$5.00/month**, shown for your billing cycle. If you pay quarterly or annually, the price reflects that term. - **Due Now** is prorated, so you only pay for the days left in your current term. After that, the add-on is included on your service's regular renewal invoice. - For help paying, see [Viewing and paying an invoice](https://vpsdime.com/knowledgebase/client-area/billing/invoices). ### Turn it off 1. Open the VPS's **Extra Features** tab. 2. In the **Nightly Backups** row, click **Remove**. Before you remove it: - **No refund or credit.** As noted in the **Downgrade Policy** message on that tab, we don't refund or credit removed features. - **Backups stop.** We stop taking new nightly backups. Don't count on your stored backups remaining available after removal, so download anything you might need first. See [Recover individual files](https://vpsdime.com/knowledgebase/client-area/nightly-backups/recover-individual-files) or [Download a full disk image](https://vpsdime.com/knowledgebase/client-area/nightly-backups/download-full-disk-image). ### Troubleshooting - **The button says "Remove," not "Buy Now."** Nightly Backups is already on for that VPS. **Remove** turns it off. - **I paid but don't see any backups yet.** Backups run once a night, so the first one appears after the next nightly run. Check the VPS's **Information** tab for the **Backups: ENABLED** badge to confirm it's active. - **I'm on a Premium VPS and don't see the option.** Premium VPS already includes Nightly Backups, so there's nothing to add. Go straight to the **Backups** page. - **I have a Windows VPS.** Add it from Extra Features like any other VPS. Restores are handled by our team, so [open a ticket](https://vpsdime.com/open-ticket/) when you need one. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - whether you're trying to add or remove Nightly Backups, - any invoice number involved, or the error you saw. ### Related questions - "How do I turn on backups for my VPS?" - "How much does the backup add-on cost?" - "Why do I have to pay an invoice to enable backups?" - "How do I cancel or remove Nightly Backups?" - "Will I get a refund if I remove backups?" - "I enabled backups but don't see any, why?" - "Do I need to enable backups on my Premium VPS?" --- ## Viewing your backups URL: https://vpsdime.com/knowledgebase/client-area/nightly-backups/viewing-your-backups Last reviewed: 2026-07-02 Summary: Where to find your VPS backups, what the Backups list and the Available Backups tab show, and what the Full and Incremental labels mean. ### What this is Where to find your VPS backups in the client area and what each part of the page shows. From here you can pick a backup to restore, browse its files, or download it (each covered in its own guide). ### Open your backups 1. In the client area, click **Backups** in the left sidebar. You'll see a list of every VPS that has at least one completed nightly backup. 2. Click the **Backups** button next to a VPS to open that VPS's backup list. (The **Restores** button opens the same page on its **Restore History** tab.) ### The VPS list ![The Backups page: each VPS with backups is listed with its last backup time, transferred data, and duration, plus Backups and Restores buttons](https://vpsdime.com/knowledgebase/client-area/nightly-backups/images/vps-list.png) The **Backups** page (https://vpsdime.com/backups) lists each VPS that has backups and shows, per VPS: - **Hostname** and **IP Address**: which VPS it is. - **Product**: the plan, for example Linux VPS - Linux6GB. - **Last Backup**: when the most recent backup ran. - **Transferred Data**: how much data the last backup moved. - **Duration**: how long the last backup took. If no VPS has a completed backup yet, the page reads **"No nightly backups have run, yet."** ### The Available Backups tab ![A VPS's backup list: the Available Backups tab with a row per backup showing date, size, duration, a Full or Incremental type badge, and an Actions button](https://vpsdime.com/knowledgebase/client-area/nightly-backups/images/available-backups.png) Open a VPS to see its backups under the **Available Backups** tab. Each row is one backup: - **Date**: when the backup was taken (Central Time). - **Size**: the size of that backup. - **Duration**: how long it took to create. - **Type**: **Full** or **Incremental**. This only tells you how the backup was stored. It doesn't change how you restore or what you can recover. Any backup in the list can be restored, browsed, or downloaded. - **Actions**: opens a menu to **Restore VPS**, **Browse Files**, or **Download Full Disk** for that backup. You'll usually see up to three backups here, one per night, matching the 3-day retention. For what each action does, see: - [Restore your VPS from a backup](https://vpsdime.com/knowledgebase/client-area/nightly-backups/restore-your-vps) - [Recover individual files](https://vpsdime.com/knowledgebase/client-area/nightly-backups/recover-individual-files) - [Download a full disk image](https://vpsdime.com/knowledgebase/client-area/nightly-backups/download-full-disk-image) ### The Restore History tab The **Restore History** tab on the same page lists your past and in-progress restores and their status. See [Restore your VPS from a backup](https://vpsdime.com/knowledgebase/client-area/nightly-backups/restore-your-vps) for how restores work. ### Troubleshooting - **The list is empty or my VPS isn't there.** A VPS appears only after its first nightly backup completes. If you just enabled Nightly Backups, check back after the next night. See [Turn on Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/enable-nightly-backups). - **I expected more backups.** Retention is three nights, so the list holds your three most recent backups. Older ones are removed automatically. - **The Actions button is disabled.** Another backup operation (a restore, file browser, or download) is already running for that VPS. Finish or stop it first. See [Restore your VPS from a backup](https://vpsdime.com/knowledgebase/client-area/nightly-backups/restore-your-vps). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the backup date you're looking at, - what you're trying to do with it. ### Related questions - "Where do I find my VPS backups?" - "How many backups do I have?" - "What does the Full or Incremental label mean?" - "What does Transferred Data mean on the backups list?" - "Why is my VPS not listed on the Backups page?" - "What can I do with a backup?" --- ## Restore your VPS from a backup URL: https://vpsdime.com/knowledgebase/client-area/nightly-backups/restore-your-vps Last reviewed: 2026-07-02 Summary: How to restore your whole VPS to a backup night, why you shut down first, and how the Complete vs Undo step and the 7-day deadline work. ### What this is Restoring rolls your **entire VPS** back to how it was on a chosen backup night. It's a two-step process: the restore runs first, then you **verify** the result and either **Complete** it (keep it) or **Undo** it (roll back). Your original disk is kept as a safety copy until you complete the restore or 7 days pass. Start from https://vpsdime.com/backups. This applies to Linux VPS (with Nightly Backups) and Premium VPS. On a **Windows VPS**, restores are handled by our team, so [open a ticket](https://vpsdime.com/open-ticket/). ### Before you start - **A full restore is destructive.** It replaces your current disk with the backup and can cause downtime. Anything created since that backup won't be on the restored disk (it's preserved on your original disk until you complete or undo). Use a full restore only when you really need it. To pull back just a few files instead, see [Recover individual files](https://vpsdime.com/knowledgebase/client-area/nightly-backups/recover-individual-files). - **Shut down your VPS first.** The restore can't run while the VPS is powered on. - **One operation at a time.** You can't start a restore while another restore, file browser, or disk download is active on that VPS. ### Restore your VPS 1. Go to **Backups**, open your VPS, and on the **Available Backups** tab find the backup you want. 2. Click **Actions** on that backup, then choose **Restore VPS** in the **Choose Action** menu. ![The Choose Action window for a backup: Restore VPS, Browse Files, and Download Full Disk options](https://vpsdime.com/knowledgebase/client-area/nightly-backups/images/cropped/choose-action-dialog.png) 3. The **Confirm Restore** window opens. It shows the backup date and size, warns that a full restore "is a destructive process and may cause a long downtime and data loss," and reminds you: *"You must shut down your VPS before starting the restore."* ![The Confirm Restore window: the destructive-process warning, backup date and size, the shut-down reminder, and Shutdown VPS / Cancel / Start Restore buttons](https://vpsdime.com/knowledgebase/client-area/nightly-backups/images/cropped/confirm-restore-dialog.png) 4. **Shut down your VPS.** Click **Shutdown VPS** in that window (it opens your VPS management page in a new tab) and power the server off. 5. Back in the **Confirm Restore** window, click **Start Restore**. 6. The **Restore Job** page opens and shows live progress ("Transferring data...") with a percentage, speed, and estimated time. Leave it to run. ![The Restore Job page showing "Transferring data..." with a progress bar, percentage, speed, and ETA](https://vpsdime.com/knowledgebase/client-area/nightly-backups/images/cropped/restore-progress-card.png) ### After the restore: Complete or Undo When the transfer finishes, the page shows **"Restore Successful - Action Required."** Your VPS is now on the restored disk, and your original disk (from just before the restore) is kept as a safety copy. ![The "Restore Successful - Action Required" screen: verify your data, the 7-day warning, and Complete Restore / Undo Restore buttons](https://vpsdime.com/knowledgebase/client-area/nightly-backups/images/cropped/restore-action-required.png) **We also email you.** When the restore finishes we send an email (subject: *"Restore Complete — Action Required"*) so you don't have to watch the progress page. It explains the same two options, links back to the **Restore Page** to Complete or Undo, and repeats the 7-day deadline. The deadline runs from when the restore completes. 1. **Start your VPS and check it.** Power it back on, log in over SSH or the console, and verify your files, databases, and services look right. Backups are taken while your VPS is running, so the restored disk is crash-consistent, the same as if the server had lost power at that moment. Most databases recover from this automatically when they start. In some cases a database may not recover cleanly, so check your databases specifically. 2. Then choose one: - **Complete Restore**: keeps the restored version. This **permanently removes** the safety copy of your original disk and can't be undone. - **Undo Restore**: rolls back to your original disk, the exact state from before the restore. Anything changed after the restore is lost. Each choice asks you to confirm. Completing warns *"This action is irreversible,"* and Undo warns that changes made after the restore will be lost. > **7-day deadline:** if you don't Complete or Undo within **7 days**, your original disk is deleted automatically and the restore becomes permanent. After that you can no longer undo it. It's best to check and decide as soon as you can. If you're unsure whether the restore looks right, [open a ticket](https://vpsdime.com/open-ticket/) and we'll help you check before you decide. ### Picking up a restore later (Restore History) You don't have to finish in one sitting. A restore that's waiting on you stays available: - On your VPS's backup page you'll see a **Restore In Progress** or **Restore Pending Action** notice with a **Go to Restore** button. - The **Restore History** tab lists your restores with a status: - **In Progress** / **Verifying**: still running. - **Pending Action**: finished and waiting for you to decide. Use **Complete**, **Undo**, or **View** to act on it. - **Completed**: the restore was finalized. - **Undone**: the restore was rolled back to the original disk. - **Failed**: the restore didn't finish (see below). ![A restore waiting on you: the Restore Pending Action notice with Go to Restore, the Actions Blocked banner, and the Restore History tab with a Pending Action row and Complete / Undo / View buttons](https://vpsdime.com/knowledgebase/client-area/nightly-backups/images/cropped/restore-history-pending.png) The 7-day deadline applies to anything left at **Pending Action**. ### If a restore fails If the page shows **Restore Failed**, the restore didn't complete and your VPS is unchanged. You can try again from the **Available Backups** tab, or [open a ticket](https://vpsdime.com/open-ticket/) with the backup date and we'll look into it. ### Troubleshooting - **"Actions Blocked," or I can't start a restore.** Another operation is active on that VPS: a running or pending restore, or an open file browser or disk download. Finish it, complete/undo it, or stop it first. A pending restore shows a **Go to Restore** button. - **The restore won't start and asks me to shut down.** The VPS must be powered off first. Shut it down from your VPS management page, then click **Start Restore**. - **My recent changes are gone after restoring.** A restore returns the VPS to the backup night, so newer changes aren't on it. If you haven't completed the restore yet, use **Undo Restore** to get your original disk back. - **My database won't start cleanly after a restore.** Because backups are crash-consistent, a database may need its normal crash-recovery step on first start, and on rare occasions can't recover fully. Run the database's recovery process, try a different backup, or [open a ticket](https://vpsdime.com/open-ticket/). - **I have a Windows VPS.** Restores are handled by our team. [Open a ticket](https://vpsdime.com/open-ticket/). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the backup date you restored or want to restore, - whether the restore is in progress, pending your action, or failed, - what looks wrong, if anything. ### Related questions - "How do I restore my VPS from a backup?" - "Do I have to shut down my VPS to restore it?" - "What's the difference between Complete and Undo?" - "I restored my VPS, how do I keep it or roll it back?" - "What happens if I don't complete the restore?" - "Do you email me when the restore is finished?" - "Can I undo a restore?" - "My restore failed, what now?" - "Will my database be intact after a restore?" - "How do I restore a Windows VPS?" --- ## Recover individual files URL: https://vpsdime.com/knowledgebase/client-area/nightly-backups/recover-individual-files Last reviewed: 2026-07-04 Summary: How to use Browse Files to open a temporary web file browser, find and download specific files from a backup, view text files, or copy files straight to another server. ### What this is **Browse Files** opens a temporary web file browser onto one of your backups, so you can find and recover specific files without restoring the whole VPS. When you find what you need, you can download it or copy it straight back onto your live VPS. You get access for about **4 hours**, then it closes automatically. Start from https://vpsdime.com/backups. This is for Linux VPS (with Nightly Backups) and Premium VPS. On a **Windows VPS**, file recovery is handled by our team, so [open a ticket](https://vpsdime.com/open-ticket/). ### Before you start - **The backup is read-only.** You're browsing a copy. Nothing you do here changes the backup or your live VPS. - **Access lasts about 4 hours.** After that the file browser closes on its own. You can also stop it sooner. - **One operation at a time.** While a file browser is open, you can't start a restore or a disk download on that VPS until you stop it. - **Keep the link private.** The access link includes a key that opens your backup files. Don't share it. ### Open the file browser 1. Go to **Backups**, open your VPS, and on the **Available Backups** tab find the backup you want. 2. Click **Actions** on that backup, then choose **Browse Files** in the **Choose Action** menu. 3. A **File Browser Active** panel appears with an access link and the time remaining (about 4 hours). Click **Open** to launch it, or **Copy** to copy the link. ![The File Browser Active panel: the backup date, the private access link with Copy and Open buttons, the time remaining, and a Stop File Browser button](https://vpsdime.com/knowledgebase/client-area/nightly-backups/images/cropped/file-browser-active-panel.png) 4. The **VPSDime Backup Disk File Manager** opens. The left side, **Local Backup Disk (Read-Only)**, shows your backup's files. ![The VPSDime Backup Disk File Manager: the read-only backup files on the left and a Connect to Remote Server form (protocol, host, port, username, password) on the right](https://vpsdime.com/knowledgebase/client-area/nightly-backups/images/file-manager.png) ### Find and download files - **Move around:** click a folder to open it; the **Path** at the top shows where you are and lets you go back up. - **Download one item:** click the **download** icon on its row. - **Download several:** tick the checkboxes, then click **Download** in the toolbar that appears. - **View a text file:** click it to open the built-in editor, where you can read, **Search**, **copy**, or **download** its contents. ### Copy files back to your VPS (or to another server) The quickest way to put recovered files back is to connect to your **own VPS** and copy them across, no download needed: 1. On the right, under **Connect to Remote Server**, choose **SFTP** as the **Protocol**. 2. Enter your VPS's IP as the **Host**, **22** as the **Port**, and your VPS login (for example **root**) and password. Click **Connect**. 3. Your VPS's filesystem appears on the right. Open the folder where the files belong. 4. Copy files from the backup onto your VPS in any of these ways: - Click the **upload** icon on a file's row. - Tick several files and click **Copy to Remote**. - Drag a file or folder from the backup onto your VPS. 5. Click **Disconnect** when you're done. ![The file manager connected over SFTP: backup files selected on the left with Download and Copy to Remote buttons, and the live VPS's filesystem on the right](https://vpsdime.com/knowledgebase/client-area/nightly-backups/images/file-manager-connected.png) You can connect to any other server the same way, not just your VPS. The supported protocols are **SFTP**, **FTP**, **S3**, **SMB**, and **WebDAV**. ### Restoring database files: read this before copying anything Copying **individual database files** out of a backup (a single `.ibd` file, one table's files, or one database's subfolder) into a running MySQL, MariaDB, or PostgreSQL server **will not work and can corrupt what you still have**. A database's files are one consistent set: for MySQL/MariaDB that means the per-table files plus `ibdata1`, the redo logs, and the system schema together. Files copied in isolation don't match the rest of the set, and the server answers with errors like "tablespace id mismatch" or marks tables corrupt, often refusing to start at all. The safe way to restore a database from a backup: 1. **Stop the database** on your VPS first, so nothing writes while you work: `systemctl stop mysql` (or `mariadb` / `postgresql`). 2. **Set aside the current data directory before touching it**, so you can always get back to where you are now: `mv /var/lib/mysql /var/lib/mysql.old` (PostgreSQL: `/var/lib/postgresql`). Don't skip this even if the database is broken, "broken but present" still beats "gone". 3. **Copy the entire data directory from the backup, not individual files.** In the file manager, connect to your VPS over SFTP and copy the whole `/var/lib/mysql` folder in one operation, everything in it, including `ibdata1`, the `ib_logfile*` / redo files, and the `mysql` system folder. The backup is taken while the server runs, so its files are only guaranteed to make sense **as a complete set** that the database can crash-recover from, exactly like after a power loss. 4. **Fix ownership**, since copied files usually arrive owned by root: `chown -R mysql:mysql /var/lib/mysql` (PostgreSQL: `chown -R postgres:postgres` and check the directory is mode `700`). 5. **Start the database and watch the log.** `systemctl start mysql`, then check the error log while InnoDB runs its normal crash recovery. If it refuses to start, work through [MySQL or MariaDB won't start after a crash](https://vpsdime.com/knowledgebase/troubleshooting/mysql-wont-start), and don't reach for `innodb_force_recovery` before reading it. If you only need **one database or one table**, restore the full directory anyway (into a copy, per step 2, your current data stays in `/var/lib/mysql.old`), start the server, and export what you need with `mysqldump`. For the future: a scheduled `mysqldump` to a file inside the VPS gives you logical dumps that restore per-database and per-table trivially, and those dump files are themselves picked up by the nightly backup, single files that are safe to recover individually. ### When you're finished - Go back to the **Backups** page and click **Stop File Browser**, or just leave it and it closes after about 4 hours. - While the file browser is open, other backup actions for that VPS are blocked, so stop it when you no longer need it. ### Troubleshooting - **My access link stopped working.** The 4-hour window has ended, or the file browser was stopped. Start **Browse Files** again to get a fresh session. - **I can't start a restore or download.** A file browser is still open for that VPS. Stop it first from the **Backups** page. See [Restore your VPS from a backup](https://vpsdime.com/knowledgebase/client-area/nightly-backups/restore-your-vps). - **I need the whole disk, not single files.** Use [Download a full disk image](https://vpsdime.com/knowledgebase/client-area/nightly-backups/download-full-disk-image) instead. - **MySQL or MariaDB won't start after I copied database files back.** This is what happens when files are copied individually instead of as the complete data directory. Follow the steps in [Restoring database files](#restoring-database-files-read-this-before-copying-anything) above, your pre-restore copy from step 2 means nothing is lost, and see [MySQL or MariaDB won't start after a crash](https://vpsdime.com/knowledgebase/troubleshooting/mysql-wont-start). - **My connection to a remote server failed.** Check the host, port, username, and password, and that the server allows connections from outside. Try again, or use **Download** and upload the files yourself. - **I have a Windows VPS.** File recovery is handled by our team. [Open a ticket](https://vpsdime.com/open-ticket/). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the backup date you're browsing, - the files you're trying to recover, - any error you saw (a screenshot helps). ### Related questions - "How do I recover a single file from a backup?" - "Can I get files back without restoring the whole VPS?" - "How long do I have to browse a backup?" - "How do I download files from a backup?" - "How do I copy recovered files back onto my VPS?" - "Can I restore just a few files instead of the whole VPS?" - "Can I copy files from a backup straight to another server?" - "Which transfer methods can I use (SFTP, FTP, S3, SMB, WebDAV)?" - "How do I recover a file from a Windows VPS backup?" - "How do I restore a database from a backup?" - "Why won't MySQL start after I copied files from a backup?" - "Can I restore just one database or table from a backup?" - "Is it safe to copy .ibd files from a backup?" --- ## Download a full disk image URL: https://vpsdime.com/knowledgebase/client-area/nightly-backups/download-full-disk-image Last reviewed: 2026-07-02 Summary: How to use Download Full Disk to get a temporary 24-hour link to your whole backup as a compressed image, and how to mount or import it. Linux VPS images are LXC container filesystems; Premium VPS images are full KVM disks. ### What this is **Download Full Disk** gives you a temporary link to download a whole backup as a single compressed image, a complete copy of your VPS. You get the link for about **24 hours**. Use it to keep an offline copy, pull files out on your own computer, or move your server elsewhere. Start from https://vpsdime.com/backups. This is for Linux VPS (with Nightly Backups) and Premium VPS. On a **Windows VPS**, this is handled by our team, so [open a ticket](https://vpsdime.com/open-ticket/). What's inside the image depends on your plan, which changes how you use it (covered below): - **Linux VPS** runs as a lightweight Linux container, so its image is a **root filesystem** (ext4) with no kernel. - **Premium VPS** is a full KVM virtual machine, so its image is a **complete bootable disk**. ### Before you start - **The file is large.** It's your whole system, so expect many gigabytes. Make sure you have the disk space and time to download it. - **Access lasts about 24 hours.** After that the link stops working. You can also stop it sooner. - **One operation at a time.** While a disk download is active, you can't start a restore or a file browser on that VPS until you stop it. - **Keep the link private.** It opens a copy of your data. Don't share it. ### Download the image 1. Go to **Backups**, open your VPS, and on the **Available Backups** tab find the backup you want. 2. Click **Actions** on that backup, then choose **Download Full Disk** in the **Choose Action** menu. 3. A **Full Disk Download Active** panel appears with a link and the time remaining (about 24 hours). Click **Open** to start the download, or **Copy** to copy the link. ![The Full Disk Download Active panel: the backup date, the private .img.gz download link with Copy and Open buttons, the time remaining, and a Stop Full Disk Download button](https://vpsdime.com/knowledgebase/client-area/nightly-backups/images/cropped/full-disk-active-panel.png) 4. The file is a gzip-compressed image, with a name ending in **`.img.gz`**. For a large file it helps to **Copy** the link and use a download tool that can resume, for example `wget -c ""` or `curl -C - -O ""`. ### What you can do with the image First decompress the `.img.gz` to get the raw `.img`: - Linux or macOS: `gunzip yourbackup.img.gz`. Windows: use 7-Zip or a similar tool. Then follow the path for your plan. #### Linux VPS (LXC container image) A Linux VPS runs as a Linux container (LXC). The image is its **root filesystem** (ext4) and does **not** contain a kernel, so you can't boot it directly as a virtual machine. You can: - **Pull files out of it.** On Linux, mount it read-only, the image is a single filesystem, so no partition step is needed: ``` sudo mount -o ro,loop yourbackup.img /mnt # ... copy what you need from /mnt ... sudo umount /mnt ``` - **Run it as a container.** Import the filesystem into **LXD**, **Incus**, or plain **LXC** and start it there. It runs on the host's kernel, which is why no kernel is included. To read the files on Windows or macOS, see the notes at the end of this section. #### Premium VPS (full KVM disk image) A Premium VPS is a full KVM virtual machine, so its image is a complete bootable disk (partition table, bootloader, and kernel). You can: - **Mount a partition** to pull files out. Attach it with partition scanning: ``` sudo losetup -fP --show yourbackup.img # prints the loop device, e.g. /dev/loop0 lsblk # find the partition, e.g. /dev/loop0p1 sudo mount -o ro /dev/loop0p1 /mnt ``` Run `fdisk -l yourbackup.img` if you're not sure which partition holds your data. If it uses LVM, run `sudo vgscan` and `sudo vgchange -ay` after attaching, then mount the logical volume. - **Boot it as a virtual machine.** QEMU/KVM can boot the raw `.img` directly. For VirtualBox or VMware, convert it first: ``` qemu-img convert -f raw yourbackup.img -O vdi yourbackup.vdi # VirtualBox qemu-img convert -f raw yourbackup.img -O vmdk yourbackup.vmdk # VMware ``` #### Reading the image on Windows or macOS Both image types store your data on a Linux filesystem (ext4), which Windows and macOS can't open on their own: - **Windows:** copy the image into a **WSL2** Linux distribution and use the Linux steps above, or use an ext4 reader such as DiskInternals Linux Reader or Paragon ExtFS. - **macOS:** run a small **Linux VM** (UTM, VirtualBox, Lima) and use the Linux steps, or install **macFUSE** with an ext4 driver to mount it read-only. ### When you're finished - Go back to the **Backups** page and click **Stop Full Disk Download**, or leave it and it stops after about 24 hours. - While the download is active, other backup actions for that VPS are blocked, so stop it when you no longer need it. The download link stops working once the session ends. ### Troubleshooting - **My link stopped working.** The 24-hour window ended, or the download was stopped. Start **Download Full Disk** again for a fresh link. - **The download failed partway.** Use the **Copy** link with a tool that resumes, such as `wget -c` or `curl -C -`, so you don't restart from zero. - **I can't start a restore or file browser.** A disk download is still active for that VPS. Stop it first from the **Backups** page. - **I just want a few files, not the whole disk.** Use [Recover individual files](https://vpsdime.com/knowledgebase/client-area/nightly-backups/recover-individual-files) instead, it's much smaller and faster. - **My Linux VPS image won't boot as a virtual machine.** That's expected. A Linux VPS image is a container filesystem with no kernel. Import it into LXD, Incus, or LXC instead, or use a Premium VPS image if you need a bootable disk. - **Windows or macOS won't open the image.** That's expected, they don't read Linux filesystems. Use one of the options above (WSL2, a Linux VM, or an ext4 reader). - **I have a Windows VPS.** Full disk images aren't self-service for Windows. [Open a ticket](https://vpsdime.com/open-ticket/). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - whether it's a Linux VPS or a Premium VPS, - the backup date you downloaded, - what you're trying to do with the image (keep it, mount it, or migrate), - the operating system on your computer. ### Related questions - "How do I download a full copy of my VPS?" - "What format is the backup image?" - "How do I mount my Linux VPS backup image?" - "How do I import my Linux VPS image into Incus, LXD, or LXC?" - "Why can't I boot my Linux VPS image as a virtual machine?" - "How do I run my Premium VPS backup as a virtual machine?" - "How do I open the backup image on Windows or macOS?" - "How long is the download link valid?" - "My download keeps failing, how do I resume it?" --- ## Backup problems and fixes URL: https://vpsdime.com/knowledgebase/client-area/nightly-backups/backup-troubleshooting Last reviewed: 2026-07-02 Summary: Quick fixes for common Nightly Backups issues, no backups showing, blocked actions, restores stuck or failed, expired file browser or download links, and reading the disk image. ### What this is Quick answers to the most common Nightly Backups questions. Each one links to the full guide if you need more detail. Your backups are at https://vpsdime.com/backups. ### I don't see my backups - **No backups, or my VPS isn't on the Backups page.** A VPS appears only after its first nightly backup completes. On a **Linux VPS**, make sure the add-on is enabled (see [Turn on Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/enable-nightly-backups)); on a **Premium VPS** it's already included. Then check back after the next nightly run. - **I enabled it but still see nothing.** Backups run once a night, so the first one shows up after the next nightly run. On the VPS's **Information** tab, the **Backups** line should read **ENABLED**. - **How far back can I go?** Retention is three nights, so you'll have your three most recent backups. - **I never had Nightly Backups. Can you still restore my VPS?** No. Without Nightly Backups (or a Premium VPS, which includes them), we don't keep snapshots, disk images, or any other recoverable copy of your VPS on our side, so there's nothing we can restore from. Enabling the add-on now starts backups going forward only; it can't recover anything from before it was turned on. ### A button is disabled, or "Actions Blocked" - **I can't start a restore, file browser, or download.** Only one backup operation can run at a time per VPS. Something else is active: a restore that's running or **pending your action**, or an open **file browser** or **disk download**. Finish or stop it first: - A restore waiting on you shows a **Go to Restore** button. Complete or undo it (see [Restore your VPS](https://vpsdime.com/knowledgebase/client-area/nightly-backups/restore-your-vps)). - An open file browser or disk download shows a **Stop** button on the Backups page. ### Restore problems - **The restore won't start and asks me to shut down.** Power the VPS off first, then click **Start Restore**. See [Restore your VPS](https://vpsdime.com/knowledgebase/client-area/nightly-backups/restore-your-vps). - **My restore is stuck at "Pending Action."** The restore finished and is waiting for you to **Complete** or **Undo** it. Start the VPS, check your data, then decide. If you do nothing within **7 days**, the restore becomes permanent. - **The restore failed.** Your VPS is unchanged. Try again from the **Available Backups** tab, or [open a ticket](https://vpsdime.com/open-ticket/) with the backup date. - **My database won't start cleanly after a restore.** Backups are crash-consistent (taken while the VPS runs), so a database may need its normal recovery step, and on rare occasions can't recover fully. Run the database's recovery, try a different backup, or [open a ticket](https://vpsdime.com/open-ticket/). Going forward, a regular database export inside the VPS gives you a clean copy in each nightly backup. ### File recovery and downloads - **My file browser link stopped working.** The 4-hour window ended, or it was stopped. Start **Browse Files** again for a fresh session. See [Recover individual files](https://vpsdime.com/knowledgebase/client-area/nightly-backups/recover-individual-files). - **My full disk download link stopped working.** The 24-hour window ended, or it was stopped. Start **Download Full Disk** again. - **A big download keeps failing.** Use the **Copy** link with a tool that resumes, such as `wget -c` or `curl -C -`. See [Download a full disk image](https://vpsdime.com/knowledgebase/client-area/nightly-backups/download-full-disk-image). - **Windows or macOS won't open the image.** Backups use a Linux filesystem (ext4) that those systems don't read natively. Use WSL2, a small Linux VM, or an ext4 reader. - **My Linux VPS image won't boot as a virtual machine.** A Linux VPS image is a container filesystem with no kernel, so import it into LXD, Incus, or LXC instead of booting it. (Premium VPS images are full bootable disks.) ### Billing and plan - **I removed Nightly Backups and my backups are gone.** Removing the add-on stops new backups, and removed features aren't refunded. Download anything you need before removing it. See [Turn on Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/enable-nightly-backups). - **Do I need to enable backups on my Premium VPS?** No. Premium VPS includes Nightly Backups, so there's nothing to add. ### Windows VPS - **I have a Windows VPS and need a restore or files back.** Windows VPS backups aren't self-service. [Open a ticket](https://vpsdime.com/open-ticket/) and we'll handle the restore for you. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what you were trying to do (restore, recover files, download, or enable backups), - the backup date involved, - any error you saw (a screenshot helps). ### Related questions - "Why don't I see any backups?" - "Why is the Actions button disabled?" - "My restore is stuck, what do I do?" - "My restore failed, can I try again?" - "My backup link expired, how do I get a new one?" - "Why won't Windows or macOS open my backup image?" - "I removed backups, can I still get them?" - "Can you restore my VPS if I never enabled backups?" - "Do you keep snapshots of my VPS without the backup add-on?" --- ## Support & help URL: https://vpsdime.com/knowledgebase/client-area/support Last reviewed: 2026-07-02 Summary: How to get help at VPSDime, open a support ticket, use the My VPS is Down troubleshooter, unblock your IP from the SSH firewall, and follow service status. How to reach us, and how to fix the most common problems yourself. ### Get help - [Getting help](https://vpsdime.com/knowledgebase/client-area/support/getting-help). Open a support ticket, find and reply to your tickets, and check service status announcements. ### Fix it yourself - [My VPS is Down (troubleshooter)](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter). Run automatic diagnostics on a VPS, use the self-service fixes, and escalate to a ticket if needed. - [SSH firewall and blocked IPs](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall). Why an IP gets blocked on port 22, and how to whitelist yours. --- Still need a person? You can [open a support ticket](https://vpsdime.com/open-ticket/) any time. --- ## Getting help URL: https://vpsdime.com/knowledgebase/client-area/support/getting-help Last reviewed: 2026-07-05 Summary: How to reach VPSDime support, picking the right department and priority, writing a ticket that gets solved on the first reply, tracking and replying to tickets, and checking service status. ### What this is The ways to reach us and actually get a problem solved: opening a support ticket, tracking it, and checking whether what you're seeing is a wider outage. It's all under **Support** in the client area, starting at [open a ticket](https://vpsdime.com/open-ticket/). Tickets are opened from your account, being signed in is what lets us verify it's you and act on your services. The one exception is **pre-sales questions**: you can ask those without an account. Two things often solve a problem faster than waiting on a reply, so try them first: - **VPS unreachable?** Run [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter). It checks the VPS, frequently fixes the cause on the spot (a blocked IP, disabled password login, a forgotten password), and if it can't, it hands us the diagnostics so the first reply is already useful. - **Think it's an outage?** Check the service status announcements (below) before opening a ticket. If a node or the network is affected, it's posted there and we're already on it. ### Guest tickets and service verification When your ticket is about an **existing service**, always open it **from your client area, signed in**. Being signed in is what proves the request comes from the account holder, which is what lets us discuss and act on the service at all. A **guest ticket** (opened without signing in) about an existing service **can't be verified**, so it won't be worked on as-is, you'll be redirected to sign in and continue from your account. - **Can't sign in?** That's the thing to fix first, and it has its own guide: [I can't sign in](https://vpsdime.com/knowledgebase/client-area/account/cant-sign-in). Recovering access to the account is the path to getting service help, a guest ticket doesn't bypass it. - **Pre-sales questions** remain the one exception: no account needed, ask away as a guest. ### Which department, and how urgent Opening a ticket asks you for a **department** and a **priority**. Neither is complicated, but both route your ticket, so: ![The Open Ticket page: department cards for My VPS is Down, Sales/Billing, and Support, with a Knowledge Base pointer above](https://vpsdime.com/knowledgebase/client-area/support/images/ticket-departments.png) - **Department.** Choose **Sales/Billing** for orders, invoices, refunds, and account questions, and **Support** for anything technical (a VPS problem, networking, configuration). If you're not sure, pick **Support**; we'll move it if it belongs elsewhere. - **Priority (High, Medium, Low).** Priority signals urgency, it isn't a queue you jump by always picking High. Use **High** for something genuinely urgent, like a VPS that's down or a suspected security issue. Use **Medium** for a normal problem that's blocking you, and **Low** for a question that isn't time-sensitive. Marking routine questions High doesn't get them answered sooner, and it makes real emergencies harder to spot. ### Writing a ticket that gets solved on the first reply The single biggest thing that speeds up support is a message we can act on without first asking you for more. Put this in the ticket up front: ![The ticket form: Priority and Department dropdowns, Subject, a Related Service selector, the message editor, and an attachments drop zone](https://vpsdime.com/knowledgebase/client-area/support/images/ticket-form.png) - **Which VPS.** Set **Related Service** to the VPS it's about, or include the hostname or IP in the message. - **What's wrong, exactly.** What you did, what happened, and the **exact error**, copied and pasted rather than paraphrased. "SSH times out" and "SSH says `Permission denied (publickey)`" are completely different problems with different fixes. - **When it started**, and whether anything changed just before, such as a reinstall, a firewall change, or an upgrade. - **What you already tried**, so we don't suggest it back to you. - **Attachments** if they help. The form takes images, video, PDFs, and log or text files, up to 50 MB. - **Your own words, not an AI transcript.** Paste exact errors and command output freely, machine output is gold, but **don't paste AI chatbot conversations or their suggested-fix essays** into the ticket. Our staff are senior admins who diagnose from real symptoms, and a chatbot transcript buries them in unrelated speculation they have to read through, which slows your fix. Use the AI to try fixing first, then tell us in one line what it helped you rule out. See [raising a ticket that gets solved fast](https://vpsdime.com/knowledgebase/getting-started/raising-a-support-ticket). We reply as quickly as we can, and genuinely urgent (High) tickets are looked at first. A precise, self-contained first message is what turns a problem into a one-reply fix instead of a three-message back-and-forth. ### After you submit: tracking and replying Your tickets are under **Support, Tickets List** (https://vpsdime.com/supporttickets), searchable by number or subject. You can reply there, or **just reply to our email**; both land in the same thread. ![The My Tickets list: each ticket with its date, department, subject, status badge, and a View Ticket button, plus a search filter](https://vpsdime.com/knowledgebase/client-area/support/images/tickets-list.png) ![The top of an open ticket: the subject, its submitted time, department, priority, and status, with Reply and Close Ticket buttons](https://vpsdime.com/knowledgebase/client-area/support/images/cropped/ticket-view-header.png) The **status** tells you whose turn it is: - **Open** or **Customer-Reply**: waiting on us. - **Answered**: we've replied and it's waiting on you. A ticket that sits in Answered isn't being ignored, it needs your reply to move. - **Closed**: resolved. Replying reopens it. ### Service status announcements ![The Service Status Announcements feed: dated incident posts, each with a Resolved badge](https://vpsdime.com/knowledgebase/client-area/support/images/cropped/announcements-top.png) **Support, Service Status Announcements** (https://vpsdime.com/announcements) is our feed of incidents, maintenance, and security notices, each marked with a state such as **Resolved**. If several things break at once, or a whole node goes unreachable, look here first: a posted incident means we already know and are working on it, so you don't need to open a ticket. It's also available as an RSS or JSON feed if you'd rather watch it. During an outage, the announcement is also where **estimated resolution times** are posted, as soon as our infrastructure team can give one, and updated as the work progresses. Worth saying plainly: opening a ticket to ask for a status update doesn't speed anything up, during an incident every available resource is already focused on restoring service, and the answer a ticket would get is the same one the announcement page already shows. Watch the page (or its feed), and save the ticket for something the incident post doesn't cover, like your VPS still being down *after* the incident is marked Resolved. ### Related questions - "How do I contact support?" - "How do I open a ticket, and do I need an account?" - "Can I open a support ticket without signing in?" - "Why was my guest ticket redirected to sign in?" - "Which department should I choose?" - "What does ticket priority do, and should I mark it High?" - "How do I get my support ticket answered quickly?" - "How long does support take to reply?" - "Where are my tickets, and what do the statuses mean?" - "Can I reply to a ticket by email?" - "How do I know if there's an outage?" - "When will the outage be fixed, is there an ETA?" - "Should I open a ticket during an outage?" --- ## My VPS is Down (troubleshooter) URL: https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter Last reviewed: 2026-07-04 Summary: The My VPS is Down troubleshooter runs automatic diagnostics on your VPS, offers self-service fixes (password reset, SSH password login, Auto-fix network, Console, network trace), and can open a pre-filled ticket. It's deepest on Linux VPS. ### What this is **My VPS is Down** (under **Support**, at https://vpsdime.com/myvpsisdown) checks a VPS you can't reach and tries to tell you why, with self-service fixes for the common causes and a one-click way to open a ticket if it can't sort it out. How much it checks depends on the plan: - **Linux VPS:** the full inside-and-out diagnostics and self-service tools below. - **Premium VPS and Windows VPS:** a lighter check (power state and connection status) plus guidance and a ticket. Windows also verifies and can reset your Administrator password. ### Running it 1. Go to **Support, My VPS is Down**. 2. Click the VPS you're having trouble connecting to. 3. It shows the VPS's live status (running, uptime, CPU, memory, disk) and runs its checks. ![The VPS Troubleshooter's selection screen: a card per VPS with its hostname, IP, product, and status](https://vpsdime.com/knowledgebase/client-area/support/images/vps-troubleshooter-select.png) ### What the diagnostics check, and what a result means (Linux VPS) At the top you get a verdict: **"Everything looks good"** (it ran a full inside-and-out check and found nothing wrong) or the specific problem it found. Below that is an expandable list of the individual checks. Each shows green when it's fine, and when one isn't, the page tells you the likely cause and the exact fix to try. The main ones: ![The diagnostics verdict: the VPS's live status strip and an "Everything looks good" result with things to try if you still can't connect](https://vpsdime.com/knowledgebase/client-area/support/images/cropped/troubleshooter-verdict.png) - **Reachable and networking.** Whether your VPS answers ping and its SSH port from an outside network, and whether the network *inside* is sane: the right IP address configured, working IPv4 and IPv6 routes, internet reachability, and DNS both configured and resolving. Anything broken there is fixed by the **Auto-fix network** button below. - **Your VPS's own firewall.** It detects what's running (firewalld, iptables/nft, ufw, CSF), shows whether your SSH, web, and DNS ports are allowed or blocked, and offers one-click fixes: **Remove the firewall rule blocking my IP**, and a last-resort **Flush firewall**. - **In-VPS IP blockers.** fail2ban, CSF, and sshguard are checked for bans on your address, with an **Unblock my IP** button (and a last-resort **Flush all IP blockers**). A manual firewall rule blocking just your IP gets its own **Remove the rule** button. - **Standard ports (SSH, HTTP, HTTPS, DNS).** Whether the ports you normally rely on are open. - **SSH server.** Whether `sshd` is running and answering on your SSH port (it auto-detects the port), whether it accepts connections from the internet or only from inside the VPS, and your login policy: root login allowed/key-only/disabled, password and key login on or off, and any AllowUsers/DenyUsers restrictions. Give it a username and it checks that specific user: exists, allowed to log in, blacklisted, or missing from the whitelist. - **Disk and resources.** Whether you have free disk space (and inodes) and healthy CPU, memory, and load, plus recent **OOM kills** (processes killed for running out of memory). A full disk is a surprisingly common reason a VPS "won't let you in", and the page points you to free space (`df -h`) or to size up. - **System health.** Whether the filesystem has dropped into emergency **read-only** mode, and whether key services have failed: your **web server, database, php-fpm, or mail server** down shows up here by name, along with degraded or stuck system units. There's also a viewer for the last of your VPS's **boot/console output** when something died before the network came up. - **IP not blocked by our SSH firewall.** If your own IP was banned for too many wrong-password logins on port 22, the tool whitelists it for you automatically and asks you to wait about two minutes before retrying. See [SSH firewall and blocked IPs](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall). ![The expandable list of individual checks, all green: reachability, network config, standard ports, SSH server, resources, and IP blocks](https://vpsdime.com/knowledgebase/client-area/support/images/cropped/troubleshooter-checks.png) ### If it's all green but you still can't connect When every check passes but you still can't get in, the problem is usually on your side or in the network path, not the VPS itself. Worth trying, in order: - **Open the Console.** It connects straight to the VPS without SSH, so you can get in even when SSH won't and see why your client is being refused. - **Check your own network.** Some office networks, ISPs, and VPNs block outbound SSH. Trying from your phone's mobile hotspot rules that out in seconds. - **Check the username.** On Linux it's usually `root` unless you created another user yourself. A wrong username fails in exactly the same way as a bad password, so it's easy to miss. ### Self-service fixes (Linux VPS) If everything checks out but you still can't connect, or the check found a fixable problem, the page offers: !["Things you can try on your own": Reset password, Enable password login, Open Console, and How to run a network trace buttons with explanations](https://vpsdime.com/knowledgebase/client-area/support/images/cropped/troubleshooter-selfservice.png) - **Auto-fix network.** Rewrites the VPS's network configuration from our records, IPs, routes, and DNS, in one click. The fix for a hand-edited config that dropped the VPS off the network; give it about 30 seconds afterwards, then reconnect. See [setting your IP address](https://vpsdime.com/knowledgebase/technical-questions/set-ip-address) for why you never need manual IP config in the first place. - **Reset your root or user password.** Sets a new password on your VPS. - **Re-enable SSH password login.** Switches password login (and root SSH login) back on, useful if you turned it off and locked yourself out. - **Open the Console.** A terminal to your VPS in the browser, no SSH needed. Use it to fix a broken config, start a service, or just get in. - **Reboot the VPS.** A clean restart from outside, for when the VPS is wedged and even the Console isn't cooperating. - **Run a network trace (MTR).** If even a ping to your VPS fails from your computer, the problem may be between you and us. The page walks you through running a trace and pasting the result, which is attached automatically if you open a ticket. There's also a **Website Down Checker**: enter a URL to see whether a site being down is a DNS or web-server issue rather than the VPS itself. ### When your IP is blocked A common reason you can't SSH in is that your IP is blocked, and the troubleshooter handles **both places that happens**: - **Our edge SSH firewall** (too many failed password logins on port 22): it auto-whitelists your own IP and gives you a form to whitelist any IP. See [SSH firewall and blocked IPs](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall). - **Blockers inside your own VPS**: if fail2ban, CSF, or sshguard banned you, or a manual firewall rule targets your address, the matching **Unblock my IP** / **Remove the rule** button clears it without you touching the Console. The full map of every layer that can block an IP is in [My IP is blocked](https://vpsdime.com/knowledgebase/troubleshooting/ip-blocked). ### Premium VPS and Windows VPS These get a lighter check: - **Premium VPS:** confirms the VPS's power state and status, with connection guidance and a ticket link. - **Windows VPS:** checks the VPS is powered on, verifies the Administrator password we have on file, and can reset it for you. It links to [connecting to a Windows VPS with RDP](https://vpsdime.com/knowledgebase/windows-vps/connect-rdp), and if the VPS is powered off it points you to Power On. ### If it can't fix it At the bottom you can **Open the Console** or **submit a ticket**. Opening a ticket from here pre-fills it with the diagnostic results (and your network trace, if you ran one) and sends it to our Support team, so you don't have to re-explain. ### Situations it flags - **Suspended for an unpaid invoice:** it links you straight to the invoice to pay. - **Suspended for another reason:** it shows the reason. - **Still provisioning:** the VPS is being set up, and you'll get an email when it's ready. - **Node maintenance:** the host your VPS is on is having problems and we're working on it. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what happens when you try to connect, with the exact error, - whether the troubleshooter found anything. ### Related questions - "My VPS is down, what do I do?" - "I can't connect to my VPS." - "The troubleshooter says everything looks good but I still can't connect." - "How do I run the VPS troubleshooter?" - "How do I reset my root password if I'm locked out?" - "How do I get back in if I disabled SSH password login?" - "Why can't I reach my VPS from my network?" - "How do I tell if my website is down or my VPS?" - "Does the troubleshooter work for Windows or Premium VPS?" --- ## SSH firewall and blocked IPs URL: https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall Last reviewed: 2026-07-02 Summary: VPSDime runs an SSH bruteforce firewall on port 22 for Linux VPS that blocks IPs after too many wrong-password logins. The My VPS is Down page auto-whitelists your own IP and has a form to whitelist any IP (up to 10). Use SSH key authentication to avoid it. ### What this is To protect Linux VPS from brute-force attacks, we run an SSH firewall on **port 22** across our network. It counts **failed login attempts with an incorrect password** on port 22 and temporarily **blocks** the IP they come from. Sometimes that IP is your own, which is why you can suddenly find yourself unable to SSH in. This applies to **Linux VPS**. Windows VPS connects over RDP, not SSH. (Curious how the system works underneath, and why it beats a local fail2ban? See [How our SSH brute-force firewall works](https://vpsdime.com/knowledgebase/technical-questions/ssh-bruteforce-firewall).) ### Why your IP got blocked The firewall counts **failed logins with an incorrect password** on port 22, and blocks the IP after too many in a short time. Correct logins don't count, so this is specifically about *wrong* passwords piling up. Common innocent causes: - Retrying a password you're not sure of, or a saved password that's out of date. - A script or automated job (rsync, a backup, a CI runner, or anything using a tool like `sshpass`) that signs in with a password that's wrong or has changed, and keeps retrying. - An SSH client set to use the wrong key, which then falls back to failed password prompts. While your IP is blocked, SSH from it times out or is refused, even though the VPS itself is fine. ### Unblock or whitelist your IP The quickest path is the **[My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter)** page (https://vpsdime.com/myvpsisdown): - When it runs its checks, it **detects whether your own current IP is blocked and whitelists it automatically**. Wait about two minutes, then try connecting again. - It also has a **"Whitelist an IP from our SSH firewall"** form. Enter any IP (for example your home or office IP) and it's whitelisted on every node, so it stays unblocked. You can whitelist up to **10 IPs**. After that, open a ticket to whitelist more. ![The "Whitelist an IP from our SSH firewall" form on the My VPS is Down page, with the remaining slot count and a Whitelist this IP button](https://vpsdime.com/knowledgebase/client-area/support/images/cropped/ssh-firewall-whitelist-form.png) Whitelisting an IP also lifts its block if it was currently banned. ### Prevent it happening again - **Use SSH key authentication instead of a password.** This is the best fix. With a key there's no password to get wrong, so a failed-password ban can't happen. Add your key on the [SSH Keys](https://vpsdime.com/knowledgebase/client-area/services/ssh-keys) page and select it when you deploy or reinstall, or add it to the VPS yourself. For automated jobs (rsync, backups, cron), give the job its own key rather than a password, instead of a tool like `sshpass`. - **Change your SSH port.** Running SSH on a port other than 22 keeps you off this firewall entirely. The lockout-safe procedure is in [How can I change my SSH port?](https://vpsdime.com/knowledgebase/technical-questions/change-ssh-port) (make sure the new port is open before you disconnect). - **Whitelist a fixed IP.** If you always connect from the same home or office IP, whitelist it once (above) so it's never blocked. ### Troubleshooting - **I whitelisted my IP but still can't connect.** Give it a couple of minutes, then retry. If it still fails, your IP may have changed (many home connections use dynamic IPs), so whitelist the new one, or run the [troubleshooter](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) again. If SSH still won't connect, the cause is probably something other than the firewall. - **I've used all 10 whitelist slots.** Open a ticket and we'll help. - **This is a Premium or Windows VPS.** The port-22 SSH firewall is for Linux VPS. For a Windows VPS you connect over RDP, so use the [troubleshooter](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the IP you're connecting from (check a "what is my IP" site if you're not sure), - what happens when you try to SSH (timeout, refused, and so on). ### Related questions - "Why can't I SSH into my VPS?" - "My IP is blocked, how do I unblock it?" - "How do I whitelist my IP on the SSH firewall?" - "Why does SSH suddenly time out?" - "Does a wrong password get my IP blocked?" - "How do I stop getting blocked on port 22?" - "Should I use SSH keys to avoid getting banned?" --- ## Affiliate program URL: https://vpsdime.com/knowledgebase/client-area/affiliates Last reviewed: 2026-07-02 Summary: Earn a recurring 10% commission by referring customers to VPSDime. Activate once, share your referral links, and track signups, commission, and withdrawals. Earning commission by referring customers to us. - [The affiliate program](https://vpsdime.com/knowledgebase/client-area/affiliates/affiliate-program). Activate your affiliate account, share your referral links (home, per product, per plan), and track signups, commission, and withdrawals. 10% recurring, 90-day cookie. --- Still need a person? You can [open a support ticket](https://vpsdime.com/open-ticket/) any time. --- ## The affiliate program URL: https://vpsdime.com/knowledgebase/client-area/affiliates/affiliate-program Last reviewed: 2026-07-02 Summary: Earn a recurring 10% commission by referring customers to VPSDime. Activate your affiliate account once, share your referral links, and track signups, commission, and withdrawals from the Affiliates page. Referrals are cookie-tracked for up to 90 days. ### What this is The **Affiliates** page lets you earn a **recurring 10% commission** for sending customers our way. You get a set of personal referral links, share them, and earn on every signup that comes through, including as those customers renew. It's worth turning on if you write about hosting, run a website or community, or refer clients to us. Open it from **Affiliates** in the client area (https://vpsdime.com/affiliates). ### Turning it on You need a VPSDime account to be an affiliate (you don't have to be a paying customer). If you don't have one yet, [create your account](https://vpsdime.com/register) first, then open the [Affiliates](https://vpsdime.com/affiliates) page in the client area. The first time you visit, you'll see **Activate Affiliate Account** with a short summary of how the program works. Click it once and your affiliate account is live, with your referral links and dashboard ready to use. You only do this once. ![The Activate Affiliate Account page: a "Get Paid for Referring Customers to Us" card summarizing the program, with an Activate Affiliate Account button](https://vpsdime.com/knowledgebase/client-area/affiliates/images/affiliate-activate.png) ### How you earn - **Share your referral link.** Every link carries your affiliate ID, so anyone who arrives through it is tied to your account. - **90-day cookie.** We track referred visitors with a cookie that lasts **up to 90 days**, so they don't have to buy on the first visit. If they come back and order any time within that window, the referral still counts for you. - **10%, recurring.** You earn 10% of what a referred customer pays, and it's recurring, so you keep earning as they renew rather than just on the first payment. ### Your referral links ![The Referral Links section: a ready-made link per destination (Home Page, per product, per plan), each with a Copy button](https://vpsdime.com/knowledgebase/client-area/affiliates/images/cropped/affiliate-referral-links.png) The **Referral Links** section gives you a ready-made link for each place you might send someone, each with a **Copy** button: - **Home Page**, for a general referral. - **Per product** (Linux VPS, Windows VPS, Premium VPS), to drop someone straight onto that product. - **Per plan** (specific Linux, Windows, and Premium plans), to link a plan you're recommending. Use the most specific link that fits. If you're recommending a particular plan, the plan link lands people right on it, which usually converts better than sending them to the home page to find it themselves. ### Reading the dashboard ![The affiliate dashboard: Total Referred, Total Signups, Conversion Rate, and Total Earned tiles, the Withdrawal Requirements notice, and the Commission Balance breakdown](https://vpsdime.com/knowledgebase/client-area/affiliates/images/cropped/affiliate-stats-balance.png) - **Total Referred, Total Signups, Conversion Rate.** How many visitors your links brought in, how many of them became signups, and the ratio between the two. A low conversion rate with plenty of referred visits usually means people are landing on the wrong page, try a more specific link. - **Total Earned.** Your commission to date. - **Commission Balance:** - **Pending Maturation** is commission you've earned that isn't withdrawable yet (see below). - **Available Commissions Balance** is what you can withdraw now. - **Total Amount Withdrawn** is what you've already taken out. - **Referrals table.** Every referred signup with its date, the product, the amount, your commission, and its status. ### Getting paid - **Maturation.** Commission has to **mature for 30 days after the customer's payment** before you can withdraw it. That covers the refund window, so a commission isn't paid out and then clawed back. Until it matures it sits in *Pending Maturation*, then moves to your available balance. - **How to withdraw:** - **Credit** to your VPSDime account, minimum **$5**. Best if you want to put your earnings toward your own services. - **Payoneer** payout, minimum **$50**. Best if you want to cash out. ### Good to know - **No mass mailing.** Promoting us by mass email (spam) is **strictly forbidden**. Share your links where they're welcome, on your own site or content, or with people who've asked, not unsolicited blasts. - **It's tied to your account.** Your affiliate earnings and your service billing live on the same account, which is what makes withdrawing to credit convenient. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). For an affiliate question, it helps to mention whether it's about a specific referral, your balance, or a withdrawal. ### Related questions - "How does the VPSDime affiliate program work?" - "How do I become an affiliate?" - "Do I need a VPSDime account to be an affiliate?" - "How much commission do I earn, and is it recurring?" - "How long does the referral cookie last?" - "Where do I find my referral links?" - "When and how can I withdraw my affiliate earnings?" - "What's the minimum payout, and what are the withdrawal methods?" - "Why is my commission pending / not withdrawable yet?" - "Can I promote my referral link by email?" --- ## Billing policies & information URL: https://vpsdime.com/knowledgebase/billing Last reviewed: 2026-07-05 Summary: How VPSDime billing works, the invoice schedule and what happens if you don't pay, the payment methods we accept, taxes, refunds, and how to query a charge. General billing information for VPSDime: the payment schedule, what we accept, taxes, refunds, and how to reach us about a charge. To pay an invoice or manage how you're billed inside your account, see [Billing in your client area](https://vpsdime.com/knowledgebase/client-area/billing). ### Paying & schedule - [When invoices are due, and what happens if you don't pay](https://vpsdime.com/knowledgebase/billing/billing-timeline). The schedule, and suspension vs termination. - [Getting your data from a suspended VPS](https://vpsdime.com/knowledgebase/billing/data-from-suspended-vps). Ask us for a 24-hour unsuspension to back up before termination. - [Payment methods we accept](https://vpsdime.com/knowledgebase/billing/payment-methods). Cards, wallets (PayPal, Apple Pay, Google Pay and more), bank and local methods, and crypto. - [Paying with cryptocurrency](https://vpsdime.com/knowledgebase/billing/crypto-payments). Bitcoin and USDT (TRC20, BEP20, ERC20) via CoinPayments: matching the network, following confirmations, fixing over/underpayments, and paying small invoices from credit. - Prefer to arrange the dates yourself? [Prepay months ahead](https://vpsdime.com/knowledgebase/client-area/billing/pay-in-advance), [sync several services onto one renewal date](https://vpsdime.com/knowledgebase/client-area/billing/sync-due-dates), or [change your billing day](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-day), all self-service in your client area. ### Taxes & refunds - [Refunds and credits](https://vpsdime.com/knowledgebase/billing/refunds). The 72-hour money-back guarantee, and what isn't refundable. - [Taxes (VAT and sales tax)](https://vpsdime.com/knowledgebase/billing/taxes). How tax is added, and your VAT/GST number on invoices. ### Questions - [Billing questions](https://vpsdime.com/knowledgebase/billing/billing-questions). A billing FAQ: pausing a service, late payment and fees, proration, saved cards, chargebacks, transfers, and querying a charge. - [Closing a PayPal dispute or case](https://vpsdime.com/knowledgebase/billing/close-a-paypal-dispute). How to withdraw a PayPal dispute, and what to do once it's a claim. - [Why did my card payment fail?](https://vpsdime.com/knowledgebase/billing/card-payment-failed). Common decline reasons, "Exceeds frequency limit", and what to try. - [My invoice shows Pending or Security Review after I paid](https://vpsdime.com/knowledgebase/billing/invoice-pending-after-paying). What each status means, how long a payment takes to clear (including the processor's security review and PayPal eChecks), and why not to pay twice. - [How to list your PayPal subscriptions](https://vpsdime.com/knowledgebase/billing/list-paypal-subscriptions). Find, view, and cancel recurring payments on PayPal. --- Still need a person? You can [open a support ticket](https://vpsdime.com/open-ticket/) any time. --- ## When invoices are due, and what happens if you don't pay URL: https://vpsdime.com/knowledgebase/billing/billing-timeline Last reviewed: 2026-07-05 Summary: VPSDime's billing schedule, when invoices are generated, the reminder and overdue notices, and what suspension (data kept, auto-reactivated) and termination (data deleted) mean. ### What this is How our billing schedule works: when you get an invoice, when it's due, and what happens at each stage if it isn't paid. ### The schedule - **New orders:** the first invoice is **due immediately**. Your service starts once it's paid. - **Renewals:** we generate the renewal invoice **14 days before** its due date, so you have two weeks to pay. - **On the due date:** we send a payment reminder. - **1 to 3 days overdue:** if it's still unpaid, we send an overdue notice each day. - **3 days overdue:** the service is **suspended**. Your data is kept. - **10 days overdue:** if it's still unpaid, the service is **terminated** and the data is permanently deleted. ### Suspension vs termination - **Suspended:** the service is offline but your **data is kept**. As soon as you pay the overdue invoice, the service is **automatically reactivated**, usually within a few minutes, with nothing else to do. - **Terminated:** the service and its data are **deleted permanently** and can't be recovered. Make sure an invoice is paid before it's **10 days overdue** if you want to keep the VPS. ### Things worth knowing - **Don't let an invoice reach 10 days overdue.** Suspension is recoverable, termination is not. - **Need your data but can't pay?** While the service is still suspended, we'll [unsuspend it for 24 hours](https://vpsdime.com/knowledgebase/billing/data-from-suspended-vps) so you can download your data before the service is terminated. - **Done with the service? Cancel it instead of letting it terminate.** The [Cancellation tab](https://vpsdime.com/knowledgebase/client-area/services/cancellation) still works while a service is suspended, and an immediate cancellation **also cancels the unpaid invoice**, nothing left to pay, no further notices. It's the clean way to walk away (grab your data first, cancellation deletes it). - **No double-charge on auto-renew.** If a service is set to renew automatically and you also pay its invoice yourself, we won't charge again for that period. See [Automatic renewals](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions). - **Clear old invoices before ordering more.** Outstanding invoices should be paid before you place new orders. - **Keep your email reachable.** Reminders and overdue notices go to your account email, so make sure you receive our mail and that your address is current on [Account Details](https://vpsdime.com/knowledgebase/client-area/account/account-details). ### Want to pay early? The renewal invoice is generated 14 days before the due date, so if your renewal is close, it's probably already sitting in [your invoices](https://vpsdime.com/knowledgebase/client-area/billing/invoices) waiting. Beyond that, two different things people mean by "paying early", each with its own path: - **Prepay months, so the renewal moves forward.** [Pay for your service in advance](https://vpsdime.com/knowledgebase/client-area/billing/pay-in-advance) is self-service: add **1 to 24 months** at your current price, pay the one-time invoice (account credit works too), and renewal invoices simply start arriving that much later. This is the one to use to renew your VPS now, spend down credit, or cover an absence. - **Just want the upcoming renewal invoice raised early**, with your due date staying where it is, say your accounting closes on a particular day? [Contact us](https://vpsdime.com/open-ticket/) and we'll generate it ahead of the 14-day window so you can pay it whenever suits you. Paying this way doesn't change your due date or shorten your term. Related self-service while you're arranging dates: [move your renewal to a day of the month that suits you](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-day), or [line several services up to renew together](https://vpsdime.com/knowledgebase/client-area/billing/sync-due-dates). ### Troubleshooting - **My service was suspended.** Pay the overdue invoice and it reactivates automatically within a few minutes. See [Viewing and paying an invoice](https://vpsdime.com/knowledgebase/client-area/billing/invoices). - **The VPS is back after paying, but my website or app isn't.** Reactivation boots the VPS fresh, and services that were never set to start on boot stay down. The one-minute fix is in [My website didn't come back after a reboot or unsuspension](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot). - **Can I restore a terminated VPS?** No. Termination **permanently deletes the VPS and its data**, so neither the service nor anything on it can be restored, by you or by us. [Open a ticket](https://vpsdime.com/open-ticket/) and we'll help you set up a fresh one; if your old IP is still free, we can usually put it on the new service. - **I didn't get the invoice or the reminders.** Check your spam folder and that your account email is correct. [Open a ticket](https://vpsdime.com/open-ticket/) if our emails aren't reaching you. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the invoice number or the service involved, - whether the service is suspended, or you're trying to avoid a due date, - a screenshot of any notice you received. ### Related questions - "When is my invoice due?" - "What happens if I don't pay my invoice?" - "My VPS was suspended, how do I get it back online?" - "Can I get temporary access to my suspended VPS to download my data?" - "Can you raise my invoice early so I can pay it now?" - "Can I pay my renewal in advance, or renew my VPS right now?" - "How do I prepay my VPS for several months?" - "Was my data deleted when my service was terminated?" - "Can I restore a terminated VPS?" - "When do you generate my renewal invoice?" - "I don't want the service anymore, do I have to pay the overdue invoice?" --- ## Getting your data from a suspended VPS URL: https://vpsdime.com/knowledgebase/billing/data-from-suspended-vps Last reviewed: 2026-07-04 Summary: If your VPS was suspended over an unpaid invoice and you need your files, contact us and we'll unsuspend it for 24 hours so you can download your data before the service is terminated. How to ask, what the deadline is, and the fastest ways to copy data off. ### What this is Your VPS was suspended, usually over an unpaid invoice, and you've decided not to continue the service, but your data is still on it. You don't have to lose it: **contact us and we'll unsuspend the VPS for 24 hours** so you can download what you need. ### How it works 1. [Open a ticket](https://vpsdime.com/open-ticket/) and ask for temporary access to back up your data. Mention the VPS hostname or IP. 2. We unsuspend the VPS for **24 hours**. It comes back online exactly as it was. 3. Copy your data off. For most setups that's an [SFTP download or an rsync](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps) to another machine; databases deserve a proper dump rather than raw files. 4. After the window, the VPS returns to suspended, and the normal [billing schedule](https://vpsdime.com/knowledgebase/billing/billing-timeline) continues. ### Mind the deadline Suspension keeps your data; **termination deletes it permanently**. On the standard schedule a service is terminated when its invoice reaches **10 days overdue**, so ask for the access window **while the service is still suspended**. After termination there is nothing left to recover. Of course, if you'd rather keep the VPS, just pay the overdue invoice, [reactivation is automatic](https://vpsdime.com/knowledgebase/billing/billing-timeline) within minutes, with no fee. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - that you'd like a temporary unsuspension to back up data, - roughly how much data you need to move, if you know it. ### Related questions - "Can I get temporary access to my suspended VPS to download my data before it's deleted?" - "My VPS is suspended, how do I get my files off it?" - "Can you unsuspend my server so I can back it up?" - "How long do I have before my suspended VPS is deleted?" - "Can I recover data after my VPS was terminated?" --- ## Payment methods we accept URL: https://vpsdime.com/knowledgebase/billing/payment-methods Last reviewed: 2026-07-04 Summary: The full list of ways you can pay for VPSDime invoices, cards, digital wallets (PayPal, Apple Pay, Google Pay and more), bank and local methods, and cryptocurrency. ### What this is The ways you can pay a VPSDime invoice. You choose a method when you check out or when you open an unpaid invoice. We accept cards, digital wallets, bank and local payment methods, and cryptocurrency. ### Methods we accept The label in brackets is the option to pick on the payment page. "Its own option" means the method appears as its own button on the selector. **Cards** - Visa (Mastercard / Visa, PayPal / Card, or Alternative PayPal) - MasterCard (Mastercard / Visa, PayPal / Card, or Alternative PayPal) - American Express (PayPal / Card or Alternative PayPal) - Discover (PayPal / Card or Alternative PayPal) - JCB (PayPal / Card or Alternative PayPal) - UnionPay (PayPal / Card) - South Korea local cards (PayPal / Card) **Digital wallets and pay services** - PayPal (PayPal / Card or Alternative PayPal) - Apple Pay (PayPal / Card) - Google Pay (PayPal / Card) - Samsung Pay (PayPal / Card) - Alipay (its own option) - Naver Pay (PayPal / Card) - Kakao Pay (PayPal / Card) - Payco (PayPal / Card) - WebMoney (its own option) **Bank and local transfer** - iDEAL (PayPal / Card) - Bancontact (PayPal / Card) - Sofort (its own option) - GiroPay (its own option) - DOKU (its own option, **not instant**, clears once the bank or over-the-counter payment completes) - Boleto (its own option, **not instant**, see the note below) - PIX (its own option, instant) - PicPay (its own option) **Cryptocurrency** - Bitcoin (its own option) - USDT (its own option, on the TRC20, BEP20, or ERC20 network) Crypto has its own guide, what to know before sending, matching the USDT network, confirmations, and fixing mistakes: [Paying with cryptocurrency](https://vpsdime.com/knowledgebase/billing/crypto-payments). ### Things worth knowing - **All billing is in US dollars (USD).** Prices and invoices are in USD, whichever method you pay with. If your card or account is in another currency, your bank or payment provider converts the charge at its own exchange rate. - **You pick the method at payment time.** When you check out or open an unpaid invoice, the available methods appear as options. Choose one and follow the prompts. See [Viewing and paying an invoice](https://vpsdime.com/knowledgebase/client-area/billing/invoices). - **Three options can take a card.** At payment time, **Mastercard / Visa** (our main card processor), **PayPal / Card**, and **Alternative PayPal** each accept a card, and each runs through a different provider behind the scenes. If your card is declined on one, the same card often goes through on another. See [why a card payment fails](https://vpsdime.com/knowledgebase/billing/card-payment-failed). - **Some options only appear for certain countries.** Country-specific methods show up for customers in those countries, for example PIX and Boleto for Brazil. You'll see the options relevant to your location, alongside cards, PayPal, and crypto, which are available everywhere. - **Boleto isn't instant, plan for it.** A Boleto payment isn't confirmed the moment you pay it; it clears through the banking system and typically takes **up to 48 hours** (sometimes longer over weekends and holidays) to show as paid. Your invoice stays unpaid until it clears. If you're paying with Boleto, **pay 3 to 4 days before your due date** so it clears in time, an invoice still unpaid at 3 days overdue is [suspended automatically](https://vpsdime.com/knowledgebase/billing/billing-timeline). If you need the payment to land immediately, use **PIX** instead, it's instant. - **Some wallets appear inside the card or PayPal checkout.** Apple Pay, Google Pay, and several regional wallets show up within the card or PayPal window depending on your device, so you may not always see them as a separate option. - **A one-time payment is different from auto-renewal.** Saving a card or setting up a subscription so a service renews on its own is a separate step. See [Automatic renewals](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions) and [Saved cards](https://vpsdime.com/knowledgebase/client-area/billing/saved-cards). - **Prefer to prepay?** You can [add account credit](https://vpsdime.com/knowledgebase/client-area/billing/add-funds) and let invoices draw from it, or [prepay a specific service](https://vpsdime.com/knowledgebase/client-area/billing/pay-in-advance) for up to 24 months so its renewal moves forward. ### Troubleshooting - **A method I want isn't listed.** Not every method is offered for every payment. Pick another from the options shown, or [open a ticket](https://vpsdime.com/open-ticket/) if none of them work for you. - **My card was declined.** Try the same card on a different card option: **Mastercard / Visa**, **PayPal / Card**, and **Alternative PayPal** each go through a different provider, so a card refused by one often works on another. You can also try a different card, or another method such as PayPal or a wallet. Card issuers sometimes block international charges, so a second attempt often goes through. See [why a card payment fails](https://vpsdime.com/knowledgebase/billing/card-payment-failed). - **I want to pay with crypto.** Choose Bitcoin or USDT at payment time, and read [Paying with cryptocurrency](https://vpsdime.com/knowledgebase/billing/crypto-payments) first if you haven't paid with crypto before, the network choice matters. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the invoice number you're trying to pay, - which method you tried and what happened (any error message), - whether you're checking out a new order or paying an existing invoice. ### Related questions - "What payment methods do you accept?" - "Can I pay with PayPal / Apple Pay / Google Pay?" - "Do you take cryptocurrency, Bitcoin, or USDT?" - "How long does a Boleto payment take to clear?" - "Why is my invoice still unpaid after I paid the Boleto?" - "What's the fastest way to pay from Brazil?" - "Why don't I see a particular payment method at checkout?" - "My card was declined, what else can I use?" - "Can I pay in my own currency, like EUR?" --- ## Paying with cryptocurrency (Bitcoin and USDT) URL: https://vpsdime.com/knowledgebase/billing/crypto-payments Last reviewed: 2026-07-05 Summary: How crypto payments work at VPSDime. We accept Bitcoin and USDT (on the TRC20, BEP20, and ERC20 networks) through CoinPayments.net. What a crypto payment actually is, why the USDT network you pick must match the one you send on, how to follow confirmations, what to do if you sent too much or too little (CoinPayments' self-service form), and the wallet-minimum workaround: load account credit with Add Funds and pay small invoices from it. Includes a starter path for people who've never bought crypto. ### What this is Paying a VPSDime invoice with cryptocurrency. We accept **Bitcoin** and **USDT**, processed through **[CoinPayments.net](https://www.coinpayments.net/)**, and both appear as their own options when you pay an invoice or check out. Crypto works everywhere, needs no card or bank account, and suits people who prefer to keep payment details private. It also comes with a few rules of its own, and knowing them before you send is the difference between a payment that lands in minutes and one that needs fixing afterward. ### Crypto payments in plain terms If you've never made one: a crypto payment is a **push** payment. Nothing is charged or pulled from you; you send the money yourself, from your wallet or exchange account, to an address we give you. The transfer is confirmed by the currency's network rather than a bank, takes minutes rather than moments, and is **irreversible**, there is no chargeback and no cancel button once it's sent. That's why crypto checkouts are precise about two things: the **exact amount** and the **exact address**. Your invoice is in US dollars, like all our billing. When you choose a crypto option, the checkout converts the USD amount to a crypto amount at that moment's exchange rate and shows you the address, a QR code, and the amount to send. ### What we accept - **Bitcoin (BTC)**, on the Bitcoin network. - **USDT (Tether)**, a "stablecoin" whose value tracks the US dollar one-to-one, which makes it the practical choice for paying dollar invoices: no exchange-rate surprises between buying it and spending it. We accept USDT on **three networks**: - **TRC20**, USDT on the Tron network. Transfer fees are typically cents, the common choice. - **BEP20**, USDT on BNB Smart Chain (the Binance network). Also very cheap to send. - **ERC20**, USDT on Ethereum. The oldest and most widely supported, but network fees can be several dollars when Ethereum is busy. A "network" here is the rail the token travels on. The same USDT balance can exist on any of the three; what matters is that a transfer happens entirely on **one** network, which brings us to the rule that matters more than everything else on this page. ### The one rule: the network must match When you pay with USDT, you pick a network, and the address you're given belongs to **that network only**. Your wallet or exchange will also ask which network to send on when you withdraw. **These must match.** USDT sent on a different network than the address expects **will not arrive**, and recovering a cross-network payment ranges from slow to impossible. So: pick TRC20 with us, send on TRC20 from your side. The names are shown in every wallet and exchange withdrawal screen; take the five seconds to check them against each other before confirming. Bitcoin has no such choice to make, BTC only travels on its own network. ### How a payment works, step by step 1. Open the unpaid invoice (or check out) and choose **Bitcoin** or **USDT**, and for USDT, the network you'll send on. 2. The payment window shows the **address**, a **QR code**, the **exact amount**, and a time limit. The amount is locked to the exchange rate for that window, so send while it's open; if it lapses before you've sent anything, just reopen the invoice and start fresh. 3. Send the exact amount from your wallet or exchange. Two fee details to get right: - The **network fee** for sending is paid by you, on top. Your wallet adds it automatically. - **Exchanges often deduct their withdrawal fee from the amount you enter**, so what arrives is less than what you typed. What matters is what *arrives*: if the invoice asks for 12.00 USDT and your exchange takes a 1 USDT withdrawal fee, withdraw 13.00. 4. Wait for confirmations. USDT on TRC20 or BEP20 typically confirms within a few minutes; Bitcoin usually within the hour (longer if your wallet chose a low fee). Once the network confirms it, the invoice is **marked paid automatically**, there's nothing to submit on our side. ### Following your payment Every crypto transaction has a **transaction ID (TXID)**, your wallet or exchange shows it as soon as you send. Paste it into the network's public explorer and you can watch the payment progress yourself, no account needed: - Bitcoin: https://mempool.space - USDT TRC20: https://tronscan.org - USDT BEP20: https://bscscan.com - USDT ERC20: https://etherscan.io The explorer shows whether the transaction is pending or confirmed and how many confirmations it has. If it's confirmed on the explorer, it's a matter of minutes until the invoice reflects it; if the explorer shows it still pending, no amount of waiting on our pages will speed it up, the network simply hasn't processed it yet. ### Sent too much, or too little? It happens, a fee got deducted, a decimal slipped, and it's fixable. CoinPayments handles under- and overpayments directly through their **self-service form**: https://legacy.coinpayments.net/supwiz-buyer. Look your transaction up there and it presents your options, completing an underpayment by sending the difference, or claiming back an overpayment. If the form doesn't resolve it, contact CoinPayments support through that same page, and if you get stuck anywhere along the way, [open a ticket](https://vpsdime.com/open-ticket/) with the **invoice number and the TXID**, underpaid and overpaid transactions are flagged to our team as well, and we'll help you get it sorted. ### Small invoice, big wallet minimum? Use account credit Some wallets and exchanges won't send small amounts: a **minimum withdrawal of $10 or more** is common. If you're paying a **$5 invoice** and your wallet refuses the amount, don't force it, use **[Add Funds](https://vpsdime.com/knowledgebase/client-area/billing/add-funds)** in the client area instead. Load a larger amount as **account credit** in a single crypto payment, and your invoices are paid from the credit automatically. One payment covers months of small invoices, and as a bonus you pay the network fee once instead of every month. ### Never used crypto? Getting some If this is your first time, you need two things: somewhere to **buy** crypto with regular money, and the ability to **send** it. Two mainstream paths: - **An exchange**: [Coinbase](https://www.coinbase.com/), [Kraken](https://www.kraken.com/), or [Binance](https://www.binance.com/). Create an account, verify your identity (their requirement, not ours), buy USDT or BTC with a card or bank transfer, then use **Withdraw** to send it to the payment address, choosing the **matching network**. Mind the withdrawal fee and minimum noted above. - **A self-custody wallet**: [Trust Wallet](https://trustwallet.com/) (mobile) or [Exodus](https://www.exodus.com/) (desktop and mobile) hold the crypto on your device, support Bitcoin and USDT on all three networks we accept, and let you **buy with a card inside the app** through their built-in purchase partners, then send from the same app. One timing note: first-time identity checks at an exchange can take anywhere from minutes to days, so set it up before the invoice is due, not on the day. ### Things worth knowing - **Crypto doesn't auto-renew.** Push payments can't be pulled on a schedule, so crypto renewals are manual: pay each [invoice](https://vpsdime.com/knowledgebase/client-area/billing/invoices) when it arrives (14 days before the due date), keep a credit balance topped up via [Add Funds](https://vpsdime.com/knowledgebase/client-area/billing/add-funds) and let it renew from credit, or, the crypto-friendliest option, [**prepay months in advance**](https://vpsdime.com/knowledgebase/client-area/billing/pay-in-advance): one transaction covers up to 24 months, one network fee, and no monthly payment ritual. The invoice schedule and what happens if one goes unpaid are in [the billing timeline](https://vpsdime.com/knowledgebase/billing/billing-timeline). - **Leave a little margin before the due date.** Confirmations take minutes, but a stuck low-fee Bitcoin transaction can take hours. Paying a day early costs nothing and removes the race. - **Privacy:** crypto (alongside prepaid and virtual cards) is the method to use if you'd rather not share card details, and we don't require ID to sign up. ### Troubleshooting - **I sent USDT on the wrong network.** Stop and gather the TXID, the network you sent on, and the network you selected at checkout, then go to CoinPayments' [self-service form](https://legacy.coinpayments.net/supwiz-buyer) and contact their support if the form can't resolve it. Recovery depends on the networks involved and isn't always possible, which is why the network check before sending is the one habit worth building. - **I paid, but the invoice is still unpaid.** Check the TXID on the explorer for your network (links above). Still pending there means the network hasn't confirmed it yet, wait it out. Confirmed on the explorer but the invoice hasn't updated after a while? [Open a ticket](https://vpsdime.com/open-ticket/) with the invoice number and TXID. - **Less arrived than the invoice asked for.** Your exchange deducted its withdrawal fee from the amount. Complete the difference through the [self-service form](https://legacy.coinpayments.net/supwiz-buyer), and next time add the fee on top when withdrawing. - **The payment window expired before I sent anything.** Nothing happened, no money moved. Reopen the invoice and start again for a fresh address and amount. - **My wallet says the amount is below its minimum.** That's the wallet-minimum case: pay via [Add Funds](https://vpsdime.com/knowledgebase/client-area/billing/add-funds) credit instead, as above. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the invoice number, - the coin and, for USDT, the network you selected and the one you sent on, - the TXID of your transaction and what the block explorer shows. ### Related questions - "Do you accept Bitcoin or USDT, and how do I pay with them?" - "Which USDT networks do you support, TRC20, BEP20, or ERC20?" - "What happens if I send USDT on the wrong network?" - "I sent too much or too little crypto, how do I fix it?" - "How long does a crypto payment take to confirm?" - "How do I track my crypto payment with the transaction ID?" - "My wallet won't send less than $10, how do I pay a $5 invoice?" - "Can my service auto-renew if I pay with crypto?" - "I've never used crypto, how do I buy some to pay my invoice?" --- ## Refunds and credits URL: https://vpsdime.com/knowledgebase/billing/refunds Last reviewed: 2026-07-05 Summary: VPSDime's refund policy, the 72-hour money-back guarantee on your first service, and why cancellations, downgrades, and account credit don't generate refunds. ### What this is When you can and can't get money back at VPSDime. ### 72-hour money-back guarantee (first service) Your **first** VPS comes with a **72-hour money-back guarantee**: if it isn't right for you, cancel within 72 hours of the service being delivered and, in good standing, we'll refund the full amount. To get the refund, within the 72-hour window: 1. **Submit a cancellation request** for the service from your client area, and choose **Immediate** (not "end of billing period"), so the service is cancelled straight away. See [Cancelling a VPS](https://vpsdime.com/knowledgebase/client-area/services/cancellation). 2. **[Open a ticket](https://vpsdime.com/open-ticket/)** to request the refund. Refunds aren't automatic, you need to ask for it. - It covers your **first service** with us. Additional services don't include the 72-hour guarantee. - After the 72 hours, the service is non-refundable. ### Cancellations If you cancel a service yourself, **no refund or credit** is issued for unused time, whether you cancel immediately or at the end of your billing period. The one exception is the 72-hour money-back guarantee above, on your first service. ### Downgrades Downgrading a service to a smaller plan **does not** generate a refund or account credit for the difference. ### Account credit Money you add as [account credit](https://vpsdime.com/knowledgebase/client-area/billing/add-funds) is **non-refundable**. ### If we end a service If **we** end a service without cause, we'll refund the prorated amount of your remaining balance. Services ended for policy or payment violations are not refunded. ### How refunds are issued Refunds go back to the **original payment method** you used. The exception is methods that can't be reversed: if you paid with **crypto currency (Bitcoin or USDT), Alipay, DOKU, Boleto, or PIX**, any refund you're due (including the 72-hour money-back) is issued as **[account credit](https://vpsdime.com/knowledgebase/client-area/billing/add-funds)** instead. You can spend that credit on your services. **How long a refund takes:** PayPal refunds usually appear within a few minutes. Card refunds typically take **4 to 6 days** to show on your statement, depending on your bank's own policy. Refunds issued as account credit are available right away. #### Refunds of pre-authorization holds Card payments happen in two steps: the bank first places a **hold** on the amount (the pre-authorization), and the charge is **captured** afterwards. If your refund is processed while the payment is still in that pre-authorization state, the money was never actually collected, so there's nothing to "send back": the refund takes the form of a **cancelled hold**, which your bank releases on its own, typically within a few days. What that means on your side: - Your statement won't show a separate refund line, the pending charge simply **disappears** once the bank drops the hold. How fast depends entirely on your bank; a few days is normal. - **No action is needed from you**, and there's nothing for us to re-run: a released hold is the complete, correct form of this refund, we can't re-process it as a different kind of transaction, because no money moved in the first place. - If your bank flags an issue or the hold seems to linger, it still resolves **automatically through the card network**; holds expire on their own even in the worst case. ### Things worth knowing - **Use the 72 hours to make sure the VPS suits you.** If it does, keep it; if not, cancel within the window for a full refund. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - whether you're within the 72-hour window, - the service and invoice involved, - what you'd like us to do. ### Related questions - "Do you offer refunds?" - "Is there a money-back guarantee?" - "Can I get a refund if I cancel?" - "Will I get credit for downgrading my plan?" - "Is my account credit refundable?" - "Can a crypto, PIX, or Alipay payment be refunded?" - "How do I claim my 72-hour refund?" - "How will my refund be paid back to me?" - "How long does a refund take to arrive?" - "My refund doesn't show on my statement, the charge just disappeared." - "You refunded me but my bank says there's no incoming payment, why?" --- ## Taxes (VAT and sales tax) URL: https://vpsdime.com/knowledgebase/billing/taxes Last reviewed: 2026-07-02 Summary: How VAT and sales tax are handled at VPSDime, added automatically at payment, and how your VAT or GST number appears on invoices. ### What this is How tax is applied to your VPSDime payments. ### How tax is added Any **VAT or sales tax** that applies to you is **calculated and added automatically at the payment page**, based on your location. You don't need to do anything: the amount is shown before you pay, and it's collected as part of the payment. ### Your VAT or GST number You can add a **VAT Number** or **GST Number** on your [Account Details](https://vpsdime.com/knowledgebase/client-area/account/account-details). Once saved, it appears on your future invoices, which is handy for business and tax records. **To have tax removed from a payment, enter your VAT or GST number on the payment form when you pay.** Saving it on Account Details adds it to your invoices, but the exemption is applied only when you enter the number on the payment form at checkout. ### Things worth knowing - The tax shown depends on your billing location and local rules. - Adding your VAT/GST number puts it on future invoices; keeping it correct is up to you. ### Troubleshooting - **Tax was added to my payment.** That's the VAT or sales tax for your location, added automatically. - **My VAT number isn't on my invoice.** Add it on [Account Details](https://vpsdime.com/knowledgebase/client-area/account/account-details); it appears on invoices generated after you save it. - **My tax wasn't exempted even though I saved my VAT number.** Saving it on Account Details only puts it on your invoices. To be exempted, enter the number on the **payment form** when you pay. - **Can you add my VAT number to an invoice I already paid?** No. Paid invoices can't be re-issued, so a VAT or GST number can't be added to them after the fact. Save your number on [Account Details](https://vpsdime.com/knowledgebase/client-area/account/account-details) and it appears on invoices generated from then on. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the invoice number, - your VAT/GST number if it should appear, - what looks wrong about the tax. ### Related questions - "Do you charge VAT or sales tax?" - "How do I add my VAT or GST number to my invoices?" - "Why was tax added to my payment?" - "How do I get tax exempted with my VAT or GST number?" - "Can you add my VAT number to a past invoice?" --- ## Billing questions URL: https://vpsdime.com/knowledgebase/billing/billing-questions Last reviewed: 2026-07-05 Summary: A billing FAQ for VPSDime, pausing and holding a service, late payment and fees, upgrades and proration, switching billing cycle, invoices and saved cards, chargebacks and crypto payments, transfers, and how to query a charge you don't recognize. Common billing questions, answered. For the invoice schedule and what happens if you don't pay, see [when invoices are due](https://vpsdime.com/knowledgebase/billing/billing-timeline); for refunds and the money-back guarantee, see [refunds and credits](https://vpsdime.com/knowledgebase/billing/refunds). Anything not covered here? [Open a ticket](https://vpsdime.com/open-ticket/). ### Pausing and holding a service **Can I pause my service for a few months and pick it back up later?** No. We reserve your VPS's resources for you the whole time it exists, so we can't hold or pause a service and stop billing for it. If you no longer need a VPS, you can [cancel](https://vpsdime.com/knowledgebase/client-area/services/cancellation) it, but cancelling deletes the data, so back up anything you want to keep first. **Does powering off my VPS reduce my bill?** No. Your resources stay reserved whether the VPS is running or powered off, so the price is the same either way. ### Late payment, suspension, and fees **If I pay an overdue invoice after my service is suspended, does it come back on automatically?** Yes. Paying the overdue invoice **reactivates the service automatically**, usually within a few minutes, with nothing else to do. See [when invoices are due](https://vpsdime.com/knowledgebase/billing/billing-timeline) for the full schedule. **Do you charge a late fee on overdue invoices?** No, we don't charge late fees. **Is there a reactivation or reconnection fee after a suspension?** No. Reactivation after payment is free. **I can't pay on time. Can I get a little longer?** Yes, just ask. [Open a ticket](https://vpsdime.com/open-ticket/) before the due date and we can extend your service a few days to get you through a rough patch. We're glad to help as a one-off, though we can't do it as a recurring arrangement. **Can I get temporary access to my suspended VPS to download my data before it's deleted?** Of course. [Contact us](https://vpsdime.com/open-ticket/) and we'll **unsuspend the VPS for 24 hours** so you can back up your data. Ask **before** the service reaches termination on the [billing schedule](https://vpsdime.com/knowledgebase/billing/billing-timeline), once a service is terminated, the data is gone. The full walk-through is in [Getting your data from a suspended VPS](https://vpsdime.com/knowledgebase/billing/data-from-suspended-vps). **My service was terminated for non-payment. Can I get it back?** No. Termination permanently deletes the data, so there's no way to reactivate a terminated service. You'd place a new order and restore from your own [backup](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview). If your old IP address is still free and not assigned to another service, we can usually put it on the new one, just [ask](https://vpsdime.com/open-ticket/). ### Upgrades, downgrades, and add-ons **If I upgrade mid-cycle, how am I charged?** The upgrade is **prorated**: you pay only for the remainder of your current billing cycle at the new rate. See [upgrading or downgrading](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade). **If I add an extra (IP, storage, bandwidth, or backups) mid-cycle, how is it billed?** It's **prorated to your renewal date**, so the add-on lines up with your existing invoice from then on. Add extras from [Extra Features](https://vpsdime.com/knowledgebase/client-area/services/extra-features). **If I downgrade to a smaller plan, do I get money back for the difference?** No. A downgrade doesn't generate a refund or account credit for the difference. See [refunds and credits](https://vpsdime.com/knowledgebase/billing/refunds). (On **Premium VPS** downgrades aren't offered at all, Premium is upgrade-only.) ### Billing cycle and multiple services **Can I switch my billing cycle, for example monthly to annual?** Yes. If the service has an unpaid invoice, it's updated to the new cycle and price automatically; otherwise your next renewal invoice is the first one on the new cycle. See [changing your billing cycle](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-cycle). **Can I line my services up on one renewal date, or onto a single invoice?** Yes, and it's self-service: [Sync your renewal dates](https://vpsdime.com/knowledgebase/client-area/billing/sync-due-dates) aligns any of your services onto one renewal date with a single one-time invoice, and from then on they renew together, services due on the same date with the same payment method are combined onto one renewal invoice. To move a single service to a particular day of the month instead (the 1st, or just after payday), use [Change your billing day](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-day). ### Invoices, cards, and paying **I placed an order by mistake and don't want it. How do I cancel it?** As long as it's **unpaid and still pending** (nothing on it provisioned yet), open [My Services](https://vpsdime.com/knowledgebase/client-area/services/my-services), find the order marked Pending Payment, and click its **Cancel** button, that abandons the order and cancels the unpaid invoice. If you don't cancel it yourself, our system does it **automatically after 3 days**. **I started an Add Funds deposit but don't want to pay it. Can I cancel it?** Yes. The unpaid Add Funds invoice shows on your [dashboard](https://vpsdime.com/clientarea) with a **Cancel** button; nothing is charged if you cancel. Left alone, it's **auto-cancelled after 24 hours**. See [Add funds](https://vpsdime.com/knowledgebase/client-area/billing/add-funds). **My service was terminated for non-payment. Is my account closed too?** No. Termination ends the **service** (and deletes its data), but your **account stays open**: you can still sign in, your invoices and history are still there, and you can [place a new order](https://vpsdime.com/knowledgebase/presales/how-to-order-a-vps) whenever you like. Nothing is held against the account for a past termination, walking away from a service you no longer needed is a normal way for hosting to end. **I cancelled my service, but it has an unpaid invoice. Do I owe it?** No. Cancelling a service **cancels its unpaid invoice** as well, so there's nothing left to pay, and a cancelled service doesn't generate further renewal invoices. This works even if the service is already **suspended for non-payment**: the Cancellation tab stays available, and an immediate cancellation clears the unpaid invoice with it. If an invoice still shows Unpaid after your cancellation went through, [open a ticket](https://vpsdime.com/open-ticket/) with the invoice number and we'll clear it. See [cancelling a VPS](https://vpsdime.com/knowledgebase/client-area/services/cancellation). **Can I get an invoice up front for my accounting or a purchase order?** Yes. Invoices are **generated before you pay** them (renewals 14 days ahead), so the invoice is usually already in your client area. If you want to **pay a renewal early** and the invoice isn't there yet, [contact us](https://vpsdime.com/open-ticket/) and we'll raise it for you, see [paying early](https://vpsdime.com/knowledgebase/billing/billing-timeline). And if what you actually want is to **prepay months up front** (a quarter, a year), that's self-service: [Pay for your service in advance](https://vpsdime.com/knowledgebase/client-area/billing/pay-in-advance). To show your company name and VAT or GST number on it, add them on [Account Details](https://vpsdime.com/knowledgebase/client-area/account/account-details); see [taxes](https://vpsdime.com/knowledgebase/billing/taxes) and [viewing invoices](https://vpsdime.com/knowledgebase/client-area/billing/invoices). **Can my accountant or team receive our invoices?** Yes. Add them as a **contact** with **Invoice Emails** enabled, or set them as your **Billing Contact**, and invoices and billing reminders go to their email. A **sub-account** with the **View & Pay Invoices** permission can also sign in and pay them. See [contacts and sub-accounts](https://vpsdime.com/knowledgebase/client-area/account/contacts-and-sub-accounts). **Do you store my card details? Is my card safe?** You can save a card to pay invoices manually, or to renew your services automatically. Your card is stored securely with our **payment processor**, not on our servers. We only keep a token that lets us charge it, so your card data stays safe. See [saved cards](https://vpsdime.com/knowledgebase/client-area/billing/saved-cards). **Do you add a surcharge for PayPal, crypto, or any payment method?** No. The price is the same however you choose to pay. See [payment methods](https://vpsdime.com/knowledgebase/billing/payment-methods). **Can I pay by card in more than one way?** Yes. At the invoice page, three options take a card: **Mastercard / Visa** (our main card processor, cards only), **PayPal / Card**, and **Alternative PayPal**, and the last two also accept a card inside their checkout, not only PayPal. Each runs through a different provider, which matters most if a payment is declined: the same card is often accepted by a different option, so if one turns your card down, try another before switching methods. See [payment methods](https://vpsdime.com/knowledgebase/billing/payment-methods) and [why a card payment fails](https://vpsdime.com/knowledgebase/billing/card-payment-failed). **How do I set up or turn off automatic renewal?** Save a card or set up a PayPal billing agreement to auto-renew, and switch it off whenever you like. See [automatic renewals](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions). ### Disputes, chargebacks, and payment problems **What will the charge look like on my card or bank statement?** It depends on the option you paid with. Card payments made through the **Mastercard / Visa** option include **VPSDIME** in the descriptor. Payments made through the **PayPal / Card** option appear as **Paddle**, and through the **Alternative PayPal** option as **Fastspring**; those are the payment providers that process the charge for us. So a Paddle or Fastspring line on your statement around your renewal date is most likely your VPSDime payment. Check the amount and date against [your invoices](https://vpsdime.com/knowledgebase/client-area/billing/invoices) before treating it as a charge you don't recognize. **I think I was charged incorrectly, or I don't recognize a charge.** Contact us first. It's usually much faster than opening a dispute with your card issuer or PayPal, which can take days or weeks. [Open a ticket](https://vpsdime.com/open-ticket/) with the **invoice number** or transaction, what looks wrong, and the payment method used, and we'll put right anything billed in error. **What happens if I file a chargeback or PayPal dispute?** Our system automatically **suspends the related service** when a chargeback or dispute is raised, and we'll reach out to understand what happened. If it was a mistake, or your bank raised it on its own, we'll give you the chance to sort it out with your bank or PayPal. Getting in touch with us first is always quicker and keeps your service online. If you've already opened a PayPal dispute, see [closing a PayPal dispute](https://vpsdime.com/knowledgebase/billing/close-a-paypal-dispute). **My card was declined, or my invoice isn't marked Paid after I paid.** See [why a card payment fails](https://vpsdime.com/knowledgebase/billing/card-payment-failed) for common decline reasons, and [Pending or Security Review after paying](https://vpsdime.com/knowledgebase/billing/invoice-pending-after-paying) for why a payment isn't marked Paid right away and clears on its own (and why not to pay twice). That guide also covers **PayPal eChecks**, which can take a few business days to clear. **I was charged twice for the same invoice. Is my money lost?** No. If a duplicate payment happens, whether from a glitch on our side or on the payment gateway's, our system accounts for the extra payment and **automatically adds it to your account as credit**, so it isn't lost. The credit is applied toward your future invoices. If you don't see the credit or the numbers don't add up, [open a ticket](https://vpsdime.com/open-ticket/) with the invoice number and both transactions. **My crypto payment underpaid, overpaid, or hasn't confirmed. What now?** We use **CoinPayments** as our crypto gateway, and they handle under- and overpayments directly: for an underpayment you can send the difference, and an overpayment can be refunded. Reach CoinPayments at https://legacy.coinpayments.net/supwiz-buyer. The full crypto guide, networks, confirmations, tracking a payment by TXID, is [Paying with cryptocurrency](https://vpsdime.com/knowledgebase/billing/crypto-payments). ### Transferring a service **Is there a fee to transfer a service to another account?** No, transfers are **free**. Both people [open a ticket](https://vpsdime.com/open-ticket/), one confirming the transfer out and one confirming it in, and we move the service across. The service can't have any unpaid invoices at the time. See [transferring a service](https://vpsdime.com/knowledgebase/client-area/account/transfer-a-service). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the invoice number or the service involved, - what you'd like us to do. ### Related questions - "Can I pause or hold my VPS and resume it later?" - "Do you charge a late fee or a reactivation fee?" - "Does paying a suspended invoice bring my VPS back automatically?" - "Can I get an extension if I can't pay on time?" - "Are upgrades and add-ons prorated?" - "What happens when I switch billing cycle?" - "Is my saved card safe, and do you add payment surcharges?" - "Can I pay by card in more than one way if one is declined?" - "What happens if I file a chargeback?" - "I cancelled my service, do I still owe its unpaid invoice?" - "Why is there a Paddle or Fastspring charge on my statement?" - "I was charged twice, what happens to the extra payment?" - "How do I get invoices sent to my accountant or team?" - "What will a VPSDime charge appear as on my card statement?" - "How do I transfer a service to another account?" - "My service was terminated, is my account closed too?" - "Can I order again after a service was terminated for non-payment?" - "Can all my services renew on the same day, on one invoice?" - "Can I prepay my VPS for a year?" --- ## Closing a PayPal dispute or case URL: https://vpsdime.com/knowledgebase/billing/close-a-paypal-dispute Last reviewed: 2026-07-02 Summary: How to close or withdraw a PayPal dispute you've opened against a VPSDime payment, why contacting us directly is usually faster, and what happens once a dispute becomes a claim. ### What this is How to close a dispute or case you've opened in PayPal against a VPSDime payment. If you opened the dispute to sort out a billing problem, the quickest fix is usually to [contact us](https://vpsdime.com/open-ticket/) directly. We can resolve most issues faster than PayPal's dispute process, which can take days or weeks. Closing a dispute you no longer need also matters because PayPal can **hold the disputed funds** while a case is open, which can get in the way of us refunding or correcting the payment. ### Contact us first If there's a genuine problem with a charge, [open a support ticket](https://vpsdime.com/open-ticket/) and tell us the invoice number and what looks wrong. We'll put it right. Closing your PayPal dispute doesn't stop us helping, we'll still resolve a legitimate issue. ### How to close a dispute You close a dispute from your own PayPal account: 1. Log in to your PayPal account at [paypal.com](https://www.paypal.com). 2. Open the **Resolution Center** (under Help, or from your account menu). 3. Find and open the case you raised. 4. Choose the option to **close** the dispute. PayPal labels it something like "Close this dispute" or "Mark as resolved". Once you close it, PayPal releases any hold it placed on the payment. ### If the dispute has become a claim A PayPal dispute can be **escalated to a claim**. Once PayPal is reviewing it as a claim, the outcome is theirs to decide and you may no longer be able to close it yourself. If that's happened, [contact us](https://vpsdime.com/open-ticket/) and we'll work with you and PayPal to get it resolved. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the invoice number or payment the dispute is about, - whether the case is still a dispute or has become a claim. ### Related questions - "How do I close or cancel a PayPal dispute?" - "How do I withdraw a dispute I opened in PayPal?" - "I opened a PayPal case by mistake, how do I remove it?" - "PayPal is holding my payment because of a dispute." - "My dispute became a claim, what happens now?" --- ## Why did my card payment fail? URL: https://vpsdime.com/knowledgebase/billing/card-payment-failed Last reviewed: 2026-07-04 Summary: Why a card payment might be declined when paying a VPSDime invoice, the most common reasons banks give (holds, wrong details, insufficient funds, blocked international payments, exceeds frequency limit), and what you can do. ### What this is Why a card payment might be declined when you try to pay a VPSDime invoice, and what you can do about it. In almost every case the decline comes from **your bank or card issuer**, not from us. ### The decline comes from your bank When you pay, your card details are passed to our card processor, which asks your bank to authorize the charge. Your bank returns an **approve** or **decline** response. On a decline there's very little we can change from our side, the decision is your bank's. The email we send about a failed payment lists the **specific reason** your bank gave, so start there. ### Common reasons a card is declined **Your bank placed a hold.** The issuer has flagged or blocked the charge. Contact your bank to check for any restriction on the card. **Your billing details need updating.** An incorrect or incomplete card number, expiry, or billing address will fail authorization, since your details are matched during the charge. Check them, and make sure the card hasn't expired. **Insufficient funds.** The charge couldn't be collected from the account. Check the balance or available credit with your bank. **International payments are blocked.** Many banks block international charges by default, even if other international payments have worked before. The block can also reset without notice after you've cleared it once. Ask your bank to allow the charge. **"Exceeds frequency limit".** This means your bank declined the charge because **too many payment attempts were made in a short time**. Wait a few hours and try again. Repeated retries can trigger this, so give it some time rather than trying again straight away. ### Charged anyway? PREAUTH and holds explained Two things on your card statement can look alarming after a failed or attempted payment, and both are normal: - **A line marked PREAUTH (or "pre-authorization").** Before charging a card, the processor may place a small **pre-authorization**, a temporary hold that verifies the card is real and active. It looks like a payment in your banking app, but no money has actually been taken, and it disappears on its own. - **A failed payment that still shows up as a charge.** When your bank declines or interrupts a payment, the **authorization hold** it created can remain visible for a while, looking exactly like a real payment, even though it was never completed and will never be collected. Your online banking may label it "pending". In both cases the entry **clears by itself after a few days**; exactly how long depends on your bank or card company's policy (typically within a week). There's nothing you need to do except wait, the invoice stays payable, and paying it again does not double-charge you, since the held amounts were never collected. If a pending entry **hasn't cleared after a few days**, contact us with the invoice number and the date and amount of the entry, and we'll check it against our processor's records. ### What you can do - Read the **reason in the failed-payment email** and act on it. Most point to something your bank can fix in a minute. - **Contact your bank** to approve the charge or lift a hold, then try again. - **Update your card or billing details** if anything is out of date. If you renew with a saved card, see [Saved cards](https://vpsdime.com/knowledgebase/client-area/billing/saved-cards). - **Try the same card on a different card option.** At the invoice, three options accept a card: **Mastercard / Visa** (our main card processor), **PayPal / Card**, and **Alternative PayPal**. Each runs through a different provider, so a card declined on one often goes through on another. It's worth trying another card option before anything else. See [payment methods](https://vpsdime.com/knowledgebase/billing/payment-methods). - **Try another method.** A different card, PayPal, a wallet, or crypto often goes straight through. See [Payment methods we accept](https://vpsdime.com/knowledgebase/billing/payment-methods). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the invoice number you're paying, - the exact error or decline reason from the email, - which card type and method you tried. ### Related questions - "Why was my credit or debit card declined?" - "My card payment isn't going through, what do I do?" - "What does 'Exceeds frequency limit' mean?" - "My bank is blocking an international payment." - "Can I pay with a different method if my card fails?" - "Can I try my card through a different processor?" - "What does PREAUTH on my statement mean?" - "My payment failed but my bank shows a charge." - "Was I charged twice? There's a pending payment that failed." - "When does a pending card hold clear?" --- ## My invoice shows Pending or Security Review after I paid URL: https://vpsdime.com/knowledgebase/billing/invoice-pending-after-paying Last reviewed: 2026-07-05 Summary: After a card payment, an invoice can show Pending (processing, clears in a few minutes) or Security Review (the card processor's anti-fraud check, which can take several hours) before it's marked Paid. Both clear on their own, so you shouldn't pay again. Also covers PayPal eChecks, which can take a few business days to clear, and which methods aren't instant in general (crypto confirmations, Boleto), with the advice to use an instant method like a card, PayPal, or PIX when time matters. ### What this is You paid a VPSDime invoice by card and it isn't marked **Paid** yet. It's showing either **Pending** or **Security Review**. Both mean your payment is being processed and the invoice will flip to **Paid** on its own, so there's nothing more to pay. ### The two in-progress statuses - **Pending:** your payment is processing. This is quick and usually clears to **Paid** within a few minutes. - **Security Review:** your card payment went through, and the card processor is running its **anti-fraud check**. The invoice sits in Security Review while that happens, which can take **several hours** (often around 6 to 8). Once the processor approves it, the invoice is marked **Paid** automatically. Neither status needs anything from you, and in both cases you should **not pay again**. The invoice is held in these states partly so you don't accidentally pay twice while a payment is in flight. And if a duplicate payment does slip through, it isn't lost: our system automatically adds the extra payment to your account as **credit**. ### If a security review isn't approved If the processor's review doesn't approve the payment, we'll **email you** to let you know it was declined and ask you to pay with a different method. The **PayPal / Card** option is a good next choice, since it runs through a different provider. See [payment methods](https://vpsdime.com/knowledgebase/billing/payment-methods) and [why a card payment fails](https://vpsdime.com/knowledgebase/billing/card-payment-failed). ### Paid with PayPal? eChecks take a few days If you paid through one of the **PayPal options** and PayPal funded it as an **eCheck** (a payment drawn from your bank account rather than a PayPal balance or card), PayPal can take around **3 to 5 business days** to clear it. The invoice is marked **Paid** automatically once the eCheck clears, so you don't need to do anything more, but if you're in a hurry, it's **safe to pay the invoice again with an instant method** (a card, or PayPal from balance): should the eCheck clear too, the extra payment becomes account credit automatically and pays a future invoice. If you're not sure whether the payment went through, check the transaction in your PayPal activity, or [contact us](https://vpsdime.com/open-ticket/) with the invoice number. ### Not every method is instant How long "paid" takes to show as **Paid** depends on the method, and none of the slow ones are a fault, they're just how those rails work: - **Card**: normally instant; a payment picked for **Security Review** can take several hours (above). - **PayPal**: instant from a balance or card; an **eCheck** takes 3 to 5 business days (above). - **Cryptocurrency**: marked Paid after network confirmations, usually **minutes**, but a low-fee Bitcoin transaction can take hours. See [paying with crypto](https://vpsdime.com/knowledgebase/billing/crypto-payments). - **Boleto** (Brazil): clears through the banking system, **up to 48 hours**, sometimes longer over weekends. **PIX** is the instant alternative. See [payment methods](https://vpsdime.com/knowledgebase/billing/payment-methods). - **DOKU** (Indonesia): also **not instant**, the invoice is marked Paid once the bank transfer or over-the-counter payment clears on DOKU's side, so plan for hours rather than seconds. **In a rush?** If a suspension is looming or you want a new order provisioned now, pick a method that confirms immediately, a **card**, **PayPal** from balance or card, or **PIX** in Brazil, rather than waiting on a slow rail. This is safe even if a slow payment is already in flight: pay with the faster method now, and if the slow one lands too, the extra payment is **added to your account as credit automatically**, so nothing is lost, it simply pays a future invoice, and your service is live now instead of whenever the slow rail clears. - **Pending or Security Review:** a payment is in progress or being reviewed. Wait for it, and don't pay again. - **Unpaid:** no payment is in progress. If your invoice is still **Unpaid** after a card attempt, the payment didn't go through, so try again or use another option. See [why a card payment fails](https://vpsdime.com/knowledgebase/billing/card-payment-failed). ### Not the same as an order review **Security Review** here is the card processor checking your **payment**. It's separate from the two checks an **order** goes through: the automated [fraud screening at checkout](https://vpsdime.com/knowledgebase/presales/order-flagged-as-fraud), and the quick [human review of every paid order](https://vpsdime.com/knowledgebase/presales/order-under-review) before activation. An invoice can be fully Paid while the order itself is still in review, and the client area notices for orders are explained on those pages. ### Will my VPS be affected? An existing service keeps running while a payment clears. A **new order** provisions once the payment is confirmed, so a payment held in a Security Review can delay first setup by a few hours. See [when invoices are due](https://vpsdime.com/knowledgebase/billing/billing-timeline). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the invoice number, - when you paid and which card or option you used, - whether the invoice shows Pending, Security Review, or Unpaid. ### Related questions - "Why does my invoice show Pending or Security Review after I paid?" - "What does Security Review mean on my invoice?" - "I paid but my invoice isn't marked Paid, why?" - "How long does a card payment take to show as Paid?" - "I paid with PayPal but my invoice isn't marked Paid." - "How long does a PayPal eCheck take to clear?" - "My payment has been in Security Review for hours, is something wrong?" - "Will I be double charged if I pay again while it's Pending?" - "My payment was declined after review, what do I do?" - "Which payment methods are instant and which take time?" - "What's the fastest way to pay if my service is about to be suspended?" --- ## How to list your PayPal subscriptions URL: https://vpsdime.com/knowledgebase/billing/list-paypal-subscriptions Last reviewed: 2026-07-02 Summary: How to find, view, and cancel the recurring payments (subscriptions and billing agreements) on your PayPal account, from PayPal's own website. ### What this is How to find and manage the recurring payments on your PayPal account, on **PayPal's own website**. PayPal calls these **automatic payments**, **subscriptions**, or **billing agreements**, and this guide walks through PayPal's interface, not your VPSDime account. It shows every merchant you have a recurring PayPal payment with, not only VPSDime. **This is not the same as our Manage Subscriptions page.** To turn a VPSDime service's auto-renewal on or off, use our own [Manage Subscriptions](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions) page. This PayPal guide is only for viewing or cancelling the agreement on PayPal's side; the section on stopping a VPSDime renewal below explains how the two fit together. ### Finding your subscriptions on PayPal 1. Log in to your PayPal account at [paypal.com](https://www.paypal.com). 2. Click the **Settings** (gear) icon near the top of the page. 3. Open the **Payments** tab. 4. Click **Manage automatic payments** (also shown as **Automatic payments** or **Pre-approved payments**). 5. PayPal lists the merchants you have automatic payments set up with. Click any one to see its details. ### Cancelling a subscription On the automatic payment's detail page, click **Cancel** (labelled something like "Cancel automatic payments") and confirm. PayPal stops future automatic charges to that merchant. Any invoice that's already due still needs to be paid. ### Stopping a VPSDime renewal Cancelling the agreement on PayPal stops PayPal charging you, but the cleanest way to switch a VPSDime service's auto-renewal on or off is from your client area. See [Automatic renewals](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions). If you cancel only on PayPal's side, the service simply falls back to **manual** renewal and you pay each invoice yourself. If you've **cancelled the service itself**, there's nothing you need to do here: we only charge for active services, so a cancelled service's agreement isn't charged again. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - which VPS the subscription is for, - whether you want to stop auto-renewal or just view what's set up. ### Related questions - "How do I see my PayPal subscriptions?" - "How do I cancel a recurring PayPal payment?" - "Where are my PayPal billing agreements?" - "How do I stop PayPal automatically paying for my VPS?" --- ## Technical questions URL: https://vpsdime.com/knowledgebase/technical-questions Last reviewed: 2026-07-02 Summary: What runs on VPSDime plans, Docker and Docker Swarm, Kubernetes and k3s, Mailcow, swap, FUSE, TUN/TAP for VPNs, NFS, PPP, and disk quotas. Straight answers to "does X work on my VPS". Short version: nearly everything works out of the box on Linux VPS, and Premium VPS (full KVM) runs anything. ### Containers and orchestration - [Can I run Docker on my VPS?](https://vpsdime.com/knowledgebase/technical-questions/docker-on-vps) Yes, out of the box, no tweaks. - [Running Docker Swarm on Linux VPS](https://vpsdime.com/knowledgebase/technical-questions/docker-swarm). Works, use `dnsrr` endpoint mode instead of the default. - [Kubernetes on VPSDime services](https://vpsdime.com/knowledgebase/technical-questions/kubernetes-on-vps). k3s works on Linux VPS; full k8s wants Premium. ### CPU, memory, and disk - [What is CPU steal time (%st)?](https://vpsdime.com/knowledgebase/technical-questions/cpu-steal) Where the metric comes from, reading it properly, and what the values mean. - [What is the IOPS metric?](https://vpsdime.com/knowledgebase/technical-questions/what-is-iops) Operations vs bytes vs latency, and why databases care about the one file copies don't. - [How can I limit an application's CPU usage?](https://vpsdime.com/knowledgebase/technical-questions/limit-cpu-usage) nice for priority, CPUQuota for hard caps, and when each is right. - [How can I find the biggest folders?](https://vpsdime.com/knowledgebase/technical-questions/biggest-folders) du sorted, ncdu, and the drill-down method. - [Can I add swap memory on Linux VPS?](https://vpsdime.com/knowledgebase/technical-questions/swap-on-linux-vps) No, and you genuinely don't need it. - [Disk quotas on your VPS](https://vpsdime.com/knowledgebase/technical-questions/disk-quotas). Supported, set them up as usual. ### Networking and modules - [How do I set my IP or IPv6 address?](https://vpsdime.com/knowledgebase/technical-questions/set-ip-address) You don't, it's automatic. Where the values live, and the Auto-fix network button when a manual edit breaks connectivity. - [Running your own VPN (WireGuard)](https://vpsdime.com/knowledgebase/technical-questions/wireguard-vpn). The ten-minute personal VPN, phone QR codes, DNS leak checks, and the honest limits. - [Private networking between your VPSes](https://vpsdime.com/knowledgebase/technical-questions/private-networking-between-vpses). Tailscale or plain WireGuard, and binding services to the overlay. - [TUN/TAP (VPNs) on your VPS](https://vpsdime.com/knowledgebase/technical-questions/enable-tun-tap). Enabled by default, run your personal VPN. - [FUSE (sshfs, rclone mount) on your VPS](https://vpsdime.com/knowledgebase/technical-questions/enable-fuse). Enabled by default. - [NFS on your VPS](https://vpsdime.com/knowledgebase/technical-questions/enable-nfs). Works, nothing to enable. - [How our SSH brute-force firewall works](https://vpsdime.com/knowledgebase/technical-questions/ssh-bruteforce-firewall). Network-wide detection, why it beats a local fail2ban, and the three-firewalls map. - [Two-factor authentication for SSH (TOTP)](https://vpsdime.com/knowledgebase/technical-questions/ssh-2fa-totp). Authenticator codes at SSH login, when it's worth it, and the lockout-safe setup. - [How can I change my SSH port?](https://vpsdime.com/knowledgebase/technical-questions/change-ssh-port) Safely, in the order that can't lock you out. - [Which application is using my bandwidth?](https://vpsdime.com/knowledgebase/technical-questions/per-app-bandwidth) nethogs, iftop, and vnstat, per process, per connection, per day. - [How can I limit an application's bandwidth?](https://vpsdime.com/knowledgebase/technical-questions/limit-bandwidth-usage) App flags first, trickle, and interface shaping. - [PPP on your VPS](https://vpsdime.com/knowledgebase/technical-questions/enable-ppp). Enabled by default. ### Applications - [Can I use Mailcow on Linux VPS?](https://vpsdime.com/knowledgebase/technical-questions/mailcow-on-linux-vps) Yes, and read the email policy first. - [Scheduling tasks with cron](https://vpsdime.com/knowledgebase/technical-questions/cron-basics). The crontab format with examples, the habits that keep jobs honest, and the cron cascade that can make a VPS unresponsive, with flock as the guard. - [Using systemd timers instead of cron jobs](https://vpsdime.com/knowledgebase/technical-questions/systemd-timers). Logged runs, no overlaps, catch-up after downtime, the two-file recipe. - [Installing a desktop environment (and connecting remotely)](https://vpsdime.com/knowledgebase/technical-questions/install-desktop-environment). XFCE/LXQt/GNOME, and xRDP vs VNC vs NoMachine vs X2Go. - [Installing Gitea: host your own code](https://vpsdime.com/knowledgebase/technical-questions/install-gitea). The self-hosted GitHub, compose install, SSL, and the backup line. ### Linux skills and tools - [How do Linux file permissions work?](https://vpsdime.com/knowledgebase/technical-questions/linux-file-permissions) rwx, octal, the special bits, umask, and chattr attributes. - [Process management: ps, top, kill, and friends](https://vpsdime.com/knowledgebase/technical-questions/process-management). Seeing, finding, stopping, and prioritizing, signals included. - [How can I find files, and text inside files?](https://vpsdime.com/knowledgebase/technical-questions/find-files-and-text) find and grep -r, plus fd and ripgrep. - [How can I keep an application running after I disconnect?](https://vpsdime.com/knowledgebase/technical-questions/keep-apps-running-after-ssh) tmux, systemd, nohup, by situation. - [How can I encrypt and decrypt files?](https://vpsdime.com/knowledgebase/technical-questions/encrypt-files) age and GPG, and encrypting backups before they leave the box. - [What is strace, and how do I use it?](https://vpsdime.com/knowledgebase/technical-questions/what-is-strace) Watching a program's system calls, hung processes, and mystery configs. --- Still need a person? You can [open a support ticket](https://vpsdime.com/open-ticket/) any time. --- ## Can I run Docker on my VPS? URL: https://vpsdime.com/knowledgebase/technical-questions/docker-on-vps Last reviewed: 2026-07-02 Summary: Yes. Docker runs out of the box on Linux VPS and Premium VPS, no modules to load, no platform tweaks, no workarounds. Install it the normal way and go; Docker Compose works as usual, and Docker Swarm works with one flag. ### What this is Yes. **Docker is fully supported on Linux VPS and Premium VPS**, and there's nothing to enable on our side, no kernel modules to load, no compatibility files, no platform quirks. If you've read older guides mentioning `.dockerenv` tricks or `br_netfilter` workarounds for our platform, those belong to a previous generation of our stack and are no longer needed. ### Installing it The standard method works as-is, on a fresh Ubuntu or Debian: ``` curl -fsSL https://get.docker.com | sh ``` Or follow Docker's own install docs for your distro. **Docker Compose** (`docker compose`) works normally, and so does Podman if you prefer it. ### Worth knowing - **Docker Swarm** works on Linux VPS with one adjustment to the service endpoint mode, see [Running Docker Swarm](https://vpsdime.com/knowledgebase/technical-questions/docker-swarm). - **Kubernetes** is its own story, k3s yes, full k8s wants Premium, see [Kubernetes on VPSDime](https://vpsdime.com/knowledgebase/technical-questions/kubernetes-on-vps). - **Exposed container ports are real open ports.** Docker publishes ports past most local firewalls, so a `-p 5432:5432` puts your database on the internet. Bind to localhost when only the VPS needs it (`-p 127.0.0.1:5432:5432`), and note our [managed firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall) still shields the riskiest app ports at the network edge. - One of our [one-click Applications](https://vpsdime.com/knowledgebase/getting-started/one-click-applications) is **Coolify**, which gives you a Docker-based deploy platform without assembling it yourself. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the docker command that misbehaves and its exact output. ### Related questions - "Does Docker work on your Linux VPS?" - "Do I need to enable anything to run Docker?" - "Does docker compose work?" - "Is the .dockerenv workaround still needed?" --- ## Running Docker Swarm on Linux VPS URL: https://vpsdime.com/knowledgebase/technical-questions/docker-swarm Last reviewed: 2026-07-02 Summary: Docker Swarm works on Linux VPS with one adjustment, use DNS round-robin endpoint mode (dnsrr) instead of the default virtual-IP mode, which relies on ipvs that our Linux VPS platform doesn't provide. How to set it per service and in stack files. ### What this is **Docker Swarm works on Linux VPS**, with one adjustment you need to know up front: create your services with **`dnsrr` endpoint mode** instead of the default. By default, Swarm gives each service a virtual IP and balances traffic to it using **ipvs**, a kernel load-balancing feature our Linux VPS platform doesn't provide. Services created in the default mode will misbehave. The built-in alternative, **DNS round-robin (`dnsrr`)**, skips the virtual IP entirely: Swarm's internal DNS returns the IPs of the service's replicas directly, and that works fine here. ### How to use dnsrr Per service: ``` docker service create --name web --endpoint-mode dnsrr myimage ``` In a stack/compose file: ```yaml services: web: image: myimage deploy: endpoint_mode: dnsrr ``` ### What dnsrr changes in practice - **Published ports:** `dnsrr` doesn't do the routing-mesh style `--publish` (mode `ingress`). Publish in **host mode** instead (`--publish published=80,target=80,mode=host`) or, more commonly, put a **reverse proxy** (Traefik, nginx, Caddy) in front, Traefik in particular works naturally with dnsrr services, discovering replicas through Swarm. - **Service-to-service traffic** inside the overlay network just works: containers resolve the service name and get replica IPs. - If you've seen older errors about `br_netfilter` when initializing Swarm on our platform, that era is over, current Linux VPS need only the endpoint-mode adjustment described here. ### Panels built on Swarm: EasyPanel Some server panels run on Swarm under the hood, **[EasyPanel](https://easypanel.io/)** is the common one, which means a fresh install on a Linux VPS creates its services in the default VIP mode and they misbehave (typically as persistent **[502 errors](https://vpsdime.com/knowledgebase/troubleshooting/502-503-errors)** on every deployed app). EasyPanel doesn't currently expose an endpoint-mode setting in its UI, so convert its services from the shell: ``` docker service update --endpoint-mode dnsrr easypanel ``` And the same for **every other service** it has created, list them and convert in one pass: ``` docker service ls --format '{{.Name}}' for s in $(docker service ls -q); do docker service update --endpoint-mode dnsrr $s; done ``` Keep in mind the panel creates a **new service per app you deploy**, and new services come up in the default mode again, re-run the update for newly deployed apps (or the loop above after adding several). ### If you'd rather have stock behavior **Premium VPS** is full KVM, a plain kernel of your own, so Swarm's default ipvs mode (and everything else) behaves exactly as on bare metal. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the service's endpoint mode (from `docker service inspect`), - the symptom (502s, an unreachable service, a panel like EasyPanel involved). ### Related questions - "Does Docker Swarm work on your Linux VPS?" - "What is endpoint-mode dnsrr and why do I need it?" - "My Swarm service isn't reachable on its virtual IP." - "How do I publish ports with dnsrr?" - "EasyPanel apps all return 502 on my Linux VPS, how do I fix it?" - "How do I switch every Swarm service to dnsrr at once?" --- ## Kubernetes on VPSDime services URL: https://vpsdime.com/knowledgebase/technical-questions/kubernetes-on-vps Last reviewed: 2026-07-02 Summary: Full Kubernetes (kubeadm and friends) doesn't work on Linux VPS, but k3s works fine and covers most single-node and small-cluster needs. For stock full-fat Kubernetes, use Premium VPS (full KVM). ### What this is Where Kubernetes stands on each product line: - **Linux VPS: full Kubernetes doesn't work, k3s works fine.** Stock distributions like kubeadm expect kernel-level facilities our Linux VPS platform doesn't expose, so a full k8s install will fail in frustrating ways. Don't fight it. - **[k3s](https://k3s.io/)** is the answer on Linux VPS: a lightweight, fully conformant Kubernetes distribution that runs happily here. For a single node or a small cluster, it does everything most people actually need from k8s, with far less overhead (which also means more of your RAM goes to workloads instead of the control plane). - **Premium VPS: everything works.** Full KVM with your own kernel is as close to bare metal as it gets, kubeadm, k3s, RKE2, whatever you like, all stock behavior. ### Getting k3s running Their one-liner works as-is on a Linux VPS: ``` curl -sfL https://get.k3s.io | sh - ``` Then `kubectl` is available via `k3s kubectl` (or copy the kubeconfig for your own tooling). k3s is maintained by SUSE/Rancher with excellent docs and community; for k3s-specific issues, their documentation and forums are the right resource, we support the VPS underneath it per our [support coverage](https://vpsdime.com/knowledgebase/support-coverage/what-support-covers). ### Choosing between the options - Just want containers on one box? Plain [Docker or Compose](https://vpsdime.com/knowledgebase/technical-questions/docker-on-vps) is simpler than any Kubernetes. - Want k8s APIs, Helm charts, operators? **k3s on Linux VPS** gives you real Kubernetes at VPS prices. - Need stock full-fat Kubernetes, exotic CNIs, or kernel-level tuning? **Premium VPS.** ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP and the product (Linux or Premium VPS), - whether it's k3s or another distribution, and the exact install error. ### Related questions - "Does Kubernetes work on your Linux VPS?" - "Can I run k3s on my VPS?" - "Why does kubeadm fail on my Linux VPS?" - "Which plan do I need for a Kubernetes cluster?" --- ## What is CPU steal time (%st)? URL: https://vpsdime.com/knowledgebase/technical-questions/cpu-steal Last reviewed: 2026-07-02 Summary: CPU steal time is the share of time a virtual CPU was ready to run but the hypervisor gave the physical core to someone else. Where the metric comes from, how to read it in top/vmstat/sar, what values mean, the first-order slowdown model, why it cannot be fixed from inside a guest, and how it differs from ordinary CPU saturation. ### Definition **Steal time** is the percentage of time a virtual CPU had work ready to run but could not run it, because the hypervisor had scheduled the underlying physical CPU to something else. It is time your virtual machine spent **involuntarily waiting for a physical core**: not idle (there was work to do), not blocked on disk or network (the task was runnable), simply not given hardware to run on during those moments. The metric exists only in virtualized environments. On physical hardware, a runnable task waits only for other tasks *on the same machine*; under virtualization, the machine itself can be made to wait, and steal time is how the guest kernel accounts for it. ### Where it comes from A hypervisor multiplexes **virtual CPUs onto physical cores** the same way an operating system multiplexes processes onto CPUs: vCPUs are, to the host, schedulable threads. When the sum of vCPUs across all guests exceeds the physical cores available, or simply when several guests demand CPU at the same instant, runnable vCPUs queue. The host informs each guest (through paravirtualized clock interfaces) how long its vCPUs sat in that queue, and the guest kernel reports it as steal. Two properties follow directly from this mechanism: - **Steal accumulates only under demand.** A vCPU that asks for nothing is never made to wait, so an idle guest shows near-zero steal regardless of how contended the host is. Steal is therefore meaningful only when measured **while your workload is actually running**. - **Steal is entirely a host-side phenomenon.** Nothing inside the guest, process priorities, `nice`, kernel or scheduler tuning, changes it, because the waiting happens below the guest's kernel. A guest can *measure* steal; it cannot *influence* it. A related, deliberate case: burstable or credit-based instance types (common at large clouds) enforce their CPU caps through the same mechanism, when the credit is spent, the hypervisor withholds cycles, and the guest sees it as steal. There, high steal is the product working as designed rather than contention. ### How to observe it The guest kernel exposes cumulative steal ticks as the eighth field of each CPU line in `/proc/stat`; the familiar tools present it as a percentage: - **top / htop**: the `st` value at the end of the CPU summary line (`%Cpu(s): ... 1.7 st`). - **vmstat 1**: the `st` column, sampled per second. - **sar -u** (sysstat): `%steal`, with history, which matters because steal is often periodic (a neighbor's nightly job) and a single glance misses the pattern. - **mpstat -P ALL** shows it per vCPU. Single samples mislead in both directions; judge steal by its **sustained value under your own load**, ideally from a time series covering at least a day. ### Interpreting the numbers - **0%**: your vCPUs get a physical core the moment they ask. The expected state on dedicated or lightly shared hosts. - **Transient low single digits**: ordinary scheduling coincidence, two guests occasionally wanting the same core at the same tick. Imperceptible for almost all workloads. - **Sustained 5 to 10%**: measurable. Throughput drops and, often more noticeable, **latency becomes jittery**, individual requests stall for scheduling gaps that the application cannot see or log, so response times develop an unexplained tail. - **Sustained above 10 to 20%**: severe contention. Everything stretches, and interactive workloads feel it constantly. A useful first-order model: sustained steal of *s* stretches CPU-bound wall-clock time by roughly a factor of **1/(1 − s)**, at 20% steal, a job that needs 60 CPU-seconds occupies about 75 seconds of real time. The model is approximate (it ignores burstiness and cache effects, which usually make the felt impact worse than the arithmetic), but it sets the scale: steal is not cosmetic once it is sustained. Steal also inflates the **load average**: tasks that are runnable-but-waiting count toward load, so a contended guest can show climbing load with modest `%us`, a signature worth recognizing. ### Distinguishing steal from your own saturation The CPU summary line separates the cases cleanly: - **High `us`/`sy`, near-zero `st`**: the machine is busy with *your* work. The remedy is inside the guest, profile, optimize, or add cores. - **Meaningful `st` while `us`+`sy` cannot reach the ceiling**: the machine is being made to wait. The remedy is structural, nothing inside the guest will change it. - **High `wa`** is a third, unrelated axis: waiting on I/O, not on CPU at all. ### What determines how much steal you see On any shared platform, steal is a function of decisions made on the host: the **overcommit ratio** (total vCPUs sold per physical core), the **demand patterns of co-tenants** (steal from neighbors is bursty and time-of-day shaped), and the **hypervisor's scheduling policy** (shares, weights, caps). At one extreme, hosts with pinned or reserved cores produce steal that is zero by construction; at the other, heavily oversold hosts produce chronic double-digit steal. Between providers and products, this ratio, not the advertised core count, is the variable that decides how much of a "4 vCPU" machine you actually get during busy hours. ### What a tenant can do 1. **Measure properly**: a `sar` or monitoring-agent time series of `%steal` under real load, over days, is objective evidence, and distinguishes chronic overcommit from a transient neighbor. 2. **Re-check your own side**: confirm the slowness correlates with `st` and not with `us`/`sy` (your code) or `wa` (your disk I/O). 3. **Structural remedies**: since steal cannot be tuned away from inside the guest, persistent high steal is resolved by moving the workload, to a host or product where CPU is dedicated or pinned, or by accepting the trade-off consciously where the workload tolerates it (batch jobs care little; latency-sensitive services care a lot). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - a `sar` or `vmstat` sample of %st under real load, with the timeframe it covers. ### Related questions - "What does st mean in top?" - "What is a normal CPU steal time value?" - "Why is my VPS slow with low CPU usage but high steal?" - "Can I reduce steal time from inside my server?" - "How does CPU overcommit cause steal time?" - "Why does my load average rise when steal time is high?" --- ## What is the IOPS metric, and how does it affect performance? URL: https://vpsdime.com/knowledgebase/technical-questions/what-is-iops Last reviewed: 2026-07-02 Summary: IOPS measures operations per second where throughput measures bytes, why the two diverge (many small random operations vs few large sequential ones), why databases are IOPS-bound while file copies are throughput-bound, how latency ties them together, reading your Graphs' IOPS charts, and what NVMe changed. ### Definition **IOPS**, input/output operations per second, counts how many **individual read or write operations** a storage device completes each second, regardless of their size. It is one of the three numbers that jointly describe storage performance, and they measure different things: - **IOPS**: how many operations per second (the *count*). - **Throughput** (MB/s): how much data per second (the *volume*). - **Latency** (ms or µs): how long one operation takes (the *wait*). They're related, throughput ≈ IOPS × operation size, but they diverge hard in practice, and knowing which one your workload needs is the entire skill. ### Why the same disk gives wildly different numbers Copying one large file is **sequential** I/O: few, large operations. A busy database is **random** I/O: thousands of tiny reads and writes scattered across the disk. The same storage that streams hundreds of MB/s sequentially may deliver a small fraction of that volume under random load, not because it's slow, but because the *cost per operation* dominates when operations are small and scattered. This is why the two classic workload families feel storage so differently: - **Throughput-bound**: file copies, backups, video serving, streaming logs. They want MB/s; IOPS barely matters. - **IOPS-bound**: databases, mail servers, busy CMSes, anything doing many small reads/writes, [the workloads that feel "slow" while CPU and RAM sit idle](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps). They want operations per second and low latency; headline MB/s is nearly irrelevant to them. ### Latency: the third leg that explains the feel Every operation takes time, and for **synchronous** operations, a database committing a transaction, a filesystem journal write, the application *waits* for each one. At 1 ms per operation, a single thread caps at ~1,000 sequential operations per second no matter how much parallel capacity the device has. This is why storage *latency* shapes how fast a single query feels, while *IOPS capacity* shapes how many queries can run at once, and why high `%wa` (I/O wait) in [top](https://vpsdime.com/knowledgebase/technical-questions/process-management) with idle CPU is the signature of a storage-bound workload. ### What NVMe changed Spinning disks managed ~100-200 IOPS (a physical head had to move); SATA SSDs brought tens of thousands; **NVMe** (which [our plans run on](https://vpsdime.com/knowledgebase/presales/pre-sales-faq)) delivers hundreds of thousands with far lower latency. The practical consequence: on NVMe, storage stopped being the default bottleneck for typical workloads, when a modern VPS is slow, [the cause is usually elsewhere](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps), and an *actually* IOPS-bound service on NVMe usually indicates something amplifying its I/O (a missing index forcing full-table scans is the classic, [the slow-query section](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps) covers it). ### Reading your own numbers - Your VPS's [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) plot **Disk IOPS (read/write)** and **Disk Throughput** separately, high IOPS with modest MB/s = random/small-operation load (database-shaped); the reverse = bulk transfer. - Live, per-process: `iostat -x 2` (the `%util` and `await` columns: how busy, how long each operation waits) and `iotop` for the culprit process. - Benchmarking honestly requires matching the test to the question: **fio** can measure sequential throughput *or* random 4K IOPS, and the two results will differ by orders of magnitude on the same disk, a benchmark that doesn't state its operation size and randomness measures nothing in particular. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what the Graphs' IOPS and throughput charts show, and the workload behind them. ### Related questions - "What's the difference between IOPS and MB/s?" - "Why is my database slow when disk throughput looks fine?" - "What does high iowait mean?" - "What are good IOPS numbers on NVMe?" - "How do I see my VPS's IOPS usage?" --- ## How can I limit the CPU an application uses? URL: https://vpsdime.com/knowledgebase/technical-questions/limit-cpu-usage Last reviewed: 2026-07-02 Summary: Four ways to keep one process from eating every core, nice/renice for priority (the polite fix), systemd CPUQuota for hard per-service caps (the right one), cpulimit for one-off processes, and Docker's --cpus, with when each applies and why priority beats caps for batch work. ### What this is One process, a backup compressing, a video encode, an [overeager script](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps), pins the CPU and everything else suffers. Two different goals hide in "limit its CPU", and they want different tools: - **"It can use idle CPU, just never at others' expense"** → priority (`nice`). Usually what you actually want: the job still finishes as fast as conditions allow. - **"It must never exceed X% no matter what"** → a hard cap (`CPUQuota`, `cpulimit`, `--cpus`). Right for untrusted or misbehaving things; understand it leaves CPU idle on purpose. ### Priority: nice and renice (the polite fix) ``` nice -n 19 tar czf backup.tar.gz /var/www # start at lowest priority renice 19 -p 12345 # demote an already-running PID ``` A nice-19 process uses **all** the idle CPU but yields instantly when anything else wants a turn, the batch job barely slows down, and the site stops noticing it. For disk-heavy jobs, the I/O sibling: `ionice -c3 `. This should be the default posture of every scheduled heavy job you own. ### Hard caps: systemd CPUQuota (the right tool for services) For anything running as a service (or a [timer job](https://vpsdime.com/knowledgebase/technical-questions/systemd-timers)), cgroup-backed limits are precise and permanent, in the unit's `[Service]` section: ```ini CPUQuota=50% ``` (50% of one core; `200%` means two cores.) One-liner for an existing service, no file editing: ``` systemctl set-property myapp.service CPUQuota=50% ``` `MemoryMax=` lives in the same family, [it's the same mechanism the timers guide recommends for heavy backup jobs](https://vpsdime.com/knowledgebase/technical-questions/systemd-timers). ### cpulimit: a cap for a one-off process For a process that isn't a service and needs restraining *now*: ``` apt install cpulimit cpulimit -p 12345 -l 50 # hold PID 12345 at ~50% of one core ``` It works by rapidly pausing/resuming the process, crude but effective, and nothing to clean up afterwards. ### Docker: --cpus Containers get the cgroup treatment natively: `docker run --cpus="1.5" ...`, or in compose, `deploy.resources.limits.cpus: "1.5"`, [the same knob the container-sprawl section recommends](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps) so one stack can't starve the VPS. ### The honest footnote A cap protects neighbors *inside* your VPS; it doesn't create CPU. If the workload legitimately needs more than the plan has, caps just make it slower, [extra vCPU or a bigger plan](https://vpsdime.com/knowledgebase/client-area/services/extra-features) is the real fix, and if the CPU is being eaten by something you don't recognize, that's [a different article entirely](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the process you're capping, and whether you want priority (nice) or a hard cap. ### Related questions - "How do I stop a backup job from slowing my website?" - "How do I cap a service at 50% CPU?" - "What's the difference between nice and CPUQuota?" - "How do I limit CPU for a Docker container?" --- ## How can I find the biggest folders on my VPS? URL: https://vpsdime.com/knowledgebase/technical-questions/biggest-folders Last reviewed: 2026-07-02 Summary: The three ways to map disk usage, du sorted for the quick answer, ncdu for interactive exploration (the best tool), and the drill-down method that finds any space hog in under a minute, plus the deleted-but-held and inode cases that fool du entirely. ### What this is Mapping where the disk went. This is the tool half; if the disk is actually **full** and things are breaking, [the disk-full guide](https://vpsdime.com/knowledgebase/troubleshooting/disk-full) is the emergency version with the cleanup advice, this page is the measurement skill on its own. ### du, the built-in answer ``` du -xhd1 / | sort -h ``` Sizes of every top-level directory, sorted, biggest last. The flags earn their keep: `-x` stays on one filesystem, `-h` human units, `-d1` one level deep. Then **drill down**, re-run against the biggest entry (`du -xhd1 /var | sort -h`), and again, three or four hops finds any hog. Impatient variant: `du -xh / 2>/dev/null | sort -h | tail -30` dumps the 30 biggest directories at *any* depth in one go. ### ncdu, the tool worth installing ``` apt install ncdu ncdu -x / ``` The same data as an **interactive browser**: arrow into directories, sizes always sorted, `d` deletes (carefully), `q` quits. One scan, then you explore instantly instead of re-running du per level. For a Windows VPS the equivalent is [WinDirStat](https://vpsdime.com/knowledgebase/windows-vps/disk-full-windows). ### When the numbers don't add up Two classic cases where `df` says full but du can't find it: - **Deleted-but-open files**: a deleted log a running service still holds open keeps consuming space invisibly, `lsof +L1` lists them; restarting the holder releases the space ([the disk-full guide covers it](https://vpsdime.com/knowledgebase/troubleshooting/disk-full)). - **Out of inodes, not bytes**: millions of tiny files, du's *size* view won't show it, [`du --inodes` and its own guide](https://vpsdime.com/knowledgebase/troubleshooting/out-of-inodes). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the `du` or ncdu output for the directory in question. ### Related questions - "How do I see which folders use the most disk space?" - "How do I find the largest files on my VPS?" - "What's the ncdu command and why is it better than du?" - "df says the disk is full but du can't find the space, why?" --- ## Can I add swap memory on Linux VPS? URL: https://vpsdime.com/knowledgebase/technical-questions/swap-on-linux-vps Last reviewed: 2026-07-02 Summary: No, swap isn't supported on Linux VPS, and it isn't needed. Swap is an obsolete workaround from when RAM was expensive; your memory is fully dedicated, and at our pricing (a 6 GB plan for $7/month) buying real RAM costs what other providers charge for swap-thin plans. ### What this is Swap files and swap partitions aren't supported on our Linux VPS plans, `swapon` won't work. Here's why that's a feature, not a gap. ### Swap is a workaround from another era Swap exists to fake extra memory by parking overflow on disk, invented when RAM was scarce and expensive. Disk, even NVMe, is orders of magnitude slower than RAM, so a system leaning on swap doesn't get more capacity, it gets **slow**: applications stall, latency spikes, and the problem you actually have (not enough memory) gets hidden instead of fixed. Your Linux VPS comes with **fully dedicated memory**, all of it real RAM, all of it yours. When that's the case, swap adds nothing but a slow failure mode. ### The economics have flipped The honest fix for needing more memory is having more memory, and that's exactly the thing we price aggressively: our **6 GB plan is $7/month** ($7 ÷ 6 GB ≈ **$1.17 per GB**), which is roughly what many providers charge for a **single gigabyte**. At that price, upgrading to real RAM costs about what limping along on swap would cost elsewhere. ### If you're hitting memory limits 1. Check whether you actually are: see [My VPS is using too much memory](https://vpsdime.com/knowledgebase/troubleshooting/vps-using-too-much-memory), Linux's cache makes healthy systems look full. 2. Find the consumer: `ps aux --sort=-%mem | head`. A mistuned database buffer or a leaking app fixes for free. 3. Genuinely outgrown the plan? [Upgrade](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade), on Linux VPS it's live and instant, no downtime, no reboot, same IP. (On **Premium VPS**, full KVM means the OS is entirely yours, swap included, if you insist. We'd still suggest sizing RAM properly instead.) ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the `free -h` output and what's eating the memory (`ps aux --sort=-%mem | head`). ### Related questions - "Can I create a swap file on my VPS?" - "Why does swapon fail on Linux VPS?" - "Do I need swap on a VPS?" - "What do I do instead of adding swap?" --- ## Disk quotas on your VPS URL: https://vpsdime.com/knowledgebase/technical-questions/disk-quotas Last reviewed: 2026-07-02 Summary: Disk quotas work on Linux VPS, install the quota tools and set per-user or per-group limits as on any Linux server. Typical uses, multi-user servers and hosting-panel setups. ### What this is **Disk quotas are supported on Linux VPS**, per-user and per-group limits work as on any Linux server. If you're setting up a multi-user box or a hosting-panel environment that expects quotas, go ahead. ### Setting them up The standard flow applies: 1. Install the tools: `apt install quota` (Debian/Ubuntu) or `dnf install quota` (RHEL-family). 2. Enable quota mount options for the filesystem, initialize with `quotacheck`, then turn on with `quotaon` (your distro's quota guide has the exact steps for its filesystem layout). 3. Set limits with `edquota -u username`, and review usage with `repquota -a`. On **Premium VPS** (full KVM, your own kernel and filesystems), quotas are similarly all yours, including journaled quota options. ### If a panel says quotas aren't working Panels like cPanel or DirectAdmin check for quota support during install. Make sure the quota packages are installed and initialized (steps above) before the panel's own quota setup step, and re-run the panel's quota fix tool afterwards (`/scripts/fixquotas` on cPanel). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which quota step fails (packages, quotacheck, a panel's check), with the output. ### Related questions - "Do disk quotas work on your Linux VPS?" - "How do I set per-user disk limits on my VPS?" - "My panel says quotas aren't enabled, what do I do?" --- ## How do I set my IP or IPv6 address on my VPS? URL: https://vpsdime.com/knowledgebase/technical-questions/set-ip-address Last reviewed: 2026-07-04 Summary: You don't need to, networking arrives fully configured on every VPS, IPv4 and IPv6, with addresses, gateway, netmask, routes, and DNS applied automatically. Where to see your values (Network tab, or ip addr inside the VPS), and the one-click Auto-fix network button in My VPS is Down that repairs the configuration if a manual change broke your connectivity. ### What this is You're looking for where to enter your IP address, gateway, and netmask, or how to configure IPv6. The short answer: **you don't need to**. Every VPS is delivered with its networking fully configured, IPv4 and IPv6 addresses, gateway, netmask, routes, and DNS are all applied automatically when the VPS is deployed, and the platform keeps them correct through reinstalls and migrations. There is no setup step you're missing. If the VPS is running, its network is configured. ### Where to see your values You may still want the numbers, to verify something, to configure an additional IP, or for your own records: - **Client area:** the [Network tab](https://vpsdime.com/knowledgebase/client-area/services/network) on your VPS's manage page lists every IPv4 and IPv6 address with its **netmask and gateway**, and is also where reverse DNS is set and extra IPs are requested. - **Inside the VPS:** `ip addr` shows the addresses, `ip route` shows the gateway, `cat /etc/resolv.conf` shows DNS. ### If you changed the config by hand and lost the VPS Editing the network configuration manually (netplan, `/etc/network/interfaces`, NetworkManager, or direct `ip` commands) is one of the most common self-inflicted outages we see: one wrong octet or a removed route, and the VPS drops off the network, taking your SSH session with it. The recovery is one click, and it works precisely because it doesn't need your VPS to be reachable: 1. Open **[My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter)** (https://vpsdime.com/myvpsisdown) and select the VPS. 2. Let the diagnostics run, then click **Auto-fix network**. 3. The platform rewrites the VPS's network configuration from our records, **IPs, routes, and DNS**, give it about 30 seconds, then connect again. That button is also the answer if you're restoring an old backup whose network config no longer matches, or if a configuration tool inside the VPS mangled things. On **Premium VPS and Windows VPS**, use the **[Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps)** to revert your change instead. ### If you're configuring something on purpose Legitimate reasons to touch network config exist, bringing up an **additional IP** you've ordered, or an advanced routing setup. The values you need are on the [Network tab](https://vpsdime.com/knowledgebase/client-area/services/network), exactly as listed (address, netmask, gateway). Make the change survivable: keep a Console session open while you apply it, and know the Auto-fix button above resets the standard configuration if it goes sideways, without touching your data. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what you changed (or which file) before connectivity was lost, - whether Auto-fix network brought it back. ### Related questions - "How do I set a static IP on my VPS?" - "What are my gateway and netmask?" - "How do I configure my IPv6 address?" - "I edited my network config and now I can't connect." - "Does my VPS use DHCP?" - "Where do I find my IP settings?" --- ## Running your own VPN on your VPS (WireGuard) URL: https://vpsdime.com/knowledgebase/technical-questions/wireguard-vpn Last reviewed: 2026-07-02 Summary: A personal VPN on your VPS is allowed and one of the best uses of a small plan, what it does and honestly doesn't do (it's privacy from the local network, not anonymity), the ten-minute setup with the wireguard-install script, adding phones by QR code, DNS leak checking, the traffic-counts-twice math, and the OpenVPN fallback for networks that block UDP. ### What this is Your own VPN server: your devices connect to your VPS and route their internet traffic through it, encrypted from the device to the datacenter. A **personal VPN for your own use is [explicitly allowed](https://vpsdime.com/knowledgebase/acceptable-use/whats-allowed)** and is one of the most popular uses of a small plan ([the required TUN/TAP support is already enabled](https://vpsdime.com/knowledgebase/technical-questions/enable-tun-tap)). The line to respect: *personal*, running a VPN or proxy service for other people is not allowed. What it gives you, honestly stated: - **Privacy from the network you're on**: hotel Wi-Fi, airports, ISPs that snoop or throttle, they see only encrypted traffic to your VPS. - **A stable, known exit IP**: useful for IP-allowlisted services ([your own servers included](https://vpsdime.com/knowledgebase/technical-questions/private-networking-between-vpses)) and for a consistent location while traveling. - **Not anonymity.** The VPS's IP is yours, on your account; a self-hosted VPN moves trust from the coffee-shop network to your own server, it doesn't make you anonymous, and commercial "no-logs" theater isn't the product here. ### The ten-minute setup The community-standard [wireguard-install script](https://github.com/Nyr/wireguard-install) (by Nyr) handles server setup, keys, forwarding, and client management: ``` wget https://git.io/wireguard -O wireguard-install.sh bash wireguard-install.sh ``` Accept the defaults (UDP **51820**), name your first client, and it prints a **QR code**, open the WireGuard app on your phone ([iOS](https://apps.apple.com/app/wireguard/id1441195209)/[Android](https://play.google.com/store/apps/details?id=com.wireguard.android)), "Create from QR code", scan, toggle on. Done. For laptops, the script writes a `.conf` file, import it into the [WireGuard client](https://www.wireguard.com/install/) (or `wg-quick up` on Linux). Re-run the script any time to **add a client per device** (one profile per phone/laptop, so a lost device is revoked by deleting *its* client, same logic as [SSH keys](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys)), or to remove one. Two housekeeping notes: if you run your own [firewall](https://vpsdime.com/knowledgebase/troubleshooting/allow-ssh-in-common-firewalls), allow `51820/udp` (the script handles its own rules on a default setup; our [edge firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall) doesn't block VPN ports). And prefer the script's defaults unless you know why not, it configures DNS through the tunnel correctly, which hand-rolled setups often miss. ### Verify it, including DNS With the VPN on, check two things from the connected device: 1. **Your visible IP** is the VPS's, any "what is my IP" site. 2. **DNS isn't leaking**: [dnsleaktest.com](https://dnsleaktest.com/) (or [browserleaks.com/dns](https://browserleaks.com/dns)) should show resolvers consistent with your tunnel, not your home ISP's. A leak means DNS queries escape the tunnel, the privacy hole people don't notice; the script's default config avoids it, custom configs should set `DNS =` in the client profile. ### The traffic math Routed VPN traffic crosses your VPS **twice**, in from your device, out to the destination, so a gigabyte browsed is roughly two gigabytes against [your monthly allowance](https://vpsdime.com/knowledgebase/acceptable-use/bandwidth-overage). Generous plans make this a non-issue for normal browsing; heavy streaming through the tunnel is where the math starts to matter, watch the [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) the first month. ### When WireGuard won't connect: the OpenVPN fallback Some restrictive networks (corporate guest Wi-Fi, certain hotel setups) block unfamiliar UDP entirely, and WireGuard is UDP-only. The classic workaround is a parallel **OpenVPN** setup via the sibling [openvpn-install script](https://github.com/Nyr/openvpn-install), configured on **TCP port 443**, indistinguishable from HTTPS to most middleboxes, slower than WireGuard, but it connects where nothing else will. Run both; use WireGuard by default and the 443 fallback when a network fights you. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the client device, - where it fails (importing the profile, the handshake, or no internet through the tunnel). ### Related questions - "Can I run a VPN on my VPS, and is it allowed?" - "How do I set up WireGuard on my VPS?" - "How do I add my phone to my VPN (QR code)?" - "Does a self-hosted VPN make me anonymous?" - "How much bandwidth does a VPN use (does traffic count twice)?" - "What if a network blocks my WireGuard connection?" --- ## Private networking between your VPSes (Tailscale or WireGuard) URL: https://vpsdime.com/knowledgebase/technical-questions/private-networking-between-vpses Last reviewed: 2026-07-05 Summary: We don't provide built-in VLANs, and the recommended pattern is better anyway: an encrypted overlay network between your servers. Tailscale as the ten-minute path (with your laptop joining too), plain WireGuard as the self-hosted path, Headscale in between, and how binding services to the overlay replaces public exposure entirely. Plus the MagicDNS gotcha: Tailscale pointing resolv.conf at 100.100.100.100 can break a server's DNS, fixed with --accept-dns=false or disabling MagicDNS. ### What this is You have two or more servers, a web VPS and a database VPS, an app and its workers, and they need to talk **privately**. We don't provide built-in private VLANs; the pattern we recommend instead is an **encrypted overlay network**, and it's genuinely the better tool: it's encrypted end to end, it works **across our locations** (and to servers elsewhere, and to your laptop), and services bound to it are [never exposed to the public internet at all](https://vpsdime.com/knowledgebase/getting-started/securing-public-services). One clarification worth making: our [edge firewall already trusts traffic between your own VPSes](https://vpsdime.com/knowledgebase/client-area/services/firewall) (no whitelisting needed for the blocked app ports), but that's a *firewall* convenience, the traffic still crosses the network unencrypted, on public IPs. The overlay adds what that can't: **encryption, plus stable private IPs** that survive [migrations](https://vpsdime.com/knowledgebase/getting-started/migrating-a-vps) and IP changes. ### Option A: Tailscale, the ten-minute path [Tailscale](https://tailscale.com/) builds a WireGuard mesh for you, key exchange, NAT traversal, and IP management handled. On **each** server: ``` curl -fsSL https://tailscale.com/install.sh | sh tailscale up ``` Authenticate each with the same account (the free tier comfortably covers a personal fleet), and every machine gets a stable **100.x.y.z** address plus a DNS name (MagicDNS), reachable from every other machine on your tailnet, and nothing else. The quiet superpower: **install it on your laptop too**, and you can reach every server's private services from anywhere, without a single public port, [databases, panels](https://vpsdime.com/knowledgebase/getting-started/securing-public-services), all of it. The trade-off to name honestly: Tailscale's coordination server is a third party (the traffic itself is end-to-end WireGuard; they broker keys and connections). If that's a dealbreaker, **[Headscale](https://headscale.net/)** is the open-source, self-hostable control plane the Tailscale clients can use instead, or go one layer down: ### Option B: plain WireGuard, the self-hosted path For a small, static set of servers, [WireGuard](https://www.wireguard.com/) by hand is simple enough to be worth owning, no third party, nothing to trust but your own configs. Two servers: ``` apt install wireguard wg genkey | tee /etc/wireguard/private.key | wg pubkey > /etc/wireguard/public.key ``` `/etc/wireguard/wg0.conf` on server A (`10.10.0.1`): ```ini [Interface] Address = 10.10.0.1/24 PrivateKey = ListenPort = 51820 [Peer] PublicKey = AllowedIPs = 10.10.0.2/32 ``` Server B mirrors it (`Address = 10.10.0.2/24`, peer = A's public key, plus `Endpoint = A.PUBLIC.IP:51820` and `PersistentKeepalive = 25`). Then on both: ``` systemctl enable --now wg-quick@wg0 ``` Allow **UDP 51820** in the listening server's own firewall, and `ping 10.10.0.1` from B proves the tunnel. Each extra server is another `[Peer]` block, which is also the honest scaling limit: past a handful of nodes, the config bookkeeping is exactly what Tailscale exists to remove. ### Using the overlay (the actual point) Once every server has its private address, **bind internal services to it instead of to public IPs**: - MySQL for the app server only: `bind-address = 10.10.0.1` (or the Tailscale IP), the port simply doesn't exist publicly, no [whitelist](https://vpsdime.com/knowledgebase/client-area/services/firewall) needed. - [NFS](https://vpsdime.com/knowledgebase/technical-questions/enable-nfs), Redis, RabbitMQ, [Docker Swarm](https://vpsdime.com/knowledgebase/technical-questions/docker-swarm) overlay traffic, everything trusted-network-shaped now has a trusted network. - Latency between your servers is [the path's latency](https://vpsdime.com/knowledgebase/troubleshooting/network-problems) plus a negligible encryption cost, same-location VPSes feel LAN-like. ### Troubleshooting: DNS problems after enabling Tailscale (MagicDNS) With **MagicDNS** enabled on the tailnet (it's on by default), Tailscale takes over the server's DNS: `/etc/resolv.conf` is rewritten to point at **100.100.100.100**, Tailscale's own resolver, which answers tailnet names and forwards everything else upstream. That's what MagicDNS is; finding that address in your `resolv.conf` is the sign it's active. On a server, this handover can break normal name resolution. A real case from support: a customer running **sshfs over Tailscale** saw intermittent login and resolution failures, and the cause turned out to be MagicDNS having taken over the server's DNS. Disabling it fixed the problem. A VPS doesn't need Tailscale managing its DNS, it has a working resolver of its own, and other machines can still reach the server by its Tailscale IP. So if resolution misbehaves and `resolv.conf` shows `100.100.100.100`: - **Tell Tailscale to leave DNS alone on that server:** `tailscale up --accept-dns=false`. The machine stays on the tailnet; its resolver config stays its own. - **Or disable MagicDNS for the whole tailnet** in the Tailscale admin console, under the **DNS** tab. - If `resolv.conf` was left pointing at `100.100.100.100` with resolution dead, put a real nameserver back (for example `nameserver 1.1.1.1`) to recover immediately, then apply one of the two fixes above so it doesn't come back. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the servers involved (hostnames or IPs), - Tailscale or plain WireGuard, - where the tunnel fails (handshake, ping, or binding a service to it). ### Related questions - "How do I connect two VPSes privately?" - "Do you offer private networking or VLANs?" - "Tailscale or plain WireGuard for connecting my servers?" - "How do I make my database reachable only by my other VPS?" - "Can my laptop join the same private network as my servers?" - "Why did DNS stop working on my VPS after enabling Tailscale?" - "What is 100.100.100.100 in my resolv.conf?" - "How do I stop Tailscale from changing my DNS settings?" --- ## How can I enable TUN/TAP? URL: https://vpsdime.com/knowledgebase/technical-questions/enable-tun-tap Last reviewed: 2026-07-02 Summary: TUN/TAP is enabled by default on Linux VPS, nothing to modprobe or request. Verify with /dev/net/tun, then run your personal VPN, WireGuard or OpenVPN (the Nyr install script makes OpenVPN a one-liner). Personal VPNs are allowed; public VPN services are not. ### What this is Nothing to enable: **TUN/TAP is available by default** on Linux VPS. You don't need to `modprobe tun` (and don't be alarmed if a guide's modprobe step errors, the functionality is already there). Verify any time: ``` ls -l /dev/net/tun ``` If that device node exists, and it does, VPN software has what it needs. On **Premium VPS** you run your own kernel, so modules are entirely yours to manage (`modprobe tun` as usual). ### Running a VPN on your VPS A **personal VPN for your own use is allowed** and is one of the most popular uses of a small VPS ([public VPN services for other people are not](https://vpsdime.com/knowledgebase/acceptable-use/whats-allowed)). Two good routes: - **WireGuard**, modern, fast, simple, the full setup (script, phone QR codes, DNS leak checks, the OpenVPN fallback) is in [Running your own VPN on your VPS](https://vpsdime.com/knowledgebase/technical-questions/wireguard-vpn). - **OpenVPN**, the battle-tested classic. Nyr's [openvpn-install](https://github.com/Nyr/openvpn-install) script remains the easiest way: run it, answer the prompts, import the generated `.ovpn` file on your devices. And for connecting your **servers to each other** (rather than your devices to the internet), the overlay pattern is [its own guide](https://vpsdime.com/knowledgebase/technical-questions/private-networking-between-vpses). If you run your own [firewall](https://vpsdime.com/knowledgebase/troubleshooting/allow-ssh-in-common-firewalls) inside the VPS, allow your VPN's port (WireGuard defaults to UDP 51820, OpenVPN to UDP 1194). Our [managed firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall) doesn't block VPN ports. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the VPN software you're setting up and its exact error. ### Related questions - "How do I enable TUN/TAP on my VPS?" - "Can I run OpenVPN or WireGuard on my VPS?" - "Is /dev/net/tun available?" - "Are personal VPNs allowed?" --- ## How can I enable FUSE? URL: https://vpsdime.com/knowledgebase/technical-questions/enable-fuse Last reviewed: 2026-07-02 Summary: FUSE is enabled by default on Linux VPS, nothing to modprobe. Verify /dev/fuse exists, then use sshfs, rclone mount, and other FUSE filesystems normally. On Premium VPS you manage modules yourself. ### What this is Nothing to enable: **FUSE is available by default** on Linux VPS. Skip any guide step that says to `modprobe fuse` (if you run it and it errors, that's fine, the functionality is already present). Verify: ``` ls -l /dev/fuse ``` On **Premium VPS**, the kernel is your own, so load modules yourself as usual (`modprobe fuse`). ### What people use it for FUSE lets ordinary programs provide filesystems, which unlocks some genuinely useful tools on a VPS: - **sshfs**, mount another server's directory over SSH: `sshfs user@otherhost:/data /mnt/data`. Handy for shuffling data between servers without setting anything up on the far side. - **rclone mount**, mount cloud storage (S3, B2, Google Drive, and dozens more) as a local directory, a nice companion to a [backup setup](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps). - Various userspace filesystems (encfs/gocryptfs, archivemount, and friends) work the same way. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the tool that needs FUSE (sshfs, rclone) and its exact error. ### Related questions - "How do I enable FUSE on my VPS?" - "Does sshfs work on your Linux VPS?" - "Can I use rclone mount on my VPS?" - "Why does modprobe fuse error but sshfs still works?" --- ## How can I enable NFS? URL: https://vpsdime.com/knowledgebase/technical-questions/enable-nfs Last reviewed: 2026-07-02 Summary: NFS works on Linux VPS with nothing to enable and no ticket needed, install the standard packages to mount NFS shares or run a server. Keep exports private, NFS has no business being open to the internet. ### What this is Nothing to enable and nothing to request: **NFS works on Linux VPS out of the box**. (Older versions of this article said to open a ticket, that's no longer necessary.) ### Using it - **Mount a share (client):** install the client tools (`apt install nfs-common` on Debian/Ubuntu, `dnf install nfs-utils` on RHEL-family), then `mount -t nfs otherhost:/export /mnt/share`. - **Serve a share (server):** `apt install nfs-kernel-server`, define exports in `/etc/exports`, and `exportfs -ra`. ### Keep it private NFS's security model assumes a trusted network, so **never export to the whole internet**. Restrict exports to specific IPs in `/etc/exports`, firewall the NFS ports to just the machines that mount from you, and prefer tunneling over an encrypted overlay when crossing networks, [the private networking guide](https://vpsdime.com/knowledgebase/technical-questions/private-networking-between-vpses) sets one up in ten minutes. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - whether you're mounting or serving, and the exact mount or export error. ### Related questions - "How do I enable NFS on my VPS?" - "Do I still need to open a ticket for NFS?" - "Can I mount an NFS share on my VPS?" - "Can my VPS act as an NFS server?" --- ## How our SSH brute-force firewall works URL: https://vpsdime.com/knowledgebase/technical-questions/ssh-bruteforce-firewall Last reviewed: 2026-07-02 Summary: Every Linux VPS sits behind a network-level firewall, built in-house at VPSDime, that watches port 22 for failed password logins and blocks offending IPs network-wide, and because it counts an attacker's failures across many VPSes rather than one, it catches sweeps that a single-server fail2ban never could. What trips it, what makes you immune, how it relates to the other two firewalls, and why the detection specifics stay undisclosed. ### What this is Every **Linux VPS** on our network is protected, automatically, with nothing to install or configure, by a firewall at the network level that watches **port 22** for **failed password logins** and temporarily blocks the IPs behind them. It's **built in-house at VPSDime**, not fail2ban, not an off-the-shelf appliance, but our own system, designed specifically for the way our network runs and operated by the same team that runs it. If you've ever managed a bare Linux server elsewhere and watched the auth log fill with thousands of guesses a day, this is the system that makes that noise mostly not reach you here. (This is the "how it works" article. If you're here because **your own IP got blocked**, the unblock and whitelist mechanics are on [the SSH firewall page](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall), the short version is that [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) detects and whitelists your IP automatically.) ### Why it beats a fail2ban on a single server fail2ban and its cousins are good tools, but they share one structural limit: they can only see **one server's logs**. An attacker sweeping a network makes three attempts against your VPS, three against your neighbor's, three against a thousand others, and stays under every individual server's threshold while making thousands of guesses in total. Our firewall inverts that: it counts a source IP's failed attempts **across many VPSes at once**, so the sweep pattern that's invisible to any single machine is obvious at the network level, and the block that follows applies **network-wide**, one detection protects every customer simultaneously. Two practical consequences: - **A VPS with nothing installed is already defended.** A fresh deploy with a password and no hardening yet benefits from every detection the whole network has ever made. - **Attackers get less out of the network than out of any single server.** Miles better math, for them, in the wrong direction. ### What trips it, and what makes you immune The counter watches **failed password authentication** on port 22. So: - **Correct logins never count**, using your VPS normally is invisible to it. - **Key-based authentication can't trip it**, there's no password to fail, which is one more reason [key-only login](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys) is the recommended state: it makes you *immune by construction*, both to attackers and to accidentally banning yourself. - **Your own typos count like anyone's.** Retrying a misremembered password, or a script (rsync, CI, anything using `sshpass`) looping on a stale one, is the most common way customers meet the system, [the page-demo covers getting unbanned and whitelisting your IPs](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall) (up to 10, applied network-wide). On the detection side, there are **multiple mechanisms in place** beyond simple counting, and we keep the specifics, thresholds, windows, escalation, deliberately undisclosed: publishing the exact rules would hand attackers the recipe for staying under them. What we'll say is that blocks are **temporary**, scale with behavior, and whitelisted IPs are never touched. ### The three firewalls, untangled Your Linux VPS is behind three distinct protective layers with easily confused names: | Layer | Watches | Configured by | Where | |---|---|---|---| | **SSH brute-force firewall** (this article) | Failed password logins on port 22 | Nobody, it's automatic (whitelist via [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall)) | Network level | | **[Managed network firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall)** | High-risk app ports (databases, caches, Docker API) | You, per-app whitelists on the Firewall tab | Network edge | | **Your own OS firewall** (ufw etc.) | Whatever you configure | You, [inside the VPS](https://vpsdime.com/knowledgebase/getting-started/first-30-minutes) | The VPS itself | They stack: a defense-in-depth setup uses all three. ### Do you still need fail2ban? Not for password attacks on SSH's default port, that's covered better than a local tool could. It remains sensible for **other exposed login surfaces** (mail, panels, WordPress) and for SSH **if you [move it off port 22](https://vpsdime.com/knowledgebase/technical-questions/change-ssh-port)**, since the network firewall watches 22 specifically, moving ports trades this protection for obscurity, another reason keys matter more than port games. ### Scope, and the edges of it - It protects **Linux VPS, port 22**. Premium and Windows VPS aren't behind it (Windows [has RDP to defend instead](https://vpsdime.com/knowledgebase/windows-vps/protecting-rdp); on Premium, bring keys and your own tooling). - There is **no opt-out**, and in practice nobody needs one: correct logins are unaffected, keys make you immune, and whitelisting covers fixed IPs and automation. The system's whole value is that it covers everyone. - Our own infrastructure isn't relying on it either, that's protected separately, with IP restrictions and keys in multiple layers. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP and the IP you connect from, - whether it's about a current block or how the system works. ### Related questions - "Do I need fail2ban on my VPS?" - "How does your SSH brute-force protection work?" - "Why is a network-level ban better than fail2ban?" - "Does key-based login protect me from the SSH firewall?" - "Can I opt out of the SSH firewall?" - "What's the difference between your firewalls?" --- ## Two-factor authentication for SSH (TOTP on Ubuntu/Debian) URL: https://vpsdime.com/knowledgebase/technical-questions/ssh-2fa-totp Last reviewed: 2026-07-02 Summary: Add authenticator-app codes to SSH logins with libpam-google-authenticator, when it's genuinely worth it (keeping password auth, or belt-and-braces over keys), the full setup (PAM line, KbdInteractiveAuthentication, AuthenticationMethods policies), the anti-lockout discipline with the Console as the safety net, and the clock-skew and scratch-code operational notes. ### What this is Requiring a **six-digit authenticator code** at SSH login, the same TOTP apps (Google Authenticator, Authy, 1Password) you use for [your account's 2FA](https://vpsdime.com/knowledgebase/client-area/account/two-factor-overview), enforced by the server through `libpam-google-authenticator`. First, the honest positioning, because this upgrade is often oversold: - **If you still allow password logins**, TOTP is a genuinely big upgrade: a leaked or guessed password stops being enough. (Though the bigger upgrade remains [switching to keys](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys), and our [network already blunts password brute-force](https://vpsdime.com/knowledgebase/technical-questions/ssh-bruteforce-firewall).) - **If you're already key-only**, a passphrase-protected key is effectively two factors (the key file + the passphrase), so TOTP adds a third, mostly protecting against a *stolen, unlocked* key. Worth it for high-stakes boxes and compliance checklists; optional for a hobby server. The strong combination this guide builds: **key + code** (`publickey,keyboard-interactive`), something you have, something you know, something that rotates. ### Setup Everything below on Ubuntu/Debian; same module on RHEL-family via the `google-authenticator` package (EPEL). **1. Install the PAM module:** ``` apt install libpam-google-authenticator ``` **2. Enroll the login user.** As the user who logs in over SSH (not necessarily root), run: ``` google-authenticator ``` Answer **y** to time-based tokens, scan the QR with your authenticator app, and **save the emergency scratch codes somewhere safe off the server**, they are your login of last resort if the phone is gone. The sensible defaults for the remaining prompts: update the file (y), disallow token reuse (y), and enable rate limiting (y). **3. Tell PAM to require the code.** Add to the top section of `/etc/pam.d/sshd`: ``` auth required pam_google_authenticator.so ``` (For a gradual rollout, `auth required pam_google_authenticator.so nullok` lets users who haven't enrolled yet log in without a code, remove `nullok` once everyone's enrolled.) **4. Tell SSH to ask.** In `/etc/ssh/sshd_config`: ``` KbdInteractiveAuthentication yes ``` (older configs call it `ChallengeResponseAuthentication`), and set the **policy** with `AuthenticationMethods`: - Key **plus** code (recommended): `AuthenticationMethods publickey,keyboard-interactive` - Password **plus** code: `AuthenticationMethods password,keyboard-interactive` (make sure `PasswordAuthentication yes` in this case) **5. Restart and test, without closing your session:** ``` systemctl restart ssh ``` Then, **from a second terminal**, log in fresh: key (or password) first, then `Verification code:` prompts for the app's six digits. ### The anti-lockout discipline PAM misconfiguration is the classic way to lock yourself out of SSH entirely, so the rules from every [firewall](https://vpsdime.com/knowledgebase/troubleshooting/allow-ssh-in-common-firewalls) and [key](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys) guide apply doubly: **keep your working session open until a second terminal proves the new flow**, keep the scratch codes off-server, and know the safety net, the **[Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps)** in your client area doesn't authenticate through SSH or PAM's sshd stack, so even a fully botched config is a fix-it-from-the-console incident, not a rebuild. ### Operational notes - **TOTP lives and dies by the clock.** Codes are time-based; if the server's clock drifts, valid codes get rejected. Verify `timedatectl` shows `System clock synchronized: yes` (systemd-timesyncd handles it by default), before blaming the app. - **Each user enrolls separately** (`google-authenticator` run as that user; the secret lives in their `~/.google_authenticator`). Automation and deploy accounts are usually better served by [keys without TOTP](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys), scope `AuthenticationMethods` per-user with a `Match User` block if you mix. - **Know what it protects**: SSH logins, that's all. Your web apps, panels, and [everything else exposed](https://vpsdime.com/knowledgebase/getting-started/securing-public-services) have their own login doors. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - where the flow fails (PAM, sshd config, a rejected code), with the exact prompt or error, - whether the Console still gets you in. ### Related questions - "How do I add two-factor authentication to SSH?" - "How do I set up google-authenticator on Ubuntu?" - "Should I use SSH keys, TOTP, or both?" - "Why are my SSH verification codes rejected (clock skew)?" - "What happens if I lose my phone (scratch codes)?" - "Can some users skip the code requirement (nullok, Match User)?" --- ## How can I change my SSH port? URL: https://vpsdime.com/knowledgebase/technical-questions/change-ssh-port Last reviewed: 2026-07-05 Summary: How to move SSH off port 22 safely on current distributions. Where the port is actually set (sshd_config everywhere, plus the ssh.socket systemd unit on Ubuntu 22.10 and later, where socket activation can ignore sshd_config entirely), the firewall rule to add before you restart (ufw, firewalld, nftables examples), registering the port with SELinux on Alma/Rocky, confirming with sshd -T and ss, and testing in a second terminal so you can't lock yourself out. ### What this is Moving SSH off the default port 22. It cuts the automated brute-force noise in your logs to near zero, and as a bonus, our network's [port-22 SSH firewall](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall) no longer applies to you, so a mistyped password can never get your IP banned. (To be clear about what it is not: it's obscurity, not security. Keep using [keys and the rest of the hardening basics](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps), this just quiets the door-rattling.) One thing has genuinely changed in recent years, and most guides haven't caught up: **on newer Ubuntu releases, the port is not always controlled by `sshd_config`**. This page covers both mechanisms, and the order below is arranged so that no step can lock you out. ### Where the port is actually set There are two mechanisms in the wild: - **The classic one: `sshd_config`.** The SSH daemon listens where the `Port` line says. This is how it works on **Debian**, **AlmaLinux and Rocky**, **Ubuntu up to 22.04**, and most everything else. - **systemd socket activation: `ssh.socket`.** Starting with **Ubuntu 22.10**, sshd is started on demand by systemd, and **systemd owns the listening port**, not sshd. On **Ubuntu 22.10 through 23.10**, the `Port` line in `sshd_config` is **ignored outright**: you can edit it, restart, see no errors, and SSH keeps listening on 22. From **Ubuntu 24.04**, socket activation remains, but Ubuntu added a generator that reads the port *from* `sshd_config` and applies it to the socket at `daemon-reload`, so the classic edit works again as long as you reload. Check which world you're in: ``` systemctl is-active ssh.socket ``` `active` means socket activation; `inactive` or "could not be found" means classic sshd. **If you're unsure, or the output surprises you, simply do both edits below.** Setting `Port` in `sshd_config` is harmless on a socket-activated system, and the socket drop-in is harmless on a classic one, the two settings don't conflict, and one of them will be the one that counts. ### The steps, in an order that can't lock you out Throughout, 2222 is the example, pick any free port you'll remember, and stay clear of ports used by your own services. #### 1. Allow the new port in your firewall, first If you run a firewall that currently allows SSH on 22, it knows nothing about your new port, and restarting SSH before the rule exists is the classic self-lockout. Add the allow rule **before touching SSH**: ``` # ufw (Ubuntu/Debian) ufw allow 2222/tcp # firewalld (Alma/Rocky) firewall-cmd --permanent --add-port=2222/tcp && firewall-cmd --reload # raw nftables nft add rule inet filter input tcp dport 2222 accept ``` More variants (iptables, and finding out which firewall you're even running) are in [allowing SSH in common firewalls](https://vpsdime.com/knowledgebase/troubleshooting/allow-ssh-in-common-firewalls). Our [managed edge firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall) doesn't block custom ports, so there's nothing to change on our side. Leave the port-22 rule in place for now, remove it only after the new port is proven (last step). #### 2. Set the port in `sshd_config` Do this on **every** system, it's the source of truth everywhere except Ubuntu 22.10-23.10, and harmless there: ``` nano /etc/ssh/sshd_config ``` Find the `#Port 22` line, uncomment it, set your port: ``` Port 2222 ``` #### 3. Ubuntu with `ssh.socket`: set the socket too If the `systemctl is-active ssh.socket` check above said `active` (any Ubuntu from 22.10 on), give the socket the same port via a drop-in: ``` systemctl edit ssh.socket ``` In the editor, add: ``` [Socket] ListenStream= ListenStream=2222 ``` The empty `ListenStream=` line first is deliberate: it clears the inherited port 22, then the second line sets yours. Save and exit. On **Ubuntu 24.04 and later** this drop-in is technically optional (the generator picks the port up from `sshd_config`), but it does no harm, and doing both is the version-proof move. #### 4. Alma/Rocky: tell SELinux about the port On the RHEL family, SELinux only permits sshd to bind to registered SSH ports, and a new port isn't one until you say so, skip this and sshd fails to start with a permission error in its log: ``` dnf install policycoreutils-python-utils # if semanage is missing semanage port -a -t ssh_port_t -p tcp 2222 ``` Debian and Ubuntu don't need this step. #### 5. Validate, then apply First, check your edit the way `nginx -t` checks a web server config: ``` sshd -t ``` Silence means the config parses; an error names the line to fix, **before** anything restarts. Then apply: ``` systemctl daemon-reload systemctl restart ssh # Debian/Ubuntu systemctl restart sshd # Alma/Rocky ``` The `daemon-reload` is what makes systemd re-read the socket drop-in, and on Ubuntu 24.04+ it's the moment the generator syncs the port from `sshd_config`. On classic systems it's a no-op, so it belongs in the sequence unconditionally. #### 6. Confirm before you trust it Two checks, and they answer different questions: ``` sshd -T | grep -i '^port' ``` `sshd -T` prints the **effective configuration** after parsing `sshd_config` (and it refuses to run if the config has a syntax error, which makes it a free config test). It should print `port 2222`. ``` ss -tlnp | grep ssh ``` This is the ground truth: **what is actually listening right now**. You want to see your new port here. On a socket-activated Ubuntu the listener may show as `systemd` rather than `sshd`, that's normal, it's the socket holding the port. If `sshd -T` says 2222 but `ss` still shows only 22, you're in the socket-activation case and step 3 is the part that's missing. #### 7. Test from a second terminal, then clean up **Keep your current session open.** From a new terminal: ``` ssh -p 2222 root@YOUR.VPS.IP ``` Only after the new port logs you in: close the old session, and if you want, remove the old firewall allowance (`ufw delete allow 22/tcp`, or the firewalld/nftables equivalent). From here on, every SSH and [SFTP](https://vpsdime.com/knowledgebase/getting-started/uploading-files-sftp) client needs the port set (`-p 2222`, or the Port field in FileZilla/WinSCP). ### Why changing your IP won't stop the scans A request we sometimes get instead: "give me a new IP, mine is being scanned." A new IP won't change anything, because the scanning isn't about your IP. Every public IPv4 address is **public knowledge**, the entire address space is only 4 billion addresses, and modern scanners sweep all of it in under an hour, around the clock. Any address, brand new or decades old, starts receiving SSH probes within minutes of going online. Security folks call it **internet background noise**: it's the weather, not a targeting decision, and it isn't tied to anything you did. So the fix is never a different address, it's making the noise irrelevant: move SSH off port 22 as above, use [key-only authentication](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys) so guesses can't succeed, and let the log noise fall to zero. The same goes for [firewalling SSH to your own IPs](https://vpsdime.com/knowledgebase/troubleshooting/allow-ssh-in-common-firewalls) if your addresses are static. ### If it went wrong anyway You still have the **[Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps)**, log in there and fix the config, socket drop-in, or firewall rule at the machine's own keyboard, no SSH needed. The full recovery flow is in [How to restore my SSH access](https://vpsdime.com/knowledgebase/troubleshooting/restore-ssh-access). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, its OS and version, and the port you moved SSH to, - what `sshd -T | grep -i '^port'` and `ss -tlnp | grep ssh` print, - whether the Console still gets you in. ### Related questions - "How do I change my SSH port?" - "I changed Port in sshd_config on Ubuntu and SSH still listens on 22." - "What is ssh.socket and why does it ignore sshd_config?" - "How do I verify which port SSH is actually listening on?" - "Why won't sshd start on my new port on AlmaLinux or Rocky?" - "I changed my SSH port and can't connect anymore." - "Does changing the SSH port improve security?" - "Do I need to tell you if I move SSH off port 22?" - "My server is being scanned, can I get a new IP?" - "Will changing my IP address stop the attacks?" --- ## How can I tell which application is using my bandwidth? URL: https://vpsdime.com/knowledgebase/technical-questions/per-app-bandwidth Last reviewed: 2026-07-02 Summary: Finding the process behind the traffic, nethogs for the per-process live view (the actual answer), iftop for per-connection, ss for who's talking to whom, and vnstat for history, plus tying the finding back to the monthly allowance and the usual suspects. ### What this is The [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) tab (or a [bandwidth warning email](https://vpsdime.com/knowledgebase/acceptable-use/bandwidth-overage)) tells you traffic is flowing, but not **which process** is sending it. These tools answer that, ordered by how directly they answer the question. ### nethogs: bandwidth per process (the answer) The one tool that groups traffic **by process**, which is almost always the question being asked: ``` apt install nethogs nethogs ``` A live table of processes with their sent/received rates. A backup shipping off-site, a busy web server, a [miner you didn't install](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery), each shows up with its name and PID. Watch it while the [traffic graph](https://vpsdime.com/knowledgebase/client-area/services/graphs) climbs and the culprit names itself. ### iftop: bandwidth per connection When the question is "talking to **whom**" rather than "which process": `apt install iftop`, run `iftop -P`, and you get a live top-list of connections with rates, remote hosts, and ports. Great for spotting one remote endpoint dominating (a scraper, a replication peer, one client downloading in a loop). ### ss: the socket census No install needed, [`ss` from the port guides](https://vpsdime.com/knowledgebase/getting-started/securing-public-services) also shows established connections: `ss -tp` lists who's connected and **which process owns each socket**, the static complement to iftop's live rates. ### vnstat: the history nethogs and iftop show *now*; **vnstat** (`apt install vnstat`) keeps per-interface daily/monthly totals from the moment it's installed, `vnstat -d` for the daily ledger. It can't attribute per-process retroactively, but it answers "which *day* did the traffic spike" so you know when to watch. (For full per-process history, an agent like [Netdata](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps) records it continuously.) ### The usual findings Backups/sync jobs on the wrong schedule, a [bot-hammered website](https://vpsdime.com/knowledgebase/troubleshooting/bot-traffic), [VPN traffic counting twice](https://vpsdime.com/knowledgebase/technical-questions/wireguard-vpn), a compromised process exfiltrating or attacking, or Docker containers (nethogs sees them as their process; `docker stats` shows per-container network too). Found it and want to cap it rather than kill it? [Limiting an application's bandwidth](https://vpsdime.com/knowledgebase/technical-questions/limit-bandwidth-usage) is the sibling guide. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what the traffic Graphs show, - what nethogs or iftop found (or didn't). ### Related questions - "What is using my VPS's bandwidth?" - "How do I see network usage per process on Linux?" - "How do I see which IPs my server is talking to?" - "How do I track daily bandwidth usage on my VPS?" --- ## How can I limit the bandwidth an application uses? URL: https://vpsdime.com/knowledgebase/technical-questions/limit-bandwidth-usage Last reviewed: 2026-07-02 Summary: Capping a process's network appetite, application-level limits first (they're the good ones: rsync, restic, wget all have flags), trickle for programs without one, Docker's per-container limits, and wondershaper/tc for whole-interface shaping, with the honest note about which layer to choose. ### What this is A process is eating the pipe, [you've identified it](https://vpsdime.com/knowledgebase/technical-questions/per-app-bandwidth), and you want it slowed rather than stopped: a backup that saturates the uplink while the site serves, a sync job that [burns the monthly allowance](https://vpsdime.com/knowledgebase/acceptable-use/bandwidth-overage). Limits exist at four layers; pick the highest one available, they get cruder as you go down. ### 1. The application's own limit (always check first) The tools that move bulk data almost all ship a throttle, and the built-in one is smooth, precise, and reliable: - **rsync**: `--bwlimit=5000` (KB/s) - **restic**: `--limit-upload 5120 --limit-download 5120` (KiB/s) - **wget** / **curl**: `--limit-rate=5m` / `--limit-rate 5M` - **scp**: `-l 40000` (Kbit/s) If your heavy process is a backup or transfer, this section is the whole answer, cap the [scheduled job](https://vpsdime.com/knowledgebase/technical-questions/systemd-timers) at a rate that leaves headroom and move on. ### 2. trickle: a rate limit for programs without one For an app with no built-in flag, **trickle** wraps it in userspace: ``` apt install trickle trickle -d 2000 -u 500 some-command # KB/s down/up ``` Honest limits: it only works on programs using standard sockets dynamically (most CLI tools yes, static binaries and some runtimes no), it's per-invocation, and it's approximate. Perfect for taming a one-off; wrong tool for infrastructure. ### 3. Docker: per-container limits Containers make it clean at the runtime level, though Docker's native flags cover CPU/memory rather than network rates; the practical pattern is either the application-level flag inside the container (layer 1), or shaping the container's interface with `tc` (layer 4), most compose stacks just use layer 1. ### 4. The interface level: wondershaper and tc When the goal is "this whole VPS should never exceed X" or per-port shaping, you're at Linux traffic control: - **[wondershaper](https://github.com/magnific0/wondershaper)** is the simple wrapper: `wondershaper -a eth0 -d 50000 -u 50000` (Kbit/s) caps the interface, everything on it. Blunt, effective, easily removed (`-c`). - **tc** itself (HTB classes, filters by port/mark) can shape *per service* at any granularity, and its syntax is famously hostile, this is the one place where [having an AI chatbot draft the tc script](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) and reading it carefully beats writing it from the man page. One thing shaping can't do: **inbound traffic has already crossed your line by the time you see it**, egress shaping is real, ingress "shaping" is polite packet-dropping. For inbound floods, the answer is [the bot guide](https://vpsdime.com/knowledgebase/troubleshooting/bot-traffic), not tc. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the process you're throttling, and the layer you tried (app flag, trickle, tc). ### Related questions - "How do I throttle a backup so it doesn't saturate my server?" - "How do I limit bandwidth for a program with no rate flag?" - "How do I cap total bandwidth on my VPS?" - "Can I limit a Docker container's bandwidth?" --- ## How can I enable PPP? URL: https://vpsdime.com/knowledgebase/technical-questions/enable-ppp Last reviewed: 2026-07-02 Summary: PPP is enabled by default on Linux VPS, nothing to request or configure on our side. Verify /dev/ppp exists and use pppd-based software normally; for a modern VPN, TUN/TAP with WireGuard or OpenVPN is usually the better tool. ### What this is Nothing to enable: **PPP is available by default** on Linux VPS. Software that needs `pppd` (L2TP/PPTP-style VPNs and other point-to-point setups) has what it requires. Verify: ``` ls -l /dev/ppp ``` On **Premium VPS** you manage your own kernel and modules (`modprobe ppp_generic` and friends) as on any KVM machine. ### Worth considering Most things people reach for PPP to build, chiefly VPNs, are better served today by [TUN/TAP with WireGuard or OpenVPN](https://vpsdime.com/knowledgebase/technical-questions/enable-tun-tap): faster, simpler, and far better maintained than PPTP-era protocols (PPTP in particular is cryptographically broken and worth avoiding). PPP remains available for the setups that genuinely need it. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the software that needs PPP and its exact error. ### Related questions - "How do I enable PPP on my VPS?" - "Does pppd work on your Linux VPS?" - "Can I run an L2TP VPN on my VPS?" --- ## Can I use Mailcow on Linux VPS? URL: https://vpsdime.com/knowledgebase/technical-questions/mailcow-on-linux-vps Last reviewed: 2026-07-02 Summary: Yes, Mailcow runs fine on Linux VPS today (it's Docker-based, and Docker works out of the box). Mind the requirements, RAM, rDNS, and above all our email policy, personal/transactional mail is fine, bulk sending is not. ### What this is **Yes.** Mailcow (dockerized) runs fine on our Linux VPS today. Older versions of this answer said no, that was our previous virtualization platform, and it no longer applies. Mailcow is Docker-based, and [Docker works out of the box](https://vpsdime.com/knowledgebase/technical-questions/docker-on-vps), so Mailcow's standard install guide applies unchanged. (Premium VPS runs it too, of course.) ### Before you install - **Size it right.** Mailcow's own requirements ask for several GB of RAM (ClamAV and Solr are the heavy parts); a **6 GB plan** is a comfortable floor for a personal or small-team setup. - **Set reverse DNS.** Deliverability lives and dies on it: set the **PTR** for your IP to your mail hostname from the [Network](https://vpsdime.com/knowledgebase/client-area/services/network) tab, and make sure the A record matches back. Add SPF, DKIM (Mailcow generates it), and DMARC in your [DNS](https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain), the full deliverability checklist with testing tools is in [Emails from my VPS go to spam](https://vpsdime.com/knowledgebase/troubleshooting/emails-going-to-spam). - **Read the [email policy](https://vpsdime.com/knowledgebase/acceptable-use/email-policy) first.** Outbound port 25 is open, and personal, team, and transactional mail is exactly what it's open for. **Bulk or marketing mail is forbidden**, our monitors block SMTP on mass-mail emission, and a blacklisted IP carries a $250-per-blacklist charge. A self-hosted mail server is for *your* mail, not a sending platform. ### Our honest take Running your own mail is genuinely satisfying and Mailcow is the best tooling for it, but it's the most unforgiving thing you can self-host: deliverability, reputation, and upkeep are ongoing work. If you just need reliable mailboxes with zero maintenance, hosted mail is less pain; if you want to own your stack, Mailcow on a right-sized VPS with correct DNS is a fine home for it. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP and the mail domain, - where the Mailcow setup stops, with the exact error. ### Related questions - "Does Mailcow work on your Linux VPS?" - "Can I run a mail server on my VPS?" - "How much RAM does Mailcow need?" - "What DNS records do I need for Mailcow?" --- ## Scheduling tasks with cron URL: https://vpsdime.com/knowledgebase/technical-questions/cron-basics Last reviewed: 2026-07-05 Summary: How cron works and how to use it well, the crontab format explained field by field with worked examples, the best practices that keep scheduled jobs honest (absolute paths, captured output, staggered times), and the cron cascade: what happens when a new run starts before the old one finishes, why it can drive load high enough to make a VPS unresponsive, and how flock, timeout, or a systemd timer prevents it. ### What this is Running commands on a schedule: a nightly backup, a report every hour, a cleanup every five minutes. **cron** is the traditional Linux scheduler, present on every distribution, and it's the right tool to learn first even though (as this page will argue at the end) it's no longer always the right tool to use. This is the happy path and the discipline; when a job misbehaves, the [troubleshooting guide](https://vpsdime.com/knowledgebase/troubleshooting/cron-not-running) picks up where this leaves off. (On a Windows VPS, the equivalent is [Task Scheduler](https://vpsdime.com/knowledgebase/windows-vps/cron-jobs-on-windows).) ### How cron works A daemon (`cron` or `crond`) wakes every minute and runs whatever the loaded **crontabs** say is due. Each user has their own crontab, and root's is separate from yours: ``` crontab -e # edit your crontab crontab -l # list it ``` A job runs with the owning user's permissions, so a job editing system files belongs in root's crontab, and a job touching one user's data belongs in that user's. (System packages also drop schedules into `/etc/cron.d/` and the `/etc/cron.daily/` family; know they exist so a mystery job can be found, but your own jobs live in `crontab -e`.) ### The crontab format Each line is five time fields followed by the command: ``` ┌───────── minute (0-59) │ ┌─────── hour (0-23) │ │ ┌───── day of month (1-31) │ │ │ ┌─── month (1-12) │ │ │ │ ┌─ day of week (0-7, both 0 and 7 are Sunday) │ │ │ │ │ * * * * * command ``` `*` means "every". A value fixes the field, `*/n` means "every n", and comma lists and ranges work (`0,30`, `9-17`). Worked examples: ``` 30 3 * * * /usr/local/bin/backup.sh # every day at 03:30 */5 * * * * /usr/local/bin/sync.sh # every 5 minutes 0 * * * * /usr/local/bin/report.sh # on every hour 15 6 * * 1 /usr/local/bin/weekly.sh # Mondays at 06:15 0 2 1 * * /usr/local/bin/monthly.sh # the 1st, at 02:00 ``` Two details that surprise people: - **Day-of-month and day-of-week combine as OR, not AND.** `0 0 13 * 5` runs on the 13th *and* on every Friday, not only on Friday the 13th. When both fields are restricted, matching either one triggers the job. - **Shortcuts exist**: `@daily`, `@hourly`, `@weekly`, `@monthly`, and `@reboot` (run once at boot) can replace the five fields. (`@reboot` jobs are usually better served by a [real systemd unit](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot), which can wait for the network and restart on failure.) Before trusting any expression, paste it into **[crontab.guru](https://crontab.guru/)**, it renders the schedule in plain words and catches every one of these surprises. ### Writing a job that behaves The habits that separate a crontab you can trust from one that fails silently: - **Absolute paths, everywhere.** Cron's environment is nearly empty (`PATH` is typically just `/usr/bin:/bin`), so write `/usr/local/bin/backup.sh`, not `backup.sh`, and have scripts use absolute paths internally too. This single habit prevents the most common cron failure there is. - **Capture the output.** Append `>> /var/log/myjob.log 2>&1` so runs and failures leave a record, the `2>&1` matters, errors go to stderr. A cron job whose output goes nowhere fails invisibly. (The fuller menu, MAILTO and dead-man's-switch pings, is in the [troubleshooting guide](https://vpsdime.com/knowledgebase/troubleshooting/cron-not-running).) - **Fail loudly inside the script.** Start shell scripts with `set -euo pipefail` so an early error stops the run with a non-zero exit instead of plowing on half-broken. - **Escape `%`.** In a crontab line, `%` is special; a `date +\%F` needs the backslash. - **Stagger your times.** Scheduling everything at `0 0 * * *` out of habit means all your jobs stampede at midnight and compete. Pick odd minutes (`17 3 * * *`), it costs nothing. - **Right user, least privilege.** Not everything needs root's crontab. ### The cron cascade: when runs pile up This is the failure mode that takes whole servers down, and it deserves its own section. The schedule and the runtime of a job are independent numbers, and **cron does not check one against the other**: when the next tick arrives, cron starts a new run whether or not the previous one is still going. Consider `*/5 * * * *` on a sync script that takes 2 minutes. Fine, for months. The data grows; the run takes 6 minutes; now a second copy starts before the first finishes. Two copies compete for CPU and disk, so both slow down, so the *third* copy joins them, and each new arrival makes every running copy slower still. The pile grows without bound, load climbs into the dozens, memory fills, and the VPS stops responding to anything, including, eventually, your SSH session. From the outside it looks like a crashed server; underneath it's one crontab line breeding processes faster than they can finish. The signature is worth memorizing: **"it was fine for months and then the VPS started hanging"**, because nothing changed except the data quietly growing until runtime crossed the schedule interval. **Spotting it** (from the [Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) if SSH won't answer): ``` uptime # load far above your vCPU count ps aux | grep -c [s]ync.sh # how many copies are running right now ``` A count above 1 for a job that should run alone is the confession. Kill the pile (`pkill -f sync.sh`), comment the crontab line out, and load falls within minutes; the [slow-VPS guide](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps) covers the wider cleanup. **Preventing it**, three layers, use at least the first: 1. **`flock`, on any job whose runtime you don't control.** It takes a lock before running and, with `-n`, simply skips the run if the previous one still holds it: ``` */5 * * * * /usr/bin/flock -n /tmp/sync.lock /usr/local/bin/sync.sh ``` One overlong run then costs you one skipped tick instead of a meltdown. (Without `-n`, flock *queues* the runs instead of skipping, which still piles up processes, for cron protection you almost always want `-n`.) 2. **`timeout`, as the backstop** for a job that might hang rather than merely run long: `timeout 20m /usr/local/bin/sync.sh` guarantees no run outlives 20 minutes, so a wedged job can't hold the lock forever. 3. **A schedule with real headroom.** Measure the job's actual runtime (`time /usr/local/bin/sync.sh`) and keep the interval several times larger, and re-check when the data it processes has grown. ### When to use a systemd timer instead Every modern distro ships a second scheduler, and for jobs that matter it's simply better. A **systemd timer**: - **cannot cascade**: it never starts a run while the previous one is still going, by design, no `flock` needed, the entire section above becomes impossible; - **logs every run** to journald with full output and exit status (`journalctl -u myjob.service`), no output-capture plumbing; - **catches up on missed runs** (`Persistent=true`), where cron silently skips anything that was due while the VPS was off; - **can cap resources** (`CPUQuota=`, `MemoryMax=`), so a heavy job can't starve the services it runs beside; - has none of cron's environment and `%` quirks. The cost is two small unit files instead of one crontab line, and the recipe is in [Using systemd timers instead of cron jobs](https://vpsdime.com/knowledgebase/technical-questions/systemd-timers). The rule of thumb from that page holds: **if you'd be upset to learn the job hadn't run for a month, it belongs in a timer.** Cron remains perfectly fine for the small stuff, a log cleanup, a curl ping, anything where a silent miss costs nothing and the runtime is seconds. ### When something doesn't run The four silent killers (empty environment, `%`, relative paths, discarded output) and the "did cron even fire?" check live in [My cron job didn't run](https://vpsdime.com/knowledgebase/troubleshooting/cron-not-running). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the exact crontab line and what the job runs, - what `uptime` and `ps aux | grep ` show if the problem is load. ### Related questions - "How do I schedule a script to run every night / every 5 minutes?" - "How does crontab syntax work?" - "Why does my cron job with day-of-month and day-of-week run more often than expected?" - "My VPS becomes unresponsive and I found many copies of my script running, why?" - "How do I stop cron jobs from overlapping?" - "What does flock -n do in a crontab?" - "Should I use cron or a systemd timer?" - "How do I run a command at boot with cron?" --- ## Using systemd timers instead of cron jobs URL: https://vpsdime.com/knowledgebase/technical-questions/systemd-timers Last reviewed: 2026-07-05 Summary: Why systemd timers are the better scheduler for jobs that matter, every run logged in journald, no overlap by design, catch-up for missed runs (Persistent), resource caps, then the two-file recipe (service + timer), OnCalendar syntax with systemd-analyze verification, and the enable-the-timer-not-the-service gotcha. ### What this is Every modern distro ships a second scheduler alongside cron: **systemd timers**. For quick one-liners, cron is fine. For jobs that *matter*, backups, certificate renewals, database dumps, timers fix every one of cron's classic failure modes ([the ones that fill the cron troubleshooting guide](https://vpsdime.com/knowledgebase/troubleshooting/cron-not-running)), and they're only slightly more work to set up. ### What you get over cron - **Every run is logged.** `journalctl -u myjob.service` shows each execution with its full output and exit status, no more "did it even run?" archaeology, no MAILTO plumbing. - **No overlapping runs, by design.** A timer won't start the service while the previous run is still going, so the [cron cascade](https://vpsdime.com/knowledgebase/technical-questions/cron-basics), runs piling onto unfinished runs until load makes the VPS unresponsive, simply can't happen. No `flock` needed. - **Missed runs can catch up.** With `Persistent=true`, a job whose moment passed while the VPS was off or rebooting runs at the next boot, cron just skips it silently. (For a VPS that gets [suspended and reactivated](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot), that difference is your nightly dump actually happening.) - **No cron environment quirks.** No `%` escaping, saner behavior, and anything the job needs can be declared explicitly in the unit. - **Resource caps.** `CPUQuota=50%` or `MemoryMax=1G` on the service keeps a heavy backup or reindex job from [starving the site it's supposed to protect](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps). - **Ordering.** `After=network-online.target` and friends, so a job that needs the network doesn't fire before it exists. ### The recipe: two small files A scheduled job is a **service** (what to run) plus a **timer** (when). Say it's a nightly backup script: **`/etc/systemd/system/backup.service`** ```ini [Unit] Description=Nightly backup [Service] Type=oneshot ExecStart=/usr/local/bin/backup.sh ``` **`/etc/systemd/system/backup.timer`** ```ini [Unit] Description=Run nightly backup at 03:30 [Timer] OnCalendar=*-*-* 03:30:00 Persistent=true RandomizedDelaySec=10m [Install] WantedBy=timers.target ``` Then activate: ``` systemctl daemon-reload systemctl enable --now backup.timer ``` (`RandomizedDelaySec` spreads the start over a window, a good habit so all your jobs don't stampede at the same second.) ### Operating it - **See all timers, with last and next run:** `systemctl list-timers` - **Read a job's history and output:** `journalctl -u backup.service` - **Run it right now** (without waiting for the schedule): `systemctl start backup.service` - **Schedule syntax:** `OnCalendar` takes shorthands (`daily`, `hourly`, `weekly`) or full expressions (`Mon *-*-* 06:00:00`). Verify any expression before trusting it, systemd has its own crontab.guru built in: ``` systemd-analyze calendar "Mon *-*-* 06:00:00" ``` which prints exactly when it will fire next. ### The gotchas - **Enable the `.timer`, not the `.service`.** Enabling the service makes it run at *boot*; the timer is what schedules it. (`enable --now backup.timer` is the whole incantation.) - `Type=oneshot` is right for scripts that run and exit, which is what scheduled jobs are. - Jobs that shouldn't run as root: add `User=deploy` to the `[Service]` section. ### When cron is still fine A one-line log cleanup, a quick curl ping, anything where a silent miss costs nothing, crontab is faster to type and perfectly adequate ([its failure modes and fixes](https://vpsdime.com/knowledgebase/troubleshooting/cron-not-running)). The rule of thumb: **if you'd be upset to learn the job hadn't run for a month, it belongs in a timer.** ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the .timer and .service files, - what `systemctl list-timers` and the job's journalctl output show. ### Related questions - "Should I use a systemd timer or a cron job?" - "How do I create a systemd timer?" - "How do I see when my timer last ran and what it printed?" - "What does Persistent=true do?" - "How do I verify an OnCalendar expression?" - "How do I stop a scheduled job from overlapping itself?" --- ## Installing a desktop environment on your VPS (and connecting to it remotely) URL: https://vpsdime.com/knowledgebase/technical-questions/install-desktop-environment Last reviewed: 2026-07-02 Summary: Turn a headless Linux VPS into a point-and-click desktop, choosing between XFCE (the VPS classic), LXQt (lightest), and GNOME (heaviest, prettiest), then the remote-access options compared honestly: xRDP (use the RDP clients you already have), TigerVNC over an SSH tunnel, NoMachine, and X2Go (the high-latency champion), with the security rule every option shares. ### What this is A Linux VPS ships **headless**, no desktop, because [the terminal](https://vpsdime.com/knowledgebase/getting-started/terminal-basics) is the efficient way to run a server. But sometimes you genuinely want a GUI: a browser running *on* the VPS, a desktop app with no CLI equivalent, a persistent workspace near the fast pipe. This is the honest setup guide: pick a desktop, pick a remote-access method, and lock the new door you just added. Two expectations first: a desktop **costs resources** (RAM mostly, see each option), and it becomes an **internet-facing login surface**, the security section at the bottom is not optional reading. ### Pick a desktop environment - **XFCE**, the VPS classic and our default recommendation: light (roughly 0.5 to 1 GB RAM idle), fast over remote protocols, stable, and boring in exactly the way a server GUI should be. Pairs best with xRDP. ``` apt install xfce4 xfce4-goodies ``` - **LXQt**, the lightest of the majors, if every megabyte counts: ``` apt install lxqt ``` - **GNOME**, the full modern desktop, prettiest, heaviest (2 GB+ before you open anything), and the most particular about remote protocols. Comfortable from a **6 GB plan** upward: ``` apt install ubuntu-desktop-minimal # Ubuntu apt install task-gnome-desktop # Debian ``` - **Also respectable:** **KDE Plasma** (`kde-plasma-desktop`, mid-weight and polished, lighter than its reputation), **MATE** (`mate-desktop-environment`, the classic GNOME 2 feel, light-mid), and **Cinnamon**. All fine; XFCE remains the sweet spot for remote use. ### Connect: the four ways, compared | Method | Protocol/client | Strengths | Watch out | |---|---|---|---| | **xRDP** | RDP, the clients you already have | Best default, native Windows client, good performance | Opens 3389, restrict it | | **TigerVNC** | VNC, any VNC viewer | Simple, universal | Weak crypto, tunnel-only | | **NoMachine** | NX, their free client | Excellent performance, audio | Own port (4000), restrict it | | **X2Go** | NX3 over SSH, their client | Best over **high latency**, rides SSH (no new ports!) | Doesn't do GNOME well | #### xRDP, the recommended default Speaks real **RDP**, so every client from [the Windows VPS guides](https://vpsdime.com/knowledgebase/windows-vps/connect-rdp), Windows' built-in Remote Desktop Connection included, works against your Linux desktop too. ``` apt install xrdp systemctl enable --now xrdp echo xfce4-session > ~/.xsession ``` Then connect any RDP client to `YOUR.VPS.IP` and log in with your **Linux user and password** (a [regular user](https://vpsdime.com/knowledgebase/getting-started/first-30-minutes), not root). Allow 3389 in your own firewall, restricted (below). One honest compatibility note: **XFCE and LXQt behave beautifully under xRDP; GNOME sessions under xRDP are historically finicky**, if you want GNOME specifically, NoMachine handles it better. #### TigerVNC, simple but tunnel-only `apt install tigervnc-standalone-server`, run `vncserver` (it prompts for a VNC password), and view with any VNC client. The rule: VNC's own encryption is weak, so **never expose the VNC port to the internet**, keep it localhost-bound (the default) and reach it through an SSH tunnel: `ssh -L 5901:localhost:5901 user@YOUR.VPS.IP`, then point the viewer at `localhost:5901`. The tunnel means VNC inherits your [SSH key security](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys), which turns its weakness into a non-issue. #### NoMachine, the performance pick Free (not open source), one `.deb` from [nomachine.com](https://www.nomachine.com/), and its NX protocol delivers the smoothest full-desktop feel of the bunch, audio included, and it copes with GNOME. It listens on port 4000: restrict it to your IPs in your firewall the same way you would RDP. #### X2Go, the high-latency champion If you're [far from your datacenter](https://vpsdime.com/knowledgebase/troubleshooting/network-problems) and every option feels like syrup, **X2Go** is built for exactly that: `apt install x2goserver`, install the X2Go client locally, and, its quiet superpower, it **connects over SSH**, so there are no new ports to open and it inherits keys, [2FA](https://vpsdime.com/knowledgebase/technical-questions/ssh-2fa-totp), everything your SSH already has. Pair it with XFCE or LXQt (GNOME isn't supported well). ### The security rule (every option) A desktop login is a password-guessing target like any other, and our [managed firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall) doesn't block these ports for you: - **Restrict the port to your IPs** in your own firewall (`ufw allow from YOUR.IP to any port 3389`), or better, **don't expose it at all**, SSH-tunnel it (VNC's mandatory pattern works for RDP too: bind xRDP to localhost and `ssh -L 3389:localhost:3389`), or pick X2Go and get that for free. - Log into the desktop as a **regular user**, keep the [SSH hardening](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps) intact underneath, and remember the desktop's browser is a browser, [treat the server's exposure accordingly](https://vpsdime.com/knowledgebase/getting-started/securing-public-services). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the desktop and remote-access method you picked (say, XFCE with xRDP), - where it fails (install, connection, login), with the exact message. ### Related questions - "How do I install a GUI on my Linux VPS?" - "Which desktop environment is best for a VPS, XFCE, LXQt, or GNOME?" - "How do I set up xRDP on Ubuntu?" - "Is VNC safe to expose to the internet?" - "What's the best remote desktop option for a high-latency connection?" - "Can I use Windows' Remote Desktop client with a Linux VPS?" --- ## How can I install Gitea and host my code on my VPS? URL: https://vpsdime.com/knowledgebase/technical-questions/install-gitea Last reviewed: 2026-07-02 Summary: Gitea gives you a self-hosted GitHub, repos, issues, pull requests, CI, in one lightweight binary. The clean Docker-compose install, the reverse proxy and SSL in front, SSH cloning options, first-run settings worth getting right (disable open registration!), and the backup line that makes it durable. ### What this is [Gitea](https://about.gitea.com/) is the self-hosted GitHub: private and public repos, issues, pull requests, a web UI, even built-in CI (Gitea Actions, workflow-compatible with GitHub's), in a single lightweight service that runs happily on a small plan. Owning your code hosting is one of the classic good reasons for a VPS, and Gitea is the tool that made it easy. ### Install: the Docker-compose way [Docker works out of the box](https://vpsdime.com/knowledgebase/technical-questions/docker-on-vps), and compose keeps Gitea and its database tidy in one file, `/opt/gitea/docker-compose.yml`: ```yaml services: gitea: image: docker.gitea.com/gitea:latest restart: unless-stopped environment: - GITEA__database__DB_TYPE=sqlite3 volumes: - ./data:/data ports: - "127.0.0.1:3000:3000" - "2222:22" ``` ``` cd /opt/gitea && docker compose up -d ``` Notes on the choices: **SQLite** is genuinely fine for a personal/small-team instance (swap in a MariaDB service later if you grow); the web port is published **to localhost only** because a reverse proxy fronts it ([the exposure rule](https://vpsdime.com/knowledgebase/getting-started/securing-public-services)); and container port 22 maps to **2222** so Gitea's SSH cloning doesn't fight [your own sshd](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys). The `restart: unless-stopped` line is what makes it [survive reboots](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot). (Prefer no Docker? Gitea also ships as a single binary with a systemd unit, their [install docs](https://docs.gitea.com/) cover it, and everything below applies the same.) ### Put a real domain and SSL in front Point a subdomain (`git.yourdomain.com`) at the VPS ([DNS](https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain)), then reverse-proxy to localhost:3000 with [nginx + certbot, or Caddy for the two-line version](https://vpsdime.com/knowledgebase/getting-started/hosting-a-website): ``` git.yourdomain.com { reverse_proxy localhost:3000 } ``` (That's the entire Caddyfile, HTTPS included.) Browse to the domain and Gitea's first-run page appears. ### First-run settings worth getting right Most defaults are fine; these four aren't cosmetic: - **Server domain / base URL**: set them to your real domain now, clone URLs are generated from these. - **SSH server port**: `2222` (matching the compose mapping), so clone URLs come out right. - **Create the admin account** on this screen, and - **Disable open registration** (or set it to invite-only) unless you *want* the internet signing up: a public registration page on a code host collects spam accounts within days, [same logic as any exposed login](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps). Enable 2FA on your admin account once inside. Then add [your SSH key](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys) in your Gitea profile, and cloning works both ways: ``` git clone ssh://git@git.yourdomain.com:2222/you/repo.git git clone https://git.yourdomain.com/you/repo.git ``` ### Make it durable Your code is now [irreplaceable data on a VPS](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps), and Gitea makes the backup half easy: `docker compose exec gitea gitea dump` produces a single restorable archive (repos, database, config), drop that into a [scheduled](https://vpsdime.com/knowledgebase/technical-questions/systemd-timers) job whose output your restic run ships off-site, and the self-hosting trade-off is fully paid. Updates: `docker compose pull && docker compose up -d`, on a schedule you own, [like any internet-facing app](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, and the domain you're putting Gitea on, - where it stops (compose, the proxy, SSL, first-run), with the log line. ### Related questions - "How do I self-host a Git server on my VPS?" - "How do I install Gitea with Docker?" - "How do I set up SSL and a domain for Gitea?" - "Why should registration be disabled on my Gitea?" - "How do I back up Gitea?" --- ## How do Linux file permissions work? (And what are attributes?) URL: https://vpsdime.com/knowledgebase/technical-questions/linux-file-permissions Last reviewed: 2026-07-02 Summary: The complete model, read/write/execute for owner, group, and others, how to read ls -l output, octal notation decoded, chmod/chown/chgrp, why execute on directories means traverse, the special bits (setuid, setgid, sticky), umask, file attributes via chattr/lsattr (the immutable flag), and a note on ACLs. ### What this is The permission model behind every `Permission denied`, every [403](https://vpsdime.com/knowledgebase/troubleshooting/403-forbidden), and every "why can't the web server read my upload". It's a small, consistent system, ten minutes here and `ls -l` output becomes legible forever. ### The model: three actions, three audiences Every file and directory carries permissions for **three actions**, read (`r`), write (`w`), execute (`x`), granted separately to **three audiences**: the **owner** (one user), the **group** (one group of users), and **others** (everyone else). It also carries exactly one owner and one group, that's the whole state. Reading `ls -l`: ``` -rw-r--r-- 1 www-data www-data 4096 Jul 2 10:00 index.php drwxr-xr-x 2 deploy deploy 4096 Jul 2 10:00 uploads ``` First character: type (`-` file, `d` directory, `l` symlink). Then three triplets, owner/group/others: `rw-` `r--` `r--` means the owner reads and writes, everyone else reads. Then the owner and group names. ### What r, w, x mean, files vs directories - On a **file**: read the contents / change the contents / run it as a program. - On a **directory**, the part that trips everyone: `r` = list the names inside, `w` = create/delete/rename entries inside, and **`x` = traverse**, enter it, or reach anything through it. A file you can read inside a directory you can't traverse is unreachable, which is why a `700` home directory above a web root [produces 403s with perfect file permissions](https://vpsdime.com/knowledgebase/troubleshooting/403-forbidden). ### Octal notation, decoded once Each triplet is a number: r=4, w=2, x=1, summed. So: - `644` = `rw-r--r--`, the standard **file**: owner edits, world reads. - `755` = `rwxr-xr-x`, the standard **directory** (and executable): owner full, world can enter/read. - `600`/`700`, private file/directory, [what `.env` files and `~/.ssh` want](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys). - `777` = everyone can do everything, [the "fix" that's always wrong](https://vpsdime.com/knowledgebase/troubleshooting/403-forbidden): on a server it means any compromised process can rewrite your code. ### Changing things: chmod, chown, chgrp ``` chmod 644 file.php # set exact permissions (octal) chmod u+x deploy.sh # symbolic: add execute for the owner chmod -R g+w /var/www/shared # recursive, careful with -R and x! chown www-data:www-data -R /var/www/site # owner and group together ``` One recursion trap: `chmod -R 644` strips the `x` from directories and breaks traversal. The idiom that sets files and directories correctly in one pass is [in the 403 guide](https://vpsdime.com/knowledgebase/troubleshooting/403-forbidden) (`find -type d` → 755, `find -type f` → 644). ### The special bits: setuid, setgid, sticky A fourth, leading octal digit covers three special cases you'll mostly *read* rather than set: - **setuid (4xxx, `s` in the owner triplet)**: the program runs as its owner regardless of who launches it, how `passwd` edits a root-owned file. On your own files, almost never; a stray setuid-root binary is a [compromise artifact](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery) worth noticing. - **setgid (2xxx)**: on a **directory**, new files inherit the directory's *group* instead of the creator's, genuinely useful for shared web roots (`chmod g+s /var/www/shared`). - **sticky (1xxx, `t` on the end)**: in a world-writable directory, only a file's owner may delete it, why `/tmp` is `1777` and everyone's temp files survive each other. ### umask: where default permissions come from New files don't appear as 666/777, the **umask** subtracts bits at creation. The usual `022` yields 644 files and 755 directories, which is why fresh files are usually right without thought. If a service creates files your web server can't read, its umask (settable per systemd unit with `UMask=`) is the suspect. ### Attributes: the layer beneath permissions Separate from permissions, ext4 supports **file attributes**, flags on the file itself, managed with `chattr` and listed with `lsattr`. The two that matter in practice: - **`i` (immutable)**: `chattr +i file`, the file can't be modified, deleted, or renamed **by anyone, root included**, until `chattr -i`. Legitimate for lock-down-this-config; also a known [malware persistence trick](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery), when a file refuses deletion as root, `lsattr` it. - **`a` (append-only)**: writes can only add, never rewrite, occasionally used to protect logs. If a permission mystery survives everything above, check `lsattr` before questioning reality. ### A note on ACLs When one-owner-one-group isn't expressive enough ("these *two* users, plus the web server, but nobody else"), POSIX **ACLs** add per-user/per-group entries on top: `setfacl -m u:deploy:rw file`, inspect with `getfacl`, and a `+` at the end of `ls -l`'s permission block is the tell that ACLs are in play. Most single-admin servers never need them; knowing the `+` exists prevents one specific afternoon of confusion. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the `ls -l` line for the file or folder, and who needs which access. ### Related questions - "What do 644, 755, and 777 actually mean?" - "Why does execute on a directory matter?" - "What are setuid, setgid, and the sticky bit?" - "Why can't root delete this file (chattr immutable)?" - "What does the + at the end of ls -l permissions mean?" --- ## Process management on Linux: ps, top, kill, and friends URL: https://vpsdime.com/knowledgebase/technical-questions/process-management Last reviewed: 2026-07-02 Summary: The complete toolkit, seeing processes (ps, top, htop), finding them (pgrep, pidof, lsof), signals and what kill actually does (TERM vs KILL, and why -9 is the last resort), pkill and killall, priorities with nice and renice, and the shell's own job control (&, Ctrl+Z, fg, bg, jobs, disown). ### What this is Everything running on your VPS is a **process** with a numeric **PID**, and this is the toolkit for seeing them, finding them, stopping them, and re-prioritizing them, the vocabulary the [slow-VPS](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps) and [keep-it-running](https://vpsdime.com/knowledgebase/technical-questions/keep-apps-running-after-ssh) guides assume. ### Seeing: ps, top, htop - **`ps aux`** is the census, every process, its user, PID, CPU/memory share, and command line. Nobody reads it raw; it gets piped: `ps aux --sort=-%cpu | head` (the hungriest), `ps aux | grep nginx` (one program's processes). - **`top`** is the live view, on every machine ever. **`htop`** (`apt install htop`) is the one you'll actually enjoy: colors, scrolling, a tree view (`F5`, who spawned whom, great for [cron pileups](https://vpsdime.com/knowledgebase/troubleshooting/cron-not-running)), sort by clicking columns, and kill from inside (`F9`). ### Finding: pgrep, pidof, lsof - **`pgrep -a nginx`**, PIDs (and command lines) matching a name; `pgrep -u www-data` by user. **`pidof nginx`** is the terser classic for exact names. - **`lsof`** answers "who has this *thing* open": `lsof -i :8080` (which process owns this **port**, the sibling of [`ss -tulnp`](https://vpsdime.com/knowledgebase/getting-started/securing-public-services)), `lsof /var/log/big.log` (who's writing this file), `lsof +L1` ([the deleted-but-held disk mystery](https://vpsdime.com/knowledgebase/troubleshooting/disk-full)). ### Stopping: signals, and what kill really does `kill` doesn't kill, it **delivers a signal**, and which one matters: - **`kill `** sends **SIGTERM** (15): "please shut down." The process gets to close files, flush buffers, and exit cleanly. **Always first.** - **`kill -9 `** sends **SIGKILL**: the kernel removes the process, no cleanup, no goodbye. Databases mid-write, half-written files, orphaned locks, this is why `-9` is the *last* resort, not the reflex. The discipline: TERM, wait five seconds, then KILL if it ignored you. - **`kill -HUP `**, many daemons treat SIGHUP as "reload your config" (though for systemd services, `systemctl reload` is the proper spelling). By name instead of PID: **`pkill nginx`** (pattern, same matching as pgrep, and `pkill -u baduser` for everything a user runs) and **`killall nginx`** (exact name). Both accept `-9` with the same warning attached. And for anything that's a *service*, prefer `systemctl stop`, killing a unit's process behind systemd's back just triggers its `Restart=` policy, [which you may have set yourself](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot). A footnote you'll meet eventually: a **zombie** (`Z` state, ``) is already dead, just unreaped by its parent, it holds no resources and can't be killed harder; a *crowd* of zombies points at a buggy parent process. ### Prioritizing: nice and renice Covered fully in [the CPU-limiting guide](https://vpsdime.com/knowledgebase/technical-questions/limit-cpu-usage), the short form: `nice -n 19 ` starts a job at lowest priority (uses idle CPU, yields to everything), `renice 19 -p ` demotes one already running, and `ionice -c3` is the disk-I/O sibling. ### The shell's own job control: &, Ctrl+Z, fg, bg Within one terminal session, the shell manages **jobs**: - `command &` starts it in the background; **Ctrl+Z** suspends the foreground job; **`bg`** resumes the suspended job in the background, **`fg`** brings it back; **`jobs`** lists them (`fg %2` by number). - The catch: jobs belong to the session, close it and they die. `disown -h %1` after `bg` is [the rescue for a job you should have started in tmux](https://vpsdime.com/knowledgebase/technical-questions/keep-apps-running-after-ssh), which remains the real answer for anything long. ### The recipes ``` ps aux --sort=-%mem | head # what's eating memory lsof -i :3306 # what owns this port pkill -f runaway-script.sh # stop every instance by pattern (-f matches full command line) kill 1234 && sleep 5 && kill -9 1234 2>/dev/null # polite, then firm ``` And when a process you don't recognize tops every list, [that's a different guide](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the process (name or PID) and what you're trying to do with it. ### Related questions - "How do I see and sort running processes?" - "What's the difference between kill and kill -9?" - "How do I find which process is using a port?" - "What's a zombie process and should I worry?" - "What do fg, bg, and Ctrl+Z do?" --- ## How can I find files, and text inside files, on Linux? URL: https://vpsdime.com/knowledgebase/technical-questions/find-files-and-text Last reviewed: 2026-07-02 Summary: The two searches that cover everything, find for files (by name, size, age, type, with the -exec superpower) and grep -r for text inside them (with the flags that matter), plus the modern upgrades fd and ripgrep, and the recipes this knowledge base keeps using. ### What this is The two halves of searching a server: **find** locates *files* by their properties (name, size, age), **grep** locates *text inside* them. Between them, every "where is..." question on a VPS has an answer, and half the recipes in this knowledge base are one of these two wearing context. ### find: locating files The shape is always `find `: ``` find /var/www -name "*.conf" # by name (quote the pattern!) find /var/www -iname "*.JPG" # case-insensitive find / -xdev -size +500M # bigger than 500 MB find /var/www -mtime -2 # modified in the last 2 days find /var/log -type f -name "*.gz" # files only (-type d for dirs) ``` The tests combine (`-name "*.log" -size +100M -mtime +30`: old fat logs), and two recipes from elsewhere in these docs show the range: [recently changed files after a compromise](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery) (`-mtime -14`), and [deleting a million tiny files](https://vpsdime.com/knowledgebase/troubleshooting/out-of-inodes) (`-type f -delete`, where `rm` chokes). The superpower is **-exec**, run a command on every match: ``` find /var/www -name "*.bak" -exec ls -lh {} \; # inspect first... find /var/www -name "*.bak" -delete # ...then act ``` (That order, inspect with `ls` before any delete, is [the safety habit](https://vpsdime.com/knowledgebase/getting-started/terminal-basics), always.) ### grep: locating text inside files ``` grep -r "database_password" /var/www # recursive through a tree grep -ri "error" /var/log/nginx/error.log # case-insensitive grep -rn "listen" /etc/nginx/ # -n: show line numbers grep -rl "wp_debug" /var/www # -l: just list matching files ``` `-r` is the flag that turns grep from a filter into a search engine. Useful companions: `-v` inverts (lines *not* matching), `-A3`/`-B3` show lines after/before a match (context around an error), and `zgrep` searches [rotated .gz logs](https://vpsdime.com/knowledgebase/troubleshooting/troubleshooting-method) without unpacking them. The combined classic, find picks the files, grep reads them: ``` find /var/www -name "*.php" -exec grep -l "base64_decode" {} + ``` (that particular one being a [web-shell hunt](https://vpsdime.com/knowledgebase/troubleshooting/chrome-dangerous-site-warning)). ### The modern upgrades: fd and ripgrep Both worth installing on a box you work on daily: **fd** (`apt install fd-find`, command `fdfind`) is find with sane defaults, `fdfind config` just works, and **ripgrep** (`apt install ripgrep`, command `rg`) is a dramatically faster recursive grep that skips `.git` and binaries by default, `rg "database_password" /var/www`. Same concepts, less typing; the classic tools remain worth knowing because they're on every machine you'll ever touch. (`locate` exists too, instant name lookups from a nightly index, but on a server its index is stale by definition; find tells the truth right now.) ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what you're searching for, and the command you tried. ### Related questions - "How do I find a file by name on Linux?" - "How do I search for text in all files in a directory?" - "How do I find files modified recently, or over a certain size?" - "What are fd and ripgrep and should I use them?" --- ## How can I keep an application running after I disconnect from SSH? URL: https://vpsdime.com/knowledgebase/technical-questions/keep-apps-running-after-ssh Last reviewed: 2026-07-02 Summary: Why your program dies when the SSH session ends (it's the terminal's child), and the three answers by situation, tmux for interactive things you'll come back to, a systemd service for anything that should always run, and nohup for the quick fire-and-forget, plus recovering a job you started without any of them. ### What this is You start something over SSH, a long build, a download, a game server, and when the connection drops (or you close the laptop), it dies. That's by design: processes you start belong to your login session, and the session's end sends them a hangup. Three tools fix it; pick by what the thing *is*. ### tmux: for interactive work you'll return to The right default for humans. **tmux** gives you a terminal session that lives on the server, detached from your SSH connection: ``` apt install tmux tmux # start a session, run your stuff inside it ``` Detach with **Ctrl+B then D** (or just let SSH drop, same effect), reconnect any time from anywhere: ``` tmux attach ``` and your program is exactly where you left it, output history included. Multiple sessions: `tmux new -s build`, `tmux ls`, `tmux attach -t build`. This is why every long-running command in this knowledge base ([migrations](https://vpsdime.com/knowledgebase/getting-started/migrating-a-vps), big transfers) says "run it in tmux". (`screen` is the older equivalent, fine if it's what your hands know.) ### systemd: for anything that should *always* run If the answer to "should this still be running next month?" is yes, a game server, an app, a bot, it isn't a terminal job at all, it's a **service**: a ten-line unit file gets it starting at boot, restarting on crash, and logging to the journal, [the same recipe as the timers guide](https://vpsdime.com/knowledgebase/technical-questions/systemd-timers), and the difference between a program that survives your disconnect and one that survives [a reboot](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot). An [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) drafts the unit from "write a systemd service for as ". ### nohup: the quick fire-and-forget For a one-shot command you just want to outlive the session, no reconnecting needed: ``` nohup ./long-job.sh > job.log 2>&1 & ``` It ignores the hangup, runs in the background, and writes output to the log you pointed it at. No way to reattach, that's tmux's job, but nothing to install. ### "I already started it without any of these" A running job in your current session can still be saved: **Ctrl+Z** to suspend it, `bg` to resume it in the background, then `disown -h %1` detaches it from the session's hangup. Cruder than starting in tmux, but it rescues the three-hour job you forgot to protect. (The `fg`/`bg`/jobs machinery has [its own section in the process guide](https://vpsdime.com/knowledgebase/technical-questions/process-management).) ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the program you're keeping alive, and the approach you tried (tmux, systemd, nohup). ### Related questions - "Why does my program stop when I close SSH?" - "How do I use tmux to keep something running?" - "Should I use tmux, nohup, or a systemd service?" - "How do I save a running job I started without tmux?" --- ## How can I encrypt and decrypt files on my VPS? URL: https://vpsdime.com/knowledgebase/technical-questions/encrypt-files Last reviewed: 2026-07-02 Summary: File-level encryption done properly, age as the modern tool (one command each way), GPG as the everywhere-installed classic (symmetric passphrase or public-key), what each protects against on a VPS, encrypting backups before they leave the box, and the passphrase-loss warning that has no fine print. ### What this is Encrypting individual files and archives, a database dump before it leaves the server, a credentials file at rest, an archive only you should ever open. Two tools cover it: **age**, the modern one designed to be un-misusable, and **GPG**, the classic that's already installed everywhere. (Whole-disk encryption is a different topic with different trade-offs on a VPS; this page is about files.) First, the honest threat model: file encryption protects data **at rest and in transit**, the copy in your off-site bucket, the archive on a stolen backup drive. It does *not* protect a file from someone who has root on the box *while you decrypt and use it*, [keeping the server unowned](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps) remains job one. ### age: the modern answer [age](https://github.com/FiloSottile/age) (`apt install age`) does one thing with no footguns: **Passphrase mode**, one file, one secret: ``` age -p secrets.tar > secrets.tar.age # prompts for a passphrase age -d secrets.tar.age > secrets.tar # prompts to decrypt ``` **Keypair mode**, encrypt *to* a recipient (yourself, elsewhere): ``` age-keygen -o key.txt # once; keep key.txt safe, off-box age -r age1xyz... backup.tar > backup.tar.age # encrypt to the public key age -d -i key.txt backup.tar.age > backup.tar # decrypt with the private key ``` The keypair pattern is the good one for **backups**: the *public* key lives on the VPS and encrypts nightly dumps; the *private* key lives only on your machine, so a fully compromised server still can't read its own backup archive. ### GPG: the everywhere classic Already on every distro, and the format the wider world speaks: ``` gpg -c backup.tar # symmetric: passphrase, makes backup.tar.gpg gpg backup.tar.gpg # decrypt (prompts) ``` Public-key mode mirrors age's (generate with `gpg --gen-key`, encrypt with `-e -r you@example.com`), with more machinery (keyrings, trust) than a single-server workflow strictly needs, which is exactly why age exists. Use GPG when interoperability matters (the other side already uses it); use age when you're choosing fresh. ### Where this fits your backups If you followed [the backup guide](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps), note that **restic already encrypts everything** it stores, that's built in, no extra layer needed. Manual patterns, a dump uploaded with rclone, an archive parked in object storage, are where `age -r` before upload earns its place: ``` mysqldump --single-transaction mydb | gzip | age -r age1xyz... > mydb-$(date +%F).sql.gz.age ``` ### The warning with no fine print **A lost passphrase or private key is the data, gone.** There is no reset flow, no support ticket ([ours included](https://vpsdime.com/knowledgebase/support-coverage/what-support-covers)) that recovers properly encrypted data. Store the passphrase in a password manager and keep a copy of the key file somewhere that isn't the VPS, before the first real file is encrypted, not after. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the tool (age or GPG), the exact command, and the error. (Never include the passphrase itself.) ### Related questions - "How do I encrypt a file with a password on Linux?" - "Should I use GPG or age?" - "How do I encrypt backups before uploading them?" - "Can encrypted files be recovered if I lose the passphrase?" --- ## What is strace, and how do I make use of it? URL: https://vpsdime.com/knowledgebase/technical-questions/what-is-strace Last reviewed: 2026-07-02 Summary: strace shows every system call a process makes, the conversation between a program and the kernel, which makes it the tool of last resort that actually works: watching a hung process, finding which config file something really reads, decoding permission errors, and the filters (-e, -p, -f, -c) that keep the firehose drinkable. ### What this is **strace** records every **system call** a process makes, every file it opens, every network connection, every read, write, and wait, the full conversation between a program and the kernel. When logs say nothing and documentation lies, strace shows what a program *actually does*, which is why it's the tool people reach for last and wish they'd reached for first. ``` apt install strace ``` The honest warning first: the output is a firehose, and the skill is entirely in **filtering** (below). Also, tracing meaningfully slows the traced process, fine for debugging, not something to leave attached to a busy production service for hours. ### The three moves that cover most uses **1. "What files does this thing actually open?"** The single most useful filter, watching a program look for its config: ``` strace -e trace=openat,stat -f myprogram 2>&1 | grep -v ENOENT ``` or *with* the failures, because the failures are often the answer: ``` strace -e trace=openat myprogram 2>&1 | grep ENOENT ``` `ENOENT` (no such file) trails show exactly which paths were tried and in what order, "why does it ignore my config" is solved here, and `EACCES` in the same view is a [permissions problem](https://vpsdime.com/knowledgebase/technical-questions/linux-file-permissions) with the exact path attached. **2. "What is this hung process doing?"** Attach to a running PID: ``` strace -p 12345 ``` A healthy busy process scrolls; a hung one shows its last call and sits there, and *which* call it's stuck in is the diagnosis: stuck in `read` on a network socket = waiting on a remote end ([whose path you can test](https://vpsdime.com/knowledgebase/troubleshooting/network-problems)); stuck in `write` = a full pipe or [slow disk](https://vpsdime.com/knowledgebase/technical-questions/what-is-iops); stuck in `futex` = waiting on a lock another thread holds. Detach with Ctrl+C, the process continues unharmed. **3. "Where does the time go?"** The summary mode: ``` strace -c myprogram ``` runs the program and prints a table, calls, errors, and time per syscall type. A program spending 95% of its traced time in `poll`/`select` is waiting on the world, not working; thousands of failed `openat` calls explain a slow startup. ### The flags worth knowing - **`-f`**: follow child processes, essential for anything that forks (which is most things, shells and web servers included). - **`-e trace=network`** / `=file` / `=signal`: pre-made filter families ("show me only its network life"). - **`-o /tmp/trace.txt`**: write to a file, then [grep it](https://vpsdime.com/knowledgebase/technical-questions/find-files-and-text) at leisure. - **`-s 200`**: show more of each string argument (default truncates at 32 chars, right where the interesting part was). - **`-t`** timestamps each line; **`-T`** shows time spent *inside* each call, the hung-call hunter's flag. ### Reading a line ``` openat(AT_FDCWD, "/etc/nginx/nginx.conf", O_RDONLY) = 3 connect(4, {sa_family=AF_INET, sin_port=htons(3306), ...}) = -1 ECONNREFUSED ``` Call, arguments, `=` result. A number is success (a file descriptor); `-1` plus an error name is the story: that second line is a program failing to reach MySQL, [connection refused, nothing listening](https://vpsdime.com/knowledgebase/troubleshooting/my-port-xxx-is-closed), captured in the act. The error names repay learning: `ENOENT` (doesn't exist), `EACCES` (permissions), `ECONNREFUSED`/`ETIMEDOUT` (network), `ENOSPC` ([disk full](https://vpsdime.com/knowledgebase/troubleshooting/disk-full), caught red-handed). For everything past the common patterns, strace output is superb [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) material, paste the last screen of a hung process's trace and ask what it's waiting on. (**ltrace** is the sibling that traces *library* calls instead of system calls, occasionally the right level, but strace answers the server questions.) ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the process you're tracing, and the last screen of strace output. ### Related questions - "How do I see what files a program opens?" - "How do I find out what a hung process is waiting on?" - "How do I attach strace to a running process?" - "What do ENOENT and EACCES mean in strace output?" --- ## Troubleshooting URL: https://vpsdime.com/knowledgebase/troubleshooting Last reviewed: 2026-07-02 Summary: Fixes for the most common VPS problems, restoring SSH access, firewall lockouts, the host identification changed warning, DNS resolution failures inside the VPS, cPanel login blocks, changing the SSH port, and understanding memory usage. Fixes for the problems that generate the most tickets, most are self-service in minutes. If your VPS is unreachable and you want a guided diagnosis, start with [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter), it checks your VPS and fixes several causes on the spot. ### Start here - [How to troubleshoot anything (and where everything logs)](https://vpsdime.com/knowledgebase/troubleshooting/troubleshooting-method). The method, the question-to-command table, and the log atlas every guide below assumes. ### Can't get in - [My IP is blocked. How do I unblock it?](https://vpsdime.com/knowledgebase/troubleshooting/ip-blocked) The four layers that can block an IP, how to tell which one got you, the fastest unblock for each, and prevention. - [How to restore my SSH access](https://vpsdime.com/knowledgebase/troubleshooting/restore-ssh-access). The step-by-step diagnosis: banned IP, your own firewall, or SSH itself. - [Commands to allow SSH access in common firewalls](https://vpsdime.com/knowledgebase/troubleshooting/allow-ssh-in-common-firewalls). The exact commands for ufw, CSF, firewalld, iptables, and nft. - [WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED](https://vpsdime.com/knowledgebase/troubleshooting/host-identification-changed). Normal after a reinstall, here's the one-line fix. - [cPanel/WHM: root login suddenly fails (cPHulk)](https://vpsdime.com/knowledgebase/troubleshooting/cpanel-cphulk-login-blocked). cPanel's brute-force protection locking you out of your own server. ### Network - [Understanding and troubleshooting network problems](https://vpsdime.com/knowledgebase/troubleshooting/network-problems). Whose fault is the lag, yours, ours, or a carrier in between, and how to prove it with mtr. - [Testing your VPS network speed](https://vpsdime.com/knowledgebase/troubleshooting/testing-network-speed). Speedtest CLI, our per-location test files, iperf3, and reading single- vs multi-stream results. - [My Port XXX is closed. Can you open it?](https://vpsdime.com/knowledgebase/troubleshooting/my-port-xxx-is-closed) Nothing to open, ports show open only when something listens, plus closed vs filtered decoded. - [Bots and crawlers are hammering my website](https://vpsdime.com/knowledgebase/troubleshooting/bot-traffic). Identify them in the access log, robots.txt vs rate limiting vs fail2ban vs Cloudflare. ### Email - [Emails from my VPS go to spam](https://vpsdime.com/knowledgebase/troubleshooting/emails-going-to-spam). Diagnose with mail-tester and MXToolbox, then rDNS, SPF, DKIM, DMARC, and reputation. - [My mail server isn't receiving email](https://vpsdime.com/knowledgebase/troubleshooting/cannot-receive-email). The inbound chain: MX record, port 25 listener, outside testing, and the mail log. ### Inside the VPS - [My VPS is slow. How do I find out why?](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps) The systematic walk-through: path vs server, OOM kills, the four CPU hogs, monitoring, and website tuning. - [Fixing 502, 503, and 504 errors](https://vpsdime.com/knowledgebase/troubleshooting/502-503-errors). The web server answered, the app behind it didn't, decode the error, read the proxy log, and the Docker cases. - [Fixing SSL certificate errors](https://vpsdime.com/knowledgebase/troubleshooting/ssl-certificate-errors). Expired (the day-91 renewal failure), name mismatches, chains, mixed content, and Cloudflare's SSL modes. - [Fixing 403 Forbidden errors](https://vpsdime.com/knowledgebase/troubleshooting/403-forbidden). Ownership after uploads, missing index files, deny rules, and why never chmod 777. - [My website didn't come back after a reboot or unsuspension](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot). Started is not enabled, the fix for the post-payment "VPS is up but site is down". - [My VPS was hacked. Recovery, step by step](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery). Why modern bots survive cleanup, the backup-and-reinstall routine, and how our suspension process works. - [Chrome shows a "Dangerous site" warning on my website](https://vpsdime.com/knowledgebase/troubleshooting/chrome-dangerous-site-warning). Google Safe Browsing flags, what was flagged, the cleanup, and the review that lifts it. - [I deleted files by accident. Can they be recovered?](https://vpsdime.com/knowledgebase/troubleshooting/recover-deleted-files) Stop writes, honest odds, and the real recovery paths through backups. - [MySQL or MariaDB won't start after a crash](https://vpsdime.com/knowledgebase/troubleshooting/mysql-wont-start). The safe order: logs, disk, OOM, patient recovery, and force_recovery only to dump and rebuild. - [My cron job didn't run](https://vpsdime.com/knowledgebase/troubleshooting/cron-not-running). The empty PATH, the % gotcha, silent failures, and making them noisy. - [Error: Failed to detect code in SYSLOG log (lfd)](https://vpsdime.com/knowledgebase/troubleshooting/lfd-failed-to-detect-code). The rsyslog imjournal bug behind the alert, and the two fixes. - [Temporary failure resolving (DNS errors during updates)](https://vpsdime.com/knowledgebase/troubleshooting/temporary-failure-resolving). The systemd-resolved fix. - [My disk is full (and it took my website or database down)](https://vpsdime.com/knowledgebase/troubleshooting/disk-full). The hidden cause behind "my site is offline" and "MySQL won't start", find it, clean it safely, prevent it. - [No space left on device, but df shows free space](https://vpsdime.com/knowledgebase/troubleshooting/out-of-inodes). The often-missed inode exhaustion: millions of tiny files, not big ones. - [My VPS is using too much memory. What's wrong?](https://vpsdime.com/knowledgebase/troubleshooting/vps-using-too-much-memory). It probably isn't, how Linux memory really works. - [Why can't I clear the RAM cache?](https://vpsdime.com/knowledgebase/troubleshooting/clear-ram-cache). You don't need to, and here's why. --- Still need a person? You can [open a support ticket](https://vpsdime.com/open-ticket/) any time. --- ## How to troubleshoot anything on your VPS (and where everything logs) URL: https://vpsdime.com/knowledgebase/troubleshooting/troubleshooting-method Last reviewed: 2026-07-02 Summary: The general diagnostic method, reproduce, observe, hypothesize, change one thing, the question-to-command table, and the log atlas: where systemd, nginx, Apache, PHP, MySQL, PostgreSQL, Docker, SSH, cron, certbot, mail, and the rest actually write their logs, with the reading techniques (tail -f, journalctl filters, zgrep) that turn logs into answers. ### What this is The general method behind every specific guide in this category, and the reference half nobody memorizes: **where each popular piece of software writes its logs**, and how to read them. Almost every server mystery ends the same way, someone finally opens the right log and the answer is sitting there in plain text. This page shortens the "finally". ### The method Troubleshooting is a discipline, not a talent: 1. **Reproduce it.** A problem you can trigger on demand is half-solved; "it happens sometimes" means your first job is finding the trigger (or a timestamp). 2. **Observe before changing anything.** Logs, resource state, what's listening, gather the evidence first. Changes made before observation destroy the crime scene. 3. **Check what changed.** Problems rarely appear from nothing. Two tools answer "what changed?" without relying on memory: the panel's **[Tasks tab](https://vpsdime.com/knowledgebase/client-area/services/tasks)** (every panel action, timestamped, including ours) and `/var/log/apt/history.log` (every package installed or upgraded, and when). Line those up against when the trouble started. 4. **Form a hypothesis, change one thing, re-test.** One. Changing three things that "might help" leaves you not knowing which one did, or which one broke something else. 5. **Match the timing against [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs)**, a resource event (CPU plateau, disk cliff, traffic spike) that coincides with the symptom is rarely a coincidence. ### The question-to-command table | Question | Command | Deep guide | |---|---|---| | Is the service even running? | `systemctl status nginx` | [services after reboot](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot) | | What did it say when it died? | `journalctl -u nginx -n 50` | | | What's eating CPU/memory? | `htop`, `ps aux --sort=-%cpu \| head` | [slow VPS](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps) | | Is memory actually short? | `free -h` (the **available** column) | [memory](https://vpsdime.com/knowledgebase/troubleshooting/vps-using-too-much-memory) | | Is the disk full? Inodes? | `df -h` and `df -i` | [disk](https://vpsdime.com/knowledgebase/troubleshooting/disk-full), [inodes](https://vpsdime.com/knowledgebase/troubleshooting/out-of-inodes) | | What's listening on what port? | `ss -tulnp` | [ports](https://vpsdime.com/knowledgebase/troubleshooting/my-port-xxx-is-closed) | | Is the network path the problem? | `mtr -rwbzc 100 ` | [network](https://vpsdime.com/knowledgebase/troubleshooting/network-problems) | | What's happening *right now*? | `journalctl -f`, or `tail -f ` | | | What happened at 3 AM? | `journalctl --since "03:00" --until "03:30"` | | | Was a process OOM-killed? | Linux VPS: [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) reports it (not visible in-guest) | [slow VPS](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps) | ### The log atlas **Start with the journal.** On systemd distros (all our images), most services log to the **journal** first, and `journalctl -u ` is the universal opener. The classic files below still exist for most of these and are what web tutorials reference; both views show the same events. - **The system itself**: `journalctl` (everything), or the classic files, `/var/log/syslog` (Debian/Ubuntu) / `/var/log/messages` (RHEL-family). - **Logins and SSH**: `/var/log/auth.log` (Debian/Ubuntu) / `/var/log/secure` (RHEL), every login, sudo, and failed attempt; `journalctl -u ssh` for the daemon itself. - **nginx**: `/var/log/nginx/error.log` (why something failed, [the 502 decoder](https://vpsdime.com/knowledgebase/troubleshooting/502-503-errors)) and `access.log` (every request: source IP, URL, status code, [the bot hunt](https://vpsdime.com/knowledgebase/troubleshooting/bot-traffic) lives here). - **Apache**: same pair under `/var/log/apache2/` (Debian/Ubuntu) or `/var/log/httpd/` (RHEL). - **Caddy**: everything goes to the journal, `journalctl -u caddy`, including the automatic-HTTPS/ACME conversation when [a certificate won't issue](https://vpsdime.com/knowledgebase/troubleshooting/ssl-certificate-errors). Per-site **access logs are opt-in** (a `log` directive in the Caddyfile, typically to `/var/log/caddy/`) and written as structured JSON, pipe through `jq` for comfortable reading. - **PHP / PHP-FPM**: the gotcha, **PHP application errors usually land in the web server's error log** (or the FPM pool's log, `/var/log/php8.2-fpm.log`), not a "php.log". A white page with nothing in nginx's error log usually means `log_errors` is off in php.ini. - **MySQL / MariaDB**: `/var/log/mysql/error.log` or `journalctl -u mariadb` ([the won't-start guide](https://vpsdime.com/knowledgebase/troubleshooting/mysql-wont-start)); the **slow query log** is separate and off by default ([the performance section](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps)). - **PostgreSQL**: `/var/log/postgresql/postgresql-*.log`. - **Docker**: per-container, `docker logs ` (`-f` to follow, `--tail 50`), and `docker compose logs` for a stack. The daemon itself: `journalctl -u docker`. - **cron**: `grep CRON /var/log/syslog` or `journalctl -u cron`, proof of whether a job fired at all ([the cron guide](https://vpsdime.com/knowledgebase/troubleshooting/cron-not-running)). - **fail2ban**: `/var/log/fail2ban.log`, every ban and unban. - **certbot / Let's Encrypt**: `/var/log/letsencrypt/letsencrypt.log`, the full ACME conversation when [renewal fails](https://vpsdime.com/knowledgebase/troubleshooting/ssl-certificate-errors). - **Mail (Postfix)**: `/var/log/mail.log`, one line per message with its fate ([inbound](https://vpsdime.com/knowledgebase/troubleshooting/cannot-receive-email) and [outbound](https://vpsdime.com/knowledgebase/troubleshooting/emails-going-to-spam) both end up here). - **Redis**: `/var/log/redis/redis-server.log`. - **ufw**: `/var/log/ufw.log` (blocked packets, when logging is on). - **WordPress**: `wp-content/debug.log`, but only after enabling it (`WP_DEBUG` + `WP_DEBUG_LOG` in wp-config.php); otherwise its errors surface in the PHP/web-server logs above. - **Your own apps**: under systemd, `journalctl -u yourapp`; under [pm2](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot), `pm2 logs`; a [scheduled script](https://vpsdime.com/knowledgebase/technical-questions/systemd-timers), wherever you pointed its output, which is why you point it somewhere. (Windows VPS: the equivalent atlas is the Event Log, [viewing and saving it](https://vpsdime.com/knowledgebase/windows-vps/view-save-event-log).) ### Reading techniques - **Follow live while reproducing**, the single most productive move: `tail -f /var/log/nginx/error.log` in one terminal, trigger the problem in another, watch the line appear. `journalctl -f` for journal-based services. - **Filter by severity and time**: `journalctl -p err -b` (errors since boot), `journalctl -u nginx --since "1 hour ago"`. - **Search**: `grep -i error file`, and for rotated logs (`.gz` files logrotate left behind), `zgrep` searches them without unpacking. `less +G file` opens a big log at the end. - **Trust timestamps over memory.** Correlate the log line's time against the Tasks tab, Graphs, and your own actions, "it broke at 14:02 and apt upgraded PHP at 14:01" closes cases. - **Read the line before the error too.** The error is often the symptom; the line above it is often the cause. ### When you've found the line A specific error line is the most valuable object in troubleshooting, three good moves, in order of speed: 1. **Search it verbatim** (quoted, minus your hostname/paths), most error strings have been solved publicly. 2. **Hand it to an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management)** with one sentence of context, exact error lines are what they're best at. 3. **[Ticket it](https://vpsdime.com/knowledgebase/getting-started/raising-a-support-ticket)**, and note the line *is* the machine output the ticket guide asks for: paste it exactly, with the timestamp and what you were doing. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the exact log line or error you found, with its timestamp, - what you were doing (or what changed) when it started. ### Related questions - "Where are the log files on my VPS?" - "Where does nginx / MySQL / PHP / Docker log to?" - "How do I watch a log live while reproducing a problem?" - "How do I see what changed on my server recently?" - "How do I search old rotated logs?" - "What's the general method for debugging a server problem?" --- ## My IP is blocked. How do I unblock it? URL: https://vpsdime.com/knowledgebase/troubleshooting/ip-blocked Last reviewed: 2026-07-03 Summary: What to do when your IP is blocked, banned, or blacklisted and you can't connect to your VPS. There are four layers that can block an IP, our SSH bruteforce firewall, your VPS's own firewall or fail2ban, cPanel's cPHulk, and the managed app-port firewall. How to tell which one it is, the fastest unblock for each, and how to prevent it happening again. ### What this is You (or someone on your team) can't connect to the VPS from a specific IP, while the VPS itself is up and works from other locations. That pattern almost always means an IP block, and there are four separate layers that can produce one. This page tells you how to identify which layer blocked you, the fastest way to unblock at each, and how to stop it recurring. The telltale sign of an IP block, as opposed to the VPS being down: **it works from somewhere else**. Try your phone off Wi-Fi, or run your VPS IP through [ping.pe](https://ping.pe/), which tests it from dozens of locations at once. Green everywhere except your location is the blocked-IP signature. ### The fast path: run the automated check Before diagnosing anything, open [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) (https://vpsdime.com/myvpsisdown). It checks that the VPS is running, **detects whether the connecting IP is banned by our SSH firewall, and unblocks it on the spot**. It fixes the most common cause of this page in under a minute, with no ticket needed. ### Layer 1: our SSH bruteforce firewall (the most common) Our network [bans IPs that accumulate failed password logins](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall) on port 22 of Linux VPS. The usual victim is not an attacker, it's the owner or their developer retrying an outdated password, or a saved session, deployment script, or SFTP client doing it for them in the background. - **Signature:** SSH to port 22 times out or is refused from one IP, everything else works, and the block appeared after failed login attempts. - **Unblock:** [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) auto-whitelists the IP you visit it from. For a teammate's IP (like a developer working from elsewhere), the same page has a whitelist form, you can whitelist up to 10 IPs per VPS. - **Prevent:** switch to [SSH key authentication](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys), keys never trigger the ban because there are no password failures. Whitelist the IPs your team regularly connects from, and fix any script or client that is still trying an old password. ### Layer 2: your VPS's own firewall or fail2ban Software on the VPS itself (ufw, CSF, firewalld, iptables, or fail2ban) can ban IPs too, and it doesn't care that the IP is yours. If you run fail2ban, it does exactly what our firewall does but with your own thresholds. - **Signature:** the block affects services beyond SSH too (or a custom SSH port), and our troubleshooter says your IP is not banned. - **Unblock:** try [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) first, it detects fail2ban, CSF, and sshguard bans on your IP (and manual firewall rules targeting it) and clears them with one click. For anything it doesn't catch, connect through the **[Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps)**, which bypasses the network entirely, and remove the ban by hand. For fail2ban: `fail2ban-client unban 203.0.113.7` (older versions: `fail2ban-client set sshd unbanip `). For CSF: `csf -dr ` removes the deny entry, `csf -a ` whitelists it. For plain firewall lockouts, the exact allow commands per firewall are in [Commands to allow SSH access in common firewalls](https://vpsdime.com/knowledgebase/troubleshooting/allow-ssh-in-common-firewalls). - **Prevent:** whitelist your static IPs in the tool you run (`ignoreip` in fail2ban's jail config, `csf -a` for CSF), and use SSH keys so failed password attempts stop happening. ### Layer 3: cPanel's cPHulk On a VPS running cPanel/WHM, cPHulk brute-force protection can lock the **account** rather than the IP, so the correct root password suddenly fails for both SSH and WHM. - **Signature:** cPanel/WHM server, the password is definitely right, and logins fail from everywhere, not just one IP. - **Unblock and prevent:** the Console commands to clear the lock, and how to whitelist your IPs in cPHulk, are in [cPanel/WHM: root login suddenly fails (cPHulk)](https://vpsdime.com/knowledgebase/troubleshooting/cpanel-cphulk-login-blocked). ### Layer 4: the managed app-port firewall (not actually an IP block) If the "block" is about reaching a **database, cache, or panel port** (MySQL, Redis, MongoDB, and similar) rather than SSH, that's not an IP ban at all. Linux and Storage VPS include a [managed firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall) that blocks the internet from reaching risky app ports by default, for every IP. - **Signature:** SSH works fine, but a specific port refuses connections from outside. - **Fix:** whitelist your IP for that app (or globally) on the Firewall tab of your VPS's manage page. If you're not sure whether a port is blocked or simply has nothing listening, see [My Port XXX is closed](https://vpsdime.com/knowledgebase/troubleshooting/my-port-xxx-is-closed). ### Still need help? If none of the four layers explains it, you can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the blocked IP and the VPS hostname or IP, - what exactly fails (SSH, a specific port, a panel) and the exact error or timeout, - whether it works from other locations, and whether the Console works. ### Related questions - "My developer's IP is blocked, how do I unblock it?" - "My IP got banned from my own server." - "SSH works from my phone but not from my office." - "How do I whitelist our office IP?" - "Why does my IP keep getting blocked?" - "How do I unban an IP in fail2ban or CSF?" --- ## How to restore my SSH access URL: https://vpsdime.com/knowledgebase/troubleshooting/restore-ssh-access Last reviewed: 2026-07-02 Summary: A step-by-step diagnosis when you can't SSH into your VPS, check whether the VPS is actually up, whether your IP was banned for failed logins, whether your own firewall is blocking you (fix it over the Console), and whether sshd itself is down. ### What this is You can't SSH into your VPS. Work through these steps in order, they're arranged from most to least likely, and every one of them is self-service. ### Step 0: run the automated check [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) (https://vpsdime.com/myvpsisdown) does the first half of this page for you: it checks whether the VPS is running and reachable, **detects whether your own IP was banned** by our SSH firewall and whitelists it automatically, and can re-enable SSH password login or reset the password. Run it first; if it fixes the cause, you're done. ### Step 1: is your IP banned? Our network [bans IPs that rack up failed password logins](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall) on port 22, and the most common victim is the owner retrying an out-of-date password (or a script doing it for them). The telltale sign: **SSH times out or is refused from your machine, but the VPS is up** and reachable from elsewhere (run the IP through [ping.pe](https://ping.pe/), which pings it from dozens of locations at once, green everywhere but dead for you is the banned-IP signature, or try your phone off Wi-Fi). The troubleshooter above unblocks you automatically, and can whitelist your IPs permanently. ### Step 2: is it your own firewall? If you recently installed or reconfigured a firewall (ufw, CSF, firewalld, iptables) and lost SSH, or lost it after a reboot when the firewall came back up without an SSH rule, this is the cause. Fix it through the **[Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps)** in your client area, which connects to the VPS's screen directly and doesn't care about network rules: 1. Open the Console and log in as `root`. 2. Allow SSH in whichever firewall you run, the exact commands for each are in [Commands to allow SSH access in common firewalls](https://vpsdime.com/knowledgebase/troubleshooting/allow-ssh-in-common-firewalls). 3. If you're not sure which firewall you installed, the same page has the stop commands, stop them one by one until access returns, then configure the one you actually use properly. ### Step 3: is SSH itself running? Still in the Console: ``` systemctl status ssh # Debian/Ubuntu systemctl status sshd # RHEL-family (Alma, Rocky) ``` If it's stopped, `systemctl start ssh` (or `sshd`). If it refuses to start, you likely have a typo in `/etc/ssh/sshd_config`, run `sshd -t` to see exactly which line is broken, fix it, and start the service again. ### Step 4: ask us If none of that restores access, run [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) to the end, it escalates into a support ticket with the diagnostics already attached, which gets you a useful first reply fastest. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP and the IP you're connecting from, - what happens when you try to SSH (timeout, refused, wrong password), copied exactly, - whether the Console works. ### Related questions - "I can't SSH into my VPS, what do I check?" - "SSH times out but my VPS is online." - "I installed a firewall and lost SSH access." - "How do I get in when SSH is broken?" - "sshd won't start after I edited the config." --- ## Commands to allow SSH access in common firewalls URL: https://vpsdime.com/knowledgebase/troubleshooting/allow-ssh-in-common-firewalls Last reviewed: 2026-07-02 Summary: The exact commands to allow SSH (port 22, or your custom port) in ufw, CSF, firewalld, iptables, and nft, plus the stop commands for each, for when you've locked yourself out and are fixing it over the Console. ### What this is You installed or reconfigured a firewall on your VPS and lost SSH access (immediately, or after a reboot). Log in through the **[Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps)** in your client area, which works regardless of network rules, and run the commands for your firewall. Replace `22` with your port if you [changed the SSH port](https://vpsdime.com/knowledgebase/technical-questions/change-ssh-port). ### First, understand the default input policy (the bit everyone misses) Every firewall has a **default policy** for inbound packets that match no rule: accept them, or drop them. This single setting explains most lockouts: - **ufw, CSF, and firewalld default to deny inbound** the moment they're enabled. That's why turning one on *without an SSH allow rule already in place* locks you out instantly, there's no rule blocking you, there's just no rule allowing you, and the default does the rest. - **With raw iptables/nft, flushing rules is not enough if the policy is DROP.** `iptables -F` removes the rules but keeps the policy, so you stay locked out. You must also reset the policy: `iptables -P INPUT ACCEPT`. - **Check where you stand** before assuming: `iptables -L INPUT -n | head -1` prints `(policy ACCEPT)` or `(policy DROP)`; `ufw status verbose` shows `Default: deny (incoming)`; CSF and firewalld are deny-inbound by design. Default-deny inbound is the **right** posture for a server ([we recommend it](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps)), the discipline it demands is simply that the SSH allow rule exists **before** the policy takes effect. ### Allow SSH **ufw** ``` ufw allow 22/tcp ``` **CSF** Edit `/etc/csf/csf.conf`, add `22` to the `TCP_IN` list (matching the existing comma-separated format), save, then apply: ``` csf -r ``` **firewalld** ``` firewall-cmd --permanent --add-port=22/tcp firewall-cmd --reload ``` **iptables** ``` iptables -I INPUT -m tcp -p tcp --dport 22 -j ACCEPT ``` (Then save the ruleset the way your distro persists it, e.g. `netfilter-persistent save`, or the rule is gone on reboot.) **nft** (replace `inet filter` with your table if it differs) ``` nft add rule inet filter input tcp dport 22 ct state new accept ``` ### Not sure which firewall you have? Stop them Run these until access returns, then set up the one you actually use properly: ``` csf -x # CSF systemctl stop ufw # ufw systemctl stop firewalld # firewalld iptables -F && iptables -P INPUT ACCEPT # raw iptables: flush + reset policy ``` (Note the iptables line does both: `-F` alone doesn't restore access when the default input policy is DROP, the `-P INPUT ACCEPT` is the half people forget.) Stopping a firewall is a diagnosis step, not a fix, once you're back in, re-enable it with an SSH rule in place. And remember your VPS still sits behind our [managed network firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall) for the highest-risk app ports either way. ### Avoid the next lockout - Add the SSH rule **before** enabling a new firewall (before the default-deny policy takes effect), and keep your current session open while you test a fresh connection from a second terminal. - ufw users: `ufw allow 22/tcp` first, `ufw enable` second. In that order. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which firewall you run (ufw, CSF, firewalld, iptables, nft) and the command you tried, - whether the Console still gets you in. ### Related questions - "How do I allow SSH in ufw / CSF / firewalld / iptables / nft?" - "I enabled a firewall and locked myself out, what now?" - "How do I stop a firewall I can't identify?" - "How do I open my custom SSH port in the firewall?" - "What is the default input policy, and why am I still locked out after flushing iptables?" --- ## WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED URL: https://vpsdime.com/knowledgebase/troubleshooting/host-identification-changed Last reviewed: 2026-07-02 Summary: The scary SSH warning is normal after reinstalling your VPS, the OS regenerates its host key and your computer notices the mismatch. Remove the old key with ssh-keygen -R and reconnect. When you haven't reinstalled, treat it seriously. ### What this is You try to SSH in and get a wall of `@` symbols shouting: ``` @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! ... Host key verification failed. ``` ### Why it happens Every SSH server has a **host key** that identifies it, and your computer saves it (in `~/.ssh/known_hosts`) the first time you connect. When you [reinstall your VPS](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os), the fresh OS generates a **new** host key. Your computer sees the same IP presenting a different identity, exactly what a man-in-the-middle attack would look like, and refuses to connect. Scary wording, routine cause. ### The fix Remove the old key for your VPS, using the same address you SSH with (IP or hostname): ``` ssh-keygen -R YOUR.VPS.IP ``` Then connect again and accept the new key at the prompt. That's it. (The warning message also names the exact `known_hosts` line if you'd rather delete it by hand.) ### When to take it seriously If you get this warning and you **haven't** reinstalled the VPS (and we haven't notified you of maintenance that would explain it), don't just bypass it, verify before typing your password anywhere. Log in through the **[Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps)** (which doesn't go over SSH), compare the server's actual host key fingerprint (`ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub`) with what the warning shows, and if they don't match, [contact us](https://vpsdime.com/open-ticket/). ### Related questions - "What does REMOTE HOST IDENTIFICATION HAS CHANGED mean?" - "I reinstalled my VPS and now SSH refuses to connect." - "How do I fix host key verification failed?" - "Is the host key warning an actual attack?" --- ## cPanel/WHM: root login suddenly fails (cPHulk) URL: https://vpsdime.com/knowledgebase/troubleshooting/cpanel-cphulk-login-blocked Last reviewed: 2026-07-02 Summary: On a VPS running cPanel/WHM, the correct root password can suddenly stop working for SSH and WHM because cPHulk brute-force protection locked the account after someone's failed attempts. How to get in, disable or tune cPHulk, and whitelist your IP. ### What this is Your VPS runs **cPanel/WHM**, and the root password that worked yesterday is suddenly rejected on SSH or WHM, sometimes intermittently. In almost every case that's **cPHulk**, cPanel's built-in brute-force protection: when bots hammer your server with failed root logins (which happens to every public server), cPHulk locks the root account, and then rejects even the **correct** password, including yours. ### Get back in The lock is on the account, not on the machine, so use the **[Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps)** in your client area (it authenticates through the VPS's screen, and a reboot from the panel also clears the immediate lock). Once you're in as root, either: - **Disable cPHulk** entirely: ``` /usr/local/cpanel/bin/cphulk_pam_ctl --disable ``` - Or keep it, but **tune it** in WHM under **Security Center → cPHulk Brute Force Protection**: whitelist your own IPs so your logins can never be locked out, and let it keep punishing everyone else. ### Our take cPHulk locking root out of its own server is a known nuisance. If you keep it enabled, **whitelisting your IPs is essential**, otherwise every bot wave can lock you out again. If you'd rather not play that game, disable cPHulk and rely on [SSH keys](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps) plus our network's own [port-22 brute-force firewall](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall), which blocks attackers' IPs without ever locking your account. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - whether the correct password fails on SSH, WHM, or both, - whether the Console still gets you in. ### Related questions - "My root password stopped working after installing cPanel." - "Why can't I log in to WHM or SSH with the correct password?" - "How do I disable cPHulk?" - "How do I whitelist my IP in cPHulk?" --- ## Understanding and troubleshooting network problems URL: https://vpsdime.com/knowledgebase/troubleshooting/network-problems Last reviewed: 2026-07-05 Summary: How to find out where a network problem actually lives, your side, ours, or a carrier in between, with a short primer on hops and routing, what normal latency looks like, how to run and correctly read mtr, testing both directions (including our Looking Glass), and what evidence to put in a ticket. ### What this is Your VPS feels slow, laggy, or drops packets, and the honest first question is **where** the problem lives: your network, our network, or one of the carriers in between. This page gives you the mental model and the tools to answer that in about ten minutes, which is also exactly the evidence that lets us act on a ticket immediately instead of asking you for it. ### How your packets actually get here The internet is a chain of routers. A packet from your laptop to your VPS passes through **hops**: your device → your home router → your ISP's routers → one or more **transit carriers** (the long-haul networks that connect ISPs together) → our network's edge → your VPS. Three things about that chain explain most confusion: - **Every hop is owned by someone different.** Your ISP owns the first few, carriers own the middle, we own the last ones. A fault at any hop affects everything *after* it, which is exactly what lets you locate it. - **The path back can be different.** Routing is chosen independently in each direction (asymmetric routing), so "there" can be clean while "back" is broken. That's why we test both directions. - **Distance is physics.** Packets travel at a large fraction of the speed of light and still need time: same-city pings run a few ms, cross-continent 60 to 90 ms, transatlantic 70 to 100 ms, US to Asia 150 ms or more. High latency to a server far away isn't a fault, it's geography. ### First, scope the problem Two minutes of scoping saves an hour of tracing: - **Is it just this VPS, or everything you browse?** If other sites feel bad too, look at your own connection first. - **Is it just your location?** Try your phone on **mobile data** (not Wi-Fi), and above all run your VPS IP through **[ping.pe](https://ping.pe/)**: it pings (and can mtr) your IP from **dozens of locations worldwide at once**, and the pattern is an instant verdict: - **Green from every probe:** the VPS and our network are fine, the problem is your connection or your ISP's path to us. - **Red from every probe:** something is genuinely down, the VPS itself or a real problem on our side. Check the [status page](https://vpsdime.com/service-status), run [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter), and ticket us. - **Bad from some regions, fine from others:** a mid-path or regional routing problem, exactly what the mtr section below pins down. - **Is the VPS itself up and healthy?** Check the panel and the [Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps). A box that's swapping, pinned on CPU, or [out of traffic](https://vpsdime.com/knowledgebase/acceptable-use/bandwidth-overage) feels exactly like a network problem. - **Anything on our side?** Check the [service status](https://vpsdime.com/service-status) page, and remember a VPS under [DDoS gets null-routed](https://vpsdime.com/knowledgebase/acceptable-use/ddos-policy), which looks like total unreachability. One more scoping distinction: this page is about **lag, jitter, loss, and unreachability**. If your complaint is transfer **speed** (slow downloads/uploads, "I'm not getting the bandwidth"), that's a throughput question, see [Testing your VPS network speed](https://vpsdime.com/knowledgebase/troubleshooting/testing-network-speed) for speedtest CLI, our test files, and iperf3. ### The VPS can't reach one specific remote service A special case worth settling early: the VPS's internet works fine, but **one particular destination** won't connect, an API, a mail server, a payment gateway, a site. Know this first: **we don't filter or block any outbound connectivity at the network level**, none, on any product. So an outbound connection that fails is one of three things: 1. **The remote side is blocking it.** By far the most common. Many services rate-limit or refuse **datacenter IP ranges** wholesale (streaming platforms, some banks and APIs), or blocklist IPs on reputation. The signature: the same request works from your home connection but not from the VPS. The fix lives with the remote service (their support, or an allowlist request), there's no setting on our side that causes or cures it. 2. **A firewall inside your own VPS.** ufw, iptables, or a security tool you installed can block outbound; `iptables -L OUTPUT -n` shows if so. 3. **DNS**, if the failure is "could not resolve host" rather than a refused or timed-out connection, that's [its own guide](https://vpsdime.com/knowledgebase/troubleshooting/temporary-failure-resolving). Two commands settle where it fails: `nc -vz remote.host 443` (does TCP connect?) and `curl -v https://remote.host/` (what happens above TCP?). A timeout to one host while others connect fine, from a VPS that's otherwise healthy, points at the remote side, test the same destination from another network to confirm. ### No outbound connection timeouts imposed by VPSDime Related reassurance, stated plainly because the question comes up with long-running work: **we impose no time limits on outbound connections from your VPS.** A long API call, a streaming response, a websocket held open for hours, none of it is intercepted, proxied, or terminated by our network; there's no middlebox between your VPS and the internet cutting flows at some duration. So when a long-running request dies with an error like **`ERR_STREAM_PREMATURE_CLOSE`** (or `ECONNRESET`, a broken pipe mid-stream), the cause is one of the parties actually on the connection: the **remote server** (idle and duration limits on their load balancers and proxies are common, and much shorter than people expect), **your own application** (its HTTP client's timeout, a worker recycled mid-request), or a fault somewhere on the network path, the thing the rest of this page diagnoses. It is not a VPSDime policy, there isn't one to tune, whitelist, or lift. One practical tip for connections that sit **idle** for long stretches: enable keepalives in the client (TCP keepalive, or protocol-level pings on websockets), since remote-side equipment routinely drops flows that go quiet, and a keepalive is what marks the connection as alive. ### Corporate and ISP firewall block pages The mirror image of the case above: you (or your users) try to open a service hosted on your VPS and get a **branded block page**, FortiGuard, Cisco Umbrella, Sophos, or similar, instead of your site. That page is the confession: a **security appliance on the network path between the visitor and your VPS** intercepted the request, typically an office or school network's firewall, or an ISP running content filtering. Neither your VPS nor our network produces pages like that. The usual trigger is the domain being **new**: these filters categorize the web, and a freshly registered or "newly observed" domain sits in a suspicious-by-default category for days until the vendor classifies it, which is why a brand-new site works everywhere except from the office. - **Confirm in one move:** open the same URL from a different connection, a phone on **mobile data** is perfect. Loads fine there? The VPS is reachable and the block lives in the filtering network. - **Fix it at the filter:** every major vendor has a public recategorization/review form (searching "FortiGuard recategorize" or the equivalent finds it), submissions on a legitimate site are usually processed within days. On a corporate network, the local IT admin can also whitelist the domain immediately. - Nothing on the VPS or in our network can cure this, the block sits in front of the visitor, not in front of the server. ### ping: the quick health check ``` ping YOUR.VPS.IP ``` Three numbers matter: **latency** (judge it against the geography above, not against zero), **jitter** (latency bouncing around, bad for games and calls even when the average looks fine), and **packet loss** (any sustained loss is worth investigating). Ping tells you *whether* something is wrong; it can't tell you *where*. For that: ### mtr: the tool that settles it mtr is traceroute and ping combined: it pings **every hop** on the path continuously, so you can see where trouble starts. - **Linux/macOS:** install it (`apt install mtr` / `brew install mtr`), then run a proper sample: `mtr -rwbzc 100 YOUR.VPS.IP` (100 rounds, report form, with hostnames and AS numbers). - **Windows:** use [WinMTR](https://sourceforge.net/projects/winmtr/), enter the IP, let it run to at least 100 sent, then Export TEXT. #### How to read it (this is the part everyone gets wrong) 1. **Loss only counts if it continues to the final hop.** Routers deprioritize replying to pings when busy, so a middle hop showing 20% loss while the destination shows 0% means that router is lazy about ICMP, **not** that your traffic is being dropped. Real loss starts at some hop and **persists on every hop after it, including the last**. 2. **A latency spike at a single hop means nothing** unless the hops after it inherit it. Same reason: the router answered your probe slowly but forwards real traffic at full speed. 3. **`???` hops are normal.** Some routers never answer probes. If later hops respond, the path is fine. 4. **Watch where the handoffs happen.** The hostnames/AS numbers show the chain: your ISP's names first, then carrier names (Cogent, Lumen, Telia, and so on), then ours. Where the problem starts tells you whose network it starts in. ### Test both directions Because return routing can differ, one mtr is half a diagnosis: - **Forward:** mtr from your machine to the VPS IP (above). - **Reverse:** mtr from the VPS back to your IP, install mtr on the VPS and run `mtr -rwbzc 100 YOUR.HOME.IP` (find your IP on any "what is my IP" site). If the VPS is unreachable, use our **[Looking Glass](https://vpsdime.com/looking-glass)** instead, it runs ping and mtr **from our network** toward any IP, giving you the from-our-side view without touching the VPS. ### Reading the verdict - **Trouble starts in the first hops** (your router, your ISP's early hops) and appears toward every destination you test: it's local, your Wi-Fi, router, or ISP. Test on a wire, reboot the router, then take the evidence to your ISP. - **Trouble starts mid-path at a carrier and persists to the end:** a transit issue between your ISP and us. Send us both MTRs, **sometimes we can adjust routing with our carriers**, though mid-path issues are often outside anyone's direct control and get fixed by the carrier itself. - **Trouble starts in the final hops, inside our network:** that's ours. Send the MTRs and we'll get on it. - **Everything is clean but the VPS still feels slow:** the network isn't the problem, look at the VPS itself ([memory](https://vpsdime.com/knowledgebase/troubleshooting/vps-using-too-much-memory), CPU, disk, the app). ### What to put in the ticket - **Both MTRs**, at least 100 cycles each, pasted **as text** (not screenshots), - the **timestamps** of when you ran them and when the problem happens (constant, or specific hours?), - your **source IP** and the VPS involved. With that, we can identify the faulty hop on the first read. If the VPS is fully down rather than slow, run [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) instead, it checks the VPS and walks you through attaching a trace when escalating. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP and the IP you're testing from, - both MTRs (at least 100 cycles each, pasted as text), - when it happens (constant, or specific hours). ### Related questions - "How do I tell if lag is my ISP's fault or the VPS's?" - "How do I run and read an mtr report?" - "Why does one hop show packet loss but my connection works?" - "What is a hop, and why do middle hops time out?" - "Is 100 ms ping to my VPS normal?" - "How do I test the network path from your side?" - "What network evidence should I include in a ticket?" - "Why can't my VPS connect to one specific site or API?" - "Do you block outgoing connections from my VPS?" - "Why do I see a FortiGuard or Cisco Umbrella block page instead of my site?" - "My new domain is blocked on my office network but works on mobile data." - "Do you terminate long-running or idle connections from my VPS?" - "What causes ERR_STREAM_PREMATURE_CLOSE on my VPS?" --- ## Testing your VPS network speed (speedtest CLI, test files, iperf3) URL: https://vpsdime.com/knowledgebase/troubleshooting/testing-network-speed Last reviewed: 2026-07-02 Summary: How to measure your VPS's real throughput, Ookla's Speedtest CLI on the server, our Looking Glass test files (100MB/1GB/10GB per location), and iperf3 between machines you control, plus how to interpret single-stream vs multi-stream results and distance effects before concluding "the port is slow". ### What this is How to measure your VPS's actual **throughput**, and how to read the numbers before concluding something is slow. (If your problem is lag, jitter, or packet loss rather than transfer speed, that's the [network problems guide](https://vpsdime.com/knowledgebase/troubleshooting/network-problems), the two pair well.) ### What to expect before you test - Your VPS sits on a fast **10 Gbps uplink**, but a speed test never measures "the port" in isolation, it measures the whole path to whatever server you test against, and the slowest link on that path wins. - **A single TCP connection slows down with distance.** That's TCP physics (latency limits how fast one stream can ramp), so one stream to a nearby server can pull gigabits while one stream across the Atlantic pulls far less, on a perfectly healthy connection. **Multiple parallel streams** show the real capacity. - **Testing from home measures your home line.** If your home plan is 100 Mbit, every download from your VPS tops out there, that's not the VPS. ### Method 1: Speedtest CLI on the VPS Ookla's official CLI is the quickest meaningful test. Install it on the VPS (their [install instructions](https://www.speedtest.net/apps/cli) cover every distro), then: ``` speedtest ``` It picks a nearby server and reports down/up/latency. Two tips: test against a **nearby** server first (that's the fair test of the VPS's connection), and if you want a specific target, list servers with `speedtest -L` and pick one with `-s ID`. Skip the older community `speedtest-cli` Python script, it underreports at high speeds. ### Method 2: our Looking Glass test files The [Looking Glass](https://vpsdime.com/looking-glass) publishes **100MB, 1GB, and 10GB test files for each of our locations** (for example `https://lg.dallas.vpsdime.com/1GB.test`, pick your location on the page). - **From your home browser:** downloading one tests the path **from our network to you**, this is the number to check before ordering, or when "downloads from my VPS are slow at home". - **From a VPS:** `wget -O /dev/null https://lg.dallas.vpsdime.com/1GB.test` tests between our locations or from another provider's box. One caution: **test downloads count against your VPS's monthly [traffic allowance](https://vpsdime.com/knowledgebase/acceptable-use/bandwidth-overage)** like any other transfer, prefer the 1GB file for routine checks and save the 10GB one for when you need it. ### Method 3: iperf3 between machines you control For measuring one specific path properly (VPS to VPS, VPS to office), iperf3 is the gold standard, run both ends yourself: ``` iperf3 -s # on the receiving machine iperf3 -c OTHER.HOST -P 4 # from the sending machine, 4 parallel streams iperf3 -c OTHER.HOST -P 4 -R # same, reversed direction ``` `-P 4` (or 8) shows path capacity rather than single-stream TCP behavior, and `-R` matters because [the two directions can differ](https://vpsdime.com/knowledgebase/troubleshooting/network-problems). Open TCP port 5201 in your own firewall on the server side for the test, and close it after. ### Reading the results - **One stream slow, parallel streams fast:** normal TCP-over-distance behavior, not a fault. Judge capacity by the parallel number. - **Slow to one destination, fast to others:** a path/peering issue toward that destination, run [mtr both ways](https://vpsdime.com/knowledgebase/troubleshooting/network-problems) and send us the traces. - **Slow everywhere, tested from home:** test from the VPS itself (Method 1); if the VPS tests fine, the bottleneck is your local line. - **Genuinely slow from the VPS to nearby servers too:** now it's worth a [ticket](https://vpsdime.com/open-ticket/), include the speedtest/iperf3 outputs, which server you tested against, when, and an mtr. ### Related questions - "How do I run a speed test on my VPS?" - "Why is a single download from my VPS slow?" - "Do you have test files I can download?" - "How do I test bandwidth between two servers with iperf3?" - "Does speed testing use up my traffic allowance?" --- ## My Port XXX is closed. Can you open it? URL: https://vpsdime.com/knowledgebase/troubleshooting/my-port-xxx-is-closed Last reviewed: 2026-07-05 Summary: We don't block arbitrary ports, everything is open by default except a short list of high-risk app ports you can whitelist. A port only shows "open" to checker tools when something is actually listening on it, and the closed-vs-filtered distinction (REJECT vs DROP) tells you exactly what's in the way. ### What this is The short answer: **there's almost certainly nothing for us to open.** We don't filter arbitrary ports, inbound traffic to your VPS is allowed on every port by default, with one exception: a short, deliberate list of high-risk application ports (databases, caches, and similar) blocked at our network edge, which you can open to chosen IPs yourself via the **Per-Application Whitelist**. The full list and how-to is in [the VPS firewall guide](https://vpsdime.com/knowledgebase/client-area/services/firewall). SSH, web, mail, game servers, VPNs, and every custom port: untouched by us. So when a port "is closed", the cause is on the VPS, and it's nearly always the next section. ### A port is only "open" if something is listening This is the part every port-checker website quietly assumes and never explains: **"open" means a program accepted the connection.** There is no switch that makes a port open on its own, a port with no service listening on it reports **closed** even with every firewall in the world turned off. Checker tools don't test "is this port allowed", they test "did anything answer". So before any firewall thinking, confirm a listener exists: ``` ss -tulnp | grep :25565 ``` You want a `LISTEN` line, and on `0.0.0.0` (or a public address), a service bound to `127.0.0.1` is invisible from outside by design ([that's usually correct](https://vpsdime.com/knowledgebase/getting-started/securing-public-services), make sure it's wrong before changing it). No LISTEN line? Start the service; that *is* the fix. And test from **outside** the VPS (your machine, not localhost), a localhost test passes things the internet can't reach. ### Closed vs filtered: what the checker is really telling you Here's the technical distinction that turns a checker result into a diagnosis. When a TCP connection attempt arrives at a port, three things can happen: - **Nothing is listening** → the kernel answers immediately with a **RST** ("go away"). Checkers report **closed**, clients say **"connection refused"**, and crucially, the answer is *instant*. An instant refusal means your packet **reached the machine**, no firewall ate it; there's simply no service there. - **A firewall REJECTs** → the packet is refused with an active response (RST or an ICMP unreachable). Looks nearly identical to the above: instant, "refused", nmap says **closed**. Polite, fast, and it tells scanners the host exists. - **A firewall DROPs** → the packet is silently discarded, no answer at all. The client waits and eventually **times out**; nmap reports **filtered**. Silence is the signature of a firewall. The rule of thumb that falls out: **"refused" = reachable but nothing listening; "timeout/filtered" = something is dropping packets.** A drop is either a firewall inside your VPS (most default-deny setups DROP, see [default input policy](https://vpsdime.com/knowledgebase/troubleshooting/allow-ssh-in-common-firewalls)) or, for the ports on our blocked list only, our edge firewall awaiting a [whitelist entry](https://vpsdime.com/knowledgebase/client-area/services/firewall). ### Testing through a domain? Cloudflare filters ports One special case produces a "closed" port with nothing wrong on the VPS at all: the domain you're testing through is **proxied by Cloudflare** (orange-clouded). Cloudflare's proxy only forwards a **fixed set of ports**, 80 and 443 plus a short list of alternates (8080, 8443, and a few others), and a request to any other port, say a control panel on **8083** (HestiaCP's default), never reaches your VPS: it dies at Cloudflare's edge as a timeout, looking exactly like a filtered port. The tell is a one-line test: try the **direct IP**. If `domain:8083` times out but `YOUR.VPS.IP:8083` connects, the port is fine and Cloudflare is the "firewall". Three ways out, in order of preference: - **Put the service behind your web server on 443** (a reverse-proxied subdomain), which keeps it proxied and protected; - **use the direct IP** for that service and leave the DNS as is; - **switch that record to DNS only** (grey cloud) so the domain resolves straight to the VPS, remembering that this reveals the VPS's IP, which matters if you rely on [Cloudflare hiding it](https://vpsdime.com/knowledgebase/getting-started/cloudflare-best-practices). ### The 60-second checklist 1. **Is anything listening?** `ss -tulnp | grep :`, LISTEN on a public address. If not, start/fix the service ([a proxy answering for a dead app is its own story](https://vpsdime.com/knowledgebase/troubleshooting/502-503-errors)). 2. **Your own firewall.** If you run ufw/firewalld/iptables, allow the port, and remember the [default-deny policy](https://vpsdime.com/knowledgebase/troubleshooting/allow-ssh-in-common-firewalls) blocks everything you haven't allowed. 3. **On our blocked list?** Only then does our firewall apply, add your source IP to the [Per-Application Whitelist](https://vpsdime.com/knowledgebase/client-area/services/firewall). 4. **Test from outside, against the IP**: `nmap -Pn -p YOUR.VPS.IP` from your own machine, and read the result with the closed-vs-filtered rule above. Test the **IP**, not the domain, a Cloudflare-proxied domain filters ports on its own (previous section). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP and the port, - the `ss -tulnp` line for that port (or that there isn't one), - whether the outside test is refused instantly or times out. ### Related questions - "Can you open port XXX for me?" - "Do you block any ports?" - "The port checker says my port is closed even though the firewall is off." - "What's the difference between connection refused and connection timed out?" - "What does filtered mean in nmap?" - "Why is my port closed when nothing is blocking it?" - "Why does my port work on the IP but not through my domain?" - "Does Cloudflare block non-standard ports like 8083?" --- ## Bots and crawlers are hammering my website URL: https://vpsdime.com/knowledgebase/troubleshooting/bot-traffic Last reviewed: 2026-07-02 Summary: When scrapers, AI crawlers, and bad bots eat your CPU and traffic allowance, how to identify them in the access log, what robots.txt can and can't do, rate limiting in nginx, fail2ban for the abusive tail, and Cloudflare's bot tools as the heavy artillery. ### What this is Your [traffic allowance](https://vpsdime.com/knowledgebase/acceptable-use/bandwidth-overage) is draining, or the [CPU graph climbed](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps), and the visitors aren't human. Automated clients, search crawlers, **AI training and scraping bots**, SEO tools, vulnerability scanners, and plain scrapers, now make up a very large share of all web traffic, and a small site can receive more bot requests than human ones. Most are harmless at low volume; the problem is the aggressive tail. Here's how to see who's hitting you and how to push back proportionately. ### Step 1: identify the culprits in the access log The access log has everything. Two summaries answer most questions: ``` # Top requesting IPs awk '{print $1}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head -20 # Top user agents awk -F'"' '{print $6}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head -20 ``` (For an ongoing view, `goaccess /var/log/nginx/access.log` gives you a live terminal dashboard from the same data.) What you'll typically find: named crawlers (`Googlebot`, `bingbot`, `GPTBot`, `ClaudeBot`, `Amazonbot`, `Bytespider`, assorted `*-AI` agents), SEO crawlers (`AhrefsBot`, `SemrushBot`, `MJ12bot`), and the shadier end, blank or fake user agents from rotating IPs. Decide what you actually mind: Googlebot is usually earning its keep; an AI scraper pulling your entire catalog every night on your bandwidth may not be. ### Step 2: robots.txt, the polite request `robots.txt` is a **request, not a control**: legitimate crawlers honor it, abusive ones ignore it, so it's the right tool exactly for the named, well-behaved bots: ``` User-agent: GPTBot Disallow: / User-agent: AhrefsBot Disallow: / ``` Also set `Crawl-delay` for bots that honor it, and make sure you're not wasting crawl budget on infinite URL spaces (calendars, faceted filters), those make even polite bots look like floods. ### Step 3: rate limiting, the enforced request For clients that ignore robots.txt, make the server enforce a budget. nginx's built-in limiter, applied per IP: ``` # in http {} limit_req_zone $binary_remote_addr zone=perip:10m rate=5r/s; # in the server/location block limit_req zone=perip burst=20 nodelay; ``` Humans browse well under 5 requests/second; scrapers slam into it and get 503s instead of your rendered pages. This alone converts most floods from a CPU problem into a log line. (Caddy and Apache have equivalents.) ### Step 4: fail2ban for the abusive tail For IPs that keep hammering after being limited, ban them at the firewall: a fail2ban jail watching the access log for repeated 403/503s (or requests to paths like `/wp-login.php` and `/.env` that only scanners touch) turns the pattern into a temporary IP ban automatically. This pairs with, not replaces, the rate limit. ### Step 5: Cloudflare, the heavy artillery If the traffic is distributed (thousands of IPs, fake agents), per-IP tools run out of road, and this is exactly what [Cloudflare's](https://www.cloudflare.com/) free tier is built for: **Bot Fight Mode**, managed challenges for suspicious clients, per-path WAF rules ("challenge everything hitting /api at >n/min"), and their **AI crawler blocking** toggle that handles the whole scraper category in one switch. Bonus: challenged bots never reach your VPS at all, so they stop costing you [traffic](https://vpsdime.com/knowledgebase/acceptable-use/bandwidth-overage) entirely, cached-and-challenged at the edge beats rate-limited at the origin. New to Cloudflare? The full setup, done right, is in [Cloudflare best practices](https://vpsdime.com/knowledgebase/getting-started/cloudflare-best-practices). ### Keep perspective - Check the damage honestly on your [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs): a bot wave that costs 2 GB and 3% CPU needs robots.txt, not an arms race. - Bots hunting `/wp-login.php`, `/xmlrpc.php`, and `/.env` aren't a traffic problem but a [security probe](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps), make sure those paths are locked or absent rather than just rate-limited. - If what you're seeing isn't crawling but a flood meant to take you down, that's the [DDoS lane](https://vpsdime.com/knowledgebase/acceptable-use/ddos-policy). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS and the site being hammered, - the top IPs or user agents from your access log, - what you've already put in place (robots.txt, rate limiting, Cloudflare). ### Related questions - "Bots are eating my bandwidth, how do I stop them?" - "How do I see which bots are crawling my site?" - "Does robots.txt actually block crawlers?" - "How do I block AI crawlers like GPTBot?" - "How do I rate limit requests in nginx?" - "Should I use Cloudflare to stop bot traffic?" --- ## Emails from my VPS go to spam URL: https://vpsdime.com/knowledgebase/troubleshooting/emails-going-to-spam Last reviewed: 2026-07-02 Summary: Why mail from a VPS lands in spam and how to fix it yourself, diagnose in minutes with mail-tester.com, Gmail's Show Original, and MXToolbox, then fix the foundations, reverse DNS matching your hostname, SPF, DKIM, and DMARC, warm up reputation, and know when a sending service is the right tool. ### What this is Your VPS sends mail, but it lands in spam folders, or bounces outright. Deliverability comes down to three things receivers check: **identity** (does DNS prove who you are), **reputation** (does your IP and domain have a history), and **content**. Almost all of it is diagnosable and fixable yourself, and this page starts with the tools that tell you *exactly* what's wrong, faster than any support ticket could. First, the ground rule: this guide is for the mail that's [allowed on our network](https://vpsdime.com/knowledgebase/acceptable-use/email-policy), personal, team, and transactional sending. If your volume is real, the honest fix is at the bottom. ### Diagnose it in five minutes (before anything else) Three free tools pinpoint the problem, use them in this order: 1. **[mail-tester.com](https://www.mail-tester.com/)**, the single best test. It gives you a one-time address; send a message to it **from your VPS the same way your app sends**, and you get a score out of 10 with an itemized list of everything wrong: missing SPF, broken DKIM, absent rDNS, blocklist hits, content flags. Fix what it lists, retest. 2. **Gmail's "Show original"**, if Gmail is where your mail lands in spam. Open the message → three-dot menu → **Show original**: the top block shows `SPF: PASS/FAIL`, `DKIM: PASS/FAIL`, `DMARC: PASS/FAIL` for your actual mail. Anything not PASS is your to-do list. 3. **[MXToolbox](https://mxtoolbox.com/blacklists.aspx)**, check whether your **VPS IP and your domain** sit on any blocklist, and use its SPF/DKIM/DMARC lookups to verify the records you publish. (Sending serious Gmail volume? [Google Postmaster Tools](https://postmaster.google.com/) shows your reputation with them directly. For an interactive walk-through of how your records evaluate, [learndmarc.com](https://www.learndmarc.com/) is excellent.) ### The foundation: your identity must line up Receivers first check that the sending server is who it claims to be. Three names must agree: - Your mail server's **hostname** (what it says in the SMTP `HELO`, e.g. `mail.yourdomain.com`), - the **reverse DNS (PTR)** of your VPS IP, set it yourself from the [Network](https://vpsdime.com/knowledgebase/client-area/services/network) tab to that same hostname, - and the **A record** of that hostname pointing back at your VPS IP. That loop (forward-confirmed reverse DNS) is table stakes: without it, many receivers junk or refuse your mail no matter what else is right. ### The authentication trio All three are DNS records at [wherever your domain's DNS lives](https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain): - **SPF**, a TXT record on your domain declaring which IPs may send for it: `v=spf1 a mx ip4:YOUR.VPS.IP ~all`. One SPF record only, multiple ones break validation. - **DKIM**, your server signs outgoing mail and you publish the public key as a TXT record. Your mail stack generates the key pair ([Mailcow does it for you](https://vpsdime.com/knowledgebase/technical-questions/mailcow-on-linux-vps); on plain Postfix, opendkim or rspamd does), and mail-tester tells you whether the signature verifies. - **DMARC**, a TXT record at `_dmarc.yourdomain.com` telling receivers what to do when SPF/DKIM fail and where to send reports: start with `v=DMARC1; p=none; rua=mailto:you@yourdomain.com`, and tighten to `p=quarantine` once reports show your legitimate mail passing. Gmail and the other large receivers now effectively **require** SPF and DKIM, with DMARC strongly weighted. With all three passing plus correct rDNS, you're ahead of most of the internet. ### Reputation: the part that takes time - **A fresh IP has no history**, and no history reads as suspicious. Warm it up: modest volume to real recipients who read the mail, ramping over weeks, not hundreds of messages on day one. - **Check the blocklists** (MXToolbox above). If your IP is listed, the blocklist's own site has a self-service delisting flow, and fix the cause first or you'll be relisted. Keeping our ranges clean is exactly why [bulk mail is forbidden](https://vpsdime.com/knowledgebase/acceptable-use/email-policy) here, which works in your favor: you're sending from a neighborhood that's kept clean. - **Rejected outright rather than spam-foldered?** Read the bounce, the `550`-style message names the reason and usually links the receiver's policy page (Gmail and Outlook bounces literally tell you what to fix). ### Content, briefly With identity and reputation right, content rarely decides alone. The quick hygiene: send real text (not one big image), skip URL shorteners, make sure links point where they say, and keep your test phrases out of production mail (mail-tester flags the specifics for you). ### When the right answer is a sending service If you're sending beyond personal and transactional volume, newsletters, campaigns, anything list-shaped, stop fighting deliverability from a single VPS: it's [not allowed on our network](https://vpsdime.com/knowledgebase/acceptable-use/email-policy), and services like **Amazon SES** or **Mailgun** exist precisely to own reputation and deliverability for you, cheaply. Many setups land on the hybrid: the VPS sends its transactional mail, the volume goes through a service. ### When to contact us Almost everything above is self-service, the exceptions worth a [ticket](https://vpsdime.com/open-ticket/): outbound **SMTP suddenly stopped working** (our monitors [block SMTP on mass-mail emission](https://vpsdime.com/knowledgebase/acceptable-use/email-policy), fix the cause, often a compromised site or form, then ask for a review), or an rDNS record that won't apply from the Network tab. ### Related questions - "Why do emails from my VPS go to spam?" - "How do I test my email deliverability?" - "How do I set up SPF, DKIM, and DMARC for my VPS?" - "What reverse DNS do I need for a mail server?" - "How do I check if my IP is blacklisted, and how do I delist it?" - "Gmail rejects or junks my server's mail, what do I check?" --- ## My mail server isn't receiving email URL: https://vpsdime.com/knowledgebase/troubleshooting/cannot-receive-email Last reviewed: 2026-07-02 Summary: The inbound checklist, an MX record pointing at an A record (not a CNAME), something actually listening on port 25, no firewall in the way, and the mail log telling the rest. How to test from outside with telnet/swaks and read sender bounces, plus where rejected-but-received mail actually went (spam scoring). ### What this is You run a mail server on your VPS ([Mailcow](https://vpsdime.com/knowledgebase/technical-questions/mailcow-on-linux-vps) or a classic Postfix stack) and mail sent **to** you isn't arriving. Inbound delivery is a short, strictly ordered chain, DNS → connection → acceptance → mailbox, and the failure is always at exactly one link. Walk it in order. ### Link 1: DNS, can senders find you? A sending server looks up your domain's **MX record**, then connects to that host: ``` dig +short MX yourdomain.com dig +short A mail.yourdomain.com ``` - The MX must exist and point at a **hostname** (`mail.yourdomain.com`), and that hostname must resolve via an **A record**, an MX pointing at a CNAME or straight at an IP is out of spec and breaks with some senders. - No MX at all? Some senders fall back to your domain's A record, many don't; set the MX. - Changed DNS recently? [Propagation applies](https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain), and mind a stale **AAAA record** on the mail hostname pointing somewhere that isn't listening. ### Link 2: is anything listening on port 25? Inbound mail arrives on **port 25**, and [a port is only open if something listens](https://vpsdime.com/knowledgebase/troubleshooting/my-port-xxx-is-closed): ``` ss -tulnp | grep :25 ``` You want a LISTEN on `0.0.0.0` (or the public address), not `127.0.0.1`. Nothing there? The mail service (or its SMTP container, in Mailcow's case) isn't running, fix that first. Then check nothing filters it: **our edge firewall doesn't touch port 25 inbound**, but your own ufw/iptables [default-deny policy](https://vpsdime.com/knowledgebase/troubleshooting/allow-ssh-in-common-firewalls) might, `ufw allow 25/tcp`. ### Link 3: test the whole path from outside From your home machine (not the VPS, that skips DNS and network): ``` telnet yourdomain.com 25 ``` A healthy server answers `220 mail.yourdomain.com ESMTP ...` within seconds. Or do the full conversation in one command with **swaks**, the SMTP Swiss army knife: ``` swaks --to you@yourdomain.com --server yourdomain.com ``` - **Connection refused instantly** → reached the machine, nothing listening (Link 2). - **Timeout** → something dropping packets ([the reject-vs-drop rule](https://vpsdime.com/knowledgebase/troubleshooting/my-port-xxx-is-closed)), your firewall, or note that many **residential ISPs block outbound port 25**, so a timeout from home Wi-Fi may mean *your ISP*, not your server; test from another VPS or use an online SMTP test to be sure. - **Connects but the recipient is rejected** (`Relay access denied`, `User unknown`) → the server doesn't consider itself responsible for that domain/mailbox: the domain or mailbox isn't configured in your mail stack. That's a mail-software config fix, not a network one. ### Link 4: it's accepted but never appears If swaks succeeds and mail still "doesn't arrive", it arrived and went somewhere: check the **spam/junk folder**, and then the mail log, which records every message's fate: ``` tail -50 /var/log/mail.log # classic stacks # Mailcow: the postfix container's logs in its UI or docker logs ``` Greylisting (first attempt deferred, retried minutes later), a full mailbox or [full disk](https://vpsdime.com/knowledgebase/troubleshooting/disk-full), and overzealous spam scoring are the usual endings. The log line for the message names which. ### Ask the sender for the bounce When a specific sender's mail fails, the **bounce message they received** is the single most useful artifact, it contains your server's (or their server's) exact rejection line. "It just doesn't arrive, no bounce" plus a clean mail log usually means the sender's message never left their side. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS and the mail domain, - what the MX lookup and the telnet/swaks test from outside show, - the exact rejection or bounce text, if a sender got one. ### Related questions - "Why isn't my mail server receiving email?" - "How do I test SMTP on port 25 from outside?" - "What should my MX record point to?" - "What does relay access denied mean?" - "Mail is accepted but not in the mailbox, where did it go?" --- ## My VPS is slow. How do I find out why? URL: https://vpsdime.com/knowledgebase/troubleshooting/slow-vps Last reviewed: 2026-07-02 Summary: A systematic method for diagnosing a slow VPS, first separate path problems from server problems, then check memory pressure and OOM kills (surfaced by My VPS is Down on Linux VPS), CPU saturation and its usual causes (miners after a compromise, container sprawl, overlapping cron jobs, unoptimized scripts), storage I/O, long-term Graphs, agented monitoring, and website-specific tuning (CDN caching, OPcache, MySQL/PostgreSQL query analysis). ### What this is "Slow" is a symptom, not a diagnosis. Behind it there is always a specific saturated resource, or a network path problem pretending to be one, and each has a check that takes minutes. This page is the systematic walk-through: where slowness actually comes from, how to measure each candidate, and what to do about what you find. One thing to rule out first, because it reframes the search: **our platform runs with deliberate headroom.** Nodes are provisioned and monitored to keep ample free CPU, memory, storage throughput, and uplink capacity at all times, that's the design (and the reason we [don't oversell](https://vpsdime.com/knowledgebase/presales/pre-sales-faq)). "The host is overloaded" is therefore the least likely explanation, and in practice slowness almost always turns out to live in one of two places: **the network path between you and the VPS**, or **inside the VPS itself**. The method below checks them in order of likelihood. ### Step 1: is the server slow, or the path to it? Separate the two with one observation: **does the VPS feel slow from within?** - Over SSH, run something purely local: `time ls -R /usr/share > /dev/null`, or watch `htop` respond. If local commands are instant and keystrokes only lag over the network, the server is fine, the **path** is your problem. - Confirm from a second vantage point: run your VPS IP through **[ping.pe](https://ping.pe/)** (pings it from dozens of worldwide locations at once, green everywhere = the VPS and our network are fine), our [Looking Glass](https://vpsdime.com/looking-glass), or your phone on mobile data. Fast from everywhere except your location means the problem sits between your location and us. Long international routes deserve a special mention: from parts of **South and East Asia**, trans-continental paths to US or EU datacenters routinely carry higher latency and congestion at peak hours, which reads as "the server is slow" when the server is idle. The [network problems guide](https://vpsdime.com/knowledgebase/troubleshooting/network-problems) shows how to prove where the path degrades with mtr, and the [speed testing guide](https://vpsdime.com/knowledgebase/troubleshooting/testing-network-speed) covers throughput specifically. If the path is the finding, that's the guide to follow, no change on the VPS will fix a mid-path problem. If the VPS is slow **from inside too**, continue. ### Step 2: memory pressure and OOM kills Exhausted memory doesn't feel like an error, it feels like slowness and instability: services restarting for no visible reason, requests stalling, a database that "crashes sometimes". - Check the real headroom: `free -h`, and read the **available** column ([how to read it correctly](https://vpsdime.com/knowledgebase/troubleshooting/vps-using-too-much-memory), high "used" alone is normal). - Check for **OOM kills**, the kernel killing your processes when memory truly runs out. Important platform fact: **on Linux VPS, OOM kills are not visible inside your VPS**, you won't find them in your own logs or dmesg. The **[My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter)** page surfaces them: run it for the VPS and it reports recent OOM kills. (On **Premium VPS**, full KVM, `dmesg | grep -i "out of memory"` works as usual.) - Found OOM kills or near-zero available memory? Identify the consumer, `ps aux --sort=-%mem | head`, then either fix its appetite (database buffer sizes are the usual oversized culprit) or [upgrade the plan](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade). Our Linux VPS run without swap by design, memory is fully dedicated, so sustained overcommitment ends in kills rather than silent disk-thrash ([and swap wouldn't help](https://vpsdime.com/knowledgebase/technical-questions/swap-on-linux-vps)). ### Step 3: CPU saturation, and its four usual causes Measure first: - `htop` (or `top`): overall CPU, and which processes hold it. - **Load average** (in `htop`'s header or `uptime`): roughly, how many processes want CPU time at once. Compare it to your **vCPU count**, a load persistently **above** the number of cores means work is queuing and everything waits. Load 6 on a 2-core VPS is saturation; load 1.5 on 4 cores is idle. - `ps aux --sort=-%cpu | head` for the ranked list. What you find is nearly always one of these four: **1. A cryptominer, meaning you've been compromised.** All cores pinned at 100% around the clock by a process you don't recognize (miners masquerade under random or system-looking names; `xmrig` is the honest one). Killing it is not the fix, something let it in and modern bots respawn what you kill. Follow the full recovery procedure: [My VPS was hacked](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery). **2. Container sprawl.** Automation that spawns containers, node-running and airdrop-farming stacks are notorious for quietly scaling to dozens or hundreds, will consume any CPU it can see. Check reality: `docker ps | wc -l` and `docker stats` (live per-container CPU/memory). If the workload is legitimate, cap it, `--cpus` and memory limits per container (or `deploy.resources` in compose), so one stack can't starve the VPS. If you didn't launch it, see cause 1. **3. Overlapping cron jobs.** A script scheduled every minute that sometimes takes longer than a minute begins accumulating: two copies, then ten, then hundreds, each slower than the last, a self-inflicted fork bomb in slow motion. Diagnose with `ps aux | grep yourscript`, if multiple generations are running, that's it. The fix is a lock so a new run refuses to start while the old one lives: `flock -n /tmp/job.lock your-command` in the crontab line, or a systemd timer with a service (which serializes by design). **4. An unoptimized script or app.** One process, pinned, legitimately yours. This is a code problem: profile it, batch its work, add the missing index (see the database section below), or accept it needs more cores, [Extra vCPU](https://vpsdime.com/knowledgebase/client-area/services/extra-features) exists for exactly this. ### Step 4: storage I/O Least common on NVMe, but cheap to check: install sysstat and run `iostat -x 2`, sustained `%util` near 100 with high `await` means something is hammering the disk, usually a database missing indexes (full-table scans are disk work), runaway logging, or a backup job at the wrong hour. And confirm the disk isn't [simply full](https://vpsdime.com/knowledgebase/troubleshooting/disk-full), a full or inode-exhausted filesystem produces spectacular, misleading slowness. ### Step 5: check the Graphs for history Everything above measures *now*. Your VPS's **[Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs)** tab holds the long view, CPU, memory, disk, traffic over time. Two questions to ask it: - **Does the slow period line up with a resource spike?** A CPU plateau starting Tuesday matches "slow since Tuesday" and points inward. - **Are the graphs flat during the slowness?** Quiet graphs during a slow spell push suspicion firmly back to the network path (Step 1) or to something the app is waiting on externally (a third-party API, a remote database). ### Step 6: still nothing obvious? Monitor continuously Intermittent slowness, fine now, awful at 3 AM, can't be caught with a live `htop`. Put an **agent** on the VPS and let it record: - **[Netdata](https://www.netdata.cloud/)** is the low-effort choice: one-line install, per-second metrics for every subsystem (CPU, memory, disk, per-process, containers, MySQL/PostgreSQL plugins), a built-in dashboard, and it's free on a single server. The next time slowness strikes, you scroll back to the exact minute and see what moved. - Prefer assembling your own: **Prometheus node_exporter + Grafana** is the standard DIY stack, more setup, more control. An agent turns "it was slow yesterday, no idea why" into a chart with the answer on it, and it's the evidence that makes any escalation (to us, or to a developer) immediately actionable. ### If "slow" means your website When the server itself checks out but the site is sluggish, the wins are at the application layer, in descending order of effect-per-effort: - **Cache at the edge.** Put the site behind a CDN, **[Cloudflare](https://www.cloudflare.com/)** (free tier included) or **[Bunny](https://bunny.net/)**, so static assets (images, CSS, JS) are served from a location near each visitor instead of from your VPS on every request. Visitors far from your datacenter feel this most, it converts geography (Step 1's unfixable problem) into cache hits. Bonus: your origin IP gets hidden, which also matters [under attack](https://vpsdime.com/knowledgebase/acceptable-use/ddos-policy). - **PHP sites: verify OPcache.** It caches compiled PHP bytecode and is the single biggest free win for WordPress and friends: `php -i | grep opcache.enable` should say On (it usually is; if not, enable it in the PHP ini). Add an **object cache** (Redis or Memcached, bound to [localhost](https://vpsdime.com/knowledgebase/getting-started/securing-public-services)) so the CMS stops recomputing queries on every page view. - **MySQL/MariaDB: find the slow queries instead of guessing.** Enable the slow query log (`slow_query_log = 1`, `long_query_time = 1`), let it collect during real traffic, then `EXPLAIN` the offenders, the overwhelming majority resolve to a **missing index**. For tuning beyond that, size `innodb_buffer_pool_size` to hold your working set (a common starting point is 50 to 70% of RAM on a database-only server, much less when it shares the box), and [MySQLTuner](https://github.com/major/MySQLTuner-perl) gives a sane automated review. - **PostgreSQL: same discipline, native tools.** Enable **pg_stat_statements** and query it for the top total-time statements, `EXPLAIN ANALYZE` those, and fix with indexes first. Check `shared_buffers` (the common starting point is ~25% of RAM) and confirm **autovacuum is on**, a table that never gets vacuumed degrades into exactly this kind of creeping slowness. - If the app is still slow with warm caches and indexed queries, the remaining time is in the code path itself (N+1 query patterns, synchronous external API calls), which an APM view in Netdata or the framework's debug toolbar will show. ### When to bring it to us If you've localized a problem you can't act on, the path degrades mid-route ([send both mtrs](https://vpsdime.com/knowledgebase/troubleshooting/network-problems)), or your measurements genuinely point at the platform, [open a ticket](https://vpsdime.com/open-ticket/) with what you measured: when it happens, what `htop`/Graphs/Netdata showed, and any mtr output. We check the node side quickly, and with evidence attached, the first reply is usually the fix, but given the headroom we run, the wins above are where the answer is found in the great majority of cases. ### Related questions - "Why is my VPS slow?" - "How do I check what's using my CPU or memory?" - "What does load average mean and what's a normal value?" - "How do I know if my VPS was OOM killed?" - "Why are there hundreds of Docker containers on my VPS?" - "My cron job made the server unusable, how do I stop it overlapping?" - "How do I find slow MySQL or PostgreSQL queries?" - "How do I make my website on a VPS faster?" - "What monitoring should I install to catch intermittent slowness?" --- ## Fixing 502, 503, and 504 errors on your VPS URL: https://vpsdime.com/knowledgebase/troubleshooting/502-503-errors Last reviewed: 2026-07-02 Summary: A 502/503/504 means your web server answered but the application behind it didn't, how to decode each error, read the proxy log, check the backend process, catch the silent causes (OOM kills, full disk), troubleshoot container-to-container communication, and the Docker Swarm/EasyPanel dnsrr case. ### What this is Your site shows **502 Bad Gateway**, **503 Service Unavailable**, or **504 Gateway Timeout**. Before anything else, notice what the error *proves*: something answered the request, so your web server or proxy (nginx, Apache, Traefik, Cloudflare) is **up and reachable**. What failed is the thing **behind** it, the application, PHP-FPM, or a container, when the front door asked it for the page. That cuts the search space in half before you've run a single command: this is an application-layer problem inside the VPS, not an outage. ### First, if you're behind Cloudflare A Cloudflare-branded error page (their logo, or codes like 521/522/523) means the failure may be between **Cloudflare and your origin**, not inside it. Isolate by asking the VPS directly, from your machine: ``` curl -I -H "Host: yourdomain.com" http://YOUR.VPS.IP/ ``` If that returns your site fine, the problem is the Cloudflare↔origin leg (origin firewall rules, TLS mode mismatch). If it returns the same 502/503, continue below, the problem is on the VPS. ### Decoding the three errors - **502 Bad Gateway:** the proxy asked the backend and got **nothing usable**, the app has crashed, PHP-FPM is down, or the proxy is pointed at a port/socket where nothing is listening. - **503 Service Unavailable:** the backend is **refusing** work, an app in maintenance mode, or a worker pool with nothing free. - **504 Gateway Timeout:** the backend is alive but **too slow**, a hung database query, a stalled external API call, or work that legitimately exceeds the proxy's timeout. ### The five-minute diagnosis **1. Is the backend actually running?** ``` systemctl status php8.2-fpm # or php-fpm, gunicorn, your app's service ``` Dead? `systemctl restart` it, then find out *why* it died before calling it fixed: `journalctl -u -n 50` shows its last words. **2. Read the proxy's error log, it names the culprit.** ``` tail -20 /var/log/nginx/error.log ``` The message is diagnostic on its own: `connect() failed (111: Connection refused)` = nothing listening at the target (backend down, or wrong port); `connect() to unix:/run/php/php-fpm.sock failed (2: No such file or directory)` = wrong socket path (or FPM not running); `(13: Permission denied)` on a socket = ownership mismatch; `upstream timed out` = the 504 case. **3. Check the proxy's target against reality.** What does the config point at (`grep -r proxy_pass /etc/nginx/`, or the `fastcgi_pass` line), and is anything listening there: `ss -tulnp`. A version bump that renamed the PHP-FPM socket (`php8.1-fpm.sock` → `php8.2-fpm.sock`) is a classic silent 502. **4. Check the two silent assassins.** Backends rarely die unprovoked: - **Out of memory.** The kernel kills the biggest process, which is usually your app or database. On **Linux VPS, OOM kills don't show in your own logs**, run [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter), which reports them (on Premium, `dmesg` shows them). If OOM is the story, fixing the 502 means [fixing the memory](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps), not just restarting. - **Full disk (or inodes).** Apps crash or refuse writes in strange ways when storage is gone, ten seconds to rule out: `df -h` and `df -i`, and the [disk-full guide](https://vpsdime.com/knowledgebase/troubleshooting/disk-full) if either is at 100%. ### If your app runs in Docker: container-to-container 502s A very common modern setup: a reverse-proxy container forwards to app containers by name (`proxy_pass http://app:3000`). When the proxy can't reach the app **across Docker's internal network**, the visitor sees a 502 even though both containers show as "running". Check, in order: - **Are they on the same Docker network?** Name resolution only works within a shared network: `docker network inspect ` should list both containers. Containers on different networks (or one on the default bridge) can't resolve each other, the proxy logs "host not found in upstream". - **Can the proxy actually reach the app?** Test from inside the proxy container: `docker exec wget -qO- http://app:3000/` (or `curl`). Failure here confirms the problem is between containers, not in your site config. - **Is the app listening on the right interface inside its container?** An app bound to `127.0.0.1` **inside the container** is unreachable from other containers, inside a container it should listen on `0.0.0.0`, and you control public exposure at publish time instead ([the 127.0.0.1 publish rule](https://vpsdime.com/knowledgebase/getting-started/securing-public-services)). - **Did the app container restart and change IP?** nginx resolves `proxy_pass` hostnames **once at startup** and caches the IP, so a recreated app container leaves nginx forwarding to a stale address. Quick fix: restart the proxy container. Durable fix: use a variable with Docker's resolver so nginx re-resolves (`resolver 127.0.0.11; set $up http://app:3000; proxy_pass $up;`), Traefik and Caddy handle this dynamically on their own. - **And check the app container itself**: `docker logs ` , a crash-looping app produces exactly intermittent 502s. ### Docker Swarm and panels built on it (EasyPanel) If your stack runs on **Docker Swarm**, including panels that use Swarm under the hood such as **EasyPanel**, there's a platform-specific cause that looks exactly like a mysterious, persistent 502: Swarm's default virtual-IP routing relies on **ipvs**, which our Linux VPS platform doesn't provide. Services must run in **`dnsrr` endpoint mode** instead. The full explanation, the commands, and how to convert all of EasyPanel's services are in [Running Docker Swarm on Linux VPS](https://vpsdime.com/knowledgebase/technical-questions/docker-swarm), if you're on Swarm and every other check on this page comes up clean, that's your answer. ### Fixing a real 504 If the log says `upstream timed out`, the backend is too slow, and the durable fix is making it faster, not making the proxy wait longer: find the slow query or hung external call ([the database section of the slow-VPS guide](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps) covers exactly this). Raise `proxy_read_timeout`/`fastcgi_read_timeout` only for work that is *legitimately* long (an export, a report), and raise it for that route, not globally. ### For 503s from a worker pool PHP-FPM logs `server reached pm.max_children` when every worker is busy, requests queue and then 503. Raising `pm.max_children` helps only if RAM allows it (each worker costs memory, size it as workers × per-worker usage against your plan), and if workers are busy because of slow queries, fix those first or more workers just pile onto the database. ### Prevent the next one - **Let systemd resurrect your app:** `Restart=always` (plus `RestartSec=2`) in the service unit turns a crash into a blip instead of an outage. - **Put an agent on it:** [Netdata](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps) records exactly what happened at the moment the backend died, memory spike, disk, crash loop, so the 3 AM 502 is diagnosable at 9 AM. - Keep the [disk](https://vpsdime.com/knowledgebase/troubleshooting/disk-full) and [memory](https://vpsdime.com/knowledgebase/troubleshooting/vps-using-too-much-memory) hygiene from their own guides, most "random" backend deaths are one of those two. ### Is it ever the platform? A 502/503/504 is almost always application-layer, by the time you see it, the network delivered your request and your web server answered it. A platform problem presents differently: the whole VPS unreachable (nothing answers at all). If that's what you're seeing, check [ping.pe](https://ping.pe/) and run [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) instead, and see [network problems](https://vpsdime.com/knowledgebase/troubleshooting/network-problems). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS and the site's domain, - which error it is (502, 503, or 504) and the matching line from the proxy's error log, - whether the backend runs directly or in Docker. ### Related questions - "What does 502 Bad Gateway mean on my VPS and how do I fix it?" - "Why does nginx say connection refused to upstream?" - "My site shows 502 after a PHP update." - "Why can't my proxy container reach my app container?" - "EasyPanel apps return 502 on my VPS, why?" - "How do I fix 504 gateway timeout properly?" - "What does pm.max_children reached mean?" --- ## Fixing SSL certificate errors on your website URL: https://vpsdime.com/knowledgebase/troubleshooting/ssl-certificate-errors Last reviewed: 2026-07-02 Summary: Decode "Your connection is not private" properly, expired certificates (the day-91 renewal failure), name mismatches, self-signed defaults, broken chains, mixed content, and Cloudflare's SSL modes (Flexible vs Full vs Full strict), with openssl one-liners and third-party checkers (SSL Labs, crt.sh) to diagnose before anyone opens a ticket. ### What this is Visitors see **"Your connection is not private"** (or the padlock is broken) on your site. The browser's error code tells you which of the distinct problems you have, so start by reading it, then this page fixes each one. - **`ERR_CERT_DATE_INVALID`**, the certificate **expired**. By far the most common, and almost always a silent renewal failure (below). - **`ERR_CERT_COMMON_NAME_INVALID`**, a **name mismatch**: the certificate served doesn't cover the hostname in the address bar. - **`ERR_CERT_AUTHORITY_INVALID`**, the certificate isn't from a trusted authority: a **self-signed or default** certificate is being served instead of your real one. - **`ERR_TOO_MANY_REDIRECTS`**, not a certificate problem at all: almost always the **Cloudflare Flexible mode** loop (below). ### See what's actually being served Don't guess, ask the server: ``` echo | openssl s_client -servername yourdomain.com -connect yourdomain.com:443 2>/dev/null | openssl x509 -noout -dates -subject -issuer ``` That prints the certificate's validity dates, what names it was issued for, and who issued it, which usually settles the "which problem is this" question on the spot. For the full third-party view: - **[SSL Labs' server test](https://www.ssllabs.com/ssltest/)**, the complete grade: certificate, **chain validation**, protocols, and exactly what's wrong, the single best tool here. - **[crt.sh](https://crt.sh/)**, the public log of every certificate issued for your domain, useful to confirm whether a renewal actually happened. - **[Why No Padlock](https://www.whynopadlock.com/)**, for the mixed-content case at the bottom. ### The day-91 story: renewals fail silently Let's Encrypt certificates live **90 days**. certbot installs a timer that renews them automatically, and when that timer breaks, nothing complains, until day 91, when the site goes red for every visitor at once. If your certificate expired, don't just renew it once, **find out why automation failed** or you'll be back in 90 days: ``` certbot renew --dry-run systemctl list-timers | grep certbot ``` The dry run either passes (automation is healthy again) or prints the actual reason it can't renew. The common ones: - **Port 80 closed.** The default HTTP-01 validation requires Let's Encrypt to reach `http://yourdomain/.well-known/acme-challenge/`. If your own firewall grew a rule blocking 80, renewal dies: `ufw allow 80/tcp`. (Our [managed firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall) never blocks web ports.) - **DNS changed since issuance.** The domain no longer points at this VPS, or, the sneaky one, a stale **AAAA (IPv6) record** points somewhere else: validators may prefer IPv6, reach the wrong machine, and fail while the site "works fine" for you over IPv4. Check with `dig +short yourdomain.com A yourdomain.com AAAA` against [where your DNS should point](https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain). - **Web-server config drift**: a rewrite/redirect added since issuance now swallows `/.well-known/acme-challenge/`. Make sure that path is served plainly. - **Rate limits**: repeated failed attempts can hit Let's Encrypt's limits; fix the underlying cause first, then use `--dry-run` (which uses the staging environment) to verify before real attempts. Locked out right now and the site is down? Issue the same names from a **different free CA**, ZeroSSL via acme.sh is the usual escape hatch, all the options are in [the certificate guide](https://vpsdime.com/knowledgebase/getting-started/ssl-certificates). ### Name mismatches The certificate works, just not for the name being visited: - **`www` vs the bare domain**: the cert covers one but not the other. Reissue covering both: `certbot --nginx -d yourdomain.com -d www.yourdomain.com`. - **A new subdomain** isn't on the certificate, issue for it (or use a wildcard via DNS validation). - **nginx is serving the wrong site's certificate**: with multiple vhosts, a request that matches no `server_name` gets the `default_server`'s cert. Check which server block actually catches the hostname. ### "I renewed, but the browser still shows the old certificate" Web servers load certificates **at startup**. A renewed file on disk changes nothing until nginx/Apache **reloads** (`systemctl reload nginx`). certbot's standard setup does this via a deploy hook, if yours didn't, add one, or you'll do this dance every 60 days. ### Broken chain: "works in my browser, fails for my users" If browsers are fine but API clients, mobile apps, or older devices report an untrusted certificate, your config likely points at the bare certificate instead of the chain. With certbot files: `ssl_certificate` must reference **`fullchain.pem`**, not `cert.pem`. SSL Labs flags this as "chain issues", and it's a one-line fix plus a reload. ### Cloudflare SSL modes, get this one setting right If your site is behind Cloudflare, the **SSL/TLS mode** (Cloudflare dashboard → SSL/TLS) decides how the Cloudflare-to-origin leg works, and the wrong mode produces exactly the errors on this page: - **Off**: no HTTPS at all. Don't. - **Flexible**: visitors get HTTPS to Cloudflare, but Cloudflare talks **plain HTTP** to your VPS. No certificate needed on the origin, which is why people pick it, but the origin leg is unencrypted, and if your VPS also redirects HTTP→HTTPS (most setups do), you get the infamous **redirect loop** (`ERR_TOO_MANY_REDIRECTS`). Avoid. - **Full**: Cloudflare connects to your origin over HTTPS but accepts **any** certificate, even expired or self-signed. Encrypted, but not authenticated, a stopgap, not a destination. - **Full (strict)**: Cloudflare requires a **valid** certificate on your origin. This is the correct setting. Satisfy it either with your normal certbot certificate, or with a free **Cloudflare Origin CA certificate** (issued in the dashboard, valid up to 15 years, trusted *only* by Cloudflare, perfect when the site is always proxied). Debugging note: with the proxy on, the certificate visitors see is **Cloudflare's edge certificate**, not yours. To inspect what your origin itself serves, test it directly: `curl -kIv https://YOUR.VPS.IP -H "Host: yourdomain.com"`, the same isolation trick as in the [502 guide](https://vpsdime.com/knowledgebase/troubleshooting/502-503-errors). ### Mixed content: padlock present, but "not secure" warnings If the certificate is fine but the padlock shows warnings (or images/scripts don't load), the page is loading some assets over plain `http://`. The browser console lists every offender, and [Why No Padlock](https://www.whynopadlock.com/) does it in one paste. On WordPress, setting the site URL to `https://` fixes most of it; hardcoded `http://` links in themes and databases account for the rest. ### Using Caddy? Caddy issues and renews automatically by design, so a certificate failure there almost always reduces to the same two causes: port 80/443 reachability or DNS not pointing at the VPS. Its logs (`journalctl -u caddy`) name the ACME error directly. ### Verify, then stop worrying After any fix: reload the web server, hit the site in a private window, and run [SSL Labs](https://www.ssllabs.com/ssltest/) once, a clean A means certificate, names, and chain are all right. Then confirm `certbot renew --dry-run` passes so day 91 never comes back. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the domain and the exact browser error code, - what `certbot renew --dry-run` (or your ACME client's log) says, - whether the site is behind Cloudflare, and which SSL mode if so. ### Related questions - "Why does my site say your connection is not private?" - "My Let's Encrypt certificate expired, why didn't it renew?" - "How do I check what certificate my server is serving?" - "The certificate works for my domain but not www (or a subdomain)." - "I renewed the certificate but browsers still show the old one." - "Which Cloudflare SSL mode should I use, Flexible, Full, or Full (strict)?" - "Why do I get too many redirects with Cloudflare?" - "Why does my API client reject my certificate when browsers accept it?" --- ## Fixing 403 Forbidden errors on your website URL: https://vpsdime.com/knowledgebase/troubleshooting/403-forbidden Last reviewed: 2026-07-02 Summary: A 403 means the web server found the path but refuses to serve it, wrong file ownership or permissions after uploads, a missing index file, a deny rule, a wrong document root, or SELinux on RHEL-family distros. How to read the error log and fix each cause without chmod 777. ### What this is **403 Forbidden** is the web server saying: I found what you asked for, and I **refuse** to serve it. Unlike a [502](https://vpsdime.com/knowledgebase/troubleshooting/502-503-errors) (backend dead) or a 404 (not there), a 403 is about **permission and policy**, and the server's error log states the exact reason, so start there: ``` tail -20 /var/log/nginx/error.log # nginx tail -20 /var/log/apache2/error.log # Apache ``` `Permission denied` points at filesystem permissions; `directory index of ... is forbidden` points at a missing index file; `access forbidden by rule` points at a deny rule. Match the message to the section below. ### Cause 1: ownership and permissions (the post-upload classic) The most common story: files [uploaded over SFTP as root](https://vpsdime.com/knowledgebase/getting-started/uploading-files-sftp) land owned by `root`, and the web server, which runs as its own user (`www-data` on Debian/Ubuntu, `nginx`/`apache` on RHEL-family), isn't allowed to read them. Fix ownership, not the world: ``` chown -R www-data:www-data /var/www/yoursite find /var/www/yoursite -type d -exec chmod 755 {} \; find /var/www/yoursite -type f -exec chmod 644 {} \; ``` Directories `755`, files `644`, readable by the server, writable only by the owner ([how the permission model works](https://vpsdime.com/knowledgebase/technical-questions/linux-file-permissions), if the numbers feel like magic). And the standing rule: **never `chmod -R 777`.** It "fixes" the 403 by making every file writable by every process on the machine, which is how [web shells get planted](https://vpsdime.com/knowledgebase/troubleshooting/chrome-dangerous-site-warning). If 777 would have fixed it, correct ownership fixes it properly. One subtle variant: the server needs **execute (traverse) permission on every parent directory** of the file. A `700` home directory above your web root produces 403s even when the files themselves are perfect. ### Cause 2: no index file Requesting a directory (`https://yourdomain.com/`) serves its index file (`index.html`, `index.php`), and if none exists, the server refuses to show a listing and returns 403. Either your upload landed in the wrong place (check the site actually lives where the config's `root` points, cause 4) or the index file is genuinely missing or misnamed. ### Cause 3: a deny rule Config blocks like `deny all`, Apache `Require all denied`, IP allowlists you set up and forgot, or security rules in `.htaccess` (WordPress security plugins write these liberally) all produce 403s on purpose. The error log's `forbidden by rule` line tells you which request matched; grep the config for `deny` and check `.htaccess` files in the site root. ### Cause 4: wrong document root If *everything* 403s (or you see a default page), the server may be looking at an empty or different directory than the one you uploaded to. Compare the config's `root`/`DocumentRoot` against where the files actually are, `grep -r "root" /etc/nginx/sites-enabled/`. ### Cause 5: SELinux (AlmaLinux, Rocky) On RHEL-family distros, files moved (not copied) into the web root can carry the wrong SELinux context, and the server gets `Permission denied` even though classic permissions look perfect, the tell is a 403 that survives correct ownership. Restore the expected context: ``` restorecon -Rv /var/www/yoursite ``` ### Still 403? Cloudflare users: an orange-cloud 403 with a Cloudflare error page is their WAF or a firewall rule you set there, not your server; check the Cloudflare dashboard's security events. Otherwise, the error log line for the exact failing request (it logs the full path it tried) settles every remaining case. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS and the site's domain, - the exact line from the web server's error log for a failing request, - the ownership and permissions of the files involved (the `ls -la` output helps). ### Related questions - "Why does my site say 403 Forbidden after I uploaded it?" - "What permissions should website files have?" - "Why is chmod 777 a bad fix?" - "Directory index is forbidden, what does that mean?" - "403 on AlmaLinux/Rocky even though permissions are right (SELinux)?" --- ## My website didn't come back after a reboot or unsuspension URL: https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot Last reviewed: 2026-07-02 Summary: The VPS is running and SSH works, but the website, app, or database is offline after a restart, typically right after paying an overdue invoice and being auto-reactivated. The cause is services that were started once by hand but never enabled to start on boot. How to diagnose in a minute, fix it with systemctl enable, handle Docker restart policies and screen/tmux apps, and verify with a test reboot. ### What this is Your VPS is **up**, it pings, SSH works, but the website, app, or database on it is **offline**. This almost always follows a power cycle, and the most common script goes: an invoice went overdue, the VPS was [suspended](https://vpsdime.com/knowledgebase/billing/billing-timeline), you paid, it **reactivated automatically**, and it booted fresh, without your services. Here's the trap: **starting a service and enabling it are two different things.** `systemctl start nginx` runs it *now*; `systemctl enable nginx` registers it to run *at every boot*. A service started by hand during setup runs happily for months, and evaporates at the first power cycle, suspension/reactivation, a [traffic-overage suspension](https://vpsdime.com/knowledgebase/acceptable-use/bandwidth-overage), your own reboot, all the same. Nothing was lost and nothing is broken: the software just wasn't told to rise with the machine. ### Diagnose it in one minute SSH in and ask systemd about the services your site depends on: ``` systemctl status nginx mariadb php8.2-fpm ``` The smoking gun is in each output's first lines: `Active: inactive (dead)` combined with `Loaded: ... ; disabled;`. **Inactive plus disabled after a reboot is this exact problem.** To see every disabled unit at once: ``` systemctl list-unit-files --state=disabled ``` ### Fix it now, and forever One command does both, per service: ``` systemctl enable --now nginx mariadb php8.2-fpm ``` `--now` starts it immediately; `enable` makes it boot-persistent. Walk your whole stack, web server, database, PHP-FPM or your app service, cache (Redis), queue workers, and confirm each: `systemctl is-enabled nginx` should say `enabled`. If a service starts but the site still misbehaves, work the [502/503 guide](https://vpsdime.com/knowledgebase/troubleshooting/502-503-errors), and if a service **refuses** to start, read its own last words: `journalctl -u mariadb -n 50`. (A database that won't start right after a suspension period is occasionally a [full disk](https://vpsdime.com/knowledgebase/troubleshooting/disk-full), the ten-second `df -h` is always worth it.) ### Docker: containers need a restart policy Containers don't participate in systemd, they come back only if Docker is told to bring them back: - Fix existing containers: `docker update --restart unless-stopped ` (repeat per container, or all at once: `docker update --restart unless-stopped $(docker ps -aq)`). - In compose files: `restart: unless-stopped` on each service. - And confirm the Docker daemon itself is enabled: `systemctl is-enabled docker`. `unless-stopped` is usually the right policy: it survives reboots but respects containers you deliberately stopped. ### Apps running in screen, tmux, or nohup Anything you launched in a `screen`/`tmux` session or with `nohup` **does not survive a reboot**, those are conveniences for your login session, not service managers. Give the app a real home: - **A systemd unit** is ten lines and does everything: starts at boot, restarts on crash (`Restart=always`), logs to journald. Any AI chatbot [drafts one correctly](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) from "write a systemd service for running as in ". - Node.js crowd: **pm2** works too, `pm2 startup` + `pm2 save` is its boot-persistence step, which people forget exactly the same way. ### Verify like you mean it The only real test of "everything starts on boot" is a boot. At a calm moment: ``` reboot ``` Give it a minute, then check the site, and `systemctl --failed` for anything that didn't make it. Two minutes of planned downtime now beats rediscovering this page after the next suspension. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which services are down, with their `systemctl status` output, - what preceded it (payment reactivation, a reboot, an upgrade). ### Related questions - "I paid my overdue invoice and the VPS is back, but my website is still down." - "Why is my site offline after my VPS was unsuspended?" - "MySQL/nginx didn't start after a reboot, why?" - "How do I make services start on boot?" - "My Docker containers are gone after a restart." - "My app was running in screen and disappeared after a reboot." --- ## My VPS was hacked. Recovery, step by step URL: https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery Last reviewed: 2026-07-02 Summary: How to recover from a compromised VPS, recognize the signs, contain without destroying evidence, find the entry point, and why modern attack bots (replaced system binaries, multiple self-respawning persistence mechanisms) make in-place cleanup a losing game, the backup-data-and-reinstall routine, rotating every credential, and how our compromise suspension process works. ### What this is Your VPS is compromised, or you suspect it. This is the recovery procedure: how to confirm it, what to save, why the only reliable way out of a root-level compromise is **backing up your data and reinstalling**, and how the process works when our monitoring found it before you did. ### How compromises announce themselves - **CPU pinned at 100% around the clock**, a cryptominer, the most common payload ([the slow-VPS guide](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps) covers spotting it). - **Outbound spam**, our monitors [block SMTP automatically](https://vpsdime.com/knowledgebase/acceptable-use/email-policy) on mass-mail emission, and blocklists start listing your IP. - **A suspension notice from us**, our monitoring detected the VPS attacking others or running malware (the process for that is at the bottom). - Defaced pages, files you didn't change, users you didn't create, an `authorized_keys` entry you didn't add, processes with random names, or traffic spikes on your [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs). - **Browsers showing a red ["Dangerous site" warning](https://vpsdime.com/knowledgebase/troubleshooting/chrome-dangerous-site-warning)** on your website, Google Safe Browsing usually notices injected content before the owner does. ### First moves: contain, don't destroy 1. **Secure your VPSDime account first**: change its password. Every account already has [2FA on by default](https://vpsdime.com/knowledgebase/client-area/account/two-factor-overview) (email login codes); if you're on the default, consider [switching to an authenticator app](https://vpsdime.com/knowledgebase/client-area/account/authenticator-app-setup), which keeps the second factor working even if your mailbox is part of the breach. An attacker holding your panel access outranks anything you do on the server. 2. **Change the root password and remove unknown SSH keys** (`~/.ssh/authorized_keys` for root *and every user*), attackers plant keys precisely so password changes don't evict them. 3. **Don't start deleting things.** You'll want the evidence intact for the next step, and half-cleaning a box creates false confidence (see below for why). ### Find the door they came through This is the step that keeps it from happening again next week. Look for the entry point: - **Web applications first**, outdated CMS/plugin/panel versions and upload forms are the majority of real-world entries. Check the web server's access logs around the time trouble started, and look for **web shells** in upload/cache directories (PHP files where only images should live). - Login history: `last` and `lastb` (successful and failed logins, with source IPs). - Scheduled persistence: `crontab -l` for **every** user, `/etc/cron.*`, and `systemctl list-timers`. - New accounts in `/etc/passwd`, unfamiliar systemd units in `/etc/systemd/system/`. Whatever you find, the lesson feeds the rebuild: the hole gets patched **before** the site goes back up. ### Why you can't just clean it: modern bots don't lose gracefully Today's compromises aren't a script you delete. Automated attack kits are built to survive removal, and on a **root-level compromise** you should assume all of the following, because current bots do all of it: - **They replace system binaries.** `ps`, `ls`, `netstat`, `ss`, even `sshd` get swapped for trojaned versions that hide the malware and backdoor your logins, so the very tools you'd use to inspect the box lie to you. - **They persist in many places at once**: cron entries for several users, systemd units and timers, `ld.so.preload` hooks that inject into every process, shell profile hooks (`.bashrc`), PAM backdoors, planted SSH keys, and web shells as a re-entry hatch. Finding four of five means the fifth reinfects you. - **They respawn each other.** Watchdog processes run in pairs and restart whichever one you kill; downloader components re-fetch the payload from the internet minutes after you remove it. - **They defend their turf**: immutable file attributes (`chattr +i`), renamed copies of themselves, and sometimes they even patch the vulnerability they used, so *other* bots can't take their box. The practical consequence: with a rooted server, in-place cleanup is a game you lose slowly while believing you're winning. **If root was compromised, the routine is: back up your data, reinstall, restore.** It's faster than the cleanup attempt, and it's the only version with a trustworthy ending. ### The backup-and-reinstall routine 1. **Inventory what must survive**: databases, uploaded files, and configs (as reference). Code redeploys from your git repository, **never copy executables or scripts off the tainted disk**, data only. 2. **Prefer a backup from before the compromise.** Check when it started (logs, Graphs) and note that [Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview) keeps **three nights**, if the breach is older, those images contain the malware too. Your own [off-site backups with longer retention](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps) are exactly what pays off here. No clean backup? Take fresh **data-only** dumps off the compromised box (database dumps, uploads) and inspect uploads for planted files. 3. **[Reinstall the OS](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os)**, the clean slate. 4. **Patch the entry point before restoring anything**: updated CMS/plugins, the [hardening basics](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps) (keys, no password auth), and [no services exposed](https://vpsdime.com/knowledgebase/getting-started/securing-public-services) that don't need to be. 5. **Redeploy code from source** (git, official packages), restore your data, and bring the site up. 6. **Rotate every credential that ever lived on that server**: database passwords, API keys, everything in `.env` files, SMTP credentials, application admin accounts, and the one everyone misses, **TLS private keys**, the attacker had read access to yours, so reissue the certificate (Let's Encrypt makes that free and instant). ### Aftermath - If the box sent spam, check the [blocklists and start delisting](https://vpsdime.com/knowledgebase/troubleshooting/emails-going-to-spam), and note [the blacklist charge](https://vpsdime.com/knowledgebase/acceptable-use/email-policy) exists precisely because this cleanup lands on you. - Put [monitoring](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps) on the fresh install, a miner-shaped CPU graph on day one of a reinfection is how you win the rematch quickly. - Schedule the [backup routine](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps) you wished you'd had this morning. ### If our monitors found it first: the suspension process When our monitoring detects a compromised VPS, attacking other machines, mining, mass-mailing, hosting malware, **our staff verifies the detection and then suspends the VPS**. That's deliberate and immediate: it stops further damage both to your server and to other computers on the internet, and it protects the network every other customer shares. From there, the path back is cooperative: - **Contact us when you're ready** to handle the cleanup or, for root-level compromises, the backup-and-reinstall routine above, and we'll coordinate access so you can do it. - **Following through is required, not optional.** We can't allow malicious software to run on our network, so the service stays suspended until the compromise is actually dealt with, a rebuilt, patched server gets you back online; ignoring it doesn't. The service is self-managed, so the hands-on work is yours, but we'll [point you in the right direction](https://vpsdime.com/knowledgebase/support-coverage/what-support-covers) throughout, and this page is most of the map. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what you found (miner, spam, defacement) and roughly when it started, - whether you have a clean backup, and where you are in the backup-and-reinstall routine. ### Related questions - "My VPS was hacked, what do I do first?" - "Can I just remove the malware instead of reinstalling?" - "Why does the miner keep coming back after I kill it?" - "My VPS was suspended for a compromise, how do I get it back?" - "What do I need to change after my server was breached?" - "Are my backups safe to restore after a hack?" --- ## Chrome shows a "Dangerous site" warning on my website URL: https://vpsdime.com/knowledgebase/troubleshooting/chrome-dangerous-site-warning Last reviewed: 2026-07-02 Summary: The red "Dangerous site" / "Deceptive site ahead" page means Google Safe Browsing flagged your site, almost always because it's genuinely serving malware, phishing pages, or injected spam after a compromise. How to see exactly what was flagged (Transparency Report, Search Console), clean the site, request the review that lifts the warning, and keep it from returning. ### What this is Visitors hit a full-screen red page, **"Dangerous site"**, **"Deceptive site ahead"**, or **"The site ahead contains malware"**, before your site even loads. That's **Google Safe Browsing**: a blocklist consulted not just by Chrome but by Firefox, Safari, Edge, and most of the internet, so a flag effectively takes your site offline for real visitors. Two things to understand before fixing it: this has **nothing to do with your VPS, DNS, or certificate**, it's a verdict about your site's *content*, and Google is **usually right**. The overwhelming majority of flags mean the site really is serving something bad, typically without the owner knowing, because the site was compromised. ### Step 1: see exactly what Google flagged - **[Google's Transparency Report](https://transparencyreport.google.com/safe-browsing/search)**, paste your domain, get the current Safe Browsing verdict and the category, no account needed. The wording maps to the cause: **"deceptive"** = phishing pages, **"malware"** = malicious downloads or injected scripts, **"unwanted software"**, or **"hacked with spam"**. - **[Google Search Console](https://search.google.com/search-console)**, this is the essential one. Verify ownership of your domain (a DNS TXT record does it), open **Security Issues**, and Google lists the **specific example URLs** it flagged and why. This is also where the review request happens later, so set it up now. - To see *what's actually on* those flagged URLs without infecting yourself, scan them with **[VirusTotal](https://www.virustotal.com/)** (URL tab) or **[Sucuri SiteCheck](https://sitecheck.sucuri.net/)** rather than opening them in your browser. ### Step 2: clean the actual problem What you found in Security Issues decides the depth of the cleanup: - **Injected content on a compromised site** (the usual case, spam pages, redirects to scam sites, phishing kits in a subdirectory, malicious JS in your theme): this is a **web-application compromise**. Find recently changed files (`find /var/www -mtime -14 -type f | sort`), look for PHP in upload directories, unknown admin users in the CMS, and edited theme/plugin files. Restore the site from a clean backup, update the CMS, plugins, and themes that let it happen, and change every application password. Check for cloaked spam too: search Google for `site:yourdomain.com` and look for pages you never wrote. - **Signs it went deeper than the web app**, unknown system users, cron entries, processes, or SSH keys: assume root-level and follow the full [compromise recovery routine](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery), a flagged site is frequently how a deeper breach first becomes visible. - **You host user-generated content?** The flag may target something a user uploaded or an open redirect being abused, remove it and close the mechanism, or you'll be re-flagged by the next abuser. Don't skip to Step 3 with the malware still in place: reviews that fail because the site wasn't actually clean make subsequent reviews slower. ### Step 3: request the review In **Search Console → Security Issues**, tick "I have fixed these issues" and **Request Review**, describe briefly what you found and fixed. Reviews typically complete within **a day or two** (malware checks are often faster, deceptive-content ones can take longer). When it passes, the warning disappears from all browsers on its own, there's nothing to clear on our side or yours. While you wait, resist the urge to move the site to a new domain: the flag follows the content, and a clean review is faster than rebuilding reputation from zero. ### Keep it from coming back The flag was the symptom; the entry point was the disease. The [securing basics](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps) (updates above all, WordPress plugins are the #1 web-compromise vector), [nothing exposed that shouldn't be](https://vpsdime.com/knowledgebase/getting-started/securing-public-services), and [real backups](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps) so "restore from a clean copy" is a ten-minute step instead of a fantasy. Keeping the Search Console property verified is also worth it: Google **emails you** the moment a new security issue is detected, which beats hearing it from a customer. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the domain being flagged, - what Search Console's Security Issues page lists, - what you've cleaned up so far, and whether you've requested a review. ### Related questions - "Why does Chrome say my website is dangerous?" - "How do I remove the deceptive site ahead warning?" - "How long does a Google Safe Browsing review take?" - "How do I find what Google flagged on my site?" - "My site was hacked and now shows a red warning, what's the order of fixes?" --- ## I deleted files by accident. Can they be recovered? URL: https://vpsdime.com/knowledgebase/troubleshooting/recover-deleted-files Last reviewed: 2026-07-02 Summary: The honest answer for a VPS, stop writing to the disk immediately, understand that undelete tools rarely work on a live ext4 server and that we keep no copies of your data beyond your backups, then recover the real way, per-file from Nightly Backups' Browse Files, or from your own off-site backups. ### What this is You deleted something that mattered, a directory, a database, the wrong `rm` target. Here's the honest picture of what's recoverable and how, worst news first so the good options get your attention fast. ### First: stop writing to the disk When a file is deleted, its data blocks aren't erased, they're marked free, and **every write to the disk from now on may overwrite them permanently**. If you intend to attempt any recovery, act immediately: stop services that write (the database, the web app, logging if you can), and don't download or install recovery tools *onto the same disk* you're trying to recover from. ### The honest expectations - **Undelete tools mostly don't work here.** Utilities like extundelete or testdisk are built for offline disks; on a **live server** that kept writing (and journaling) after the deletion, recovery odds drop fast, and partial recovery of a database's files is usually as useless as none. They're a last resort, not a plan. - **We hold no copy of your data.** There are [no snapshots or copies on our side](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview) beyond the backups you've set up, we can't "restore it from our end", however the ticket is worded. - What actually saves you is a **backup taken before the deletion**, and there are two kinds you might have: ### If you have Nightly Backups (or a Premium VPS) This is the good outcome, and it's self-service in minutes: - **A few files or folders:** use **[Browse Files](https://vpsdime.com/knowledgebase/client-area/nightly-backups/recover-individual-files)** on last night's backup, a web file browser over the backup image where you can download files directly or copy them straight back to your VPS over SFTP. No full restore needed. - **A whole database:** if you followed the [dump-nightly advice](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps), pull the latest dump file out via Browse Files and load it. If not, a [full restore](https://vpsdime.com/knowledgebase/client-area/nightly-backups/restore-your-vps) rolls the entire VPS back to last night (everything else rolls back with it, so weigh that). - **Timing matters:** retention is **three nights**, and tonight's backup will reflect the deletion. Recover what you need **today**, not next week. - Windows VPS backups are restored [by ticket](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview). ### If you have your own backups Restore from your [off-site copies](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps), restic and friends restore single files trivially (`restic restore --include /path`). This is also the moment you learn whether the backup job you set up months ago still works, which is why that guide nags about restore testing. ### If you have neither - For genuinely irreplaceable data, the last resort is the undelete route: power the services down to stop writes and work with testdisk/extundelete (ideally against the disk image, a [full disk download](https://vpsdime.com/knowledgebase/client-area/nightly-backups/download-full-disk-image) requires the backup add-on, so on a bare VPS you'll be working live). Set expectations at "maybe fragments". - If the data is gone, it's gone, and the only useful output of the incident is the setup that makes it a non-event next time: **[enable Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/enable-nightly-backups)** ($5/month, tonight is your first restore point) and an [off-site routine](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps) for the long retention. An evening of setup converts every future version of this page into a ten-minute fix. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what was deleted and when, - whether the VPS has Nightly Backups, or you have backups of your own. ### Related questions - "I accidentally deleted files on my VPS, can you restore them?" - "Does VPSDime keep copies of my files?" - "How do I recover one file from my nightly backup?" - "Do undelete tools work on a VPS?" - "I deleted my database, what are my options?" --- ## MySQL or MariaDB won't start after a crash URL: https://vpsdime.com/knowledgebase/troubleshooting/mysql-wont-start Last reviewed: 2026-07-02 Summary: How to bring a database back safely, read the error log before touching anything, rule out the two usual killers (full disk, OOM), let InnoDB's normal crash recovery finish, and only then consider innodb_force_recovery, used read-only, to dump and rebuild, never as a setting you leave on. ### What this is The database died and won't come back up. This is the guide where **order of operations matters most**: the wrong first move can convert a recoverable situation into data loss, so the sequence below is arranged to be safe at every step. The single rule: **read before you write**, diagnose from logs before changing anything, and take a copy before any risky action. ### Step 0: read the error log Everything MySQL/MariaDB knows about why it won't start is in its error log: ``` journalctl -u mariadb -n 100 # or -u mysql tail -100 /var/log/mysql/error.log # location varies by distro ``` The last screen of output nearly always names the cause directly. Match it below. ### Step 1: rule out the two usual killers - **Full disk (or inodes).** InnoDB refuses to start, or crashed in the first place, when it can't write: `Disk full`, `errno 28`, or just cryptic write failures. `df -h && df -i`, and if either is at 100%, fix that first, [the disk-full guide](https://vpsdime.com/knowledgebase/troubleshooting/disk-full), then start the service. This resolves a large share of "corrupt database" panics with zero database surgery. - **The OOM killer.** If memory ran out, the kernel likely killed mysqld mid-write, and may kill it again on startup while it replays. On **Linux VPS**, OOM kills don't show in your own logs, run [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter), which reports them. If OOM is the story, shrink `innodb_buffer_pool_size` (the usual oversized culprit) or [add memory](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade) before restart attempts, or you'll crash in a loop. ### Step 2: let normal crash recovery run InnoDB is designed to survive crashes: on startup it replays its redo log and rolls back unfinished transactions on its own. On a large or busy database this can take **many minutes** while the service looks "stuck", watch the error log in a second terminal (`journalctl -u mariadb -f`); as long as recovery messages keep progressing, **wait**. Restarting it mid-recovery restarts the recovery. ### Step 3: take a copy before anything risky If recovery genuinely fails (the log shows a crash during recovery itself, or names corrupted pages), stop. Before any forced measure, copy the raw data directory somewhere safe: ``` systemctl stop mariadb cp -a /var/lib/mysql /root/mysql-datadir-copy ``` Every step after this point becomes reversible. (Check `df -h` first, you need the space.) ### Step 4: innodb_force_recovery, the escape hatch, not a fix `innodb_force_recovery` starts InnoDB while **skipping parts of its own safety machinery** so you can get your data out. Understand the contract: it's a **read-only rescue mode for dumping**, not a setting that repairs anything, and higher levels can themselves corrupt data. 1. Add to the `[mysqld]` section of your config: `innodb_force_recovery = 1`, and try to start. If it won't, step up one level at a time, **2, 3, 4**, using the **lowest level that starts**. 2. Once it starts, **do not resume normal operation.** Dump everything immediately: `mysqldump --all-databases > /root/all.sql`. 3. Treat levels **4 and above** as data-affecting (they skip undo/redo application), only with your Step 3 copy in place, and if 1 to 3 didn't start it, this is the moment to consider [asking for direction](https://vpsdime.com/open-ticket/) before going further. 4. Rebuild clean: stop the server, move the broken data directory aside, reinitialize (or reinstall the DB packages), start **without** `force_recovery`, and load `/root/all.sql`. Remove the setting from the config, leaving it on silently breaks the database later. ### If you have backups, weigh them first A [nightly dump](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps) or a [Nightly Backups image](https://vpsdime.com/knowledgebase/troubleshooting/recover-deleted-files) from before the crash may cost you a day of data but zero surgery, often the better trade than hours of forced recovery for a database that was corrupted anyway. This is also the standing argument for the dump-nightly cron: dumps restore cleanly, always. ### Prevent the rerun The crash had a cause: usually [OOM](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps) (right-size the buffer pool against your plan's RAM), a [full disk](https://vpsdime.com/knowledgebase/troubleshooting/disk-full), or hard power-offs during writes. And make sure the service is [enabled to start on boot](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot) while you're here. ### Related questions - "MariaDB won't start after my VPS crashed, what's the safe order of steps?" - "What is innodb_force_recovery and is it safe?" - "How long does InnoDB crash recovery take?" - "MySQL says disk full or errno 28 and won't start." - "Should I restore a backup or repair the database?" --- ## My cron job didn't run URL: https://vpsdime.com/knowledgebase/troubleshooting/cron-not-running Last reviewed: 2026-07-05 Summary: The four reasons cron jobs fail silently, the minimal environment (PATH), the % character gotcha, relative paths, and no output capture, plus how to check whether cron even fired, make failures noisy with MAILTO or logging, prevent overlaps with flock, and when a systemd timer is the better tool. ### What this is A scheduled job didn't do its thing, or so it seems. Cron fails **silently by design**, so this page does two jobs: find out what happened, and make sure the next failure announces itself. (New to cron entirely? Start with [Scheduling tasks with cron](https://vpsdime.com/knowledgebase/technical-questions/cron-basics), the format, the habits, and the overlap trap, then come back here when something misfires.) ### First: did cron fire it at all? Check the record instead of guessing: ``` grep CRON /var/log/syslog | tail -20 # Debian/Ubuntu journalctl -u cron -n 20 # or crond on RHEL-family ``` - **The job appears at the right time** → cron did its part; the *command* failed. Continue below. - **It doesn't appear** → the schedule or the crontab itself is the problem: confirm the entry exists under the right user (`crontab -l`, root's and yours are different crontabs), that the cron service runs (`systemctl status cron`), and that the schedule means what you think, paste the five fields into **[crontab.guru](https://crontab.guru/)**, which explains any expression in plain words and catches the classic day-of-week/day-of-month surprises. ### The four silent killers **1. Cron's environment is nearly empty.** Jobs don't get your shell's environment: `PATH` is typically just `/usr/bin:/bin`, so a command that works at your prompt (`certbot`, `restic`, `node`) dies with "command not found" in cron. Fix: use **absolute paths** (`/usr/bin/certbot`), or set `PATH=` at the top of the crontab. **2. The `%` character is special.** In a crontab line, unescaped `%` means "newline, and feed the rest to stdin", so a date format like `date +%F` breaks the command in half. Escape every one: `date +\%F`. **3. Relative paths.** Cron runs from the user's home directory, not your project folder, `./script.sh` and relative config/output paths miss. `cd /path/to/project && ./script.sh`, or absolute paths throughout. **4. The output went nowhere.** The job may have run and *failed*, and told nobody. Which is the fix that matters most: ### Make failures noisy Pick one (or both): - **MAILTO**: put `MAILTO="you@example.com"` at the top of the crontab and cron emails you any output, and failures produce output. (Requires the VPS to [send mail](https://vpsdime.com/knowledgebase/troubleshooting/emails-going-to-spam); also note a job erroring every minute into a local mailbox is [an inode story](https://vpsdime.com/knowledgebase/troubleshooting/out-of-inodes).) - **Log it**: append `>> /var/log/myjob.log 2>&1` to the entry, `2>&1` is the crucial part, error messages go to stderr, and without it your log shows success while the job fails. For the truly critical (backups!), add a dead-man's-switch ping (healthchecks.io style) so you're alerted when the job *doesn't* run. ### Two upgrades while you're in there - **Prevent overlaps** on jobs that might outlive their interval: `flock -n /tmp/myjob.lock /path/to/command`, the [cron cascade](https://vpsdime.com/knowledgebase/technical-questions/cron-basics) is one of the classic ways a VPS ends up unresponsive. - **Consider a systemd timer** for anything important: timers log every run to journald, serialize by design, can catch up on missed runs, and don't have cron's environment quirks. Cron is fine for simple things; timers are the better tool once a job matters, the full recipe is in [Using systemd timers instead of cron jobs](https://vpsdime.com/knowledgebase/technical-questions/systemd-timers). (`@reboot` cron entries in particular are better served by a [real systemd unit](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot).) ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the exact crontab line and when you expected it to run, - what the cron log shows around that time. ### Related questions - "Why didn't my cron job run?" - "My script works manually but fails in cron." - "How do I see cron logs?" - "What does the % sign do in crontab?" - "How do I get emailed when a cron job fails?" - "Cron job or systemd timer, which should I use?" --- ## Error: Failed to detect code in /var/log/syslog.log or /var/log/messages (lfd) URL: https://vpsdime.com/knowledgebase/troubleshooting/lfd-failed-to-detect-code Last reviewed: 2026-07-03 Summary: The lfd alert "Failed to detect code ... in SYSLOG log" means syslog checking is failing, almost always because of a known rsyslog imjournal bug that stops messages reaching the log at all. Reboot once, then either switch rsyslog off the imjournal module (recommended) or disable lfd's SYSLOG_CHECK. ### What this is You're getting alert emails from **lfd** (the login failure daemon that ships with the CSF firewall) saying something like: ``` Error: Failed to detect code [xnxnxnx] in SYSLOG_LOG [/var/log/messages] ``` referencing `/var/log/syslog.log` or `/var/log/messages`. This is lfd's **SYSLOG_CHECK** feature doing its job: it periodically writes a random code through syslog and then checks that the code actually appeared in the log. When the code never shows up, lfd alerts you, because a server whose syslog isn't recording is a server whose security logging is blind. So the alert isn't lfd misbehaving. It's lfd correctly reporting that **syslog itself isn't logging**. The root cause is almost always a known bug in rsyslog's **imjournal** module (the piece that reads messages from the systemd journal), which stops rsyslog writing messages properly and leaves lfd's test code missing. The bug is documented here: https://bugzilla.redhat.com/show_bug.cgi?id=1088021 ### First step: one reboot Reboot the server. This can clear the wedged state and the alerts stop. Note that **one reboot is all it takes to find out**: if a single reboot doesn't fix it, rebooting again won't either, move on to the real fix below. (After any reboot, remember [the started-vs-enabled rule](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot) if something else stays down.) ### Fix option 1 (recommended): take rsyslog off the imjournal module This sidesteps the buggy module entirely by letting rsyslog collect local messages itself instead of through the journal: 1. Edit `/etc/rsyslog.conf` with your favorite editor and adjust the following: - Comment out the `$ModLoad imjournal` line - Comment out the `$IMJournalStateFile imjournal.state` line - Change `$OmitLocalLogging` from `on` to `off` - Save the file 2. Restart rsyslog: ``` systemctl restart rsyslog ``` (On a cPanel server, the cPanel-managed way is `/usr/local/cpanel/scripts/restartsrv rsyslogd`.) 3. Confirm the restart reports success, then verify logging works end to end: `logger lfd-test-123` followed by `grep lfd-test-123 /var/log/messages` should find your test line. Once real messages flow again, the lfd alerts stop on their own. ### Fix option 2 (easier, not recommended): disable lfd's syslog checking This silences the alarm rather than fixing the logging, so your logs may still be incomplete. Perform at your own risk: 1. Edit `/etc/csf/csf.conf` and change `SYSLOG_CHECK` from `1` to `0`, then save. 2. Restart lfd: ``` systemctl restart lfd ``` 3. Confirm the restart reports success. The alerts stop, but do check now and then that `/var/log/messages` is actually receiving entries. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the exact lfd alert text, - whether `/var/log/messages` is currently receiving any new lines at all. ### Related questions - "What does the lfd 'Failed to detect code in SYSLOG log' email mean?" - "Why is /var/log/messages empty or not updating?" - "How do I fix the rsyslog imjournal bug?" - "Is it safe to turn off SYSLOG_CHECK in csf.conf?" --- ## Temporary failure resolving (DNS errors during updates) URL: https://vpsdime.com/knowledgebase/troubleshooting/temporary-failure-resolving Last reviewed: 2026-07-02 Summary: If apt or other tools fail with "Temporary failure resolving", DNS resolution inside your VPS is broken. Point systemd-resolved at a public resolver (DNS=8.8.8.8 in resolved.conf) and restart it. ### What this is Running `apt update` (or curl, git, anything that needs a hostname) fails with **"Temporary failure resolving 'archive.ubuntu.com'"** or **"Could not resolve host"**. Your VPS's network is fine, but its **DNS resolver** isn't answering, so it can't turn names into IPs. ### The fix Point systemd-resolved at a public resolver: 1. Edit the resolver config: `nano /etc/systemd/resolved.conf` 2. Find the `#DNS=` line, uncomment it, and set a resolver: `DNS=8.8.8.8` 3. Save (Ctrl+X, then Y) and restart the resolver: `systemctl restart systemd-resolved` Or as a single command: ``` sed -i 's/#DNS=/DNS=8.8.8.8/' /etc/systemd/resolved.conf && systemctl restart systemd-resolved ``` Then retry the update. `8.8.8.8` is Google's public resolver; `1.1.1.1` (Cloudflare) works just as well. ### If that doesn't do it - **Check `/etc/resolv.conf`** exists and isn't empty. On systemd-resolved systems it should be a symlink managed for you; on others, a plain `nameserver 8.8.8.8` line in it does the job. - **Check your own firewall** isn't blocking outbound DNS (UDP/TCP port 53), an overzealous ruleset with a default-deny on output does exactly this. - Still stuck? [Open a ticket](https://vpsdime.com/open-ticket/) with the exact error and what you've tried. ### Related questions - "Why does apt update say temporary failure resolving?" - "My VPS can't resolve any hostnames." - "How do I fix DNS inside my VPS?" - "Could not resolve host errors on my VPS." --- ## My disk is full (and it took my website or database down) URL: https://vpsdime.com/knowledgebase/troubleshooting/disk-full Last reviewed: 2026-07-02 Summary: A full disk rarely announces itself, it shows up as a website suddenly offline, MySQL/MariaDB refusing to start or going read-only ("No space left on device", errno 28), or apps crashing on write. How to confirm with df -h, find what's eating the space, clean it safely, and keep it from recurring. ### What this is A full disk almost never *says* "disk full". It says something else: - your **website is suddenly offline**, throwing 500 errors or blank pages, - **MySQL/MariaDB won't start**, crashes, or goes read-only, logs show `Disk full (errno 28)` or `No space left on device`, - your **app crashes** whenever it writes (uploads, sessions, caches, queues), - cron jobs, updates, even logins misbehave in strange ways. If a service died "for no reason", **check the disk before anything else.** It's a ten-second test and one of the most common hidden causes of "my site/app/database is down": ``` df -h ``` If a filesystem (usually `/`) shows **100%** (or 99%), you've found it. And if `df -h` shows **plenty free** yet writes still fail with "No space left on device", check `df -i`: you're likely **out of inodes** instead, millions of tiny files rather than big ones, which has [its own guide](https://vpsdime.com/knowledgebase/troubleshooting/out-of-inodes). ### Find what's eating the space Work down from the root, largest first: ``` du -xhd1 / | sort -h ``` Then re-run it on the biggest directory (`du -xhd1 /var | sort -h`, and so on) until you find the culprit. If you'd rather browse interactively, `apt install ncdu` and run `ncdu -x /`. The usual suspects, and how to clean each **safely**: - **systemd journal logs.** Check with `journalctl --disk-usage`; shrink with `journalctl --vacuum-size=200M`, and cap it permanently with `SystemMaxUse=200M` in `/etc/systemd/journald.conf`. - **Application and web-server logs** in `/var/log`. An app stuck in an error loop can write gigabytes overnight. Empty a huge live log with `: > /var/log/thefile.log` (truncation) rather than deleting it, a deleted file that a running service still holds open **keeps occupying space** until the service restarts. (Find those ghosts with `lsof +L1`.) - **Docker.** Check with `docker system df`. Old images, stopped containers, unused volumes, and unbounded container logs add up fast. `docker system prune` clears the safe stuff; add `-a` to also drop unused images (they'll re-download on next use). Cap container logs going forward with log rotation in `/etc/docker/daemon.json`. - **Package caches:** `apt clean` (or `dnf clean all`). - **Old dumps and backups** parked in `/var/backups`, `/root`, or your home directory, ship them [off-site](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps) instead of hoarding them on the disk they're supposed to protect. ### What NOT to do - **Don't delete things you can't identify**, especially anything under `/var/lib` (that's where your **databases live**, `/var/lib/mysql` is your data, not clutter), `/usr`, or `/etc`. Freeing space by deleting the wrong file turns an outage into data loss. - Don't bulk-delete in `/tmp` on a live system without looking, running services may be mid-write there. - Not sure what something is? Ask us, or [ask an AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) with the exact path, before removing it. ### After you've freed space Restart whatever fell over, databases especially don't recover from a full disk until restarted: ``` systemctl restart mariadb # or mysql, postgresql, nginx, your app... systemctl status mariadb ``` Then load your site and confirm. If MySQL/MariaDB won't come back cleanly after an errno-28 incident, stop, don't experiment against your only copy of the data, follow [the safe recovery order](https://vpsdime.com/knowledgebase/troubleshooting/mysql-wont-start), and [open a ticket](https://vpsdime.com/open-ticket/) with the exact log lines if it doesn't recover. ### Keep it from happening again - **Log rotation is your friend:** logrotate handles `/var/log` by default, but confirm your app's own logs are covered, and cap journald and Docker logs as above. - **Glance at the disk graph** on your VPS's [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) tab now and then, disk usage grows slowly and visibly; catching it at 85% is painless. - **Genuinely need more room?** [Additional Storage](https://vpsdime.com/knowledgebase/client-area/services/extra-features) adds disk without changing your plan, or [upgrade](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade) if everything is getting tight. ### Related questions - "My website suddenly went down, could the disk be full?" - "MySQL won't start and says disk full (errno 28), what do I do?" - "How do I find what's using all my disk space?" - "Is it safe to delete Docker images or journal logs?" - "Why does it say no space left when the disk isn't full (inodes)?" - "How do I add more disk space to my VPS?" --- ## No space left on device, but df shows free space (out of inodes) URL: https://vpsdime.com/knowledgebase/troubleshooting/out-of-inodes Last reviewed: 2026-07-02 Summary: When writes fail with "No space left on device" while df -h shows plenty free, the disk ran out of inodes, the per-file records a filesystem has a fixed number of. Confirm with df -i, find the directory hoarding millions of tiny files (PHP sessions, caches, mail queues), delete them the right way, and stop the producer. ### What this is The confusing cousin of a [full disk](https://vpsdime.com/knowledgebase/troubleshooting/disk-full): writes fail with **"No space left on device"**, your site or database misbehaves exactly as if the disk were full, but `df -h` shows **gigabytes free**. What actually ran out is **inodes**, and because almost nobody checks for it, it's one of the most-missed causes of a broken server. Confirm it in five seconds: ``` df -i ``` If **IUse%** is at (or near) **100%** on the affected filesystem, this page is your problem. ### What an inode is Every file and directory on a filesystem is tracked by an **inode**, the record holding its metadata and where its data lives. A filesystem is created with a **fixed budget** of them (roughly one per 16 KB of disk on default ext4). Normal use never gets close, but **millions of tiny files** spend inodes while barely using any bytes, which is how you end up "full" with free space: the byte tank has room, the file-count tank is empty. ### Find the hoard You're looking for the directory with a ridiculous **number** of files, not big ones. GNU `du` counts inodes directly, drill down largest-first exactly like a disk hunt: ``` du --inodes -xd1 / | sort -n ``` Re-run it on the worst directory (`du --inodes -xd1 /var | sort -n`, and so on) until you hit the pile. The usual suspects: - **PHP session files** in `/var/lib/php/sessions`, the classic, when session garbage collection is off or the site is busy or being spammed. - **Cache directories:** app caches, WordPress cache plugins, composer/npm caches, thumbnail caches. - **Mail queues and mailboxes:** a cron job erroring every minute for a year quietly writes half a million messages to `/var/mail/root`; a stuck postfix queue does the same in `/var/spool`. - **Temp and job files** from an app or queue worker that creates but never deletes. - **Docker** layers and volumes holding many-small-file images. ### Clean it up, the right way A directory with millions of entries breaks the naive tools: `rm *` fails with **"Argument list too long"**, and even `ls` can hang. Use find, which streams: ``` find /var/lib/php/sessions -xdev -type f -delete ``` (Point it at the guilty directory, and only at files you've confirmed are disposable, sessions, caches, and queue debris usually are; when unsure, ask first, same rule as the [what-not-to-delete list](https://vpsdime.com/knowledgebase/troubleshooting/disk-full).) For very large piles this can take a while, that's normal, let it run. ### Stop the producer Deleting the pile without fixing the source buys you weeks, not a cure: - **PHP sessions:** make sure session garbage collection runs (`session.gc_probability`/`gc_divisor`, or the distro's session-clean cron/timer). - **Caches:** give them a TTL or a max size; most frameworks and cache plugins have one that's just not enabled. - **Cron mail:** fix the erroring job, and set `MAILTO=""` on jobs whose output nobody reads. - **Queues/temp files:** make the app clean up after itself, or add a tmpfiles/cron cleanup for its directory. ### Worth knowing - **You can't add inodes to an existing filesystem** by tuning, the budget is set when it's created. But **growing the disk grows the budget**: when you [upgrade the plan or add storage](https://vpsdime.com/knowledgebase/client-area/services/extra-features) and the filesystem expands, the inode count expands proportionally with it. It's still the wrong fix for a runaway producer, right fix for a genuinely file-heavy workload (huge maildirs, node_modules farms). - Add `df -i` to your mental checklist right next to `df -h`, the pair takes ten seconds and covers both ways a disk can be "full". ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the `df -i` output and the directory the inode hunt pointed at, - what appears to be producing the files. ### Related questions - "Why does it say no space left on device when df shows free space?" - "What is an inode and why did I run out?" - "How do I find which directory has millions of files?" - "How do I delete millions of files (argument list too long)?" - "Does upgrading my disk add more inodes?" --- ## My VPS is using too much memory. What's wrong? URL: https://vpsdime.com/knowledgebase/troubleshooting/vps-using-too-much-memory Last reviewed: 2026-07-04 Summary: It probably isn't. Linux deliberately uses idle RAM as disk cache and releases it on demand, so "used" memory looks high by design. How to read free -h correctly (the available column), what real memory pressure looks like, and what to do about it. ### What this is Your monitoring, `htop`, or `free` shows memory nearly full and it looks alarming. In most cases **nothing is wrong**: Linux deliberately uses RAM that would otherwise sit idle as **disk cache**, because cached reads are enormously faster than disk reads. The moment your applications need that memory, Linux hands it back. Full-looking RAM is Linux doing its job well, the classic explainer is [linuxatemyram.com](https://www.linuxatemyram.com/). ### How to read the numbers Run `free -h` and look at the **available** column, not "used" or "free": - **available** is what your applications can actually claim right now (free memory plus reclaimable cache). If it's comfortable, you have no memory problem, whatever "used" says. - Your control panel's memory graph reads your VPS the same way, so the [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) tab reflects real usage accurately. #### cgroup counters count cache as used There's a second family of memory numbers that inflates the same way for a different reason: **cgroups** (control groups) counters. The cgroup v2 `memory.current` value (and v1's `memory.usage_in_bytes`) is the kernel's total charge for the group, and it **includes the page cache**, not just what your applications allocated. Anything that reports from these counters inherits that behavior: - `docker stats` and container dashboards, - `systemctl status ` / systemd's `MemoryCurrent`, - anything reading `memory.current` from `/sys/fs/cgroup/...` directly. So a service or container can show hundreds of MB "used" when its processes hold a fraction of that, the rest is cache for the files it touched, reclaimable like any other cache. To see the split, read the group's `memory.stat` and compare `anon` (real application memory) with `file` (cache). And since a Linux VPS is itself a container, a tool that reads the VPS's own cgroup counter directly will show cache as used for the whole VPS, `free -h`'s **available** remains the number that tells the truth about pressure. ### What real memory pressure looks like - **available** in `free -h` staying near zero during normal operation. - Processes being killed by the **OOM killer**. Platform note: on **Linux VPS** these kills are **not visible inside your VPS**, they won't appear in your own logs or dmesg; run **[My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter)**, which reports recent OOM kills for your VPS. On **Premium VPS** (full KVM), `dmesg | grep -i "out of memory"` shows them as usual. (Our Linux VPS run without swap, memory is fully dedicated, so when RAM is truly exhausted the kernel kills the biggest consumer rather than grinding into slow disk-swap.) - Services (databases especially) restarting or dying under load for no visible reason. ### If you genuinely need more First check *what's* eating it (`ps aux --sort=-%mem | head`), a leaking app or an oversized database buffer setting is cheaper to fix than more RAM. If the workload has simply outgrown the plan, [upgrade](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade), on Linux VPS it's live and instant with no downtime. And no, [adding swap](https://vpsdime.com/knowledgebase/technical-questions/swap-on-linux-vps) isn't the answer. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the output of `free -h`, - whether anything is actually misbehaving (kills, restarts, slowness) or the number just looks high. ### Related questions - "Why does my VPS show almost all memory used?" - "Is high memory usage on Linux a problem?" - "How do I read free -h properly?" - "How do I know if I really need more RAM?" - "What is the OOM killer and why did it kill my process?" - "Why does docker stats show so much memory used?" - "Why is memory.current higher than what my processes use?" - "Why does systemctl status show a huge memory number for my service?" --- ## Why can't I clear the RAM cache on my VPS? URL: https://vpsdime.com/knowledgebase/troubleshooting/clear-ram-cache Last reviewed: 2026-07-05 Summary: You don't need to clear Linux's RAM cache, and doing so makes performance worse. Cache is reclaimable by design and Linux frees it automatically under memory pressure. What the cache actually does and why drop_caches is a placebo. ### What this is You've noticed a lot of memory listed as cache/buffers and want to "free" it. The short answer: **you don't need to, and you shouldn't.** Linux has decades of refined memory management built in; it uses otherwise-idle RAM to cache frequently accessed files, and it releases that cache **automatically and instantly** the moment your applications need the memory. It will never let the system run out of memory just to keep things cached. ### Why clearing it hurts The cache is pure upside: reads served from RAM instead of disk make your entire VPS faster. Forcing it empty (the `drop_caches` trick) doesn't create memory your apps couldn't already claim, it just throws away the speed boost, and Linux has to rebuild the cache from disk afterwards. It solves no real problem and creates a small one. If a monitoring tool is scaring you by counting cache as "used", read [My VPS is using too much memory](https://vpsdime.com/knowledgebase/troubleshooting/vps-using-too-much-memory), the **available** column in `free -h` is the number that matters, and our panel [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) already measure it correctly. Tools that read **cgroups counters** (`docker stats`, `systemctl status`, anything reading `memory.current`) are the usual scare source: the cgroup charge **includes the page cache by design**, so their "used" is application memory plus cache lumped together. The long-form explainer: [linuxatemyram.com](https://www.linuxatemyram.com/). ### Seeing stale content on your website? That's a different cache entirely If what brought you here is a website **showing old content**, an edit that won't appear, a stale page, yesterday's prices, the RAM cache is the wrong suspect: Linux's page cache stores file data transparently and can't serve your visitors outdated pages. What does is one of the **application-level caches**, and the fix is at that layer: - **The browser**: rule it out first with a hard refresh or a private window. - **Cloudflare or another CDN**: if the site is proxied, the edge may be serving a cached copy, purge the URL (or flip on Development Mode while you work). See [Cloudflare best practices](https://vpsdime.com/knowledgebase/getting-started/cloudflare-best-practices). - **Your CMS or app's cache**: WordPress caching plugins and framework page caches keep rendered copies, clear the cache from within the app. - **PHP OPcache**: caches compiled PHP code, so an edited `.php` file can keep running as the old version. Reloading PHP clears it: `systemctl reload php8.2-fpm` (your version may differ). - **Redis or Memcached**: object caches the application put data in, and the application should be the one to clear (its own cache-flush command or admin button), avoid a blanket `FLUSHALL` on a Redis instance that might also hold real data, like sessions or queues. Work from the outside in (browser → CDN → app → OPcache) and the stale layer announces itself. None of these involve `drop_caches`, and clearing the RAM cache won't refresh a single page. ### The one takeaway If **available** memory is healthy, there is nothing to clear. If it isn't, clearing cache won't help, find the process eating RAM or [upgrade the plan](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the output of `free -h`, - what made you look at memory in the first place (slowness, crashes, a graph). ### Related questions - "How do I clear cached memory on my VPS?" - "Should I use drop_caches to free RAM?" - "Why is so much memory shown as buffers/cache?" - "Does clearing the cache speed up my server?" - "My website shows old content, do I need to clear the server's cache?" - "I edited a PHP file but the site still runs the old version." --- ## Windows VPS help URL: https://vpsdime.com/knowledgebase/windows-vps Last reviewed: 2026-07-04 Summary: Guides for your Windows VPS, connecting over RDP from every device, passwords and the troubleshooter, securing the server (firewall, RDP hardening, updates), backups, keeping apps running across reboots, troubleshooting slowness and full disks, hosting on IIS, SSH access, and the nested-virtualization boundary. Guides for running your Windows VPS. New here? Start with the connection guide for your device, everything you need is `Administrator` plus the password from your provisioning email. ### Connecting - [How to connect using RDP](https://vpsdime.com/knowledgebase/windows-vps/connect-rdp). The overview, quick steps for every platform. - [From another Windows computer](https://vpsdime.com/knowledgebase/windows-vps/connect-from-windows), [from a Mac](https://vpsdime.com/knowledgebase/windows-vps/connect-from-mac), [from an iPhone or iPad](https://vpsdime.com/knowledgebase/windows-vps/connect-from-iphone-ipad), [from Android](https://vpsdime.com/knowledgebase/windows-vps/connect-from-android). Step-by-step with screenshots. - [How many people can connect at once?](https://vpsdime.com/knowledgebase/windows-vps/rdp-connection-limit) The two-session limit, RDS CALs, and screen-sharing alternatives. - [SSH and PowerShell remoting](https://vpsdime.com/knowledgebase/windows-vps/ssh-on-windows). The optional OpenSSH server, for terminal-style management and transfers. - [How to transfer files](https://vpsdime.com/knowledgebase/windows-vps/transfer-files-windows-vps). RDP clipboard, drive redirection, fetch-on-the-VPS, and SCP, ranked by setup cost. - [RDP feels laggy: performance tuning](https://vpsdime.com/knowledgebase/windows-vps/rdp-performance). Resolution, color depth, Experience presets, and which lag is physics. ### Password and access problems - [What is my Administrator password?](https://vpsdime.com/knowledgebase/windows-vps/administrator-password) Where it comes from, and the whitespace trap. - [My Administrator password doesn't work](https://vpsdime.com/knowledgebase/windows-vps/administrator-password-not-working). The two checks that solve it. - [The Windows Troubleshooter](https://vpsdime.com/knowledgebase/windows-vps/windows-troubleshooter). Automated power/RDP/password checks with self-service reset. - [The VPSDime Support Account (DIME user)](https://vpsdime.com/knowledgebase/windows-vps/vpsdime-support-account). The service user behind password resets, upgrades, and migrations, and what changes if you remove it. ### Security - [Securing your Windows VPS](https://vpsdime.com/knowledgebase/windows-vps/securing-your-windows-vps). The layered checklist, and why the firewall matters more here: there's no managed edge firewall on Windows VPS. - [Using Windows Defender Firewall](https://vpsdime.com/knowledgebase/windows-vps/windows-firewall). Open ports for your apps, restrict RDP to your IPs. - [Protecting RDP from brute force](https://vpsdime.com/knowledgebase/windows-vps/protecting-rdp). NLA, lockout policy, IP restriction, and reading Event 4625. - [How can I change my RDP port?](https://vpsdime.com/knowledgebase/windows-vps/change-rdp-port) Lockout-safe, firewall rule first, and the ip:port client syntax. - [Windows Updates on your VPS](https://vpsdime.com/knowledgebase/windows-vps/windows-updates). Keep updates on, manage the reboots, and the patch-day slowness explained. ### Running the server - [Backing up a Windows VPS](https://vpsdime.com/knowledgebase/windows-vps/backing-up-windows-vps). The Nightly Backups add-on (restores by ticket), restic on Windows, and SQL Server dumps. - [My app didn't come back after a restart](https://vpsdime.com/knowledgebase/windows-vps/windows-services-after-reboot). Startup types, the Recovery tab, Task Scheduler, and NSSM. - [How to set up cron jobs (Task Scheduler)](https://vpsdime.com/knowledgebase/windows-vps/cron-jobs-on-windows). Scheduled scripts that run unattended, with output captured. - [How to view and save the Event Log](https://vpsdime.com/knowledgebase/windows-vps/view-save-event-log). The three logs that matter, filtering, and exporting .evtx evidence. - [Hosting a website on IIS](https://vpsdime.com/knowledgebase/windows-vps/hosting-a-website-iis). The Web Server role, bindings, and free auto-renewing SSL with win-acme. - [Connecting to a VPN from your Windows VPS](https://vpsdime.com/knowledgebase/windows-vps/vpn-client-on-windows-vps). Run a VPN client without losing RDP: the default-route trap, the safety net, and per-client split-tunnel settings. ### Troubleshooting - [My Windows VPS is slow](https://vpsdime.com/knowledgebase/windows-vps/windows-vps-slow). Path vs server, TiWorker and Defender, miners, and RAM honesty. - [My Windows VPS is frozen or unresponsive](https://vpsdime.com/knowledgebase/windows-vps/windows-vps-unresponsive). Memory exhaustion and pagefile thrashing: why nothing responds, the Reset button, and sizing that prevents it. - [Can't RDP after joining a domain](https://vpsdime.com/knowledgebase/windows-vps/rdp-after-domain-join). The RD licensing grace period, domain GPO and firewall-profile changes, the .\ local-login syntax, and mstsc /admin. - [How to monitor resource usage](https://vpsdime.com/knowledgebase/windows-vps/monitor-resources-windows). Task Manager, Resource Monitor, and Performance Monitor history. - [C: is full](https://vpsdime.com/knowledgebase/windows-vps/disk-full-windows). WinDirStat, the sanctioned cleanups, and extending the volume after a plan upgrade. - [I can't download anything in the browser](https://vpsdime.com/knowledgebase/windows-vps/cant-download-ie-esc). IE Enhanced Security Configuration, and the package-manager habit. - [Can I run Ubuntu, WSL2, or a Linux VM?](https://vpsdime.com/knowledgebase/windows-vps/no-linux-vms-on-windows-vps) No nested virtualization, and what works for each goal instead. ### Inside Windows - [Enabling sound](https://vpsdime.com/knowledgebase/windows-vps/enabling-sound). Audio is off by default, one service away. - [Changing the time zone (Server 2019)](https://vpsdime.com/knowledgebase/windows-vps/change-time-zone-server-2019). The timedate.cpl method. - [Changing the language](https://vpsdime.com/knowledgebase/windows-vps/change-windows-language). Display language vs keyboard layout vs formats, untangled. - [Finding the device name or ID](https://vpsdime.com/knowledgebase/windows-vps/find-device-id). For licensing and activation tools. For plans, editions, and what's included (license, Hyper-V, editions 2025/2022/2019), see [Windows VPS](https://vpsdime.com/knowledgebase/presales/windows-vps) in presales. --- Still need a person? You can [open a support ticket](https://vpsdime.com/open-ticket/) any time. --- ## How to connect to my Windows VPS using RDP URL: https://vpsdime.com/knowledgebase/windows-vps/connect-rdp Last reviewed: 2026-07-05 Summary: Your Windows VPS comes with Remote Desktop ready to use, connect with the username Administrator and the password from your provisioning email. Quick steps for Windows, Mac, iPhone/iPad, Android, and Linux, with links to detailed screenshot guides per device. ### What this is Your Windows VPS comes with **Microsoft Remote Desktop (RDP) activated and ready to use**, no setup needed on the server. You need two things, both in your welcome email (subject: **"New Windows VPS - Provisioning Started"**): - your **VPS IP address**, - your **Administrator password** (the username is always `Administrator`). Copy and paste the password rather than typing it, stray whitespace and typos are the number one login problem. Lost it? See [What is my Administrator password?](https://vpsdime.com/knowledgebase/windows-vps/administrator-password) ### From Windows Every Windows PC has the client built in, nothing to install: 1. In the taskbar search, type "Remote Desktop Connection" and open it. 2. Enter your VPS IP in **Computer** and click **Connect**. 3. Log in as `Administrator` with your password. 4. Accept the certificate prompt with **Yes**. Step-by-step with screenshots: [Connecting from another Windows computer](https://vpsdime.com/knowledgebase/windows-vps/connect-from-windows). ### From a Mac 1. Install **Windows App** (Microsoft's remote desktop client, formerly "Microsoft Remote Desktop") from the [Mac App Store](https://apps.apple.com/us/app/windows-app/id1295203466). 2. **Add PC**, enter your VPS IP as the **PC name**, and **Add**. 3. Double-click the PC, log in as `Administrator`, and accept the certificate. Step-by-step with screenshots: [Connecting from a Mac](https://vpsdime.com/knowledgebase/windows-vps/connect-from-mac). ### From an iPhone or iPad Install Microsoft's [Windows App Mobile](https://apps.apple.com/us/app/remote-desktop-mobile/id714464092), add a PC with your VPS IP, and log in as `Administrator`. Screenshots: [Connecting from an iPhone or iPad](https://vpsdime.com/knowledgebase/windows-vps/connect-from-iphone-ipad). ### From Android (or a Chromebook) Install Microsoft's [Remote Desktop client from Google Play](https://play.google.com/store/apps/details?id=com.microsoft.rdc.androidx), add a PC with your VPS IP, and log in as `Administrator`. Screenshots: [Connecting from an Android device](https://vpsdime.com/knowledgebase/windows-vps/connect-from-android). ### From Linux Any RDP client works: **Remmina** (usually preinstalled on desktop distros), **FreeRDP** (`xfreerdp /v:YOUR.VPS.IP /u:Administrator`), or rdesktop. Same IP, username, and password as above. ### Can't get in? **Just provisioned, or just reinstalled?** Windows finishes setting itself up for a few minutes after provisioning or a [reinstall](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os) completes, and RDP is one of the last things to come up. If the connection is refused or times out right after either, that's normal: **wait up to 5 minutes and try again** before treating it as a problem. Still nothing? Run the [Windows Troubleshooter](https://vpsdime.com/knowledgebase/windows-vps/windows-troubleshooter), it checks that your VPS is powered on, that RDP is enabled, and that the password on file works, and lets you reset the password if it doesn't. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the device and client you're connecting from, with the exact message it shows, - what the Windows Troubleshooter reported. ### Related questions - "How do I connect to my Windows VPS?" - "What program do I use for RDP?" - "What are my Windows VPS login details?" - "Can I connect to my Windows VPS from a phone or a Mac or Linux?" - "I just got my Windows VPS and RDP won't connect yet." - "RDP doesn't work right after reinstalling Windows, is something wrong?" --- ## How to connect to my Windows VPS from another Windows computer URL: https://vpsdime.com/knowledgebase/windows-vps/connect-from-windows Last reviewed: 2026-07-02 Summary: A screenshot walkthrough of connecting to your Windows VPS with the built-in Remote Desktop Connection app, no extra software and no Windows Pro needed, log in as Administrator with the password from your provisioning email. ### What this is Connecting to your Windows VPS from a Windows PC with the built-in **Remote Desktop Connection** app. Every edition of Windows includes it, you don't need Windows Pro and nothing extra to install. Have your **VPS IP** and **Administrator password** handy (both are in your welcome email, subject "New Windows VPS - Provisioning Started"). Two things worth knowing before you start: - The app's name is **localized**: on a non-English Windows, search for your language's equivalent of "Remote Desktop Connection". - You do **not** want "RemoteApp", that's a different thing. Make sure it's **Remote Desktop Connection**. ### Steps 1. Click **Start**, type "remote", and open **Remote Desktop Connection**. ![Windows Start menu search showing Remote Desktop Connection](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-windows-1-search.png) 2. In the **Computer** field, copy and paste your VPS IP address, then click **Connect**. ![Remote Desktop Connection window with the Computer field filled in](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-windows-2-computer.png) 3. Enter your credentials: the **User name** is `Administrator`, and we strongly recommend **copy and pasting the password** to avoid typos. Click **OK**. ![Windows credentials prompt with Administrator as the user name](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-windows-3-credentials.png) 4. A certificate warning pops up, that's normal for a fresh server. Tick **"Don't ask me again for connections to this computer"** and click **Yes**. ![Certificate warning dialog with the don't-ask-again checkbox](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-windows-4-certificate.png) 5. You're in, the Windows desktop of your VPS. ![Windows Server desktop shown over Remote Desktop](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-windows-5-connected.png) ### Can't get in? Run the [Windows Troubleshooter](https://vpsdime.com/knowledgebase/windows-vps/windows-troubleshooter) (https://vpsdime.com/wintroubleshooter), it checks power, RDP, and your password, and can reset the password on the spot. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the exact message Remote Desktop Connection shows, - what the Windows Troubleshooter reported. ### Related questions - "How do I RDP into my Windows VPS from my PC?" - "Do I need Windows Pro to use Remote Desktop Connection?" - "What do I do with the RDP certificate warning?" - "I can't find Remote Desktop Connection on my computer." --- ## How to connect to my Windows VPS from my Mac URL: https://vpsdime.com/knowledgebase/windows-vps/connect-from-mac Last reviewed: 2026-07-02 Summary: A screenshot walkthrough of connecting to your Windows VPS from macOS with Microsoft's Windows App (formerly Microsoft Remote Desktop), add a PC with your VPS IP and log in as Administrator. ### What this is Connecting to your Windows VPS from macOS. You'll use Microsoft's free client, now called **Windows App** in the Mac App Store (older guides and screenshots call it "Microsoft Remote Desktop", same app). Have your **VPS IP** and **Administrator password** handy (both in your welcome email, subject "New Windows VPS - Provisioning Started"). ### Steps 1. Install [Windows App from the Mac App Store](https://apps.apple.com/us/app/windows-app/id1295203466) and open it. 2. Click the **+** icon, then **Add PC**. ![The Add PC menu in the Mac remote desktop client](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-mac-1-add-pc.png) 3. Copy and paste your VPS IP into the **PC name** field. Leave everything else at the defaults and click **Add**. ![Add PC dialog with the PC name field filled in](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-mac-2-pc-name.png) 4. Double-click the newly created PC. ![The saved PC tile ready to be opened](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-mac-3-open-pc.png) 5. Enter `Administrator` as the **Username**, and **copy and paste** your password to avoid typos. Click **Connect**, and accept the certificate prompt with **Continue**. ![macOS credentials prompt for the remote connection](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-mac-4-credentials.png) 6. You're in, the Windows desktop of your VPS, from your Mac. ![Windows Server desktop displayed in the Mac client](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-mac-5-connected.png) ### Can't get in? Run the [Windows Troubleshooter](https://vpsdime.com/knowledgebase/windows-vps/windows-troubleshooter) (https://vpsdime.com/wintroubleshooter), it checks power, RDP, and your password, and can reset the password on the spot. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the exact message the Mac client shows, - what the Windows Troubleshooter reported. ### Related questions - "How do I connect to a Windows VPS from macOS?" - "What RDP client do I use on a Mac?" - "Microsoft Remote Desktop vs Windows App, which one?" --- ## How to connect to my Windows VPS using an iPhone or iPad URL: https://vpsdime.com/knowledgebase/windows-vps/connect-from-iphone-ipad Last reviewed: 2026-07-02 Summary: A screenshot walkthrough of connecting to your Windows VPS from iOS/iPadOS with Microsoft's Windows App Mobile (formerly Remote Desktop Mobile), add a PC with your VPS IP and log in as Administrator. ### What this is Connecting to your Windows VPS from an iPhone or iPad with Microsoft's free client, now called **Windows App Mobile** on the App Store (older screenshots say "Remote Desktop Mobile", same app). Have your **VPS IP** and **Administrator password** handy (both in your welcome email, subject "New Windows VPS - Provisioning Started"). ### Steps 1. Install [Windows App Mobile from the App Store](https://apps.apple.com/us/app/remote-desktop-mobile/id714464092) and open it. 2. Tap the **+** icon in the upper right, then **Add PC**. ![The Add PC option in the iOS client](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-ios-1-add-pc.jpeg) 3. Tap the **PC Name** field. ![Add PC screen with the PC Name field highlighted](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-ios-2-pc-name-field.jpeg) 4. Enter your VPS IP address, **copy and paste it** to avoid typos, then tap the **Back** arrow. ![PC Name screen with the VPS IP entered](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-ios-3-pc-name.jpeg) 5. Leave the other settings at their defaults and tap **Save**. ![Add PC screen ready to be saved](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-ios-4-save.jpeg) 6. On the **PCs** screen, tap the newly created entry. ![The saved PC tile on the PCs screen](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-ios-5-open-pc.jpeg) 7. Enter `Administrator` as the **Username**, **paste** your password, and tap **Continue**. ![iOS credentials prompt for the remote connection](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-ios-6-credentials.png) 8. You're in, your Windows VPS desktop on your iPhone or iPad. ![Windows Server desktop displayed on an iPhone](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-ios-7-connected.png) ### Can't get in? Run the [Windows Troubleshooter](https://vpsdime.com/knowledgebase/windows-vps/windows-troubleshooter) (https://vpsdime.com/wintroubleshooter), it checks power, RDP, and your password, and can reset the password on the spot. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the exact message the iOS client shows, - what the Windows Troubleshooter reported. ### Related questions - "How do I RDP into my Windows VPS from my iPhone?" - "Is there a remote desktop app for iPad?" - "What username do I use on the mobile RDP app?" --- ## How can I connect my Windows VPS using an Android phone or device URL: https://vpsdime.com/knowledgebase/windows-vps/connect-from-android Last reviewed: 2026-07-02 Summary: A screenshot walkthrough of connecting to your Windows VPS from Android (or a Chromebook) with Microsoft's Remote Desktop client, add a PC with your VPS IP and log in as Administrator. ### What this is Connecting to your Windows VPS from an Android phone, tablet, or Chromebook with Microsoft's free **Remote Desktop** client. Have your **VPS IP** and **Administrator password** handy (both in your welcome email, subject "New Windows VPS - Provisioning Started"). ### Steps 1. Install [Remote Desktop by Microsoft from Google Play](https://play.google.com/store/apps/details?id=com.microsoft.rdc.androidx), open it, and accept the license. 2. Tap the **+** icon in the top right. ![The add button in the Android client](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-android-1-add.jpeg) 3. Tap **Add Manually**. ![The Add Manually option](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-android-2-add-manually.jpeg) 4. Enter your VPS IP in the **PC name** field and save. ![Add PC screen with the PC name field](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-android-3-pc-name.jpeg) 5. Tap the connection you just created. ![The saved connection tile](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-android-4-connection-added.jpeg) 6. Enter `Administrator` as the **Username**, **paste** your password, and tap **Continue**. ![Android credentials prompt](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-android-5-credentials.jpeg) 7. Tick **"Never ask again for connections to this PC"** and tap **Connect**. ![Certificate trust prompt with the never-ask-again checkbox](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-android-6-trust.jpeg) 8. You're in, your Windows VPS desktop on Android. ![Windows Server desktop displayed on an Android device](https://vpsdime.com/knowledgebase/windows-vps/images/rdp-android-7-connected.jpeg) ### Can't get in? Run the [Windows Troubleshooter](https://vpsdime.com/knowledgebase/windows-vps/windows-troubleshooter) (https://vpsdime.com/wintroubleshooter), it checks power, RDP, and your password, and can reset the password on the spot. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the exact message the Android client shows, - what the Windows Troubleshooter reported. ### Related questions - "How do I RDP into my Windows VPS from Android?" - "Can I manage my Windows VPS from a Chromebook?" - "What app do I use for remote desktop on Android?" --- ## How many people can connect to my Windows VPS at once? URL: https://vpsdime.com/knowledgebase/windows-vps/rdp-connection-limit Last reviewed: 2026-07-02 Summary: Windows Server allows two simultaneous RDP sessions out of the box, a Microsoft licensing limit, not ours. More concurrent users require Remote Desktop Services with RDS CALs you purchase yourself, but check the alternatives first, screen-sharing tools like TeamViewer/AnyDesk for assist scenarios, or separate VPSes per user. ### What this is Out of the box, Windows Server allows **two simultaneous Remote Desktop sessions**. A third person connecting gets *"Too many users are signed in"* and is asked to pick an existing session to disconnect. Two related behaviors that look like bugs but aren't: - **The same account takes over its own session.** If you log in with an account that's already connected, Windows hands you that session and the other device sees *"Your Remote Desktop Services session has ended, another user connected."* That's per-account behavior by design, give each person their **own Windows user account** instead of sharing Administrator, and the two of you can genuinely work side by side. - **The limit counts sessions, not attempts**, two colleagues on two accounts is fine; the third concurrent desktop is where the wall is. ### Where the limit comes from This is **Microsoft licensing, not a VPSDime restriction**. The Windows Server Datacenter license [included with your VPS](https://vpsdime.com/knowledgebase/presales/windows-vps) covers the two administrative sessions. Concurrent desktops beyond that require **Remote Desktop Services (RDS)**: the RD Session Host role plus **RDS CALs** (client access licenses, per-user or per-device) which **you purchase yourself** from Microsoft or a licensing reseller and install with the RD Licensing role. Setting RDS up is standard Windows administration, and like everything inside the OS it's [self-managed territory](https://vpsdime.com/knowledgebase/support-coverage/what-support-covers), we don't sell or provision CALs. ### Before you buy CALs: cheaper ways to share a server Match the solution to what people actually need: - **They need to see or assist, not own a desktop:** screen-sharing tools, **TeamViewer**, **AnyDesk**, **RustDesk** (open source, self-hostable), or Chrome Remote Desktop, share the *existing* session with any number of viewers, need no extra Windows licenses, and are the right tool for support sessions, demos, and pair work. - **Each person needs their own simultaneous desktop:** that's what RDS CALs are for, or, often simpler and cleaner, **a separate Windows VPS per user**: no RDS plumbing, no license administration, full isolation, and predictable cost. - **They only need the application or its data:** serving it as a web app or letting them connect to the service directly (a database, an API) needs no desktop sessions at all. ### Managing the sessions you have - **See who's connected:** Task Manager → **Users** tab, or `query session` in a terminal. - **Free a slot:** sign out a session from that Users tab (right-click → Sign off), or `logoff `. Signing out ends their programs; disconnecting merely detaches and **keeps consuming the slot**. - Locked out because both slots are taken by stale sessions? Connect once more with one of the *same* accounts, you'll take over its session rather than needing a third. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - how many people need to be connected at once, - whether they need their own desktops or just to see one screen. ### Related questions - "How many RDP users can connect to my Windows VPS at the same time?" - "What does 'too many users are signed in' mean?" - "Why does my RDP session end when a colleague logs in?" - "Do I need terminal services / RDS CALs, and where do I get them?" - "Is there a way to share a Windows VPS without buying licenses?" - "How do I sign out another RDP session?" --- ## SSH and PowerShell remoting on your Windows VPS URL: https://vpsdime.com/knowledgebase/windows-vps/ssh-on-windows Last reviewed: 2026-07-02 Summary: Windows Server includes an optional OpenSSH server, install it in two commands and manage the VPS from a terminal, scp/rsync-style transfers, scripted administration, key authentication (with the administrators_authorized_keys gotcha), even terminal AI agents. Plus the same restrict-and-key security rules RDP gets. ### What this is RDP is the desktop; sometimes you want the **terminal**: quick edits over a slow link, scripted administration, `scp`-style file transfers, or pointing a [terminal AI agent](https://vpsdime.com/knowledgebase/getting-started/claude-code-on-vps) at the machine. Windows Server ships an **OpenSSH server** as an optional feature, two commands and your Windows VPS speaks the same SSH as everything else you run. ### Install and start it In an elevated PowerShell (over RDP): ```powershell Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0 Start-Service sshd Set-Service sshd -StartupType Automatic ``` Installing the capability normally creates the firewall rule for port 22, verify rather than assume: `Get-NetFirewallRule -Name *ssh*` (and [add it if missing](https://vpsdime.com/knowledgebase/windows-vps/windows-firewall)). Then from your own machine: ``` ssh Administrator@YOUR.VPS.IP ``` with your Administrator password, you land in a Windows shell on the VPS. Two nice upgrades: make **PowerShell the default SSH shell** (instead of cmd): ```powershell New-ItemProperty -Path "HKLM:\SOFTWARE\OpenSSH" -Name DefaultShell -Value "C:\Program Files\PowerShell\7\pwsh.exe" -PropertyType String -Force ``` (or the `powershell.exe` path for built-in 5.1), and `scp`/`sftp` now work against the VPS for file transfer, the [same clients and habits](https://vpsdime.com/knowledgebase/getting-started/uploading-files-sftp) as on Linux. ### Key authentication, and the Windows gotcha Keys work, and [the generation story is identical](https://vpsdime.com/knowledgebase/getting-started/setting-up-ssh-keys), but Windows has one famous trap: for accounts in the **Administrators group**, OpenSSH does **not** read `~/.ssh/authorized_keys`. Admin keys go in a shared file instead: ``` C:\ProgramData\ssh\administrators_authorized_keys ``` Append your public key there, and the file's permissions must be restricted to Administrators and SYSTEM (if you created it fresh, run: `icacls C:\ProgramData\ssh\administrators_authorized_keys /inheritance:r /grant "Administrators:F" /grant "SYSTEM:F"`). Half of all "key auth won't work on Windows" threads are this one paragraph. Once keys work, the [RDP hardening logic](https://vpsdime.com/knowledgebase/windows-vps/protecting-rdp) applies to SSH too: consider disabling password auth (`PasswordAuthentication no` in `C:\ProgramData\ssh\sshd_config`, then `Restart-Service sshd`), and IP-restrict the port 22 rule the same way as RDP's. ### PowerShell remoting, the other door Native Windows remote administration is **WinRM** (`Enter-PSSession`, `Invoke-Command`), powerful inside trusted networks, but its authentication over the open internet is fiddlier than SSH's. On a lone VPS, SSH (which modern PowerShell rides happily, `Enter-PSSession -HostName vps -UserName Administrator` works over it) is the simpler, better-understood door. Pick one, secure it well, and don't leave both wide open. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what fails (install, connection, key auth) with the exact message, - whether password SSH works while key auth doesn't. ### Related questions - "How do I SSH into my Windows VPS?" - "How do I install OpenSSH Server on Windows Server?" - "Why doesn't my SSH key work for Administrator on Windows?" - "How do I make PowerShell the default SSH shell?" - "SSH or WinRM for managing a Windows VPS?" --- ## How to transfer files to and from your Windows VPS URL: https://vpsdime.com/knowledgebase/windows-vps/transfer-files-windows-vps Last reviewed: 2026-07-02 Summary: The ways to move files, ranked by setup cost: copy-paste through the RDP clipboard, RDP drive redirection (your local disks appear on the VPS, zero install), downloading directly on the VPS, SCP/SFTP via the optional OpenSSH server for scripted and large transfers, and the one method to never use across the internet (SMB). Plus the stuck-clipboard fix everyone eventually needs. ### What this is Moving files between your computer and your Windows VPS, five ways, ranked by how much setup they cost. The first two need nothing installed at all, they're built into the RDP connection you already use. ### 1. Copy-paste through RDP (zero setup, small files) The RDP clipboard carries **files**, not just text: copy a file in Explorer on your computer (Ctrl+C), click into the [RDP session](https://vpsdime.com/knowledgebase/windows-vps/connect-rdp), and paste (Ctrl+V) onto the desktop or into a folder. Works both directions. Right tool for documents, configs, and installers; wrong tool for multi-gigabyte transfers, the clipboard channel is slow and a dropped session cancels the copy with no resume. ### 2. RDP drive redirection (zero install, the proper way) Your **local drives can appear inside the VPS's Explorer**, then any copy is a normal file copy: - **Windows client:** in Remote Desktop Connection, **Show Options → Local Resources → More... → Drives**, tick what to share, then connect. Your disks show up on the VPS as `C on YOURPC` under "This PC". - **Mac / mobile clients:** edit the PC entry → folder redirection in the connection settings, pick a local folder to share into the session. Transfers run at your connection's real speed, handle big files fine, and there's nothing to install or expose, the share exists only inside your RDP session. (Set it **before** connecting; drives ticked mid-session don't appear until you reconnect.) ### 3. Download directly on the VPS (often the fastest) If the file lives on the internet, on a website, cloud storage, a git repo, don't route it through your home connection at all: fetch it **on the VPS**, which sits on the fat pipe. A browser (after the [IE ESC fix](https://vpsdime.com/knowledgebase/windows-vps/cant-download-ie-esc)), or PowerShell: ```powershell Invoke-WebRequest -Uri "https://example.com/big-installer.iso" -OutFile "C:\Users\Administrator\Downloads\big-installer.iso" ``` The same logic applies in reverse: for getting something big *off* the VPS to a third place, upload from the VPS directly. ### 4. SCP/SFTP, for scripted and heavy-duty transfers Install the [optional OpenSSH server](https://vpsdime.com/knowledgebase/windows-vps/ssh-on-windows) once, and the whole SSH transfer toolbox works against your Windows VPS: `scp`, `sftp`, WinSCP and FileZilla, [the same clients and habits as on Linux](https://vpsdime.com/knowledgebase/getting-started/uploading-files-sftp). This is the right layer for automation, repeated deployments, and anything you'd script, and for **recurring backup-shaped transfers**, skip ad-hoc copying entirely and use [a real backup tool](https://vpsdime.com/knowledgebase/windows-vps/backing-up-windows-vps) (restic ships the changes, encrypted, on a schedule). ### 5. The one to avoid: SMB across the internet Windows file sharing (mapping `\\YOUR.VPS.IP\share`) is built for trusted networks, **never expose port 445 to the internet**, [it's the most attacked Windows port in history](https://vpsdime.com/knowledgebase/windows-vps/securing-your-windows-vps). If you genuinely want SMB between your machines, put a VPN (WireGuard/Tailscale) between them first and share over that. ### Troubleshooting - **Paste suddenly stopped working in the session.** The clipboard helper on the VPS wedged, the classic fix: in Task Manager on the VPS, end the **rdpclip.exe** process, then File → Run new task → `rdpclip`. Copy-paste returns instantly. - **My drives don't show up on the VPS.** The Drives box wasn't ticked before connecting, disconnect, tick it, reconnect. Some mobile clients need the folder added to the PC entry, not the global settings. - **A huge transfer keeps dying.** Use method 3 (fetch on the VPS) or method 4 (scp/WinSCP), both beat the RDP channel for bulk, and check [the path](https://vpsdime.com/knowledgebase/troubleshooting/testing-network-speed) if speeds look wrong everywhere. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which method you're using (clipboard, drive redirection, SCP), - roughly how big the transfer is and what happens when it fails. ### Related questions - "How do I copy files to my Windows VPS?" - "Why can't I paste files into my RDP session?" - "How do I see my local drives inside the VPS?" - "What's the fastest way to get a large file onto my VPS?" - "Can I use FileZilla or WinSCP with a Windows VPS?" - "Is it safe to map a network drive to my VPS over the internet?" --- ## RDP feels laggy: resolution, color depth, and performance tuning URL: https://vpsdime.com/knowledgebase/windows-vps/rdp-performance Last reviewed: 2026-07-02 Summary: Making a Remote Desktop session responsive over a long or slow path (connecting from far away, mobile connections), lower the resolution, drop color depth to 16-bit, use the Experience presets, trim the server's visual effects, and know which lag is physics (and what to do about that instead). ### What this is Making an RDP session feel responsive when the connection between you and the VPS is long or thin, connecting from another continent, hotel Wi-Fi, or mobile data. RDP sends **pixels**, so everything that reduces pixels-per-second makes typing and clicking snappier; the knobs below are ordered by payoff. One check first: confirm the lag is the **path**, not the server, Task Manager on the VPS quiet while the session feels bad = path ([the discriminator](https://vpsdime.com/knowledgebase/windows-vps/windows-vps-slow)). A busy server lags in its own way and no display setting fixes that. ### 1. Lower the resolution (the biggest lever) Painting a 4K desktop over a 200 ms path is the problem in one sentence. In Remote Desktop Connection: **Show Options → Display tab → slide the size down**, 1600×900 or 1366×768 is dramatically lighter than full-screen-on-a-4K-monitor and still perfectly workable for admin tasks. On the Mac and mobile clients it's the **resolution setting on the PC entry**. Windowed beats full-screen on high-DPI displays for the same reason. ### 2. Drop the color depth Same tab, **Colors → High Color (16 bit)**. For server administration you will genuinely not miss the other 16 million colors, and the bandwidth cut is large. ### 3. The Experience tab **Experience tab → choose "Low-speed broadband"** (or "Modem" for truly bad links), or untick manually: desktop background, font smoothing, window contents while dragging, menu animation, all of it is decoration you're paying latency for. Keep **Persistent bitmap caching** ticked, it's the one that *helps*, reusing already-sent pixels. ### 4. Trim the server side On the VPS itself: run `SystemPropertiesPerformance` → **Adjust for best performance** (or keep just "smooth edges of screen fonts"). Fewer animations and shadows generated means fewer pixels shipped. A solid-color desktop background does the same for wallpaper. ### 5. Let UDP work Modern RDP negotiates a **UDP transport** alongside TCP, and it copes far better with latency and packet loss. The clients do this automatically; it only breaks when a network in between blocks UDP, so if a session feels much worse from one location (office network) than another, that's a suspect. Nothing to configure on the VPS. ### 6. Don't stream video over RDP The worst case for a pixel protocol is a screen full of pixels changing 30 times a second. If the task is "watch/process a video that's on the VPS", [transfer it down](https://vpsdime.com/knowledgebase/windows-vps/transfer-files-windows-vps) and play it locally; if it's "download something to the VPS", do it [on the VPS directly](https://vpsdime.com/knowledgebase/windows-vps/transfer-files-windows-vps), no reason for those pixels to travel at all. ### When it's physics From South Asia to a US datacenter, 200 ms round trips are [geography, not a fault](https://vpsdime.com/knowledgebase/troubleshooting/network-problems), the settings above make typing and clicking comfortable at that distance, but they can't make it feel local. If the latency itself is the problem and it's persistent: verify the path is *clean* (mtr, [the network guide](https://vpsdime.com/knowledgebase/troubleshooting/network-problems), sustained loss is fixable, distance isn't), and consider whether a **datacenter closer to you** is the right call, location is chosen at [deploy](https://vpsdime.com/knowledgebase/client-area/deploy/deploying-a-new-vps) time, and existing VPSes can be [migrated](https://vpsdime.com/knowledgebase/client-area/services/migrate-location) (the IP changes with a move; $4 with your data kept, free as a clean re-provision). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP and where you're connecting from, - which settings you've already lowered, - whether Task Manager on the VPS is quiet while the session lags. ### Related questions - "How do I change the resolution of my RDP session?" - "How do I make RDP less laggy from far away?" - "What color depth should I use for RDP?" - "Which Experience settings make Remote Desktop faster?" - "Why is RDP choppy on my office network but fine at home (UDP)?" - "Can anything make RDP feel local from another continent?" --- ## What is my Administrator password? URL: https://vpsdime.com/knowledgebase/windows-vps/administrator-password Last reviewed: 2026-07-04 Summary: Your Windows VPS Administrator password is generated at deployment and sent in the provisioning email (subject "New Windows VPS - Provisioning Started"). Copy-paste it without surrounding whitespace; if it's lost or not working, the Windows Troubleshooter can verify and reset it. ### What this is Your Windows VPS login is the built-in **Administrator** account, and its password is generated when your VPS is provisioned. It's sent to you in the provisioning email, subject: **"New Windows VPS - Provisioning Started"**, along with your VPS IP. ### Using it - The username is always `Administrator`. - **Copy and paste the password**, and make sure you're not picking up **whitespace before or after it**, a trailing space from the email is the most common "wrong password" cause. - Once you're in, you can change it inside Windows (Ctrl+Alt+End in an RDP session opens the security screen with the change-password option). ### Lost it, or it doesn't work? The [Windows Troubleshooter](https://vpsdime.com/knowledgebase/windows-vps/windows-troubleshooter) checks whether the password on file actually works against your VPS and offers a **reset** right on the page, no ticket needed. If the password is rejected when you try to log in, see [My Administrator password doesn't work](https://vpsdime.com/knowledgebase/windows-vps/administrator-password-not-working). Self-service resets depend on the **[VPSDime Support Account](https://vpsdime.com/knowledgebase/windows-vps/vpsdime-support-account)**, the service user starting with `DIME` that we add at provisioning. If that account has been removed from your server, the reset tools can't reach it, and a manual reset by our team carries a **$25 fee**. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - whether the Windows Troubleshooter's password check passes or fails, - the exact message your RDP client shows. ### Related questions - "What is my Windows VPS password?" - "Where do I find my Administrator login details?" - "How do I change or reset my Administrator password?" --- ## My Administrator password doesn't work URL: https://vpsdime.com/knowledgebase/windows-vps/administrator-password-not-working Last reviewed: 2026-07-05 Summary: When your Windows VPS rejects the Administrator password, check for copied whitespace first, then run the Windows Troubleshooter, it verifies the password on file against your VPS and lets you reset it on the spot. If the error mentions Remote Desktop License Servers, the password isn't the problem, an RD Session Host role's 120-day licensing grace expired, get in via the Console, reset the grace, and remove or properly license the role. ### What this is Your Windows VPS rejects the Administrator password at the RDP login. Two checks solve nearly every case, and one look-alike error, about license servers, isn't a password problem at all (covered below). ### 1. Check what you're actually pasting The password came in your provisioning email ("New Windows VPS - Provisioning Started"). When copying from email, it's very easy to pick up **whitespace before or after the password**, which makes a correct password wrong. Paste it into a plain text field first to inspect it, or re-select it carefully character to character. Also confirm the username is exactly `Administrator`, and that you're connecting to the right IP if you have several servers. ### 2. Let the troubleshooter test and reset it The **[Windows Troubleshooter](https://vpsdime.com/knowledgebase/windows-vps/windows-troubleshooter)** does the definitive check: it verifies your VPS is powered on, that Remote Desktop is enabled, and **whether the password on file actually works** against the server. 1. In your client area, open **Support** in the top menu and click **"I can't login to Windows VPS"** (or go to https://vpsdime.com/wintroubleshooter), then pick the VPS. ![Windows Troubleshooter, selecting the VPS to check](https://vpsdime.com/knowledgebase/windows-vps/images/windows-troubleshooter-1-select-vps.png) 2. It runs the checks against your VPS. ![Windows Troubleshooter running its status and health checks](https://vpsdime.com/knowledgebase/windows-vps/images/windows-troubleshooter-2-checks.png) 3. If the password on file **doesn't** work, it offers a **reset option right on the page**. If everything checks out, it shows your working credentials with copy-to-clipboard buttons, so you can paste them cleanly into your RDP client. ![Windows Troubleshooter results with credentials and reset option](https://vpsdime.com/knowledgebase/windows-vps/images/windows-troubleshooter-3-results.png) ### If the error mentions license servers, it's not the password One failure wears a password-problem disguise. If the **Remote Desktop Session Host** role was installed on the server (often ticked during a domain or multi-user setup) and never pointed at a licensing server, Windows grants a **120-day grace period**, then stops issuing normal RDP sessions. From that day, logins fail no matter how correct the password is, most recognizably with: > *The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license.* The password is fine; the RD licensing grace is what expired. The way back in is the **[Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps)** in your client area, console sessions aren't gated by RD licensing. From there you can reset the grace period to get RDP accepting sessions again (delete the `GracePeriod` key under `HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM`, you'll need to take ownership of it first, then reboot), but treat that as a stopgap: it restarts the same 120-day clock, it doesn't license anything. Fix the cause while you're in there: - **Remove the role if you don't actually use it.** Without it, Windows returns to its built-in two-admin-session model, which never expires: `Uninstall-WindowsFeature RDS-RD-Server -Restart` - **Or configure it properly** if you genuinely need more than two concurrent sessions: an RD Licensing server with purchased RDS CALs, and the Session Host pointed at it. The full walkthrough, including the other ways a domain setup breaks RDP logins, is in [Can't RDP into your Windows VPS after joining a domain](https://vpsdime.com/knowledgebase/windows-vps/rdp-after-domain-join). ### If the reset doesn't work (or isn't offered) The troubleshooter's reset works through the **[VPSDime Support Account](https://vpsdime.com/knowledgebase/windows-vps/vpsdime-support-account)**, a service user starting with `DIME` that we add to every Windows VPS at provisioning. If you (or someone hardening the server) removed that account, self-service resets can't reach your VPS anymore, in that case a manual reset by our team is the path, and it carries a **$25 fee**. ### Still locked out? If the troubleshooter's checks pass, the password resets, and you still can't get in, finish the troubleshooter flow, it escalates into a ticket with the diagnostics attached, or [open a ticket](https://vpsdime.com/open-ticket/) with the VPS IP and what the RDP client says. ### Related questions - "My Windows VPS says the password is wrong." - "How do I reset my Administrator password?" - "Why does the password from my email not work?" - "How do I check if RDP is enabled on my VPS?" - "RDP says no Remote Desktop License Servers are available, is my password wrong?" - "Why did RDP logins stop working 120 days after setting up my server?" --- ## How can I use the Windows Troubleshooter? URL: https://vpsdime.com/knowledgebase/windows-vps/windows-troubleshooter Last reviewed: 2026-07-04 Summary: The Windows Troubleshooter (Support, "I can't login to Windows VPS") automatically checks that your VPS is powered on, that Remote Desktop is enabled, and that the Administrator password on file works, then hands you working credentials or a password reset. ### What this is An automated checker for Windows VPS connection problems, use it **before** opening a ticket, because it fixes the common causes on the spot. It's at https://vpsdime.com/wintroubleshooter, or from your client area: **Support** in the top menu, then **"I can't login to Windows VPS"**. (It's the Windows counterpart of the checks [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) runs.) ### What it does 1. Pick the VPS you can't reach. ![Windows Troubleshooter, selecting the VPS to check](https://vpsdime.com/knowledgebase/windows-vps/images/windows-troubleshooter-1-select-vps.png) 2. It checks three things automatically: the VPS is **powered on**, **Remote Desktop is enabled**, and the **Administrator password on file works**. ![Windows Troubleshooter running its status and health checks](https://vpsdime.com/knowledgebase/windows-vps/images/windows-troubleshooter-2-checks.png) 3. Then it acts on what it finds: - **All three checks pass:** it shows your **connection credentials with copy-to-clipboard buttons** (IP, `Administrator`, password), paste them straight into your RDP client, plus links to the [per-device connection guides](https://vpsdime.com/knowledgebase/windows-vps/connect-rdp). - **The password on file doesn't work:** it offers a **reset option** on the same page. The reset works through the [VPSDime Support Account](https://vpsdime.com/knowledgebase/windows-vps/vpsdime-support-account) (the service user starting with `DIME`); if that account was removed from your server, the reset can't run and a manual reset by our team carries a $25 fee. ![Windows Troubleshooter results with credentials and reset option](https://vpsdime.com/knowledgebase/windows-vps/images/windows-troubleshooter-3-results.png) ### If it doesn't solve it Finish the flow, it escalates into a support ticket with the diagnostics already attached, which is the fastest route to a useful first reply. ### When even the troubleshooter can't reach it The troubleshooter's checks need the VPS's OS to respond. A machine that has been driven deep into memory exhaustion (pagefile thrashing) can't answer them, and the Console won't help either, it shows the screen of an OS too starved to react. For that state, use **Reset** on the [manage page](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) for a hard reboot, then see [My Windows VPS is frozen or unresponsive](https://vpsdime.com/knowledgebase/windows-vps/windows-vps-unresponsive) for why it happened and how to keep it from recurring. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what the troubleshooter's checks reported, - what your RDP client says when you try to connect. ### Related questions - "How do I use the Windows Troubleshooter?" - "I can't log in to my Windows VPS, what do I run first?" - "How do I check whether RDP is enabled?" - "Where do I reset my Windows VPS password myself?" --- ## The VPSDime Support Account (DIME user) URL: https://vpsdime.com/knowledgebase/windows-vps/vpsdime-support-account Last reviewed: 2026-07-04 Summary: Every Windows VPS is provisioned with a service user whose name starts with DIME. Our backend uses it for self-service Administrator password resets, plan upgrades and downgrades, usage statistics, and live migrations. You may remove it, but self-service password resets stop working, and a manual reset by our team carries a $25 fee. ### What this is When your Windows VPS is provisioned, we add a service user to it whose **username starts with `DIME`**, followed by a string of random characters, so it looks something like `DIMExxxxxx` in your user list. It's mentioned in your provisioning email, and if you're auditing the accounts on your server, this is the one you didn't create. It is not an intruder, it's how our backend operates your VPS on your behalf. The Support Account is what makes these features work: - **Self-service Administrator password resets**, in the client area and the [Windows Troubleshooter](https://vpsdime.com/knowledgebase/windows-vps/windows-troubleshooter), - **Plan upgrades and downgrades**, - **Usage statistics** shown in your control panel, - **Live migrations**, moving your VPS between host machines without downtime. We never need your Administrator password for any of these while the Support Account exists. ### The Console signs in as this account When you open the out-of-band **Console** for a Windows VPS from your client area, it signs you into the **Support Account's session**, not your Administrator session. So the desktop you see there, and its settings, wallpaper, and open windows, will look nothing like your own. That's expected, it's a different user, and it's set up this way so there's always a working way into the server when RDP or your own account isn't cooperating. Use that session to fix whatever brought you to the Console. If you need your own environment instead, **sign out** (Start, user icon, Sign out) and log in as `Administrator` with your own password, the Console works with any local account. ### Can I remove it? Yes. It's your server, and you're welcome to remove or disable the account. Before you do, understand what changes: - **Password resets stop being self-service.** The reset options in the client area and the Windows Troubleshooter depend on the Support Account, without it they can't touch your server. If you later forget the Administrator password, recovery becomes **manual work for our engineers and carries a $25 fee**. - **Upgrades, downgrades, and live migrations** can no longer happen automatically. Where our backend would have handled these invisibly, they turn into tickets, and may require your Administrator password. - **Usage statistics** in your control panel stop updating. If you manage your own credentials carefully (password manager, tested backups of what matters), removing the account is a legitimate hardening choice, several customers run this way. Just make that choice knowing the password-reset safety net goes with it. ### If you removed it and want it back [Open a ticket](https://vpsdime.com/open-ticket/). Because the account is gone, we can't act on the server from the outside anymore, so restoring it is something we arrange together, have your Administrator password ready. ### A note on hardening Auditing the accounts on your server is good practice, and this page exists so the audit doesn't end with deleting ours by accident. If you keep the account, leave it as provisioned, changing its group memberships or rights can break the same features as removing it. Put your hardening effort into [RDP protection](https://vpsdime.com/knowledgebase/windows-vps/protecting-rdp) and [firewall rules](https://vpsdime.com/knowledgebase/windows-vps/windows-firewall) instead, that's where Windows VPS attacks actually arrive. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - whether the `DIME`-prefixed user still exists on the server (Computer Management, Local Users and Groups), - what you were trying to do when something failed (password reset, upgrade, statistics). ### Related questions - "There's a user starting with DIME and random letters on my Windows VPS, what is it?" - "Can I delete the VPSDime service account?" - "Why doesn't the password reset in the client area work anymore?" - "Is there a fee for resetting my Administrator password manually?" - "Why did my control panel usage statistics stop updating?" - "Why does the Console show a different desktop than my RDP session?" - "The Console logged me in as some other user, is that normal?" --- ## Securing your Windows VPS URL: https://vpsdime.com/knowledgebase/windows-vps/securing-your-windows-vps Last reviewed: 2026-07-04 Summary: The layered checklist for a Windows Server VPS, and the platform fact that frames it: Windows VPS has no managed edge firewall, so Windows Defender Firewall is your only network layer. Accounts and passwords, RDP hardening, updates, Defender stays on, never exposing SQL/SMB, auditing with Sysinternals, and backups. ### What this is The security checklist for your Windows Server VPS, layered like [its Linux counterpart](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps), but with one platform fact that changes the priorities: **Windows VPS does not sit behind our managed edge firewall** (that's a Linux VPS feature). Every service listening on your Windows VPS is internet-facing unless **Windows Defender Firewall** says otherwise, which makes the firewall and RDP sections below the load-bearing ones. ### 1. Accounts and passwords - The **Administrator password** is the key to everything: long, unique, from a password manager, and pasted carefully ([the whitespace trap](https://vpsdime.com/knowledgebase/windows-vps/administrator-password-not-working)). - **One account per human.** Sharing Administrator between colleagues costs you [your second RDP session](https://vpsdime.com/knowledgebase/windows-vps/rdp-connection-limit) and any ability to tell who did what. Create additional accounts (Computer Management → Local Users and Groups), and give daily-use accounts **standard user** rights where full admin isn't needed. - Leave **UAC on**, it's the consent prompt between a mistake and a system change. - When auditing accounts, you'll find a user whose name starts with `DIME`: that's the [VPSDime Support Account](https://vpsdime.com/knowledgebase/windows-vps/vpsdime-support-account), it powers self-service password resets, upgrades, and live migrations. Read that page before deciding to remove it. ### 2. RDP is your front door, treat it accordingly Port 3389 gets scanned and brute-forced the way SSH does on Linux, and here there's no network-level ban system in front of it, the hardening is yours. The short version: **Network Level Authentication on** (it's the modern default, verify in System Properties → Remote), an **account lockout policy**, and ideally **IP-restricting** the RDP firewall rule. The full treatment, including moving the port and reading the failed-logon log, is in [Protecting RDP from brute force](https://vpsdime.com/knowledgebase/windows-vps/protecting-rdp). ### 3. Keep Windows updated Patch Tuesday exists because the holes are real, and unpatched RDP/SMB vulnerabilities are how Windows servers get owned at scale. Leave automatic updates on and manage the **reboots** rather than the updates, the how (and the "why is my VPS slow on patch day" answer) is in [Windows Updates on your VPS](https://vpsdime.com/knowledgebase/windows-vps/windows-updates). ### 4. Defender stays on Microsoft Defender (antivirus **and** firewall) ships enabled, keep both. Don't install "optimizer" tools or crack-adjacent software that asks you to disable protection first, on a server, that request *is* the attack. If Defender flags something you installed on purpose, add a scoped exclusion for that path rather than lowering the shields globally. ### 5. Don't expose services that don't need exposing The Windows equivalents of the classic self-inflicted holes: - **SQL Server** reachable from the internet (port 1433) with a weak `sa` password, bind it to localhost or firewall it to the app server's IP only. - **SMB file sharing (port 445) to the internet**: never. It's the single most attacked Windows port in history; sharing files off-box goes over a VPN or SFTP instead. - Audit what's listening the same way you would on Linux: `Get-NetTCPConnection -State Listen` (or `netstat -abno` to see which program owns each port), and make each public listener justify itself, [firewall](https://vpsdime.com/knowledgebase/windows-vps/windows-firewall) everything else. If the output is a wall of mystery, pasting it into an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) and asking it to identify each listener works as well on Windows as anywhere. ### 6. Audit with the real tools Microsoft's own **[Sysinternals](https://learn.microsoft.com/sysinternals/)** suite is free and made for exactly this: **Process Explorer** shows what every process actually is (with built-in VirusTotal checking), and **Autoruns** lists everything configured to start with the machine, the first place to look when something feels off, and the same place [miners hide](https://vpsdime.com/knowledgebase/windows-vps/windows-vps-slow). ### 7. Backups are the last line Same doctrine as everywhere: when prevention fails, restoration is the plan. [Backing up a Windows VPS](https://vpsdime.com/knowledgebase/windows-vps/backing-up-windows-vps) covers the add-on and the do-it-yourself layers. And if you're compromised despite everything, the [recovery doctrine](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery) is OS-agnostic: data off, rebuild, rotate every credential. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what you're locking down, or what prompted the check, - anything odd you've already spotted (log entries, processes, listeners). ### Related questions - "How do I secure my Windows VPS?" - "Does my Windows VPS have a firewall in front of it?" - "Should I disable Defender on my server?" - "Is it safe to expose SQL Server or file sharing to the internet?" - "How do I see what's listening on my Windows server?" --- ## Using Windows Defender Firewall on your VPS URL: https://vpsdime.com/knowledgebase/windows-vps/windows-firewall Last reviewed: 2026-07-02 Summary: On a Windows VPS the built-in firewall is your only network layer, how inbound blocking works by default, opening a port for your app (GUI and PowerShell), restricting RDP to your own IPs safely, and verifying from outside. ### What this is Windows VPS has **no managed edge firewall in front of it** (that's a Linux VPS feature), so Windows Defender Firewall is the network layer, and the good news is its default posture is already right: **inbound connections are blocked unless a rule allows them**. Windows and its services create their own rules (RDP's exists out of the box), so your job is only two things: open ports for what you deliberately serve, and tighten the rules you inherited. ### Opening a port for your application Say your app listens on TCP 8080. First, remember [a port only answers if something is listening](https://vpsdime.com/knowledgebase/troubleshooting/my-port-xxx-is-closed), confirm your app runs, then allow it: **PowerShell (fastest):** ```powershell New-NetFirewallRule -DisplayName "MyApp 8080" -Direction Inbound -Protocol TCP -LocalPort 8080 -Action Allow ``` **GUI:** run `wf.msc` → Inbound Rules → New Rule → Port → TCP, 8080 → Allow → name it. Same result. Then verify from **outside** (your own machine): `Test-NetConnection YOUR.VPS.IP -Port 8080`, or any online port checker, reading the result with the [closed-vs-filtered rule](https://vpsdime.com/knowledgebase/troubleshooting/my-port-xxx-is-closed). Ask an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) to draft rules for anything fancier (port ranges, UDP, specific programs), `New-NetFirewallRule` has a parameter for everything. ### Restricting RDP to your own IPs The highest-value tightening on the whole server, RDP reachable only from addresses you control ends the brute-force question outright: 1. `wf.msc` → **Inbound Rules** → find **Remote Desktop - User Mode (TCP-In)**. 2. Properties → **Scope** tab → Remote IP address → **These IP addresses** → add your home/office IPs (find yours on any "what is my IP" site). 3. OK, the change applies immediately. Two safety notes: **your home IP may be dynamic**, so add a range or your mobile carrier's egress too if you can, and know the fallback before you need it, the **Console** in your client area reaches the VPS without RDP, so a scope mistake locks the door, not the house (it signs in as the [VPSDime Support Account](https://vpsdime.com/knowledgebase/windows-vps/vpsdime-support-account), so expect a different desktop). (PowerShell equivalent: `Set-NetFirewallRule -DisplayName "Remote Desktop - User Mode (TCP-In)" -RemoteAddress 203.0.113.7`.) ### The habits - **Don't turn the firewall off** to "test something", allow the specific port instead. Off means every listener on the machine is public. - **Profiles** (Domain/Private/Public): on a VPS the network is Public; when creating rules, applying them to all profiles avoids surprises. - Audit occasionally: `Get-NetFirewallRule -Enabled True -Direction Inbound | Where-Object Action -eq Allow` lists everything you're allowing in. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP and the port involved, - the rule you created or changed, - what an outside test of the port shows (refused, or a timeout). ### Related questions - "How do I open a port on my Windows VPS?" - "How do I restrict RDP to my IP address?" - "Is there a firewall in front of my Windows VPS?" - "Should I disable Windows Firewall to test?" - "How do I list my inbound firewall rules?" --- ## Protecting RDP from brute-force attacks URL: https://vpsdime.com/knowledgebase/windows-vps/protecting-rdp Last reviewed: 2026-07-02 Summary: Port 3389 gets hammered the way SSH does, and on a Windows VPS the defense is yours, Network Level Authentication, an account lockout policy, IP-restricting the firewall rule (the real fix), optionally moving the port, and reading the failed-logon evidence in Event ID 4625. ### What this is Any Windows server on the public internet gets its RDP port scanned and password-guessed around the clock, it's the Windows equivalent of the SSH brute-force noise on Linux, but here there's **no network-level ban system in front of you**, so the defense is configured on the server. The measures below are ordered by how much each one actually buys. First, see the problem for yourself: **Event Viewer → Windows Logs → Security**, filter for **Event ID 4625** (failed logon). A fresh public VPS collects thousands of these, random usernames from random IPs. That's the internet's background radiation, the goal isn't zero attempts, it's making attempts worthless. ### 1. IP-restrict the RDP rule (the real fix) If RDP only answers your own addresses, the entire attack class ends, no guesses, no lockouts, no noise. The [firewall guide walks the exact steps](https://vpsdime.com/knowledgebase/windows-vps/windows-firewall) (scope the built-in Remote Desktop rule to your IPs), including the dynamic-IP caution and the Console-as-fallback safety net. If you can list where you connect from, do this one and the rest becomes defense in depth. ### 2. Verify Network Level Authentication is on NLA makes the connection authenticate **before** a desktop session is created, which starves both credential-guessing and pre-auth exploits. It's the default on every supported Server version, verify it stayed that way: System Properties → Remote → "Allow connections only from computers running Remote Desktop with Network Level Authentication" should be ticked. Leave it ticked; every [client we document](https://vpsdime.com/knowledgebase/windows-vps/connect-rdp) supports it. ### 3. Set an account lockout policy Make guessing self-defeating: after N wrong passwords, the account locks for a cooldown. 1. Run `secpol.msc` → **Account Policies → Account Lockout Policy**. 2. Sensible values: threshold **5** invalid attempts, lockout duration **15 minutes**, reset counter after **15 minutes**. The honest caveat: a lockout policy can lock **you** out for its duration if you fat-finger the password repeatedly (or an attacker deliberately locks a known username). That's recoverable, wait out the cooldown, or use the **Console** in your client area, which doesn't go through RDP (it signs in as the [VPSDime Support Account](https://vpsdime.com/knowledgebase/windows-vps/vpsdime-support-account), so a different desktop is normal), and it's still a good trade: 5-guesses-per-15-minutes reduces brute force from millions of attempts to statistical irrelevance. ### 4. Optionally, move the port Changing RDP off 3389 eliminates the drive-by scanner traffic (targeted attackers will still find it, it's noise reduction, not security). The lockout-safe procedure, firewall rule first, then the registry value, then test, plus the `ip:port` client syntax, is its own guide: [How can I change my RDP port?](https://vpsdime.com/knowledgebase/windows-vps/change-rdp-port) ### 5. Strong, unique password, always Everything above assumes the password isn't "P@ssw0rd2026". Long, unique, from a manager, [pasted without whitespace](https://vpsdime.com/knowledgebase/windows-vps/administrator-password-not-working), and per-person accounts rather than a shared Administrator ([which also fixes the session fights](https://vpsdime.com/knowledgebase/windows-vps/rdp-connection-limit)). ### What good looks like afterwards IP-restricted RDP + NLA + lockout policy means Event 4625 goes quiet, and any entry that *does* appear is worth reading. Check in occasionally; a change in the noise is your early warning. If you suspect someone actually got in, that's the [compromise doctrine](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery), not a settings tweak. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what you've applied so far (NLA, lockout policy, IP restriction), - what the Event ID 4625 activity looks like. ### Related questions - "How do I stop brute-force attacks on RDP?" - "What is Event ID 4625 and why do I have thousands?" - "How do I set an account lockout policy?" - "Should I change the RDP port?" - "What is Network Level Authentication?" --- ## How can I change my RDP port? URL: https://vpsdime.com/knowledgebase/windows-vps/change-rdp-port Last reviewed: 2026-07-02 Summary: Moving Remote Desktop off port 3389 safely, firewall rule for the new port first, then the PortNumber registry value, restart, and test before closing your session, plus the ip:port syntax in every RDP client, the honest obscurity framing, and the Console fallback. ### What this is Moving Remote Desktop off the default **port 3389**. It eliminates the drive-by scanner and brute-force noise (targeted attackers will still find the new port, it's obscurity, not security, [same honesty as the SSH version](https://vpsdime.com/knowledgebase/technical-questions/change-ssh-port)). The measures that actually defend RDP, NLA, a lockout policy, and above all **IP-restricting the rule**, are in [Protecting RDP from brute force](https://vpsdime.com/knowledgebase/windows-vps/protecting-rdp); do those first, and treat the port move as optional noise reduction. ### Steps, in an order that can't lock you out 1. **Firewall rule for the new port first** (say you picked 3390), before anything listens on it: ```powershell New-NetFirewallRule -DisplayName "RDP 3390" -Direction Inbound -Protocol TCP -LocalPort 3390 -Action Allow ``` ([The firewall guide](https://vpsdime.com/knowledgebase/windows-vps/windows-firewall) if you prefer the GUI.) 2. **Change the port in the registry.** Run `regedit`, go to: ``` HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp ``` double-click **PortNumber**, select **Decimal**, and enter your port. (PowerShell equivalent: `Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" -Name PortNumber -Value 3390`.) 3. **Restart** the VPS (or restart Remote Desktop Services, which will drop your session either way). 4. **Test before you trust it**: connect to `YOUR.VPS.IP:3390`, the `ip:port` syntax works in every client we document, the **Computer** field in [Remote Desktop Connection](https://vpsdime.com/knowledgebase/windows-vps/connect-from-windows), the **PC name** field on [Mac](https://vpsdime.com/knowledgebase/windows-vps/connect-from-mac), [iPhone/iPad](https://vpsdime.com/knowledgebase/windows-vps/connect-from-iphone-ipad), and [Android](https://vpsdime.com/knowledgebase/windows-vps/connect-from-android). 5. Once the new port works, remove the old allowance if you'd added a custom 3389 rule (the built-in Remote Desktop rule can simply be disabled), so the old door isn't left open for the scanners you moved to avoid. ### If it went wrong The **Console** in your client area reaches the VPS without RDP, open it, fix the registry value or the firewall rule, restart, and you're back. Don't be surprised by the desktop there: the Console signs in as the [VPSDime Support Account](https://vpsdime.com/knowledgebase/windows-vps/vpsdime-support-account), not as Administrator, a different desktop is normal. Worst case, [the troubleshooter](https://vpsdime.com/knowledgebase/windows-vps/windows-troubleshooter) checks whether RDP is answering at all. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP and the port you moved RDP to, - whether the firewall rule for the new port exists, - whether the Console still gets you in. ### Related questions - "How do I change the RDP port on my Windows VPS?" - "How do I connect to RDP on a custom port?" - "Does changing the RDP port improve security?" - "I changed the RDP port and can't connect anymore." --- ## Windows Updates on your VPS URL: https://vpsdime.com/knowledgebase/windows-vps/windows-updates Last reviewed: 2026-07-02 Summary: Keep automatic updates on and manage the reboots instead, why the VPS feels slow on patch days (TiWorker), the pending-reboot state that causes weirdness, checking and installing updates on Server, scheduling restarts on your terms, and why disabling updates on an internet-facing server is never the answer. ### What this is How updating works on a Windows Server VPS, and the two realities worth knowing in advance: updates are **not optional** on an internet-facing Windows machine (unpatched RDP/SMB holes are how these servers get owned in bulk), and the friction people actually feel, slowdowns and surprise reboots, is a **reboot-management** problem, not a reason to disable updating. ### The rhythm Microsoft ships the main security rollup monthly (**Patch Tuesday**, the second Tuesday), plus occasional out-of-band fixes for actively exploited holes. Windows Server downloads and installs these automatically by default, leave that on, and manage the two side effects below instead. ### "My VPS is slow today", patch-day behavior During and after update installation, **TiWorker.exe** (Windows Modules Installer) and the update service legitimately eat CPU and disk for a while, on smaller plans, noticeably. It finishes on its own; check Task Manager and if TiWorker is the one working, let it, [interrupting servicing is how installs corrupt](https://vpsdime.com/knowledgebase/windows-vps/windows-vps-slow). If it's still grinding many hours later, a reboot usually completes what it's waiting on. ### The pending-reboot state Updates often finish only at the next restart, and a server that sits "pending reboot" for weeks accumulates weirdness: things half-installed, [services misbehaving](https://vpsdime.com/knowledgebase/windows-vps/windows-services-after-reboot), the next update refusing to start. Settings → Windows Update tells you when a restart is pending, do it on your schedule (a quiet hour, after checking your [services start automatically](https://vpsdime.com/knowledgebase/windows-vps/windows-services-after-reboot)) rather than letting it happen on Windows' schedule. **Active hours** (Settings → Windows Update → Advanced) tells Windows when *not* to auto-restart; set it to your working window. ### Driving updates by hand - **GUI:** Settings → Windows Update → Check for updates. - **sconfig** (in a terminal): the classic Server text menu, option 6 handles updates, handy over a laggy session. - **PowerShell:** the community-standard **[PSWindowsUpdate](https://www.powershellgallery.com/packages/PSWindowsUpdate)** module (`Install-Module PSWindowsUpdate`, then `Get-WindowsUpdate` / `Install-WindowsUpdate`) gives you scripted control, including update-then-reboot in one planned maintenance window. ### What not to do Don't disable the Windows Update service to "stop the interruptions", the interruptions move from scheduled to catastrophic, just later. Every mass-exploited Windows worm of the last decade feasted on servers patched months behind. Manage the reboot timing, keep the updates. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what the Windows Update page shows (pending, failed, or a specific KB), - whether a reboot has been pending, and for how long. ### Related questions - "Why is my Windows VPS slow after updates (TiWorker)?" - "How do I control when my Windows VPS reboots for updates?" - "How do I check for updates on Windows Server?" - "Is it safe to disable Windows Update on a VPS?" - "What is a pending reboot and why does it matter?" --- ## Backing up a Windows VPS URL: https://vpsdime.com/knowledgebase/windows-vps/backing-up-windows-vps Last reviewed: 2026-07-02 Summary: The backup doctrine applied to Windows, the Nightly Backups add-on (whole-server images, three-night retention, restores handled by ticket on Windows), plus your own layers: restic for off-site file backups, SQL Server native backups on a schedule, and testing restores before you need them. ### What this is The [backup doctrine](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps) is OS-agnostic, redundancy isn't backup, 3-2-1, dumps for databases, test your restores, this page is how it lands on Windows specifically, including the one platform difference that matters. ### Layer 1: the Nightly Backups add-on [Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview) works on Windows VPS: a whole-server image every night, three-night retention, [enabled from Extra Features](https://vpsdime.com/knowledgebase/client-area/nightly-backups/enable-nightly-backups) for $5/month. The platform difference: **Windows restores aren't self-service**, the Backups panel doesn't cover Windows VPS, so when you need a restore or a file back, you [open a ticket](https://vpsdime.com/open-ticket/) and we handle it. Worth knowing *before* the emergency: build the ticket round-trip into your recovery expectations, and keep your own layer (below) for the fast-path and the long history. ### Layer 2: your own off-site backups - **restic runs beautifully on Windows** ([downloads](https://restic.net/)): the same encrypted, deduplicated, incremental backups to any S3-compatible bucket that the Linux doctrine recommends. Point it at your data folders, schedule it in **Task Scheduler** (daily, "run whether user is logged on or not"), and retention is the same one-liner. An [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) drafts the PowerShell wrapper script and the scheduled-task setup from your paths in one go. - **Windows Server Backup** (the built-in, add it via Server Manager → Features) does scheduled image and volume backups, its catch on a VPS is that it wants a *destination*, and backing up to the same disk protects against nothing. Use it only if you have somewhere real to point it; otherwise restic-to-cloud is the stronger default. - Simple file mirroring in a pinch: `robocopy /MIR` to a remote share over a VPN, honest, but it's a mirror, not versioned history, deletions and ransomware mirror too. ### Databases need their own dumps Same rule as everywhere, copying a live database's files gives you backups that may not restore: - **SQL Server:** native backups are the way, `BACKUP DATABASE MyDb TO DISK='D:\Backups\MyDb.bak'`, scheduled via SQL Server Agent (or Task Scheduler + `sqlcmd` on Express, which lacks Agent). Then your restic job ships the `.bak` files off-site, and, bonus, those dumps inside the nightly image make it cleanly restorable too. - MySQL/PostgreSQL on Windows: `mysqldump`/`pg_dump` on the same schedule, identical logic to [the Linux guidance](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps). ### Test the restore A `.bak` you've never restored and a bucket you've never pulled from are hopes, not backups. Twice a year: restore a database dump to a scratch name, pull a folder back from restic, and confirm the Task Scheduler job has actually been running (History tab, and make failures noisy, a dead-man's-switch ping at the end of the script). ### Related questions - "How do I back up my Windows VPS?" - "How do Nightly Backups restores work on Windows?" - "Does restic work on Windows?" - "How do I schedule SQL Server backups?" - "Is Windows Server Backup enough on its own?" --- ## My app didn't come back after my Windows VPS restarted URL: https://vpsdime.com/knowledgebase/windows-vps/windows-services-after-reboot Last reviewed: 2026-07-02 Summary: The Windows twin of the classic post-unsuspension story, the VPS reboots (after paying an overdue invoice, an update, or your own restart) and the app or database is down because its service isn't set to start automatically, or it never was a service. Startup types, the Recovery tab, Task Scheduler at-startup, and NSSM for turning any program into a service. ### What this is The VPS is up and RDP works, but your application, game server, or database is down, right after a restart. The classic trigger is the [suspension-for-nonpayment story](https://vpsdime.com/knowledgebase/billing/billing-timeline): invoice overdue, VPS suspended, you pay, it reactivates, and it boots **fresh**, without anything that wasn't configured to start on boot. [Update restarts](https://vpsdime.com/knowledgebase/windows-vps/windows-updates) and your own reboots trigger the identical failure. Nothing is lost; the software just wasn't told to rise with the machine. ### If it's a Windows service: check the startup type 1. Run `services.msc`, find the service (SQL Server, your app's service, the web server). 2. Look at **Startup Type**: **Manual** or **Disabled** after a reboot means exactly what you're seeing. Set it to **Automatic**, or **Automatic (Delayed Start)** for things that should wait for the network and heavier services to settle. 3. **Start** it now, and you're back. PowerShell version: `Set-Service MyService -StartupType Automatic; Start-Service MyService`. Two refinements worth doing while you're in there: - **A service set to Automatic that still isn't running** *tried* and failed, check Event Viewer (Windows Logs → Application/System) for its error, a missing drive, a busy port, or a dependency that started too late (that's what Delayed Start is for). - **The Recovery tab** on the service's properties can restart it automatically on failure (First/Second/Subsequent failures → Restart the Service), the Windows equivalent of `Restart=always`, and it turns a random crash into a blip. ### If it's not a service: it dies with your session A program you started by double-clicking, or left running in an RDP window, is tied to your logon session, a reboot (or even a sign-out) ends it. Give it a real home: - **Task Scheduler** (built-in): Create Task → trigger **At startup** → action: run your program → and crucially, "**Run whether user is logged on or not**". Good for scripts and simple daemons. - **[NSSM](https://nssm.cc/)** (the "Non-Sucking Service Manager", the community-standard free tool): wraps *any* executable as a genuine Windows service, with startup type, automatic restart on crash, and log capture, the better answer for anything long-running, like game servers. `nssm install MyApp` opens its little GUI and you're done in a minute. (An [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) will happily tailor the Task Scheduler or NSSM setup to your exact program.) ### Verify like you mean it Same rule as [the Linux twin](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot): the only real test of "starts on boot" is a boot. Pick a calm moment, restart from the Start menu, and confirm everything comes up without you. Two minutes of planned downtime beats rediscovering this page after the next invoice hiccup. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the service or app that didn't come back, and its startup type, - anything from Event Viewer around the boot time. ### Related questions - "I paid my invoice and my Windows VPS is back, but my app is down." - "Why didn't SQL Server start after a reboot?" - "How do I make a program start automatically on Windows Server?" - "What is Automatic (Delayed Start)?" - "How do I run a game server as a Windows service?" --- ## How to set up cron jobs on a Windows VPS (Task Scheduler) URL: https://vpsdime.com/knowledgebase/windows-vps/cron-jobs-on-windows Last reviewed: 2026-07-02 Summary: Task Scheduler is Windows' cron, creating a scheduled job the reliable way (run whether logged on or not, correct start-in folder), the PowerShell and schtasks equivalents, translating crontab thinking to triggers, capturing output so failures aren't silent, and the same discipline the Linux cron guide teaches. ### What this is Windows' cron is **Task Scheduler**: it runs scripts and programs on a schedule (or at events like startup), and it's the right home for the recurring work on your VPS, [backup scripts](https://vpsdime.com/knowledgebase/windows-vps/backing-up-windows-vps), cleanups, report jobs. This is the setup that *keeps working*, most "my scheduled task doesn't run" stories trace to two checkboxes covered below. ### Creating a job (the GUI way) Run `taskschd.msc` → **Create Task** (not "Basic Task", the full dialog is worth it): 1. **General tab**: name it, select **Run whether user is logged on or not** (the checkbox, without it the job only runs while you're RDP'd in, which on a server means never), and **Run with highest privileges** if the script needs admin. 2. **Triggers tab**: **New** → Daily at 03:30, or On a schedule of your choice, or **At startup** ([the other classic need](https://vpsdime.com/knowledgebase/windows-vps/windows-services-after-reboot)). Add a random delay if several jobs share a time. 3. **Actions tab**: **Start a program**. For a PowerShell script, the program is `powershell.exe` (or `pwsh.exe`) with arguments: ``` -NoProfile -ExecutionPolicy Bypass -File "C:\Scripts\backup.ps1" ``` and set **Start in** to the script's folder, relative paths inside scripts fail without it, [the same trap as cron's working directory](https://vpsdime.com/knowledgebase/troubleshooting/cron-not-running). 4. OK, enter the account password when prompted (that's what lets it run unattended). ### The command-line ways One-liner with the classic tool: ``` schtasks /Create /TN "NightlyBackup" /TR "powershell -NoProfile -ExecutionPolicy Bypass -File C:\Scripts\backup.ps1" /SC DAILY /ST 03:30 /RU Administrator /RP ``` Or PowerShell-native, script-friendly: ```powershell $action = New-ScheduledTaskAction -Execute "powershell.exe" -Argument "-NoProfile -ExecutionPolicy Bypass -File C:\Scripts\backup.ps1" $trigger = New-ScheduledTaskTrigger -Daily -At 3:30am Register-ScheduledTask -TaskName "NightlyBackup" -Action $action -Trigger $trigger -User "Administrator" -Password "yourpassword" -RunLevel Highest ``` (An [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) converts any crontab line you're used to into either form on request.) ### Translating crontab thinking | Crontab habit | Task Scheduler equivalent | |---|---| | `30 3 * * *` | Daily trigger, 03:30 | | `*/5 * * * *` | Daily trigger + "Repeat task every 5 minutes for a duration of 1 day" | | `@reboot` | Trigger: At startup ([or make it a real service](https://vpsdime.com/knowledgebase/windows-vps/windows-services-after-reboot)) | | `flock` (no overlaps) | Settings tab → "Do not start a new instance" (the default) | | `MAILTO` | Capture output to a log (below), Task Scheduler doesn't email | ### Make failures noisy (the cron lesson applies here too) Task Scheduler records **Last Run Result** (0x0 = success) and a History tab, but nobody looks until it's been broken for a month, [same story as cron](https://vpsdime.com/knowledgebase/troubleshooting/cron-not-running). So capture output in the script itself: ```powershell Start-Transcript -Path "C:\Scripts\logs\backup.log" -Append # ... the actual work ... Stop-Transcript ``` and for jobs that matter (backups!), end the script with a dead-man's-switch ping so you're alerted when it *stops* running, not just when it errors. ### When the task "doesn't run" The checklist, in order of likelihood: "Run whether user is logged on or not" wasn't set (it ran only during your RDP sessions), the account password changed since the task was registered (re-enter it in task properties), **Start in** is empty and the script needed its folder, or execution policy blocked the script (the `-ExecutionPolicy Bypass` argument sidesteps that per-task). The History tab plus your transcript log names which. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the task's trigger and action (a screenshot of its properties helps), - the Last Run Result code and anything in the History tab. ### Related questions - "How do I run a script on a schedule on Windows Server?" - "What is the Windows equivalent of cron?" - "Why does my scheduled task only run when I'm logged in?" - "How do I run a task every 5 minutes on Windows?" - "How do I log a scheduled task's output?" --- ## How to view and save the Event Log on your Windows VPS URL: https://vpsdime.com/knowledgebase/windows-vps/view-save-event-log Last reviewed: 2026-07-02 Summary: Event Viewer is where Windows explains itself, which logs matter (System, Application, Security), filtering to the events you're hunting, and the part everyone needs eventually: saving a log or a filtered view as an .evtx file, in the GUI, with wevtutil, or PowerShell, including the right way to attach evidence to a support ticket. ### What this is The Event Log is where Windows explains itself, why a service didn't start, what crashed, who tried to log in. Reading it is half of Windows troubleshooting; **saving** it is how you preserve evidence (before a reboot clears the picture) and share it without screenshots-of-scrollbars. Both take a minute. ### Viewing: the three logs that matter Right-click **Start → Event Viewer** (or run `eventvwr`). Under **Windows Logs**: - **System**: Windows itself and services, [service start failures](https://vpsdime.com/knowledgebase/windows-vps/windows-services-after-reboot), driver issues, unexpected shutdowns live here. - **Application**: your software's errors, app crashes, [SQL Server complaints](https://vpsdime.com/knowledgebase/windows-vps/windows-vps-slow), IIS application errors. - **Security**: logons and audit events, including the [brute-force noise and Event 4625](https://vpsdime.com/knowledgebase/windows-vps/protecting-rdp). Reading tips that save time: sort by **Level** (Error/Critical first, Information is mostly noise), and use **Filter Current Log** (right-hand pane) to cut to a **time window** ("when did it break?") or a specific **Event ID**. The Event ID plus Source is the searchable unit, paste those two into a search engine or an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) with the message text, and most events decode instantly. ### Saving a log (the .evtx file) - **Whole log:** right-click the log (say, System) → **Save All Events As...** → `.evtx`. When asked about display information, include it, that keeps the file readable on other machines. - **Just your filtered slice:** apply the filter first, then right-click → **Save Filtered Log File As...**, a small file with only the relevant events, usually what you actually want. - **Command line** (great over a [slow session](https://vpsdime.com/knowledgebase/windows-vps/windows-vps-slow) or in scripts): ``` wevtutil epl System C:\Users\Administrator\Desktop\system-log.evtx ``` - **PowerShell**, when you want text rather than .evtx (for pasting a handful of events): ```powershell Get-WinEvent -LogName System -MaxEvents 50 | Format-List TimeCreated, Id, ProviderName, Message > $env:USERPROFILE\Desktop\system-events.txt ``` Anyone can open an `.evtx`, double-clicking it loads it in Event Viewer on any Windows machine, so the file travels well. ### Attaching logs to a support ticket, the right way Event logs are exactly the **machine output** [a good ticket wants](https://vpsdime.com/knowledgebase/getting-started/raising-a-support-ticket): save the **filtered** slice around the incident time (not the 200 MB full log), attach the `.evtx` or the exported text, and describe in your own words what happened and when, the log corroborates your story rather than replacing it. ### Two housekeeping notes - **Don't clear logs to "clean up"**, they rotate themselves (old events age out as the log hits its size limit), and cleared logs are exactly what you'll wish you had after the next incident. Clearing the Security log in particular is what intruders do, [not what owners do](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery). - Logs survive reboots, but the *context* in your head doesn't, when something odd happens, save the filtered slice **then**, timestamped, while you still know what you're looking at. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which log and Event ID you're looking at, - the saved .evtx or exported text, if you have it. ### Related questions - "How do I open Event Viewer on my Windows VPS?" - "How do I save the event log as a file?" - "How do I export only certain events (filtered log)?" - "Which Windows log shows why a service failed?" - "How do I attach event logs to a support ticket?" --- ## Hosting a website on your Windows VPS (IIS) URL: https://vpsdime.com/knowledgebase/windows-vps/hosting-a-website-iis Last reviewed: 2026-07-02 Summary: From fresh Windows Server to a live site on IIS, install the Web Server role, create the site and bindings, open the web ports, point the domain, and get free auto-renewing SSL with win-acme. Plus the honest note on when a Linux VPS is the better home for a site. ### What this is The Windows path from fresh server to live site, with **IIS**, Windows' built-in web server. One honest note first: if your stack is PHP/WordPress/LAMP-shaped, a [Linux VPS](https://vpsdime.com/knowledgebase/getting-started/hosting-a-website) is the more natural (and cheaper) home. IIS is the right tool when the stack is **.NET / ASP.NET, or Windows-only software**, where it's excellent. ### 1. Install IIS Server Manager → Add Roles and Features → **Web Server (IIS)**, or the one-liner: ```powershell Install-WindowsFeature Web-Server -IncludeManagementTools ``` Browse to `http://localhost` on the VPS, the default IIS page confirms it's alive. For ASP.NET apps, also install the [.NET Hosting Bundle](https://dotnet.microsoft.com/download) matching your app's version ([grabbing installers without a browser](https://vpsdime.com/knowledgebase/windows-vps/cant-download-ie-esc)). ### 2. Create the site In **IIS Manager** (`inetmgr`): right-click **Sites → Add Website**, name it, point the physical path at your site's folder (conventionally `C:\inetpub\yoursite`), and set the **binding**: type http, port 80, and your domain in **Host name** (that's what lets several sites share the server). Each site gets its own **application pool** by default, keep that, it isolates crashes and recycles per site. ### 3. Open the ports and point the domain - Allow web traffic in [Windows Firewall](https://vpsdime.com/knowledgebase/windows-vps/windows-firewall), the IIS role usually adds the World Wide Web rules itself; verify 80 and 443 are allowed rather than assuming. - Point your domain's A record at the VPS IP, [same DNS story as everywhere](https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain), and give it a few minutes before the SSL step, which validates over that DNS. ### 4. Free SSL with win-acme The IIS equivalent of certbot is **[win-acme](https://www.win-acme.com/)**, the standard free Let's Encrypt client for Windows: 1. Download win-acme and run `wacs.exe` as Administrator. 2. Choose the simple option (**N**, create certificate with default settings), pick your IIS site from the list. 3. It validates the domain, installs the certificate, **creates the https binding on the site for you**, and registers a **scheduled task that auto-renews**, the whole lifecycle in one run. Verify the padlock in a browser, and that the renewal task exists in Task Scheduler. Certificate errors later have [their own guide](https://vpsdime.com/knowledgebase/troubleshooting/ssl-certificate-errors), the concepts (expiry, names, chains) are identical on IIS. ### When something misbehaves - **IIS request logs** live in `C:\inetpub\logs\LogFiles`, and application errors land in **Event Viewer** (Windows Logs → Application). Between those two and pasting the exact error into an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management), most IIS mysteries resolve quickly, HTTP error codes mean the same things here ([403s](https://vpsdime.com/knowledgebase/troubleshooting/403-forbidden) included, though the fix on Windows is NTFS permissions and app-pool identity rather than chown). - Site slow or the server grinding? [The Windows triage](https://vpsdime.com/knowledgebase/windows-vps/windows-vps-slow). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS and the site's domain, - what fails (site not loading, a binding, the certificate) with the exact error, - anything relevant from the IIS logs or Event Viewer. ### Related questions - "How do I host a website on my Windows VPS?" - "How do I install IIS?" - "How do I get a free SSL certificate for IIS (win-acme)?" - "Can I host multiple sites on one Windows VPS?" - "Where are the IIS logs?" --- ## Connecting to a VPN from your Windows VPS URL: https://vpsdime.com/knowledgebase/windows-vps/vpn-client-on-windows-vps Last reviewed: 2026-07-04 Summary: How to run a VPN client (OpenVPN, WireGuard, NordVPN, ExpressVPN, and similar) on a Windows VPS without losing your RDP connection. Why RDP dies the moment a full-tunnel VPN connects (the default route moves and return traffic goes into the tunnel), the safety net to set up before you connect, the persistent host route that fixes it for any client, per-client split-tunnel settings, and how to recover through the Console if you're already locked out. ### What this is You want your Windows VPS to route some or all of its outbound traffic through a VPN, a commercial provider, your company's OpenVPN, a WireGuard peer. That's allowed and it works, Windows VPS is a full virtual machine, so TAP and WireGuard adapters install without any platform tweaks. The catch is one of the most reliable footguns in server administration: **connect a VPN client with default settings, and your RDP session dies within seconds**, taking your access with it. This page explains why that happens, how to set up so it can't lock you out, the one fix that works with every client, and how to recover if you're reading this from the outside of a VPS you can no longer reach. ### Why RDP dies the moment the VPN connects Understanding the mechanism makes every fix below obvious. Your RDP session rides on a conversation: packets from your computer arrive at the VPS's **public network adapter**, and the VPS sends replies back the same way, using its **default route**. A consumer VPN client's whole job is to capture your traffic, so on connect it makes itself the default route (OpenVPN pushes `redirect-gateway`, WireGuard uses `AllowedIPs = 0.0.0.0/0`, commercial apps do one or the other under the hood). The moment that happens: 1. Your RDP packets still arrive at the public adapter, inbound routing hasn't changed. 2. But the VPS's **replies** now follow the new default route, into the tunnel, exiting somewhere else on the internet with a different source address. 3. Your computer gets replies from an address it never talked to (or nothing at all) and discards them. The session freezes, then drops. This is **asymmetric routing**, and it's not a bug in the VPN client, it's the client doing exactly what it was designed to do on a laptop, where nobody connects *in*. On a server, "capture all traffic" and "stay reachable" are in direct conflict. Two aggravators worth knowing: - **Kill switches** (NordVPN, Surfshark, Proton, Mullvad, and others have them) add firewall rules that block any traffic outside the tunnel. With one active, even correct routing won't save you, inbound RDP is simply dropped. - **`redirect-gateway def1`** (OpenVPN) doesn't replace your default route, it adds two more-specific routes (`0.0.0.0/1` and `128.0.0.0/1`) that win against it. `route print` will still show your original default route, looking innocent, while the /1 pair above it takes all the traffic. ### Before you connect: the safety net Do these three things before the first connection attempt, they cost two minutes and convert "locked out" into "mildly inconvenienced". 1. **Know the Console exists.** The out-of-band [Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) in your client area reaches your VPS's screen without RDP or working networking. Note that on Windows VPS it signs into the [VPSDime Support Account](https://vpsdime.com/knowledgebase/windows-vps/vpsdime-support-account)'s session, a different desktop is normal, sign out and log in as `Administrator` for your own session. 2. **Schedule an undo.** Before connecting the VPN, arm a reboot: ``` shutdown /r /t 900 /c "VPN experiment safety net" ``` If the VPN eats your access, the VPS reboots itself in 15 minutes, and since a freshly installed VPN client doesn't auto-connect at boot unless you've told it to, the reboot comes back clean. If everything works, cancel it with `shutdown /a`. (Make sure the client's "launch and connect at startup" option is **off** until you've proven the configuration.) 3. **Write down two numbers**: your own public IP as the VPS sees it, and the VPS's gateway. Both in one look: ``` netstat -n | findstr :3389 route print 0.0.0.0 ``` The `netstat` line shows the established RDP connection, the remote address is **your IP**. The route print shows the **gateway** of the public adapter. You'll want both below. ### The fix that works with every client: a host route for yourself Whatever the VPN does to the default route, a **more specific route always wins**. Pin the path back to your own IP through the real adapter, and your RDP replies can never be captured by the tunnel: ``` route -p add 203.0.113.7 mask 255.255.255.255 192.0.2.1 metric 1 ``` Replace `203.0.113.7` with your IP (from the netstat line above) and `192.0.2.1` with the VPS's gateway (from route print). The `-p` makes it survive reboots. Undo later with `route delete 203.0.113.7`. This one line is the universal answer: it works under OpenVPN, WireGuard, and every commercial app, because it operates at the routing layer they're all fighting over. Two caveats: - **A kill switch can still block you** at the firewall layer regardless of routes. Turn the kill switch off, on a server you don't want it anyway (a VPN drop on a server should degrade its outbound privacy, not sever its administration). - **If your home IP is dynamic**, the route goes stale when your IP changes. Add your current one again (or a broader mask covering your ISP's range if you know it), or rely on split tunneling below instead. ### Per-client configuration The host route makes you safe. These settings make the client behave properly so you're not depending on it. #### OpenVPN The server config usually pushes the full tunnel (`redirect-gateway def1`). Override it on the client, edit your `.ovpn` file (in `C:\Program Files\OpenVPN\config\`) and add: ``` pull-filter ignore "redirect-gateway" ``` The tunnel comes up, routes to the VPN's own subnets work, but your default route stays put. If you *want* specific networks through the tunnel, add explicit `route` lines for them. The heavier alternative, `route-nopull`, ignores every pushed route, then nothing goes through the tunnel except what you route by hand. #### WireGuard The full tunnel is spelled `AllowedIPs = 0.0.0.0/0` in the peer config, and the Windows app shows a **"Block untunneled traffic (kill-switch)"** checkbox whenever it sees it, make sure that's **unticked** on a server. For split tunnel, replace `0.0.0.0/0` with just the networks that belong in the tunnel (for example `10.8.0.0/24, 192.168.100.0/24`). With a scoped AllowedIPs, WireGuard never touches your default route at all. #### Commercial apps (NordVPN, ExpressVPN, Surfshark, Proton, Mullvad, PIA) Every major client has two settings that matter here, the names vary: - **Split tunneling** (Surfshark calls it **Bypasser**): configure it so the tunnel carries only the apps you choose (browser, downloader), rather than "everything except". Inverse-mode ("only selected apps use the VPN") is the server-friendly mode, RDP and system traffic never enter the tunnel. - **Kill switch**: off, for the reason above. And keep "auto-connect on startup" off until the configuration has survived a reboot with RDP intact. #### Tailscale and ZeroTier Safe by default: they route only their own overlay subnets, not your default route, so RDP keeps working. The exception is Tailscale's **exit node** feature, telling your VPS to *use* another machine as exit node is exactly the full-tunnel trap again. Bonus: once the VPS is on your tailnet, you can RDP to its overlay IP, which keeps working even if you later break public routing. ### Locked out already? Recovery 1. Open the **[Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps)** from your client area (expect the [Support Account](https://vpsdime.com/knowledgebase/windows-vps/vpsdime-support-account)'s desktop; sign out and log in as `Administrator`). 2. Disconnect the VPN: from the client's own UI, or bluntly, end its process in Task Manager. For Windows' built-in VPN: `rasdial "ConnectionName" /disconnect`. 3. If RDP is still dead, inspect `route print`: look for `0.0.0.0/1` and `128.0.0.0/1` entries or a default route pointing at a TAP/WireGuard adapter, and delete the offenders (`route delete 0.0.0.0 mask 128.0.0.0` and `route delete 128.0.0.0 mask 128.0.0.0`). A reboot achieves the same if the client doesn't auto-connect. 4. Before reconnecting the VPN, add the [host route](#the-fix-that-works-with-every-client-a-host-route-for-yourself) and fix the client's settings as above. ### A note on the built-in Windows VPN If you use Windows' native VPN (IKEv2/SSTP/L2TP) instead of a third-party app, the same trap lives in one checkbox: the connection's **"Use default gateway on remote network"**. Disable it in one line: ```powershell Set-VpnConnection -Name "ConnectionName" -SplitTunneling $true ``` ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which VPN client and whether a kill switch or split tunneling is configured, - whether the Console works, and what `route print` shows if you've looked. ### Related questions - "I connected a VPN on my VPS and lost RDP, how do I get back in?" - "How do I run a VPN client on my Windows VPS without losing access?" - "Why does RDP drop the moment my VPN connects?" - "How do I set up split tunneling on a VPS?" - "Should the VPN kill switch be on for a server?" - "How do I stop OpenVPN from taking over the default route?" - "What does AllowedIPs 0.0.0.0/0 do in WireGuard?" --- ## My Windows VPS is slow. How do I find out why? URL: https://vpsdime.com/knowledgebase/windows-vps/windows-vps-slow Last reviewed: 2026-07-04 Summary: The Windows triage, first separate RDP-feel lag (a network path question) from actual server slowness, then Task Manager and Resource Monitor to find the consumer, the usual suspects (TiWorker on patch days, Defender scans, a miner after a compromise, RAM pressure on small plans), Process Explorer for "what even is this process", and when to resize. ### What this is "Slow" on a Windows VPS is one of three different problems, the path to it, the machine itself, or your expectations of the plan size, and each has a quick test. Same method as [the Linux version](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps), Windows tooling. ### Step 1: is it the server, or the connection to it? An RDP session that feels laggy, choppy screen, delayed typing, while the server itself is idle is a **network path** symptom, not a server one. The discriminator: open Task Manager *on the VPS*, if CPU/memory/disk are quiet while the session feels bad, test the path, [ping.pe](https://ping.pe/) from outside, and the [network problems guide](https://vpsdime.com/knowledgebase/troubleshooting/network-problems) with mtr. Long international routes make RDP feel heavy at peak hours with nothing wrong on either end. If things are slow *on* the server (apps take forever, disk grinds), continue. ### Step 2: Task Manager, then Resource Monitor **Task Manager** (Ctrl+Shift+Esc) → Details tab, sort by CPU, then by Memory, the consumer is usually staring at you. For the deeper view, **Resource Monitor** (`resmon`, or the link at the bottom of Task Manager's Performance tab) breaks out disk and network per process, which catches the "CPU is fine but the disk is pinned" cases. ### The usual suspects - **TiWorker.exe / Windows Modules Installer** grinding CPU and disk: **patch-day servicing**, legitimate, let it finish. The full story (and the pending-reboot state) is in [Windows Updates](https://vpsdime.com/knowledgebase/windows-vps/windows-updates). - **MsMpEng.exe (Microsoft Defender)** busy: a scheduled scan. Normal in bursts; if it's constantly hot, exclude your heavy data folders (databases, backup targets) from real-time scanning rather than disabling Defender, that's the sanctioned tuning. - **A process you don't recognize at 100%, around the clock**: assume a **cryptominer** until proven otherwise, which means a compromise. Don't just kill it; the [recovery doctrine](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery) applies on Windows exactly as on Linux. - **Memory pressure**: Windows Server itself is comfortable at 4 GB, but Windows plus a real workload wants **8 GB and up**, and an over-committed box pushes into the **pagefile**, which converts RAM shortage into constant disk grind (visible as high disk activity on `pagefile.sys` in Resource Monitor, and as **Hard Faults/sec** on its Memory tab). The fix is less workload or [more plan](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade); shrinking the pagefile just converts slowness into crashes. Pushed far enough past RAM, this doesn't stay "slow", it becomes a full lockup where nothing responds: [My Windows VPS is frozen or unresponsive](https://vpsdime.com/knowledgebase/windows-vps/windows-vps-unresponsive). - **Disk full** produces spectacular, misleading slowness on Windows too, ten seconds to rule out: [the Windows disk guide](https://vpsdime.com/knowledgebase/windows-vps/disk-full-windows). ### "What even is this process?" For anything ambiguous, Microsoft's free **[Process Explorer](https://learn.microsoft.com/sysinternals/downloads/process-explorer)** (Sysinternals) is Task Manager with answers: full paths, signing info, and a built-in **VirusTotal check** per process (Options → VirusTotal.com → Check). Pasting a suspicious process name and path into an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) is also a fast sanity check, it knows the legitimate Windows processes cold. ### History, and when to escalate Your VPS's [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) hold the long view, does the slow period line up with a CPU/disk plateau, or are the graphs flat (which points back at the network path)? If you've localized something you can't explain, [the ticket recipe](https://vpsdime.com/knowledgebase/getting-started/raising-a-support-ticket) applies: what you measured, when, and what Task Manager showed, in your own words. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what sits at the top of Task Manager while it's slow, - when it started, and whether it lines up with anything on the Graphs. ### Related questions - "Why is my Windows VPS so slow?" - "What is TiWorker.exe and why is it using all my CPU?" - "Why is MsMpEng using CPU on my server?" - "How much RAM does a Windows VPS need?" - "How do I check what's using disk on Windows Server?" - "Is my RDP lag the server or my connection?" --- ## My Windows VPS is frozen or unresponsive URL: https://vpsdime.com/knowledgebase/windows-vps/windows-vps-unresponsive Last reviewed: 2026-07-04 Summary: When a Windows VPS is pushed far past its RAM, it falls into pagefile thrashing, the system spends its time moving memory to disk and back instead of running your programs, and eventually nothing responds, not RDP, not the troubleshooter's checks, not even the Console. The immediate fix is the Reset button in your client area; this page explains the mechanism, why Windows fails this way, what Windows Server's own memory footprint means for small plans, and how to size and monitor so it doesn't recur. ### What this is Your Windows VPS stopped responding: RDP won't connect or connects to a black screen, pages hosted on it time out, and even the [Windows Troubleshooter](https://vpsdime.com/knowledgebase/windows-vps/windows-troubleshooter)'s checks hang or fail. The most common cause, by far, is **memory exhaustion**: the workload grew past the plan's RAM by a wide margin, Windows fell back on the pagefile, and the machine is now spending nearly all of its time shuffling memory to disk and back instead of doing work. This state is called **thrashing**, and it's self-sustaining, the VPS won't come out of it on its own in any timeframe you'll want to wait for. ### The immediate fix: Reset from the client area A thrashing system can't be rescued from inside, every tool you'd use needs the OS to respond, and the OS is exactly what's starved: - **RDP** can't get a session scheduled. - The **Troubleshooter's** checks talk to the OS, so they hang along with it. - Even the **Console** isn't a way in: it faithfully shows the VPS's screen, but a starved OS can't respond to the keyboard either. The one thing that always works is out-of-band power control, it happens at the host level and doesn't need the OS's cooperation: 1. Open your VPS's [manage page](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) (https://vpsdime.com/myservices). 2. Click **Reset**. This is a hard reboot, the virtual equivalent of pulling the power cord, and it's the right tool here precisely because nothing softer can get through. 3. The VPS boots clean in a minute or two. Then read on, because whatever filled the memory will do it again. ### The mechanism: why "a bit too much" becomes "completely dead" Windows, like every modern OS, uses **demand paging**: when programs need more memory than physically exists, it moves the least-recently-used pages out to `pagefile.sys` and brings them back when touched. In moderation this is invisible. The problem is the cost ratio: RAM access is measured in **nanoseconds**, a pagefile access in **tens to hundreds of microseconds**, roughly a thousandfold difference, even on NVMe. While the overflow is small, only rarely-touched memory lives in the pagefile and you just see [general slowness](https://vpsdime.com/knowledgebase/windows-vps/windows-vps-slow). But once the *actively used* memory of your running programs exceeds physical RAM, the system needs pages back **as fast as it evicts them**. Every process touch becomes a disk wait, the disk queue saturates, and CPU sits idle while everything waits on paging. That's thrashing: throughput collapses not linearly but off a cliff, a VPS at 90% memory feels fine, one at 120% is effectively dead. Two Windows-specific notes complete the picture: - **Windows has no equivalent of Linux's OOM killer.** Linux, out of memory, kills the biggest process to save the machine. Windows instead keeps its promise to every program: it expands paging until the **commit limit** (RAM plus pagefile) is reached, and only then do allocations start failing, by which point the system has usually been unresponsive for a while. The design degrades instead of sacrificing, which on a server means lockup instead of one crashed process. - **Growing the pagefile doesn't help.** It raises the commit limit, which just widens the zone where the system is alive-but-thrashing. Disabling the pagefile is worse: it converts slowness into outright allocation failures and crashes. The pagefile's size was never the problem; the ratio of workload to RAM is. ### Windows Server's own appetite, and what a plan's RAM really buys Windows Server with the desktop experience uses roughly **2 GB doing nothing**: the kernel, system services, Defender, and the servicing stack claim their share before your first program starts, and patch-day servicing or a Defender scan will temporarily want more. This is a property of the OS, not something to tune away. So on an entry plan, subtract the OS's share first and treat the remainder as your actual budget. Then price the workload honestly: - **Browsers** are the heaviest common load: each tab is an isolated process tree, typically **150 to 400 MB** for real-world sites, more for web apps. Twenty tabs can consume 4 to 6 GB by themselves. Automation ("botting") setups multiply this, every headless or driven browser instance is a full browser. - **Trading platforms**: a single MT4/MT5 terminal is modest, but the standard pattern of **many terminals with indicators and EAs** adds up in the hundreds of MB each, and they're all active working set, exactly the kind of memory that can't be paged out without pain. - Ordinary server duties (IIS site, a modest database, a service or two) fit entry plans comfortably. It's the desktop-style concurrent workloads that don't. The arithmetic conclusion, stated plainly: a **6 or 8 GB plan holds light-to-moderate workloads**, and heavy multi-tab browsing, browser automation fleets, or many-terminal trading setups will exceed it **structurally**, no setting changes that. The honest options are reducing concurrency (fewer tabs, fewer instances, staggered schedules) or [more RAM](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade). We'd rather you size it right than meet this page again. ### Seeing it coming The lockup announces itself, if you're watching: - **Task Manager → Performance → Memory**: sustained use above ~90% with your normal workload is the warning line. - **Resource Monitor → Memory tab → Hard Faults/sec**: this is paging made visible. Near zero is healthy; a persistent elevated rate under normal load means the working set no longer fits. - Your panel's [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) hold the history: if memory ratchets up over days (a leak, or tabs accumulating) you'll see the slope before the cliff. The full monitoring tour is in [How to monitor resource usage](https://vpsdime.com/knowledgebase/windows-vps/monitor-resources-windows). ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - whether Reset brought it back, and what was running when it froze, - what Task Manager's memory figure and Resource Monitor's hard-fault rate show under your normal workload. ### Related questions - "My Windows VPS is frozen and RDP won't connect, what do I do?" - "Why doesn't the Console work when my VPS is unresponsive?" - "How do I force reboot my VPS?" - "Why did my VPS lock up when I opened a lot of browser tabs?" - "How much RAM does Windows Server itself use?" - "Is 8 GB enough for browsing or trading on a Windows VPS?" - "Should I make the pagefile bigger?" --- ## Can't RDP into your Windows VPS after joining a domain URL: https://vpsdime.com/knowledgebase/windows-vps/rdp-after-domain-join Last reviewed: 2026-07-04 Summary: After joining a Windows VPS to an Active Directory domain, RDP logins can start failing, most famously with "no Remote Desktop License Servers available to provide a license". The causes are the RD Session Host role's expired 120-day licensing grace, domain Group Policy revoking Remote Desktop rights or firewall rules, and username resolution changing after the join. How to get back in (Console, mstsc /admin, local accounts with the .\ prefix), how to fix each cause, and the precautions that make a domain join safe on a server you can only reach remotely. ### What this is You joined your Windows VPS to an Active Directory domain (or promoted it, or restructured its roles as part of a domain setup), and some time later, immediately or months after, RDP stopped letting you in. The most recognizable version is this exact message: > *The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license.* Others look like authentication failures: credentials that worked yesterday are "incorrect", or the connection succeeds and immediately closes. These are different failures with different fixes, but they share a root: **a domain join hands significant control of your server to domain configuration**, licensing expectations, Group Policy, firewall profile, and how usernames resolve all change. This page takes them in order of likelihood, after getting you back in first. ### First: get back in Three doors, in the order to try them: 1. **`mstsc /admin`** from your computer (run `mstsc /admin /v:YOUR.VPS.IP`). The `/admin` switch requests the **administrative session**, which is exempt from Remote Desktop licensing. If your error is the license-server message, this usually connects immediately, because the licensing check applies to normal user sessions, not administration. 2. **A local account with the explicit prefix.** At the RDP credential prompt, the username `.\Administrator` (or `VPSHOSTNAME\Administrator`) forces a **local** logon instead of a domain one. After a join, a bare `Administrator` may silently resolve against the domain, where that password is different or the account is restricted, entering the same credentials with `.\` in front is the fix for a surprising share of "wrong password after domain join" cases. Local accounts keep working after a join **unless a domain policy disabled them**, more on that below. 3. **The [Console](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps)** in your client area. This isn't just "RDP by another route", it attaches to the machine's **local console session**, the virtual equivalent of a physical monitor and keyboard, and RD licensing only gates sessions that come through the Remote Desktop stack. A server with an expired licensing grace still accepts console logons, exactly as a physical terminal server would at its own keyboard. On Windows VPS the Console opens on the [Support Account](https://vpsdime.com/knowledgebase/windows-vps/vpsdime-support-account)'s already-signed-in session; signing out and logging in as your own account there is a **local** logon, governed by the "Allow log on locally" right rather than the Remote Desktop one. (A harsh domain policy *can* restrict local logon too, see the GPO cause below, but the licensing error never applies here.) ### Cause 1: the RD licensing grace period expired The license-server error has a precise mechanism behind it: - Out of the box, Windows Server permits **two concurrent administrative RDP sessions** with no licensing at all ([the two-session model](https://vpsdime.com/knowledgebase/windows-vps/rdp-connection-limit)). This never expires. - Installing the **Remote Desktop Session Host (RDSH)** role changes the deal: the server now expects per-user or per-device **RDS CALs** served by a licensing server, and grants a **120-day grace period** to set that up. Domain deployments are exactly where this role tends to get installed, sometimes deliberately (multi-user plans), often incidentally, ticked in a role wizard during the domain setup because it sounded relevant. - For 120 days everything works, which is what makes this failure so disorienting: the grace expires **months after** whoever installed the role touched the machine, and RDP "suddenly" refuses normal sessions. Diagnose in one line (in an `/admin` session or the Console): ```powershell Get-WindowsFeature RDS-RD-Server ``` If it shows **Installed** and you never intended to run a multi-user terminal server, the fix is simply removing it, the server returns to the unlicensed two-admin-session model: ```powershell Uninstall-WindowsFeature RDS-RD-Server -Restart ``` If you **do** need more than two concurrent user sessions, the role is right and the licensing is what's missing: you need an **RD Licensing server** with purchased **RDS CALs**, and the Session Host pointed at it (deployment properties or the `Licensing` GPO under Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services). CALs come from Microsoft or a reseller, they're not something a VPS plan includes. Timer-reset tricks for the grace period circulate on forums; note that they don't license anything, they postpone the same wall. ### Cause 2: domain Group Policy took the right away Joining a domain subscribes your server to its Group Policy, and hardened domains commonly ship policies that assume "server in the office LAN", not "VPS administered over the internet": - **"Allow log on through Remote Desktop Services"** (the user right) may be restricted to specific groups that your account isn't in, and a matching **Deny** right wins over everything. - **Remote Desktop Users** group membership may be enforced by policy, removing the accounts you added locally. - **Local accounts can be disabled or denied network/RDP logon** by policy, this is standard hardening (it's how domains stop lateral movement via shared local admin passwords), and it's the case where "local accounts still work" stops being true. If `.\Administrator` is rejected outright rather than failing on password, suspect this. The strictest variants also deny **"log on locally"**, which is the one policy that can close the Console door as well. - A GPO can also **disable RDP entirely** or enforce NLA/security settings your client can't meet. See what actually applies with `gpresult /r` (or `gpresult /h report.html` for the readable version) from the Console or an `/admin` session, look at the winning GPOs under Computer Settings. The clean fixes are on the domain side: put the server in an **OU with policies fit for a remotely administered machine**, or adjust the offending GPO. Editing local policy is futile while a domain GPO overrides it, it will reapply on the next refresh. ### Cause 3: the domain firewall profile Windows Firewall keeps three profiles, and **which one is active changes at domain join**: the network is now classified as a *Domain* network, so the domain profile's rules apply. If domain policy configures that profile with no RDP allowance, or scopes the built-in Remote Desktop rule to the corporate subnet, external RDP dies even though "the firewall was fine" before, a different profile was fine. Check and fix from the Console: ```powershell Get-NetFirewallProfile | Select Name, Enabled Get-NetFirewallRule -DisplayGroup "Remote Desktop" | Select DisplayName, Enabled, Profile Enable-NetFirewallRule -DisplayGroup "Remote Desktop" ``` If a GPO manages the firewall, the same OU/GPO reasoning as above applies, local changes get overwritten on refresh. The general firewall guidance is in [Using Windows Defender Firewall](https://vpsdime.com/knowledgebase/windows-vps/windows-firewall). ### Cause 4: DNS and reachability of the domain controller Domain joins usually repoint the server's DNS at the domain controller. If that DC is unreachable from your VPS (a lab DC that's off, a corporate DC behind a VPN that isn't up), domain logons fail or hang at "Please wait", and even local logons can slow down. Cached credentials mask this for a while, then it "suddenly" breaks. If your domain lives elsewhere, make sure the VPS can actually reach a DC at logon time, and keep a local account as the fallback that doesn't depend on it. ### Before the next risky change: precautions A domain join is one of a family of changes (VPN clients, firewall tightening, RDP hardening) that can cut off the very connection you manage the server through. The pattern that keeps you safe: - **Install an independent remote-access tool first.** TeamViewer, AnyDesk, or RustDesk connect **outbound** from the VPS, so they don't care what happens to RDP licensing, logon rights, or inbound firewall rules. Five minutes of setup before the change buys you a full desktop afterwards, whatever went wrong. (For assist-style use these are also the [sane alternative to RDS CALs](https://vpsdime.com/knowledgebase/windows-vps/rdp-connection-limit).) - **Know the Console exists** and how its [login works](https://vpsdime.com/knowledgebase/windows-vps/vpsdime-support-account), it's the recovery path that needs nothing installed. - **Test in a second session.** Keep your working RDP session open, make the change, and verify a *fresh* RDP login works before signing out, the same discipline as [changing the SSH port](https://vpsdime.com/knowledgebase/technical-questions/change-ssh-port) on Linux. - **Keep a local admin account with a known password**, and note the `.\` login syntax somewhere you'll find it while stressed. - **Don't install the RD Session Host role casually.** If you're not deliberately building a multi-user terminal server with CALs budgeted, you don't want it. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - the exact error text, and whether `mstsc /admin` and `.\Administrator` behave differently, - whether the RD Session Host role is installed (`Get-WindowsFeature RDS-RD-Server`), and roughly when the domain join happened. ### Related questions - "Why can't I RDP into my server after joining it to a domain?" - "What does 'no Remote Desktop License Servers available' mean?" - "My RDP worked for months and suddenly stopped with a licensing error." - "How do I log in with a local account instead of a domain account?" - "Does mstsc /admin bypass the license error?" - "Do I need RDS CALs on my VPS?" - "What should I install before joining my VPS to a domain?" --- ## How can I monitor resource usage on my Windows VPS? URL: https://vpsdime.com/knowledgebase/windows-vps/monitor-resources-windows Last reviewed: 2026-07-02 Summary: The three built-in layers, Task Manager for now, Resource Monitor for the per-process detail (including disk and network per process), and Performance Monitor with Data Collector Sets for history you can scroll back through, plus the panel Graphs for the host-side view and when each tool is the right one. ### What this is Watching what your Windows VPS is doing with its CPU, memory, disk, and network, the built-in tools cover three depths (now / detailed now / history), and knowing which to open is most of the skill. (If you're here because the VPS is currently slow, [that guide](https://vpsdime.com/knowledgebase/windows-vps/windows-vps-slow) applies this toolkit to the hunt.) ### Layer 0: the panel Graphs (the outside view) Your VPS's [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) tab plots CPU, memory, disk, and traffic over time, measured **from the host**, so it works even when the VPS itself is wedged, and it's the fastest answer to "when did this start" and "[is my plan the right size](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade)". The tools below add the inside view: *which process*. ### Layer 1: Task Manager, the glance **Ctrl+Shift+Esc** → **Details** tab, sort by CPU or Memory, and the hungriest process is at the top; the **Performance** tab shows the machine-wide curves for the last 60 seconds. This answers most questions in ten seconds, and its limits are exactly two: no per-process **disk/network** breakdowns worth trusting, and no memory of anything before you opened it. ### Layer 2: Resource Monitor, the detail The link at the bottom of Task Manager's Performance tab, or run **`resmon`**. Four tabs, each per-process: - **CPU**: like Task Manager, plus per-service breakdown. - **Memory**: the honest per-process working sets, and the machine-wide *In Use / Standby / Free* map (standby is cache, [not a problem](https://vpsdime.com/knowledgebase/windows-vps/windows-vps-slow)). - **Disk**: **which process is hitting which file**, and disk queue length, the tab that finds runaway logging and answers "what is grinding the disk". - **Network**: **per-process traffic with remote addresses**, Windows' answer to [nethogs](https://vpsdime.com/knowledgebase/technical-questions/per-app-bandwidth), and the place a [miner or exfiltration](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery) shows its destinations. Filter by ticking a process at the top and every tab scopes to it, the fastest way to profile one suspect. ### Layer 3: Performance Monitor, the history Task Manager and resmon evaporate when closed; **`perfmon`** records. The two uses that matter on a VPS: - **Live counters**: Monitoring Tools → Performance Monitor, add counters (green +), Processor, Memory → Available MBytes, PhysicalDisk → Avg. Disk Queue Length, LogicalDisk → % Free Space, and watch them plot. - **Data Collector Sets, the 3 AM answer**: right-click *User Defined* → New → Data Collector Set, use the System Performance template (or your counter list), set a schedule, and it logs to disk continuously. The next time something happens overnight, the report (under *Reports*) has the curves for that exact window, the built-in equivalent of what [Netdata does on Linux](https://vpsdime.com/knowledgebase/troubleshooting/slow-vps). Keep collector logs on a leash (they grow; point them at a folder you [watch](https://vpsdime.com/knowledgebase/windows-vps/disk-full-windows), and set a stop condition), and pair the resource history with the [Event Log](https://vpsdime.com/knowledgebase/windows-vps/view-save-event-log) for the *why* behind any spike, timestamps across the two are how cases close. ### Which tool, when | Question | Tool | |---|---| | "What's eating CPU right now?" | Task Manager, Details | | "What's hammering the disk / talking to the network?" | Resource Monitor | | "What happened at 3 AM?" | Performance Monitor collector set (+ Event Log) | | "When did this start / is the plan too small?" | Panel [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) | ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which resource looks wrong and when (a screenshot of Task Manager or the Graphs helps), - what was running at the time. ### Related questions - "How do I see what's using CPU, disk, or network on Windows Server?" - "What's the Windows equivalent of htop or nethogs?" - "How do I record resource usage history on my Windows VPS?" - "How do I set up a Data Collector Set?" --- ## C: is full on my Windows VPS URL: https://vpsdime.com/knowledgebase/windows-vps/disk-full-windows Last reviewed: 2026-07-02 Summary: A full C: drive breaks Windows in confusing ways, find what's eating it with WinDirStat or TreeSize, clean the legitimate bulk (Disk Cleanup, DISM component cleanup, update leftovers, IIS logs, recycle bin), understand the pagefile's share, and, after a plan upgrade, extend the volume if the new space didn't apply automatically. ### What this is A full system drive on Windows fails the same way [it does on Linux](https://vpsdime.com/knowledgebase/troubleshooting/disk-full), sideways: databases refuse writes, updates fail half-installed, apps crash on save, RDP sessions misbehave. Confirm in seconds (This PC, or `Get-PSDrive C`), then find the bulk, clean it properly, and know the plan-upgrade wrinkle at the bottom. ### Find what's eating the space Don't guess, map it: **[WinDirStat](https://windirstat.net/)** (open source) or **[TreeSize Free](https://www.jam-software.com/treesize_free)** visualize the whole drive by folder size in a minute. Run either as Administrator so system folders count, and the culprit is usually obvious at a glance. ### Clean the legitimate bulk In order of typical yield: - **Disk Cleanup, with system files**: run `cleanmgr`, click **Clean up system files**, and let it take Windows Update leftovers, temp files, and old error dumps, this is the sanctioned cleaner and often frees gigabytes on its own. - **Component store (WinSxS)**, the folder that scares everyone in WinDirStat: don't delete from it by hand, ever, service it properly: ``` Dism.exe /Online /Cleanup-Image /StartComponentCleanup ``` - **Application logs**: IIS logs (`C:\inetpub\logs`) grow forever by default, archive or delete old ones and add a scheduled cleanup; the same goes for your app's own log folders. - **Recycle Bin** (it counts!), old user profiles of accounts you removed, and forgotten downloads/installers. - **Old backups parked on C:**: `.bak` files belong [shipped off-site](https://vpsdime.com/knowledgebase/windows-vps/backing-up-windows-vps), not accumulating on the drive they're meant to protect. - **The pagefile** (`pagefile.sys`) legitimately occupies RAM-sized gigabytes. Leave it system-managed, shrinking it to reclaim disk trades [slowness for crashes](https://vpsdime.com/knowledgebase/windows-vps/windows-vps-slow); if its size is the problem, the disk is undersized for the plan's RAM, see below. What **not** to do: delete anything in `C:\Windows` by hand because a forum said so, and don't remove things WinDirStat shows that you can't identify, ask an [AI chatbot](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) what the folder is first, the ten seconds beats an unbootable server. ### Genuinely need more room? And the upgrade wrinkle More disk comes with a [plan upgrade or Additional Storage](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade). After the upgrade, the new space is normally **extended into C: automatically**. If Windows still shows the old size, finish it yourself in two minutes: 1. Right-click **Start** → **Disk Management** (`diskmgmt.msc`). 2. **Action → Rescan Disks.** You should see the new space as **Unallocated** after the C: partition. 3. Right-click **C:** → **Extend Volume** → Next through the wizard (defaults take all the new space) → Finish. Applies live, no reboot. PowerShell one-liner, same result: ```powershell Resize-Partition -DriveLetter C -Size (Get-PartitionSupportedSize -DriveLetter C).SizeMax ``` If Disk Management shows no unallocated space at all after an upgrade, [open a ticket](https://vpsdime.com/open-ticket/) with the VPS and what Disk Management shows. ### Related questions - "How do I find what's using disk space on Windows Server?" - "Is it safe to clean the WinSxS folder?" - "Why is pagefile.sys so large?" - "I upgraded my plan but C: still shows the old size." - "How do I extend the C: volume on my VPS?" --- ## I can't download anything in the browser on my Windows VPS URL: https://vpsdime.com/knowledgebase/windows-vps/cant-download-ie-esc Last reviewed: 2026-07-02 Summary: Fresh Windows Server blocks browser downloads by design, IE Enhanced Security Configuration. How to turn it off for administrators in Server Manager, and the better habit: install real software with winget, Chocolatey, or a PowerShell download instead of fighting the built-in browser. ### What this is You RDP into a fresh Windows Server, open the browser to grab an installer, and every download and half the web is blocked with security prompts. That's **IE Enhanced Security Configuration (IE ESC)**, a lockdown Windows Server ships **on by default**, on the theory that servers shouldn't browse the web. The theory is sound; the first-day experience is maddening. Two ways forward. ### Option 1: turn IE ESC off (for administrators) 1. Open **Server Manager** (it usually greets you at logon). 2. Click **Local Server** in the left pane. 3. Find **IE Enhanced Security Configuration** on the right, click its **On** link. 4. Set **Administrators: Off** (leave it On for Users), OK, and reopen the browser. Downloads work now. The security posture is fine, the real protection on a server is [not browsing casually on it at all](https://vpsdime.com/knowledgebase/windows-vps/securing-your-windows-vps), download what you administer, and do your surfing on your own computer. ### Option 2 (the better habit): install software without the browser Server admins mostly skip the browser entirely, from PowerShell: - **winget**, Microsoft's package manager (included on recent Server versions; try `winget --version`): `winget install Google.Chrome`, done. Thousands of packages, upgrades with `winget upgrade --all`. - **[Chocolatey](https://chocolatey.org/)**, the veteran community package manager, works on every Server version: install it with the one-liner from their site, then `choco install googlechrome firefox 7zip` and friends. Great for scripting a server's whole toolkit. - **Direct download in PowerShell**, for a single file with a known URL: ```powershell Invoke-WebRequest -Uri "https://example.com/tool.msi" -OutFile "$env:USERPROFILE\Downloads\tool.msi" ``` Package managers also fix the *next* problem, updates: `choco upgrade all` or `winget upgrade --all` keeps the third-party software patched, which [matters on a server](https://vpsdime.com/knowledgebase/windows-vps/securing-your-windows-vps) as much as Windows Update does. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what you're trying to download or install, - whether you've turned IE ESC off, and what still blocks. ### Related questions - "Why can't I download files on Windows Server?" - "How do I turn off IE Enhanced Security Configuration?" - "How do I disable Internet Explorer Enhanced Security (Extended Protection) on Windows Server?" - "How do I install Chrome on my Windows VPS?" - "Does winget work on Windows Server?" - "How do I install software from PowerShell?" --- ## Can I run Ubuntu, WSL2, or a Linux VM on my Windows VPS? URL: https://vpsdime.com/knowledgebase/windows-vps/no-linux-vms-on-windows-vps Last reviewed: 2026-07-02 Summary: No, your Windows VPS is itself a virtual machine, and nested virtualization isn't supported, so Hyper-V, VirtualBox, VMware, WSL2, and Docker Desktop won't run inside it. What actually works for each underlying goal: a Linux VPS alongside (usually cheaper than the workaround), WSL1 for light command-line use, and where containers should really live. ### What this is The short answer: **no**, and it's a physics-of-virtualization no, not a policy one. Your Windows VPS **is itself a virtual machine** (running on Hyper-V), and **nested virtualization, a VM inside a VM, isn't supported** on our platform. Everything on this list needs exactly that, so none of it will run on a Windows VPS: - the **Hyper-V role** itself, - **VirtualBox** and **VMware Workstation**, - **WSL2** (Windows Subsystem for Linux version 2, which is a lightweight VM under the hood, `wsl --install` will end in a virtualization error), - **Docker Desktop** (it requires WSL2 or Hyper-V). The installers mostly fail with messages about virtualization support or hypervisor errors, that's this page. ### What you're actually after, and what works **"I want a Linux machine."** Then have one, a [Linux VPS](https://vpsdime.com/knowledgebase/presales/linux-vps-vs-premium-vps) is a *real* separate machine, starting at $5/month, which is almost certainly less than the RAM you'd have sacrificed carving a VM out of your Windows plan. Run both side by side, each OS on hardware-level footing, managed from the same account, and connected to each other over the network like any two servers. **"I just want Linux command-line tools on the Windows box."** Two honest options: **WSL1**, the older translation-layer version of WSL, is not a VM and doesn't need nested virtualization, `wsl --install` with the distro, then `wsl --set-version 1` (or set version 1 as default first), gives you bash, ssh, grep, and friends for light use, with WSL1's known limits (no systemd, slower file I/O across worlds, some software incompatible). Or skip WSL entirely: **Git for Windows** bundles bash and the common Unix tools, and [PowerShell](https://vpsdime.com/knowledgebase/windows-vps/ssh-on-windows) covers more ground than people expect. **"I want to run containers."** Docker's Linux containers belong on a Linux host: a [Linux VPS runs Docker natively](https://vpsdime.com/knowledgebase/technical-questions/docker-on-vps), no Desktop app, no VM layer, full performance. (Windows *containers*, the niche Windows-image kind, also rely on virtualization features unavailable here.) **"I want to test another OS."** A second small VPS is the honest lab bench, deploy, experiment, [reinstall](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os) or cancel when done. ### Why this limitation exists Hardware virtualization extensions don't pass through to guests by default, and enabling nested virtualization trades away stability and performance isolation on shared hosts, so we don't. The same answer applies on [Linux VPS and Premium VPS](https://vpsdime.com/knowledgebase/presales/pre-sales-faq): no nested hypervisors anywhere on the platform. The practical pattern is always the same, **one VPS per operating system**, which is also how they perform best. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what you tried to run (WSL2, a VM, Docker Desktop), - what you're ultimately after, so we can point you at the setup that works. ### Related questions - "Why does WSL2 fail to install on my Windows VPS?" - "Can I run VirtualBox or Hyper-V on my VPS?" - "Why doesn't Docker Desktop work on my Windows VPS?" - "How do I get Linux tools on Windows Server without WSL2?" - "Can I run Windows and Linux on the same VPS?" --- ## Enabling sound on Windows VPS URL: https://vpsdime.com/knowledgebase/windows-vps/enabling-sound Last reviewed: 2026-07-02 Summary: Windows Server VMs ship with audio disabled. Enable it from the volume icon prompt, or start the Windows Audio service manually, then reconnect your Remote Desktop session. Sound plays through RDP, but not in the browser Console. ### What this is Windows Server, and therefore your Windows VPS, ships with **audio disabled by default**. Turning it on takes a minute, and sound then plays through your Remote Desktop connection. ### The easy way 1. Right-click the **volume icon** (the one with the red X) in the system tray, then click **Sounds**. 2. Windows asks whether to enable the **Windows Audio service**, accept. 3. **Close and reopen your Remote Desktop connection.** Sound should now work. ### If that didn't do it: enable the service manually 1. Right-click the **Start** button and open **Computer Management**. 2. Expand **Services and Applications**, then click **Services**. ![Computer Management with the Services list open](https://vpsdime.com/knowledgebase/windows-vps/images/sound-1-services.png) 3. Scroll to **Windows Audio**, double-click it, set **Startup type** to **Automatic**, and click **Start**. ![Windows Audio service properties set to Automatic and started](https://vpsdime.com/knowledgebase/windows-vps/images/sound-2-windows-audio.png) 4. Click **OK**, then **close and reopen your Remote Desktop connection**. ### Two things to keep in mind - Whichever method you use, sound only starts working after you **reconnect the RDP session**, the audio device is provided by Remote Desktop, and it's negotiated at connection time. - **Sound does not work in the browser Console** in your client area; it comes through RDP only. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - whether the Windows Audio service is running and set to Automatic, - whether you reconnected the RDP session after enabling it. ### Related questions - "Why is there no sound on my Windows VPS?" - "How do I enable the Windows Audio service?" - "Does audio work over RDP?" - "Why is there no sound in the Console?" --- ## How to change the time zone in Windows Server 2019 URL: https://vpsdime.com/knowledgebase/windows-vps/change-time-zone-server-2019 Last reviewed: 2026-07-02 Summary: On Windows Server 2019 the regular Settings methods fail to change the time zone, run timedate.cpl as Administrator instead and set it from the classic Date and Time applet. ### What this is Due to how **Windows Server 2019** is set up, changing the time zone through the regular Settings interface fails. The fix is to use the classic **Date and Time** applet, run as Administrator. ### Steps ![Running timedate.cpl as Administrator from the search results](https://vpsdime.com/knowledgebase/windows-vps/images/change-time-zone-2019.png) 1. Click the **Search** icon and search for `timedate.cpl`. 2. **Right-click** the result and choose **Run as administrator**, and approve the prompt with **Yes**. 3. The **Date and Time** applet opens. Click **"Change time zone..."**. 4. Pick your time zone and click **OK**. The change applies immediately, no reboot needed. (Server times default to UTC, which is a perfectly good choice for servers, change it only if your applications genuinely need local time.) ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which method you tried (Settings or timedate.cpl) and what happened. ### Related questions - "How do I change the time zone on my Windows VPS?" - "Why can't I change the time zone in Windows Server 2019 settings?" - "What is timedate.cpl?" --- ## How can I change the language of my Windows VPS? URL: https://vpsdime.com/knowledgebase/windows-vps/change-windows-language Last reviewed: 2026-07-02 Summary: Windows Server installs in English, adding your display language via Settings, Time & Language (download the pack, set as display language, sign out), the separate knobs people conflate, display language vs keyboard layout vs regional formats, and applying the change to new accounts and system screens. ### What this is Your Windows VPS comes with Windows Server in **English**, and Windows can run in your language instead. Three separate settings hide under "language", and most frustration comes from changing the wrong one, so, the map first: - **Display language**: what menus, Settings, and dialogs are written in, the big one, needs a language pack. - **Keyboard layout**: what your keys type, changeable instantly, no pack needed, and *independent* of display language (English Windows with a German keyboard is a perfectly normal combination). - **Regional format**: dates, currency, decimal separators, also independent. ### Changing the display language 1. **Settings → Time & Language → Language** (on Server 2025/2022; *Language & region* on newer builds). 2. **Add a language**, pick yours, and make sure **"Set as my Windows display language"** is ticked in the add dialog (and include the Language pack component if offered). 3. Windows downloads the pack, then **sign out and back in** (your [RDP session](https://vpsdime.com/knowledgebase/windows-vps/connect-rdp), disconnect and reconnect), the interface comes back in your language. Two Server realities worth knowing: the download needs a few minutes (watch for it under the language's Options), and on some Server builds the list of *display*-capable languages is shorter than the full input-language list, if yours appears without the "display language" option, that build ships it as input/format support only. ### Keyboard layout only If what you actually want is to **type** in your layout: same Language page → Add a language → *untick* the display option, or add a keyboard under your existing language's Options. Switch layouts with **Win+Space**. One RDP nuance: the client usually carries your local keyboard into the session, so if typing produces wrong characters, align the layout *inside* the VPS with the physical keyboard you're using. ### Formats, and the deeper system screens - **Regional format** (dates, decimals): Settings → Time & Language → Language & region → Regional format, apps pick it up per-account. - The display language applies to **your account**. To also cover the login screen, system accounts, and new users: **Control Panel → Region → Administrative tab → "Copy settings..."**, tick *Welcome screen and system accounts* and *New user accounts*. (The [time zone](https://vpsdime.com/knowledgebase/windows-vps/change-time-zone-server-2019) is its own separate setting, and its own article.) If a language pack refuses to download, check [Windows Update health](https://vpsdime.com/knowledgebase/windows-vps/windows-updates) first, packs come through the same pipe. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP and your Windows Server version, - the language you're adding, - what's still in the wrong language (display, keyboard, or formats), and whether the pack downloaded. ### Related questions - "How do I change Windows Server to my language?" - "How do I add a keyboard layout on my Windows VPS?" - "Why does my RDP session type the wrong characters?" - "How do I apply the language to the login screen and new accounts?" --- ## How to find the device name or device ID of a Windows VPS URL: https://vpsdime.com/knowledgebase/windows-vps/find-device-id Last reviewed: 2026-07-02 Summary: Find your Windows VPS's Device Name, Device ID, and Product ID under Settings, System, About, some software licensing and activation tools ask for these values. ### What this is Some software licensing, activation, and management tools ask for your machine's **Device Name**, **Device ID**, or **Product ID**. On your Windows VPS they're all on one screen. ### Steps ![Navigating to Settings, System, About to reveal the Device ID](https://vpsdime.com/knowledgebase/windows-vps/images/find-device-id.gif) 1. Click the **Search** button, type `Settings`, and press Enter. 2. Click **System**. 3. Scroll down in the left menu and click **About**. 4. The right-hand pane shows **Device name**, **Device ID**, and **Product ID**. Tip: the values have copy options on right-click, paste them rather than retyping. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - which value you need (Device Name, Device ID, or Product ID) and what it's for. ### Related questions - "Where do I find the Device ID on my Windows VPS?" - "How do I find my Windows device name?" - "Where is the Product ID in Windows?" --- ## Buying a VPS URL: https://vpsdime.com/knowledgebase/presales Last reviewed: 2026-07-04 Summary: Everything you need to choose and order a VPS with confidence, what a VPS is, Linux vs Premium, Windows VPS, how to size and pick one, how to order, the money-back guarantee, and a pre-sales FAQ. Choosing and ordering a VPS, with the answers you'll want first. ### New to this? - [What is a VPS?](https://vpsdime.com/knowledgebase/presales/what-is-a-vps). What a VPS is, how it differs from shared hosting, and the many things you can do with one. - [What is a hostname?](https://vpsdime.com/knowledgebase/presales/what-is-a-hostname). The name a server calls itself, how it differs from a domain name, what an FQDN is, and what to enter when ordering. ### How a VPS compares Objective comparisons, if you're weighing a VPS against another kind of hosting. - [VPS vs shared hosting](https://vpsdime.com/knowledgebase/presales/vps-vs-shared-hosting). Your own isolated server with root access, versus a managed account on a shared server. - [VPS vs cloud server](https://vpsdime.com/knowledgebase/presales/vps-vs-cloud-server). Local NVMe and flat pricing, versus separate storage nodes and metered hourly billing. - [VPS vs dedicated server](https://vpsdime.com/knowledgebase/presales/vps-vs-dedicated-server). A slice you can resize, snapshot, and replace in minutes, versus a whole physical machine. - [VPS vs managed app platforms](https://vpsdime.com/knowledgebase/presales/vps-vs-managed-app-platforms). Running your own server, versus a push-code-and-forget platform (PaaS). - [Managed vs self-managed](https://vpsdime.com/knowledgebase/presales/managed-vs-unmanaged). Who runs the software layer, and why self-managing a server is very doable now. ### Choosing the right one - [Choosing the right VPS](https://vpsdime.com/knowledgebase/presales/choosing-the-right-vps). The four quick decisions: type, size, OS, and datacenter, with a safe default. - [Linux VPS vs Premium VPS](https://vpsdime.com/knowledgebase/presales/linux-vps-vs-premium-vps). Shared vs dedicated resources, and which is right for you. - [Windows VPS](https://vpsdime.com/knowledgebase/presales/windows-vps). What it is, what it's for, and how it works. - [How to choose a plan size](https://vpsdime.com/knowledgebase/presales/choosing-a-vps-plan-size). Sizing RAM, CPU, storage, and traffic by workload. ### Ordering - [How to order a VPS](https://vpsdime.com/knowledgebase/presales/how-to-order-a-vps). The full walkthrough, from picking a plan to a running server. - [Refunds and money-back guarantee](https://vpsdime.com/knowledgebase/billing/refunds). Your first order is risk-free for 72 hours; no contract. - [My order is under review](https://vpsdime.com/knowledgebase/presales/order-under-review). Every paid order gets a quick human review before activation; first orders and dormant accounts get a closer look. - [My order was flagged by fraud screening](https://vpsdime.com/knowledgebase/presales/order-flagged-as-fraud). The automated checkout screening, the usual triggers (VPN, country mismatch), and how false positives get reviewed. ### Still have questions? - [Pre-sales FAQ](https://vpsdime.com/knowledgebase/presales/pre-sales-faq). Billing, technical, support, and privacy questions answered. - For payment, tax, refund, and billing-schedule details, see the [Billing](https://vpsdime.com/knowledgebase/billing) section. --- Prefer to talk to a person? [Open a support ticket](https://vpsdime.com/open-ticket/) any time. We reply in minutes. --- ## What is a VPS? URL: https://vpsdime.com/knowledgebase/presales/what-is-a-vps Last reviewed: 2026-07-02 Summary: A VPS (Virtual Private Server) is your own private server in a datacenter, a slice of a powerful machine that's entirely yours to control, with full root or Administrator access, the operating system you choose, a dedicated IP, and an always-on connection. This is what a VPS is, how it differs from shared hosting and a home server, and the many things you can do with one. ### The short version A **VPS (Virtual Private Server)** is your own private server, running in a professional datacenter, that you control completely. You get **full root (or Administrator) access**, the **operating system you choose**, a **dedicated IP address**, and a fast, always-on connection. In practice it behaves exactly like a computer that's yours alone, except it lives on enterprise hardware, never sleeps, and is reachable from anywhere in the world. The "virtual" part just means one powerful physical server is divided into several private servers, each fully isolated. The "private" part is the important bit: it's yours. You decide what runs on it. ### How it's different from... - **Shared hosting.** Shared hosting gives you a locked-down account on someone else's setup, you can upload a website, but you can't install what you want or touch the system. A VPS hands you the keys: root access, any software, full control. See [VPS vs shared hosting](https://vpsdime.com/knowledgebase/presales/vps-vs-shared-hosting). - **A computer at home.** You could run a server on an old PC in a cupboard, but a VPS gives you a static IP, enterprise NVMe hardware, a fast datacenter network, and true 24/7 uptime, without the noise, the power bill, or a home connection that drops. - **A dedicated server.** A dedicated server is a whole physical machine. A VPS gives you the same freedom and root access for a fraction of the price, because you take the slice you actually need. See [VPS vs dedicated server](https://vpsdime.com/knowledgebase/presales/vps-vs-dedicated-server). ### What can you do with a VPS? Quite a lot. Some of the most popular uses: - **Host websites and web apps.** WordPress, a custom site, a Node/Python/PHP app, an online store, all on a server you control end to end. - **Run a database.** PostgreSQL, MySQL/MariaDB, MongoDB, Redis, on dedicated storage with room to grow. - **Self-host your own apps.** Your own private cloud (Nextcloud), a password manager, a media server, analytics, a Git server, the "de-Google your life" project starts here. - **Game servers.** Minecraft, and other multiplayer servers you and your friends actually control. - **A personal VPN or secure exit node.** Your own private, encrypted way onto the internet. - **Development and staging.** A clean, reproducible environment for building, testing, and CI, separate from your laptop. - **Automation and bots.** Cron jobs, scrapers, trading or chat bots, scheduled tasks that need to keep running when your computer is off. - **Docker and containers.** Deploy containerized apps and services however suits you. - **Remote desktop.** With a [Windows VPS](https://vpsdime.com/knowledgebase/presales/windows-vps), a full Windows desktop in the cloud for software that only runs on Windows. - **Learn real skills.** Managing your own server is one of the best ways to learn Linux, networking, and systems, skills that are in genuine demand. ### What you get and control - **Root / Administrator access**, do anything, install anything. - **Your choice of OS**, a range of Linux distributions, or Windows Server. - **Dedicated resources** on **NVMe SSD** storage, with generous RAM for the price. - **A dedicated IP address** and full network control. - **A management panel** to power, reinstall, resize, and monitor your server, plus an out-of-band console for when you need it. ### Is a VPS right for you? If you want real control and room to build, yes. VPSDime servers are **self-managed**, which means the server is yours to run, and that's the point: nobody locks you out of your own machine. You don't need to be an expert to start; modern Linux is friendly, there's a huge community, and if you ever get stuck our support team replies **in minutes, 24/7**. Prefer not to touch the command line at all? You can hire a freelancer to handle the technical side and still enjoy the value. ### Getting started Pick your side, [Linux VPS](https://vpsdime.com/linux-vps) for value and flexibility, [Premium VPS](https://vpsdime.com/premium-vps) for fully dedicated performance, or [Windows VPS](https://vpsdime.com/knowledgebase/presales/windows-vps) for a Windows desktop, choose a plan that fits (you can [resize later](https://vpsdime.com/knowledgebase/presales/choosing-a-vps-plan-size)), and you'll be up and running in minutes. New to it? Start with [Choosing the right VPS](https://vpsdime.com/knowledgebase/presales/choosing-the-right-vps). --- Questions before you order? You can [open a ticket](https://vpsdime.com/open-ticket/), and we typically reply within minutes. ### Related questions - "What is a VPS and how does it work?" - "What can I use a VPS for?" - "What's the difference between a VPS and shared hosting?" - "VPS vs dedicated server, what's the difference?" - "Do I need a VPS?" - "Can I host a website on a VPS?" - "Can I run my own cloud / VPN / game server on a VPS?" - "Do I need to be technical to use a VPS?" --- ## What is a hostname? URL: https://vpsdime.com/knowledgebase/presales/what-is-a-hostname Last reviewed: 2026-07-05 Summary: A hostname is the name a server calls itself, a label for the machine, not its address on the internet. This explains what a hostname actually does, how it differs from a domain name, what a fully qualified domain name (FQDN) is, and what to enter, if anything, in the Hostname field when you order a VPS. ### The short answer A **hostname is the name a computer gives itself**. It's a label for the machine, the same way "work-laptop" might be the name of your laptop. It identifies the server to you and to the software running on it. It is **not your website's address**. Visitors reach a server through a **domain name** and **DNS**, which are set up separately, and the hostname plays no part in that. Typing `www.example.com` into the Hostname field when you order doesn't register that domain, doesn't point it at your server, and doesn't make a website appear there. It just makes the machine call itself that. And yes, a hostname is always included: the field on our order form is **optional**, and if you leave it blank we assign a sensible one automatically. You can change it later, any time, from inside the server. ### A name, not an address Once your VPS is running, its hostname shows up in exactly the places you'd expect a name to: - in your **shell prompt** when you're logged in (`root@myserver:~#`), which is how you tell three open terminal windows apart, - in the server's own **logs**, so entries say which machine wrote them, - in your **client area**, as the label on the service in your list. That's the job. It's a name for your own benefit, so "the server" has something to be called. It doesn't have to be registered anywhere, it costs nothing, it takes effect instantly, and nobody on the internet needs to approve it, because nothing on the internet routes traffic by it. A useful way to hold the distinction: the hostname is the name written on the machine; the domain name is the address people use to find it. ### Hostname vs domain name A **domain name** (`example.com`) is a name you rent from a **registrar** for an annual fee. It lives in the public **DNS**, the internet's directory, where a record you create maps the name to your server's IP address. That mapping is what makes `example.com` reach your VPS, and it's the only thing that does. Side by side: | | Hostname | Domain name | |---|---|---| | What it is | The name a machine calls itself | A name registered in the public DNS | | Who assigns it | You (or your provider) | A registrar, for an annual fee | | Who can see it | You, your software, your logs | Everyone on the internet | | Makes a website reachable? | No | Yes, once a DNS record points it at your server's IP | | Has to be unique? | Only among your own machines | Globally | | Cost | Free | A small yearly fee to the registrar | The two get confused for a good reason: **the same text can be both**. It's normal, and good practice, to name a server `web1.example.com` *and* create a DNS record for `web1.example.com` pointing at it. When that's done, the machine's self-given name and its public address happen to match. But nothing enforces the match; they're two separate systems that you align by convention. A server named `web1.example.com` with no DNS record is unreachable by that name, and a DNS record works fine even if the server calls itself `potato`. ### The FQDN: where hostname and domain meet A **fully qualified domain name (FQDN)** is the complete, unambiguous form of a name: a **host label plus the full domain** it belongs to. In `web1.example.com`: - `web1` is the **short hostname**, the machine's own name, - `example.com` is the **domain**, - the whole string, `web1.example.com`, is the FQDN. DNS names read right to left, from general to specific: `com` is the top-level domain, `example` the domain registered within it, `web1` a host within that. Each dot-separated part is a *label*, and labels follow simple rules: letters, digits, and hyphens, up to 63 characters per label and 253 for the whole name, case doesn't matter. Why give a machine an FQDN instead of just `web1`? For a single hobby server it genuinely doesn't matter much. It starts to matter when other systems inspect your server's name: **mail is the classic case**, since receiving mail servers check that the name your server announces, its DNS record, and the reverse DNS on its IP all agree, and a bare one-word hostname fails that test. If you plan to send mail from the VPS, name it with an FQDN under a domain you own (a common choice is `mail.example.com`) and set the matching reverse DNS. ### What the Hostname field does when you order When you [order a VPS](https://vpsdime.com/knowledgebase/presales/how-to-order-a-vps), the configuration page has a **Hostname** field. Here's precisely what it does and doesn't do: - **It's optional, and automatic if skipped.** Leave it blank and we pick a hostname for you, so there's nothing you must prepare or buy beforehand. Every VPS ends up with one either way. - **It sets the operating system's hostname** on your new server, and nothing else. You can enter a short name (`myserver`) or an FQDN (`web1.example.com`), whichever you prefer. - **It doesn't touch the domain system at all.** Entering `www.example.com` doesn't register `example.com`, doesn't create DNS records, and doesn't make a website load at that address. It's harmless, the server will simply call itself that, but the website part is a separate job (next section). - **On Windows VPS** the field is a **Label** instead: a friendly display name for the service in your client area. It doesn't name Windows itself. If you're still deciding which VPS to order in the first place, that decision is covered in [Choosing the right VPS](https://vpsdime.com/knowledgebase/presales/choosing-the-right-vps). ### So how does a website get its name? Three steps, and the hostname isn't one of them: 1. **Register the domain** at a registrar (Namecheap, Porkbun, Cloudflare, and many others). We don't sell domain names ourselves, any registrar works with our VPS. 2. **Point the domain at your VPS** by creating a DNS **A record** that maps the name to your server's IP. You can host the DNS at your registrar, at Cloudflare, or on our **free DNS Manager**, whichever suits you. The walkthrough is [Pointing your domain at your VPS](https://vpsdime.com/knowledgebase/getting-started/pointing-your-domain). 3. **Serve the site** with a web server on the VPS, covered step by step in [Hosting a website on your VPS](https://vpsdime.com/knowledgebase/getting-started/hosting-a-website). Once step 2 is done, `www.example.com` reaches your server whatever its hostname is. Renaming the server to match your domain afterward is a nice finishing touch, not a requirement. ### Choosing a hostname, and changing it later There's no wrong answer, but the conventions exist for a reason: - **Keep it short and lowercase**, letters, digits, and hyphens. Name servers by role (`web1`, `db1`, `staging`) and the names stay meaningful as you add machines. - **Use an FQDN under a domain you own** if the server will send mail, as explained above. - **Don't use a domain you don't own** as the name. It works, but it's a small lie in your logs that will confuse you or a colleague later. Changing it on a running Linux server takes one command and no reboot: ``` hostnamectl set-hostname web1.example.com ``` There's also a **Hostname** button on the VPS's [manage page](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps) in the client area that does the same thing, use whichever is handier. Two reassurances, since this question comes up: a hostname change **doesn't affect the websites hosted on the server**. Websites answer to their domains through the web server's configuration, not to the machine's name, so renaming the machine doesn't touch them, unless something on the server was deliberately configured around the old name (an `/etc/hosts` entry, a mail server's `myhostname`, a script that reads the hostname), which is a quick check after renaming. And the change is instantly reversible: if anything acts up afterward, set the old name back with the same command. So if you ordered with the auto-assigned name, or a name you've gone off, nothing is stuck. The hostname is the most easily changed setting on the whole server. --- Questions before you order? You can [open a ticket](https://vpsdime.com/open-ticket/), and we typically reply within minutes. ### Related questions - "Is the hostname on the order form used for my website, or is it just an internal name?" - "Is a hostname included and assigned automatically when I buy a VPS?" - "What should I enter in the Hostname field when ordering?" - "What's the difference between a hostname and a domain name?" - "What is an FQDN (fully qualified domain name)?" - "If I set my hostname to www.mydomain.com, will my website work there?" - "Do you sell or register domain names?" - "Can I change my server's hostname later?" - "Will changing my hostname break my website?" --- ## VPS vs shared hosting URL: https://vpsdime.com/knowledgebase/presales/vps-vs-shared-hosting Last reviewed: 2026-07-02 Summary: Shared hosting and a VPS are two ways to run a website or application on someone else's hardware. The core difference is isolation and control: shared hosting gives you a managed account alongside many other users on one server, while a VPS gives you your own isolated server with root access. This compares the two and explains when each makes sense. Shared hosting and a VPS are two different ways to run a website or application on hardware you don't own. The core difference is **isolation and control**: shared hosting gives you a managed account alongside many other users on one server, while a VPS gives you your own isolated server that you control fully. ### What shared hosting is On shared hosting, one physical server runs many customers' websites at once, all behind a control panel such as cPanel. You get an account on that server, not the server itself. The provider manages the machine, the operating system, and the software; you upload your site and manage it through the panel. CPU and memory are shared across everyone on the server, usually with limits on each account so that one user can't consume the whole machine. ### What a VPS is A VPS (Virtual Private Server) is your own private, isolated server: a virtualized slice of a physical machine with resources allocated to you. You get root or Administrator access, install any software you like, and control the operating system directly. It's typically self-managed, meaning you run the software layer yourself. See [What is a VPS?](https://vpsdime.com/knowledgebase/presales/what-is-a-vps). ### Side by side | | Shared hosting | VPS | |---|---|---| | What you get | An account on a shared server | Your own isolated server | | Root access | No | Yes | | Install any software | No, limited to what the panel allows | Yes | | Resources | Shared, with account limits | Allocated to you | | Isolation from neighbours | Limited | Strong | | Control panel | Usually included (cPanel and similar) | None by default; install your own | | Who manages the OS | Provider | You (self-managed) | | Learning curve | Low | Higher | | Typical price | Lowest | Low, above shared hosting | | Scales to | Small sites | Small to large workloads | ### The main difference: control versus simplicity Shared hosting is simple and hands-off. The provider handles the server, the updates, and the security, and you work within the boundaries of the control panel. That simplicity is also its limit: you can't install arbitrary software, you can't change system configuration, and your site shares a machine, and that machine's reputation, with many other users. A VPS removes those boundaries. Root access means you can install and configure anything, tune the system, and run software that shared hosting would never permit. The cost of that freedom is responsibility: a VPS is normally self-managed, so keeping the operating system updated and secured is your job rather than the provider's. See [Managed vs self-managed](https://vpsdime.com/knowledgebase/presales/managed-vs-unmanaged). ### When each makes sense **Shared hosting** is a reasonable fit when: - you're running a straightforward website, or a few of them, - you want everything managed for you and prefer not to touch the system, - the lowest possible price matters most, - a control panel covers everything you need. **A VPS** is the better fit when: - you need root access, or software that shared hosting won't allow, - you've outgrown the resource limits or performance of a shared account, - you want isolation from other users, your own IP address, and predictable resources, - you're running applications beyond a basic website (custom apps, databases, services, automation). Many people start on shared hosting and move to a VPS when they hit its limits. If you're weighing that step, [What is a VPS?](https://vpsdime.com/knowledgebase/presales/what-is-a-vps) covers what you'd gain, [Choosing the right VPS](https://vpsdime.com/knowledgebase/presales/choosing-the-right-vps) helps you pick one, and [the migration guide](https://vpsdime.com/knowledgebase/getting-started/migrating-to-a-vps) walks the actual move. --- Questions before you order? You can [open a ticket](https://vpsdime.com/open-ticket/), and we typically reply within minutes. ### Related questions - "What's the difference between a VPS and shared hosting?" - "Is a VPS better than shared hosting?" - "Should I move from shared hosting to a VPS?" - "Why can't I install my own software on shared hosting?" - "Does a VPS come with cPanel?" - "When should I upgrade from shared hosting?" --- ## VPS vs cloud server URL: https://vpsdime.com/knowledgebase/presales/vps-vs-cloud-server Last reviewed: 2026-07-02 Summary: VPS" and "cloud server" overlap heavily; both give you a virtual server you control. The meaningful differences are architectural and commercial: how storage is attached, and how you're billed. A cloud server typically separates compute and storage nodes with network storage and hourly metered billing, while a VPS keeps storage local on the host and is usually a flat monthly price. This compares the two. "VPS" and "cloud server" overlap heavily. Both give you a virtual server you control with root access. The meaningful differences are architectural and commercial: **how your storage is attached, and how you're billed.** This article uses "cloud server" to mean the model built on separate compute and storage nodes, and "VPS" to mean a virtual server with storage local to its host. ### Two storage architectures The central technical difference is where your disk lives. - **A cloud server usually separates compute and storage.** Your server's processing runs on one pool of compute nodes, and its disk lives on a separate pool of storage nodes, reached across the network (often called network-attached, block, or distributed storage). Compute and storage scale independently, and because the disk isn't tied to any one physical host, the running server can be moved between compute nodes, and the storage survives a host failure. - **A VPS usually keeps compute and storage together** on the same physical machine, on local disks. On modern hardware that means local NVMe SSDs sitting directly on the host, which is what VPSDime uses. There's no network hop between the processor and the disk. Neither is "better" in the abstract. They trade different things. ### What that trade-off means - **Performance and consistency.** Local NVMe gives the lowest disk latency and the most consistent I/O, because reads and writes never leave the machine. Network storage adds latency to every disk operation, and its performance can vary with network load and the state of the storage cluster. For disk-heavy work such as databases or busy I/O, local storage is generally faster and steadier. - **Flexibility and resilience.** Network storage decouples the disk from the host, which enables things local storage can't do as easily: resize storage independently of compute, move a live server to different hardware, and keep the data intact if a compute node fails. With local storage, the disk is bound to the host, so moving or resizing is a copy operation rather than a detach-and-reattach. | | Cloud server (compute + storage nodes) | VPS (local NVMe) | |---|---|---| | Storage location | Separate storage nodes, over the network | Local disks on the same host | | Disk latency | Higher (network hop) | Lowest (local) | | Performance consistency | Varies with network and cluster load | Steady | | Resize storage independently | Yes | Tied to the host | | Survives host failure | Storage persists, server can move | Restored from backup onto new host | | Billing model | Usually hourly, metered per resource | Usually one flat monthly price | ### The billing difference The two models are usually sold differently, and the commercial difference matters as much as the technical one. **Cloud servers are typically billed hourly and metered on every resource separately:** compute time, storage capacity, data transfer (outbound "egress" bandwidth is a common and easily overlooked charge), IP addresses, snapshots, and more. That's flexible and precise, and it's well suited to workloads that start and stop or scale up and down constantly. It also makes costs harder to predict: a bill is the sum of many metered line items, and it's common to be surprised by charges, egress especially, that weren't obvious up front. **A VPS is usually sold as a single flat monthly price** that bundles the compute, storage, and a traffic allowance together. You trade the fine-grained, pay-only-for-what-you-use model for a predictable, all-in figure you know in advance. ### When each makes sense **A cloud server's model** fits when: - your workload scales up and down, or starts and stops, frequently enough that hourly billing genuinely saves money, - you need to resize storage independently or move servers between hosts routinely, - you're building on the wider set of managed cloud services that sit around the compute. **A VPS** fits when: - you want the fastest, most consistent disk performance from local NVMe, - your server runs continuously, so a flat monthly price is cheaper and more predictable than metered hourly billing, - you prefer a simple, all-in bill over a metered one. For how a virtual server compares to a full physical machine, see [VPS vs dedicated server](https://vpsdime.com/knowledgebase/presales/vps-vs-dedicated-server). For what a VPS is in general, see [What is a VPS?](https://vpsdime.com/knowledgebase/presales/what-is-a-vps). --- Questions before you order? You can [open a ticket](https://vpsdime.com/open-ticket/), and we typically reply within minutes. ### Related questions - "What's the difference between a VPS and a cloud server?" - "Is a VPS the same as cloud hosting?" - "Local NVMe vs network storage, which is faster?" - "Why is cloud billing so complicated?" - "What are egress or bandwidth fees?" - "Is a VPS cheaper than a cloud server?" --- ## VPS vs dedicated server URL: https://vpsdime.com/knowledgebase/presales/vps-vs-dedicated-server Last reviewed: 2026-07-02 Summary: A dedicated server is an entire physical machine rented to one customer; a VPS is a virtualized slice of a physical machine, isolated from other slices. Both give you full root access. The difference is whether you rent the whole machine or a portion of one, and what that means for raw performance, cost, and how easily the server can be reinstalled, backed up, migrated, and replaced. This compares the two. A **dedicated server** is an entire physical machine rented to one customer. A **VPS** is a virtualized slice of a physical machine, isolated from the other slices on the same hardware. Both give you full root or Administrator access and a server of your own. The difference is whether you're renting the whole machine or a portion of one, and what that implies for performance, cost, and how easily the server can be managed, backed up, and replaced. ### What each is - **A dedicated server** is a single physical computer with all of its hardware allocated to you. There's no hypervisor and no other tenant. You get the full, raw performance of the hardware and complete physical isolation. - **A VPS** runs on a physical host alongside other VPSes, divided up by a virtualization layer (the hypervisor). Each VPS has its own operating system and its allocated share of the host's resources, isolated from its neighbours. See [What is a VPS?](https://vpsdime.com/knowledgebase/presales/what-is-a-vps). ### Where a dedicated server is stronger - **Raw performance.** With no virtualization layer and no neighbours, a dedicated server gives you the machine's full performance. For a workload that needs every bit of a large machine continuously, that ceiling is higher than a slice of one. - **Hardware control.** You can specify particular hardware, more disks or specialized components, and use the full physical resources directly. - **Physical isolation.** Being the only tenant can matter for certain compliance or single-tenancy requirements. - **Cost at scale.** When you genuinely need a whole machine's worth of resources around the clock, renting it outright can be more economical per unit of raw resource than an equivalent slice. ### Where a VPS is stronger Virtualization gives a VPS a set of operational advantages that a physical machine can't match easily: - **Reinstalling is near-instant.** Wiping and reinstalling the OS on a VPS takes seconds to a couple of minutes, because it's software provisioning an image rather than someone re-imaging physical hardware. - **Backups and snapshots are simple.** The whole server can be captured as an image and restored the same way, because it's already a virtual machine. Imaging a physical box is more involved. - **Migrating is easy.** Because a VPS is an image, moving it to a different host or a new server is straightforward compared to migrating a physical machine. - **Replacing is fast.** If something goes wrong, a VPS can be rebuilt or restored onto healthy hardware in minutes. A failed dedicated server waits on hardware repair or replacement. - **Provisioning is fast.** A new VPS is ready in minutes; a dedicated server can take hours or longer to provision. - **Resizing is flexible.** You can scale a VPS up or down without physically changing hardware, and pay for only the fraction of a machine you actually need. - **Resilience to hardware failure.** If a host's hardware fails, a VPS can be restored or moved to other hardware. On a dedicated server, its own hardware failing means downtime until it's fixed. | | Dedicated server | VPS | |---|---|---| | What you rent | A whole physical machine | A slice of a machine | | Virtualization overhead | None | Minimal | | Other tenants | None | Isolated neighbours | | Raw performance ceiling | Highest | High, up to your allocation | | Reinstall | Re-image hardware | Seconds to minutes | | Backup / snapshot | More involved | Simple, whole-machine image | | Migrate / replace | Slow, hardware-bound | Fast, image-based | | Provisioning time | Hours or more | Minutes | | Resize | Hardware change | Software, up or down | | Recover from hardware failure | Wait for repair | Restore or move to other hardware | | Cost | Higher, whole machine | Pay for the portion you need | ### When each makes sense **A dedicated server** makes sense when: - you need the full, uninterrupted performance of an entire machine, - you require specific or specialized hardware, - single-tenancy is a hard requirement, - your resource use is high and constant enough that a whole machine is justified. **A VPS** makes sense when: - your workload fits comfortably within a portion of a machine, as most do, - you value agility: fast provisioning, easy resizing, simple backups, quick recovery, - you want to pay for only the resources you need, - easy replacement and migration matter more than squeezing out the last of the raw hardware. For how a virtual server's storage and billing compare to the cloud model, see [VPS vs cloud server](https://vpsdime.com/knowledgebase/presales/vps-vs-cloud-server). --- Questions before you order? You can [open a ticket](https://vpsdime.com/open-ticket/), and we typically reply within minutes. ### Related questions - "What's the difference between a VPS and a dedicated server?" - "When do I need a dedicated server instead of a VPS?" - "Is a dedicated server faster than a VPS?" - "Why is a VPS easier to back up or migrate?" - "What happens if the hardware fails?" - "Is a dedicated server worth it?" --- ## VPS vs managed app platforms URL: https://vpsdime.com/knowledgebase/presales/vps-vs-managed-app-platforms Last reviewed: 2026-07-02 Summary: A VPS and a managed app platform (Platform-as-a-Service, or PaaS) both get your application online, but at very different levels of abstraction. With a VPS you run a server and deploy your app onto it; with a managed app platform you push code and the platform builds, deploys, scales, and runs it with no server to manage. This compares the two on control, cost, lock-in, and what each can run. A VPS and a managed app platform (also called **Platform-as-a-Service**, or **PaaS**) aim at the same end goal, getting your application online, at very different levels of abstraction. With a VPS you run a server and deploy your app onto it. With a managed app platform you push your code and the platform builds, deploys, scales, and runs it for you, with no server to manage. The trade-off is control and predictable cost on one side, convenience and zero operations on the other. ### What a managed app platform is A managed app platform takes your code (usually straight from a Git repository) and handles everything needed to run it: building it, deploying it, serving it, scaling it under load, and keeping the underlying servers patched and healthy. You never see or touch a server. Many of these platforms are serverless or edge-based, running your code on demand rather than on a machine you rent, and they bundle in extras such as CI/CD, TLS certificates, a CDN, and managed databases. You configure the app through the platform, and it takes care of the rest. ### What a VPS is A VPS is your own server. You install the runtime (Node, Python, PHP, and so on), deploy your application yourself, and run it however you like. You have root access and full control over the operating system, the stack, and the configuration. It's self-managed, so the setup, deployment process, updates, and scaling are yours to handle. See [What is a VPS?](https://vpsdime.com/knowledgebase/presales/what-is-a-vps). The one-line difference: **a managed app platform abstracts the server away; a VPS gives you the server.** ### Side by side | | Managed app platform (PaaS) | VPS | |---|---|---| | You manage | Just your code | The whole server | | Deploy model | Push code, platform builds and runs it | You deploy and run it yourself | | Server access | None | Full root access | | What you can run | The platform's supported runtimes, within its limits | Anything: any language, binaries, background workers, databases | | Scaling | Automatic (often) | You size and scale it | | Operations (patching, uptime) | Handled for you | Yours (self-managed) | | Billing | Usage-based or tiered | Usually a flat monthly price | | Vendor lock-in | Higher (platform-specific config) | Low, it's a standard server | | Stateful / persistent workloads | Often limited | Fully supported | ### Where a managed app platform is stronger - **Speed from code to live.** Connect a repository and your app is deployed. There's nothing to provision, configure, or maintain. - **Zero operations.** No OS to patch, no server to secure, no scaling to plan. The platform handles it. - **Built-in tooling.** CI/CD, preview deployments, TLS, and a CDN are usually included and wired up for you. - **Automatic scaling.** Many platforms scale your app up and down with traffic without any action from you. For a front-end site, a static or JAMstack app, or a small team that wants to ship without thinking about servers, that convenience is the whole point. ### Where a VPS is stronger - **Full control and freedom.** You can run anything: any language or framework, custom binaries, background workers, cron jobs, message queues, your own database, long-running processes. Managed platforms often restrict some of these (execution-time limits, no persistent processes, a fixed set of runtimes). - **Predictable cost.** A VPS is usually one flat monthly price. Platform billing is usage-based, which is cheap at rest but can climb sharply, and less predictably, as traffic, build minutes, function calls, or bandwidth grow. - **No lock-in.** A VPS runs a standard operating system, so your app isn't tied to one vendor's configuration and conventions. Moving it elsewhere is straightforward. - **Stateful and heavy workloads.** Databases, persistent storage, and processes that must stay running are native to a VPS, and awkward or unsupported on many platforms. ### The middle ground: a self-hosted platform on a VPS The two approaches aren't strictly either/or. [Open-source tools](https://vpsdime.com/knowledgebase/getting-started/open-source-control-panels) such as **Coolify, Dokku, and CapRover** install on a VPS and give you a git-push-to-deploy experience much like a managed platform, on a server you own. You get most of the convenience (push to deploy, automatic TLS, easy rollbacks) while keeping full control, flat pricing, and no lock-in. The catch is that you run the platform yourself, which is part of the self-managed trade-off. (Coolify is available as a one-click app on VPSDime.) ### When each makes sense **A managed app platform** fits when: - you want to ship code with no server to manage, - your app suits the platform's model (front-end, static or JAMstack, standard serverless functions), - automatic scaling and built-in CI/CD matter more than control or flat cost, - you're happy to trade some lock-in and variable billing for convenience. **A VPS** fits when: - you want full control and the freedom to run anything, including databases and background services, - you prefer a flat, predictable bill over usage-based pricing, - you want to avoid vendor lock-in, - you're running stateful or non-standard workloads, or you want the platform experience without giving up the server (via a self-hosted tool). For who runs the software layer either way, see [Managed vs self-managed](https://vpsdime.com/knowledgebase/presales/managed-vs-unmanaged). For a VPS compared with the broader cloud model, see [VPS vs cloud server](https://vpsdime.com/knowledgebase/presales/vps-vs-cloud-server). --- Questions before you order? You can [open a ticket](https://vpsdime.com/open-ticket/), and we typically reply within minutes. ### Related questions - "What's the difference between a VPS and a managed app platform?" - "VPS vs a managed app platform, which should I use?" - "What is Platform-as-a-Service (PaaS)?" - "Is a VPS cheaper than a managed platform?" - "Can I get a git-push-to-deploy experience on a VPS?" - "Why would I choose a VPS over a serverless platform?" - "Do managed platforms lock me in?" --- ## Managed vs self-managed VPS URL: https://vpsdime.com/knowledgebase/presales/managed-vs-unmanaged Last reviewed: 2026-07-02 Summary: Managed and self-managed (unmanaged) describe who is responsible for the software layer of a server, the operating system, its updates, security, and the applications on it. The provider always runs the infrastructure underneath; the difference is whether you or the provider runs everything inside the server. This explains the split, the cost and control trade-offs, and why self-managing a server is far more approachable than it used to be. When you rent a server, someone has to keep the software on it healthy: apply updates, configure services, watch security, and fix things when they break. "Managed" and "self-managed" (also called "unmanaged") describe who that someone is. The distinction is about responsibility for the operating system and everything running inside it, not about the quality of the hardware or network underneath. ### The dividing line Every hosted server has two layers: - **The infrastructure:** the physical hardware, power, network, and, for a VPS, the virtualization platform. The provider always runs this. - **The server itself:** the operating system, its updates and security, and the applications you install. This is the layer that "managed" versus "self-managed" is about. Who handles what: | | Self-managed (unmanaged) | Managed | |---|---|---| | Hardware, power, network | Provider | Provider | | Virtualization / platform uptime | Provider | Provider | | Operating system install | Provider (from an image) | Provider | | OS updates and patching | You | Provider | | Security hardening, firewall | You | Provider | | Web server, database, app setup | You | Provider (often) | | Backups configuration | You | Provider (often) | | Cost | Lower | Higher | Exactly what "managed" covers varies from one provider to the next, so it's worth checking where a given provider draws the line. ### What self-managed means in practice You get root or Administrator access and full control. The provider makes sure the server is powered, connected, and running, and hands you a clean operating system. From there, everything inside is yours: you choose the software, you apply the updates, you decide how it's secured. Two things follow from that: - **It costs less.** You aren't paying for anyone's time to administer the server, so a self-managed VPS is typically far cheaper than an equivalent managed one. - **You are the only one in control.** Nobody else logs into your server. You aren't waiting in a support queue for a provider to change a setting, restart a service, or approve a change, and you aren't depending on someone else's priorities or schedule for your own machine. The trade-off is that the responsibility is also yours. If an update breaks something, or a service needs configuring, that's your task to handle, or to delegate to someone you hire. ### Managing a server is far easier than it used to be Self-managed once implied years of system administration experience, which is what made "unmanaged" sound intimidating. That barrier has largely fallen. AI assistants have changed what a non-expert can do on a server. You can paste an error message and get a plain explanation of the cause and a fix. You can ask for a working web server or firewall configuration and have it generated for you. You can have each step of a setup explained as you go, and learn the underlying system while you do it. Tasks that used to mean hours of reading documentation or forum threads now take a short conversation. The practical result is that "self-managed" no longer means "on your own." Someone with little prior experience can stand up and maintain a server today with far less background knowledge than the same task demanded a few years ago. ### What managed hosting is for Managed hosting still has a clear place. It makes sense when: - you have no time to spend on server administration, or simply don't want to, - you want the provider to be accountable for the software layer, not just the hardware, - the workload is important enough that you'd rather pay for professional administration than do it yourself. You pay more, and you give up some direct control, in exchange for handing the work to someone else. ### Which is right for you? It comes down to three things: time, money, and control. - **Self-managed** suits you if you want the lowest cost and full control, and you're willing to run the server yourself, which, with modern tooling and AI help, is very approachable. - **Managed** suits you if you'd rather pay to have the software layer handled and don't need hands-on control. Most VPS hosting is self-managed: the provider runs the infrastructure, and the server itself is yours to run. (For where VPSDime draws that line in practice, see [What support covers](https://vpsdime.com/knowledgebase/support-coverage/what-support-covers).) For what a VPS is in general, see [What is a VPS?](https://vpsdime.com/knowledgebase/presales/what-is-a-vps). For how a VPS compares to other kinds of hosting, see [VPS vs shared hosting](https://vpsdime.com/knowledgebase/presales/vps-vs-shared-hosting). --- Questions before you order? You can [open a ticket](https://vpsdime.com/open-ticket/), and we typically reply within minutes. ### Related questions - "What's the difference between managed and unmanaged hosting?" - "What does a self-managed VPS mean?" - "Do I have to manage the server myself?" - "Is a VPS hard to manage if I'm not technical?" - "Why is unmanaged hosting cheaper?" - "Can I manage a server using AI tools?" --- ## Choosing the right VPS URL: https://vpsdime.com/knowledgebase/presales/choosing-the-right-vps Last reviewed: 2026-07-02 Summary: A simple way to pick the right VPS: four quick decisions, which type (Linux, Premium, or Windows), how big, which operating system, and which datacenter, none of which are permanent. This walks through each choice with a sensible default, so you can order with confidence and adjust later. Picking a VPS comes down to four quick decisions. The good news: **none of them lock you in**, you can resize the plan, reinstall a different OS, and add resources later, so aim for a sensible fit and get going. ### 1. Which type of VPS? - **[Linux VPS](https://vpsdime.com/linux-vps)** is the right call for most people: the best value, generous RAM on fast NVMe, and everything you need for websites, web apps, databases, VPNs, game servers, and self-hosting. - **[Premium VPS](https://vpsdime.com/premium-vps)** reserves resources entirely for your server, for consistent, enterprise-grade performance, and its full virtualization lets you run virtually any operating system. Choose it when performance has to stay steady under load, or you need a non-standard OS. See [Linux VPS vs Premium VPS](https://vpsdime.com/knowledgebase/presales/linux-vps-vs-premium-vps). - **[Windows VPS](https://vpsdime.com/knowledgebase/presales/windows-vps)** is for when you specifically need **Windows**, to run Windows-only software or a full Windows desktop you reach over Remote Desktop. New to all this? Start with [What is a VPS?](https://vpsdime.com/knowledgebase/presales/what-is-a-vps). ### 2. How big? Go with what comfortably fits what you're running **today**. RAM is usually the deciding factor, and our plans lead with plenty of it. A small site or VPN is happy on the entry plans; busier sites, databases, or Windows want more. Full guidance and per-workload starting points are in [How to choose a plan size](https://vpsdime.com/knowledgebase/presales/choosing-a-vps-plan-size), and remember you can **upgrade later** (instantly, with no downtime, on Linux VPS). ### 3. Which operating system? - **On Linux VPS**, pick a distribution, a current **LTS** release like Ubuntu or Debian is the safe default for most people, or use a one-click **Application** to deploy a ready-made stack. - **On Premium VPS**, choose from the Linux distributions, or install **virtually any non-Windows OS yourself**, including BSD or a custom image, by sending us the ISO in a support ticket. - **On Windows VPS**, choose **Windows Server 2025, 2022, or 2019**. You can always [reinstall](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os) a different OS later, so this isn't a one-way door. ### 4. Which datacenter? Pick the location **closest to the people who'll use your server**, that's what gives you the lowest latency and the snappiest feel. Don't guess, measure: our [Looking Glass](https://vpsdime.com/looking-glass) lets you ping and download a test file from every location before you order. Your IP address belongs to the location, so it's worth choosing well up front. We run six datacenters: - [Dallas, US](https://vpsdime.com/dallas-vps) - [Seattle, US](https://vpsdime.com/seattle-vps) - [Los Angeles, US](https://vpsdime.com/los-angeles-vps) - [New Jersey, US](https://vpsdime.com/new-jersey-vps) - [London, UK](https://vpsdime.com/london-vps) - [Amsterdam, NL](https://vpsdime.com/amsterdam-vps) Availability can vary and a location is occasionally out of stock, the order form shows the ones you can deploy to right now. If you specifically need a location that isn't listed, just ask. ### Not sure? Here's a safe default For most people, a **Linux VPS** with **4 to 6 GB** of RAM, running the current **Ubuntu LTS**, in the **datacenter nearest your users**, is an excellent starting point. And if it's your first order with us, it's covered by a **[72-hour money-back guarantee](https://vpsdime.com/knowledgebase/billing/refunds)**, so you can try us with nothing to lose. Still torn? [Contact our team](https://vpsdime.com/open-ticket/) and we'll point you the right way. ### Related questions - "Which VPS should I choose?" - "Linux, Premium, or Windows, what's the difference?" - "What size VPS do I need?" - "Which operating system should I pick?" - "Which datacenter location is best for me?" - "Can I change my plan, OS, or size later?" - "What do you recommend for a beginner?" --- ## Linux VPS vs Premium VPS URL: https://vpsdime.com/knowledgebase/presales/linux-vps-vs-premium-vps Last reviewed: 2026-07-02 Summary: Both give you a full root VPS on fast NVMe storage with the same control panel. The real difference is shared vs dedicated resources. Linux VPS is the great-value choice for most Linux workloads, while Premium VPS is your own slice of a dedicated server, with resources reserved entirely for you, full KVM virtualization (run any OS you like), and free Nightly Backups, for consistent, enterprise-grade performance. ### The short answer Both are real virtual private servers: you get full **root access**, fast **NVMe SSD** storage in RAID10, a dedicated IPv4, and the same easy control panel. If you're running a typical Linux workload and want the best value, **Linux VPS** is the one to pick. If you need performance you can count on every second of the day, or you want to run an operating system outside the usual list, step up to **Premium VPS**. The core difference in one line: **Linux VPS shares the server's capacity efficiently to keep the price low; Premium VPS dedicates resources entirely to your VPS.** ### At a glance | | [Linux VPS](https://vpsdime.com/linux-vps) | [Premium VPS](https://vpsdime.com/premium-vps) | |---|---|---| | **Best for** | Most Linux workloads, best value | Consistent, enterprise-grade performance | | **Resources** | Shared node capacity (actively monitored for headroom) | Fully dedicated to your VPS | | **Virtualization** | Our optimized Linux platform | Full **KVM** virtualization | | **Operating systems** | Our curated Linux distributions + one-click apps | Virtually any non-Windows OS, including your own via ISO | | **Storage** | Write-intensive NVMe SSD (RAID10) | Write-intensive NVMe SSD (RAID10) | | **Backups** | Optional Nightly Backups add-on | **Free Nightly Backups included** | | **Resizing** | Up or down, live and instant, no downtime | Upgrade-only, applies with a quick reboot | | **Access** | root over SSH | root over SSH | | **Starting price** | From $5/mo | From $20/mo | ### Shared vs dedicated resources (the main difference) **Linux VPS** makes smart use of a powerful host's capacity, with monitoring that keeps plenty of headroom available at all times. That efficiency is exactly how we hand you generous RAM and NVMe storage at a genuinely low price. For the vast majority of sites, apps, and projects, it's fast, stable, and more than enough. **Premium VPS** is effectively **your own slice of a dedicated server**: the resources are reserved for your server alone. Nothing you run competes with a neighbour, so performance stays flat and predictable even under sustained load. If your workload is latency-sensitive or business-critical, a busy database, a production app, a service where a slow moment costs you, that guarantee is the whole point. Rule of thumb: **choose Linux VPS by default, and Premium VPS when consistent performance is non-negotiable.** ### Freedom to run any OS (Premium) Linux VPS installs from our **curated list of Linux distributions** (Ubuntu, Debian, AlmaLinux, Rocky, and more), plus one-click **Applications** if you'd rather deploy a ready-made stack. That covers almost everyone. Premium VPS runs **full KVM virtualization**, which means it isn't limited to a list. You can install **virtually any non-Windows operating system**, including BSD variants or a custom image, by sending us the ISO in a support ticket and we'll attach it. If "I need to run something unusual" describes you, Premium is the answer. (After Windows itself? That's its own product, [Windows VPS](https://vpsdime.com/knowledgebase/presales/windows-vps), with the license included.) ### Storage and performance Both product lines run on **write-intensive, high-DWPD enterprise NVMe SSDs in RAID10**, built on hand-tested Dell hardware, drives rated for heavy, sustained write activity. Write-heavy databases, busy logging, and high-churn workloads stay smooth on either product line. ### Backups **Premium VPS includes free Nightly Backups** in the price, so a good restore point is always there without you lifting a finger. **Linux VPS** keeps things lean and lets you add **Nightly Backups** as an optional feature whenever you want it. Either way, backing up matters, see [Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview) for how it works. ### Upgrading later On **Linux VPS**, moving to a bigger (or smaller) plan is **live and instant, with no downtime and the same IP**, so you can start small and scale the moment you need to. On **Premium VPS**, an upgrade applies with a **quick reboot**, and note that Premium is **upgrade-only**: you can't move down to a smaller plan later, so start with the size you actually need and grow from there. Both are self-service from your client area. ### Which should you choose? **Pick Linux VPS if you:** - want the best value for the resources, - are running websites, web apps, dev/test environments, a VPN, game servers, or self-hosted tools, - are happy on a mainstream Linux distribution, - like the idea of instant, no-downtime upgrades as you grow. **Pick Premium VPS if you:** - need performance that stays consistent under sustained load, - run a production service, a busy database, or anything latency-sensitive, - want backups included for free, - want to run a non-standard OS (BSD, a custom image, and so on). Still weighing it up? See [Choosing the right VPS](https://vpsdime.com/knowledgebase/presales/choosing-the-right-vps) for the full decision, or [how to size your plan](https://vpsdime.com/knowledgebase/presales/choosing-a-vps-plan-size). If you're after Windows rather than Linux, that's a different product, see [Windows VPS](https://vpsdime.com/knowledgebase/presales/windows-vps). --- Questions before you order? You can [open a ticket](https://vpsdime.com/open-ticket/), and we typically reply within minutes. ### Related questions - "What's the difference between Linux VPS and Premium VPS?" - "Is Premium VPS worth it?" - "What does 'dedicated resources' actually mean?" - "Which VPS is best for a production database?" - "Can I run FreeBSD or a custom OS on your VPS?" - "Do I get free backups on Premium?" - "Can I upgrade from Linux VPS to Premium later?" - "Which VPS should I buy for my project?" --- ## Windows VPS URL: https://vpsdime.com/knowledgebase/presales/windows-vps Last reviewed: 2026-07-02 Summary: A Windows VPS is your own Windows Server machine in the cloud, with full Administrator access, that you reach over Remote Desktop (RDP) from anywhere. It runs on Hyper-V with a choice of Windows Server 2025, 2022, or 2019 Datacenter, on fast NVMe storage. This is what a Windows VPS is, what people use it for, and how it works. ### What it is A **Windows VPS** is your own **Windows Server** machine running in our datacenter, that you control with full **Administrator** access and connect to over **Remote Desktop (RDP)** from any device. It's a complete Windows desktop and server in the cloud: always on, on a fast connection, reachable from your PC, Mac, or phone, wherever you are. If you know your way around a normal Windows PC, you already know how to use it. The difference is it lives on enterprise hardware, never turns off, and you get to it remotely. ### The technology behind it - **Virtualization: Hyper-V**, Microsoft's own server virtualization, so Windows runs exactly as it's meant to. - **Operating system:** your choice of **Windows Server 2025, 2022, or 2019** (Datacenter edition). The Windows license is included in your plan price, nothing extra to buy or activate. - **Storage: write-intensive enterprise NVMe SSD in RAID10**, built on hand-tested Dell hardware, so it's genuinely fast. - **A dedicated IP address**, generous RAM and traffic, and the same management panel and out-of-band console as our other VPS products. ### What can you do with a Windows VPS? - **A full Windows desktop in the cloud.** Work from a consistent Windows environment on any device, including a laptop, tablet, or phone, with your files and apps always where you left them. - **Run Windows-only software.** Accounting suites, trading platforms (MetaTrader and similar), industry and line-of-business apps, anything that simply won't run on Linux or a Mac. - **Keep tools running 24/7.** Trading bots, automation, or scheduled jobs that need to stay up even when your own computer is off. - **Host Windows applications.** .NET apps, IIS websites, Windows services, and databases like MSSQL. - **Browser and GUI automation.** Tasks that need a real desktop and screen, not just a command line. - **Test and support on Windows.** A clean, disposable Windows Server for testing, or a shared machine your team can all reach. ### How you connect You use **Remote Desktop (RDP)** with the **Administrator** password we generate for you. A Remote Desktop client is **built into Windows**, and free clients are available for **Mac, Linux, iOS, and Android**, so you can reach your server from practically anything. Point the client at your VPS's IP, sign in as Administrator, and you're at the Windows desktop. Step-by-step guides for every device are in [How to connect using RDP](https://vpsdime.com/knowledgebase/windows-vps/connect-rdp). If you can't connect, the [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) tool checks your Windows VPS and can reset the Administrator password for you. ### Windows VPS or Linux VPS? Simple rule: **choose a Windows VPS when you specifically need Windows**, to run Windows-only software or a Windows desktop. For websites, web apps, databases, and most server workloads, a [Linux VPS](https://vpsdime.com/linux-vps) is faster to work with and better value. Not sure what a VPS even is yet? Start with [What is a VPS?](https://vpsdime.com/knowledgebase/presales/what-is-a-vps). ### Getting started Pick a [Windows VPS plan](https://vpsdime.com/windows-vps), choose your Windows Server version and datacenter, and it deploys in minutes. You'll get the IP and Administrator password to connect over Remote Desktop. Not sure how big to go? See [how to size your plan](https://vpsdime.com/knowledgebase/presales/choosing-a-vps-plan-size), you can resize later. --- Questions before you order? You can [open a ticket](https://vpsdime.com/open-ticket/), and we typically reply within minutes. ### Related questions - "What is a Windows VPS?" - "What can I use a Windows VPS for?" - "How do I connect to a Windows VPS?" - "Which Windows Server versions do you offer?" - "Is the Windows license included?" - "Can I run trading software / MetaTrader on a Windows VPS?" - "Windows VPS vs Linux VPS, which do I need?" - "What virtualization do you use for Windows VPS?" --- ## How to choose a VPS plan size URL: https://vpsdime.com/knowledgebase/presales/choosing-a-vps-plan-size Last reviewed: 2026-07-02 Summary: How to pick the right amount of RAM, CPU, storage, and traffic for what you're running, with sensible starting points for common workloads like websites, databases, game servers, and VPNs. The golden rule: start with what fits today, because you can resize later (instantly and with no downtime on Linux VPS). ### The short answer Pick the plan that comfortably fits what you're running **today**, then grow when you actually need to. You don't have to predict the future or over-buy "just in case", because resizing later is easy: on **Linux VPS** an upgrade is **live, instant, and keeps your IP**, and on Premium and Windows it's a quick reboot. So aim for a sensible fit, not a perfect guess. ### What each resource does - **RAM (memory)** is usually the one that matters most. It's what your apps, databases, and the operating system actually run in. Run out and things slow to a crawl or get killed, so give yourself a little headroom. Our plans lead with generous RAM for exactly this reason. - **vCPU / CPU cores** handle the work. Most sites and apps are happy with a few cores; you only need lots of CPU for heavy, constant computation (large sites under load, video processing, busy build servers). - **Storage (NVMe SSD)** is your disk space, for the OS, your app, files, and databases. Estimate what you'll store and leave room to grow. - **Traffic (bandwidth)** is how much data your server sends and receives each month. Our allowances are generous; you'd usually only stress them with heavy downloads, streaming, or a very busy site. ### Sensible starting points These are comfortable starting sizes, not hard limits, adjust up if your workload is heavy: - **A personal site, blog, or small WordPress site:** a **4GB** plan is plenty, and often more than enough. - **A few websites or a small web app:** **6GB** gives you comfortable headroom for the app plus its database. - **A busy site or a real database workload:** **12GB and up**, and if performance needs to stay rock-steady under load, consider [Premium VPS](https://vpsdime.com/knowledgebase/presales/linux-vps-vs-premium-vps) for dedicated resources. - **A game server (for example Minecraft):** memory is the key ingredient, **6GB** suits a small group, more players and mods want **12GB+**. - **A personal VPN or lightweight automation:** even the smallest **4GB** plan is ample, these barely touch RAM or CPU. - **Development, staging, or self-hosted apps (Nextcloud, media, tools):** **6GB** is a good all-rounder; scale with how much you pile on. - **A Windows desktop or Windows apps:** Windows itself likes more memory, so start around **8GB+**. See [Windows VPS](https://vpsdime.com/knowledgebase/presales/windows-vps). ### How do I know if I picked wrong? Once you're running, your control panel shows **usage graphs** for CPU, memory, disk, and traffic. If memory or CPU sits near the limit during normal use, size up. If everything's barely ticking over, you may be paying for more than you need and can size down (Premium excepted, it's upgrade-only). It's all self-service, so it's a quick change either way. ### You can always change later - **Upgrade or downgrade** the whole plan from your client area, live and instant on Linux VPS. (**Premium VPS is upgrade-only**: you can't move to a smaller plan later, so on Premium start with what you need and grow.) - Or **add just one resource** (extra storage, an extra IP, more bandwidth) without changing your base plan, so you can top up the exact thing you're short on. Start reasonable, watch the graphs, adjust when needed. That's the whole game. --- Questions before you order? You can [open a ticket](https://vpsdime.com/open-ticket/), and we typically reply within minutes. ### Related questions - "How much RAM do I need for a VPS?" - "What plan size should I choose?" - "How much CPU/storage/bandwidth do I need?" - "What size VPS for WordPress / a database / a game server / a VPN?" - "Can I change my plan size later?" - "How do I know if my VPS is too small?" - "Should I add resources or upgrade the whole plan?" --- ## How to order a VPS URL: https://vpsdime.com/knowledgebase/presales/how-to-order-a-vps Last reviewed: 2026-07-04 Summary: A step-by-step walkthrough of ordering your first VPS, from picking a plan through configuring it, creating your account, entering billing details, choosing how to pay, and completing the order. Most servers are ready within minutes. Ordering is quick: pick a plan, set it up how you like, create your account, and pay. Most servers are **provisioned within minutes**. Here's the whole thing, start to finish. ### 1. Pick a plan Head to the product you want, [Linux VPS](https://vpsdime.com/linux-vps), [Premium VPS](https://vpsdime.com/premium-vps), or [Windows VPS](https://vpsdime.com/windows-vps), and each plan lists its vCPU, RAM, NVMe storage, traffic, and price. Click **Order Now** on the one that fits. Not sure which to get? See [Choosing the right VPS](https://vpsdime.com/knowledgebase/presales/choosing-the-right-vps); you can always resize later, so a close fit is fine. ### 2. Configure your VPS Order Now takes you to the configuration page, where you set your server up before it's built: - **Hostname** (or **Label** on Windows) is optional, leave it blank and we'll pick one for you. It's the server's own name, not your website's address, see [What is a hostname?](https://vpsdime.com/knowledgebase/presales/what-is-a-hostname) - A temporary **root password** (or **Administrator password** on Windows) is generated and shown once, with a **Copy** button. Save it somewhere safe. - **Location:** choose the datacenter nearest your users. - **Operating system:** pick a Linux distribution (a current LTS like Ubuntu is a safe default), or a one-click **Application**, or, on Windows, your Windows Server version. On Premium VPS you can also install your own non-Windows OS from an ISO later. - **Optional extras:** depending on the product, you can add Nightly Backups, extra vCPU, extra storage, extra bandwidth, or additional IPs, now or any time later from your client area. - **SSH key (Linux and Premium):** under Optional Configuration you can select or paste an SSH key and choose your login mode. Using a key is the most secure way in; you can also just use the password. - **Billing cycle:** monthly, quarterly, semi-annually, or annually. When it looks right, click **Deploy Now**. A short review box confirms your choices (and reminds you to save the password), then you continue to checkout. ### 3. Create your account and enter billing details At checkout, tell us who you are, so we can set up your account and send your invoice: - **New customer:** enter your **name, email, and a password**, or sign up instantly with **Google** or **GitHub**. Then add your **billing address** and phone number. - **Already have an account?** Switch to **Existing client** and sign in, your details are already on file. ### 4. Choose how to pay Pick a payment method: **Credit/debit card, PayPal, Google Pay, Bitcoin, USDT, or Alipay**. Have a promo code? There's a box for it. Your order total and what renews are shown on the right, with any **VAT or sales tax** for your location added automatically (see [taxes](https://vpsdime.com/knowledgebase/billing/taxes)). For more on payments, see [payment methods](https://vpsdime.com/knowledgebase/billing/payment-methods). ### 5. Complete your order Click **Complete Order** and pay the invoice. Two checks stand between payment and your VPS, and both are usually invisible: orders are **screened automatically at checkout** (if yours gets flagged, you'll see an alert page, see [My order was flagged by fraud screening](https://vpsdime.com/knowledgebase/presales/order-flagged-as-fraud)), and every **paid order is reviewed by a person** before activation, a few minutes, though a **first order** can take a little longer and we may ask a quick question by ticket (see [My order is under review](https://vpsdime.com/knowledgebase/presales/order-under-review)). Once cleared, your VPS is **provisioned within minutes** and we email you the details. ### After you order You'll get your server's IP and login. Connect over **SSH** (Linux and Premium) or **Remote Desktop** (Windows), and manage everything, power, reinstall, resize, backups, from your client area. And if it's your first order with us, it's covered by our **[72-hour money-back guarantee](https://vpsdime.com/knowledgebase/billing/refunds)**, so you can buy with confidence. From then on, renewal invoices arrive 14 days before they're due, so there are no surprises, see [when invoices are due](https://vpsdime.com/knowledgebase/billing/billing-timeline), and billing bends to you, not the other way around: you can [prepay months ahead](https://vpsdime.com/knowledgebase/client-area/billing/pay-in-advance), [pick the day of the month you're billed](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-day), or [line several services up to renew together](https://vpsdime.com/knowledgebase/client-area/billing/sync-due-dates), all self-service. --- Questions before you order? You can [open a ticket](https://vpsdime.com/open-ticket/), and we typically reply within minutes. ### Related questions - "How do I order a VPS?" - "Do I need an account before ordering?" - "How do I pay, and what methods do you accept?" - "How long until my VPS is ready after I pay?" - "Why is my first order taking longer?" - "Can I sign up with Google or GitHub?" - "What happens after I complete my order?" --- ## My order is under review URL: https://vpsdime.com/knowledgebase/presales/order-under-review Last reviewed: 2026-07-04 Summary: Every paid order is reviewed by a person before the service is activated, usually a matter of minutes. First orders and orders on long-dormant accounts get a closer look, and we may open a ticket with a quick question; the client area shows an Action Required notice when a reply from you is what the review is waiting on. ### What this is Every **paid** order at VPSDime is reviewed by a person before the service is activated. This is a normal step that all orders go through, not a flag on yours, and it usually adds only **a few minutes** between payment and your VPS being provisioned. This is different from [an order flagged by fraud screening](https://vpsdime.com/knowledgebase/presales/order-flagged-as-fraud), which is an automated check at checkout with its own alert page, and from an invoice sitting in [Security Review](https://vpsdime.com/knowledgebase/billing/invoice-pending-after-paying), which is the card processor checking a payment. This page is about the human review of a paid order. ### When we look closer Most reviews are quick approvals. We take a closer look, and may have a question for you, when: - it's your **first order** with us, or - your account has been **dormant**: you were a customer in the past, had no active services for a long time, and a new order just came in. ### What you'll see while it runs Your client area shows the state of the order: - **"Order Processing"**: your payment is in and we're working on the order. Nothing is needed from you. - **"Action Required"**: we've opened a **support ticket with a question** that supports the review, and the order is waiting on your reply. The client area shows this warning until you've answered, so if you see it, the fastest path to your VPS is replying to that ticket. Replying quickly is genuinely the whole game here: once the review clears, provisioning takes minutes. ### Things worth knowing - **A long review is credited.** If clearing a review takes multiple days, we credit your account for the number of days it took. - **You can nudge us any time.** If your paid order has been sitting longer than you'd expect and there's no ticket asking you anything, [open a ticket](https://vpsdime.com/open-ticket/) and we'll look at it right away. - A couple of details that confirm the order is genuinely yours help us clear it faster. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address and order number on the account, - whether the client area shows Order Processing or Action Required, - anything that helps confirm the order is genuinely yours. ### Related questions - "Why is my paid order not active yet?" - "How long does the order review take?" - "What does Action Required on my order mean?" - "Why did you open a ticket asking about my order?" - "I'm a returning customer, why is my order being reviewed?" - "My order hasn't been set up yet, what's going on?" --- ## My order was flagged by fraud screening URL: https://vpsdime.com/knowledgebase/presales/order-flagged-as-fraud Last reviewed: 2026-07-05 Summary: Every order is screened automatically at checkout. A flagged order shows an "Automated Fraud Screening Alert" with the specific reason. The usual causes are ordering over a VPN or proxy, a billing country that doesn't match your IP's location, automated ordering tools, many orders at once, or a region we can't serve. Most causes you can fix yourself and order again; false positives are reviewed by ticket. ### What this is Every order placed with us is screened **automatically at checkout**, by industry anti-fraud services and our own in-house checks. When the screening flags an order, you see an **"Automated Fraud Screening Alert"** page with the specific reason, and the order is held with a fraud status instead of being processed. Automated screening protects our network and our customers, but no screening is perfect: **false positives happen**, and a flagged order is not an accusation. This page covers the usual causes, what you can fix yourself, and how to reach us when the flag is wrong. This is **not** the same as the [review every paid order goes through](https://vpsdime.com/knowledgebase/presales/order-under-review) before activation, that's a human step that happens to all orders. It's also not the same as an invoice sitting in [Security Review](https://vpsdime.com/knowledgebase/billing/invoice-pending-after-paying), which is the card processor checking a payment. ### The usual causes - **You ordered over a VPN, proxy, or Tor.** Anonymized connections are the single most common trigger. Disconnect the VPN or proxy, then place the order again from your normal connection. - **Your billing country doesn't match your IP's location.** The screening compares the country of your billing address with the country your connection comes from. If you're on a VPN, disconnect it. If your account details are incomplete or out of date, update them fully on the [Account details](https://vpsdime.com/knowledgebase/client-area/account/account-details) page (https://vpsdime.com/accountdetails), address, city, state, and country, as if we were shipping you a physical product, then order again. If you're **travelling** and that's genuinely why your IP is in a different country from your contact details, please don't keep re-ordering, [open a ticket](https://vpsdime.com/open-ticket/) and contact us so we can verify you and clear the order. - **The order was placed with automated tools.** Scripted or automated checkouts get flagged. Place the order normally in a browser. - **A high number of orders at once.** Many orders in quick succession looks like abuse to the screening. If you genuinely need a large deployment, [contact us](https://vpsdime.com/open-ticket/) first and we'll make sure it goes smoothly. - **You're in a region we cannot serve.** In this case the screen will say the order requires manual verification or can't be accepted, and re-ordering won't change the outcome, see below. ### What happens to a flagged order Our staff **checks flagged orders**. If we can verify the order with the data available to us, we **contact you** ourselves, usually by ticket or email, so watch your inbox. While the order is in this state, your client area shows a **Fraud Check** notice for it, and if we've opened a verification ticket, the notice asks you to reply to it, that reply is what moves things forward. If you believe the flag is a **false positive**, don't wait for us: [open a ticket](https://vpsdime.com/open-ticket/) and ask us to review the order. A person looks at every such request. ### What to do, in order 1. **Read the reason on the alert page.** It names the specific trigger. 2. **If it's a fixable cause**, VPN/proxy or the country mismatch, fix it (disconnect, or complete your [account details](https://vpsdime.com/knowledgebase/client-area/account/account-details)) and **place the order again**. 3. **If your reason isn't one of the fixable ones**, place **one** more order to rule out a one-off false positive. 4. **Flagged again? Stop and talk to us.** [Open a ticket](https://vpsdime.com/open-ticket/) and ask for a manual review, a person looks at every such request. ### Don't keep re-ordering Placing the same order **over and over** after it's been flagged works against you: an account that collects several flagged orders in a row (three or four is enough) is **closed automatically** by our systems. See [Account closed](https://vpsdime.com/knowledgebase/client-area/account/account-closed) for what that means. Creating **another account** to get around it doesn't work either, the order screening recognizes repeat orders across accounts, and it puts the new account on the same path. The pattern that works is the one above: fix a fixable cause, retry **once** otherwise, and then bring a human into it. A genuine order has nothing to lose from a manual review. ### Some decisions are final A manual review is a real second look, and many false positives are reversed there, but it's honest to say the review is not an appeals process that always ends in approval: **some refusals are final**. When that's the case, we also **can't disclose the specific reasons** behind the decision, not to be evasive, but because explaining exactly what the screening keys on would hand a working evasion manual to the people it exists to stop. A final refusal isn't a judgment of you personally; it means the order, as we're able to verify it, sits outside what we can accept, and re-ordering or opening further tickets won't change that outcome. In that situation, the practical path is simply a different provider, with no hard feelings on our side. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the email address you ordered with, and the order number if you have one, - the exact reason shown on the screening alert, - whether you were using a VPN or proxy at the time, and your billing country. ### Related questions - "My order was flagged as fraud, what do I do?" - "Why was my order blocked at checkout?" - "I ordered through a VPN and my order was rejected." - "My billing country doesn't match my IP, why does that matter?" - "I'm travelling and my IP is in a different country than my address, what do I do?" - "The fraud screening flagged me by mistake, how do I get reviewed?" - "Can I place many orders at once?" - "Will my account be closed if my orders keep getting flagged?" - "Can I just make a new account after being flagged?" - "Where do I update my address before ordering again?" - "My order was refused after review, can it be overturned?" - "Why won't you tell me the exact reason my order was declined?" --- ## Pre-sales FAQ URL: https://vpsdime.com/knowledgebase/presales/pre-sales-faq Last reviewed: 2026-07-02 Summary: Answers to the questions people ask before ordering a VPS at VPSDime, pricing and value, billing, plans and specs, virtualization and operating systems, the control panel, network and IPs, email, performance and reliability, backups, security, support, privacy and legal, ordering, and how we compare. If your question isn't here, our team typically replies within minutes. The questions people ask before ordering, answered. Still have a question? [Open a ticket](https://vpsdime.com/open-ticket/) and we typically reply within minutes. ### Price and value **How much does it cost? What's the cheapest plan?** Our entry plan is the **4 GB Linux VPS at $5/month**. See the full range on the [plans](https://vpsdime.com/linux-vps) pages. **Why are you so cheap? Is it too good to be true?** There's no catch. We **own our hardware, compute nodes, IP space, network, and virtualization software**, so we don't pay anyone else's margin and we run our nodes efficiently. Owning the whole stack keeps our costs low, and that's reflected in the price. **Are there hidden fees or a setup fee?** None. No setup fee, no hidden charges. The price you see is the price you pay. **What's included in the price, and what's an add-on?** Every plan includes a full VPS: root access, the OS, NVMe storage, a dedicated IP, and a monthly traffic allowance. **Premium VPS also includes free Nightly Backups.** On Linux and Windows VPS, backups are an optional add-on. Extra vCPU, storage, bandwidth, and IPs can be added any time if you need them. **Do prices renew at the same rate, or is it a promo that jumps later?** The **same rate**, always. There's no teaser price that jumps at renewal. In fact, we've **never raised our prices since we started in 2013**. **Do you offer discounts, coupons, or Black Friday deals?** We don't run promos. Rather than inflating prices and then "discounting" them, we keep them at the **same low rate all year round**, so the price you see is the best we offer whenever you order. **Do you offer volume or bulk discounts?** Our prices are already set as low as we can make them, so there isn't a separate bulk rate to negotiate. You can order as many servers as you need from one account, and for a large or unusual deployment, [contact us](https://vpsdime.com/open-ticket/) so we can make sure it goes smoothly. **Do you offer student, nonprofit, or open-source discounts?** We don't discount, but we do **sponsor nonprofits and open-source projects** with free service. See our [Free VPS](https://vpsdime.com/free-vps) page to apply. **What currency are prices in? Can I pay in EUR/GBP?** Prices are in **US dollars (USD)**. If your card or account is in another currency, your provider converts it automatically at checkout. ### Billing and payments **What payment methods do you accept?** Major credit and debit cards, PayPal, Google Pay, Bitcoin, USDT, and Alipay, including prepaid and virtual cards. Full details in [payment methods](https://vpsdime.com/knowledgebase/billing/payment-methods). **Do you accept Bitcoin or crypto?** Yes, both Bitcoin and USDT (on the TRC20, BEP20, or ERC20 network), alongside prepaid and virtual cards if you'd rather keep your payment private. One practical tip: some wallets and exchanges won't send small amounts (a $10+ minimum is common), so for a $5 invoice, [add funds](https://vpsdime.com/knowledgebase/client-area/billing/add-funds) as account credit in one larger payment and invoices are paid from it automatically. The full guide is [Paying with cryptocurrency](https://vpsdime.com/knowledgebase/billing/crypto-payments). **Can I pay monthly, quarterly, or annually?** Choose monthly, quarterly, semi-annually, or annually. Longer cycles are priced proportionally. There's no annual "discount" because we don't inflate the monthly price to begin with. You can [change your cycle](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-cycle) any time. **Can I set up auto-pay, or cancel auto-renew?** Yes. [Save a card or set up a PayPal billing agreement](https://vpsdime.com/knowledgebase/client-area/billing/manage-subscriptions) to renew automatically, and switch it off whenever you like. **Do you charge VAT / GST / sales tax? Can I add my VAT number?** We add VAT and other sales taxes only where they apply, calculated automatically at the payment page. Add your **VAT or GST number** on [Account Details](https://vpsdime.com/knowledgebase/client-area/account/account-details) and it appears on your invoices. See [taxes](https://vpsdime.com/knowledgebase/billing/taxes). **Can I add account credit / pay in advance?** Yes, both. Top up a credit balance from the [Add Funds](https://vpsdime.com/knowledgebase/client-area/billing/add-funds) page and let invoices draw from it automatically, or [prepay a specific service](https://vpsdime.com/knowledgebase/client-area/billing/pay-in-advance) for 1 to 24 months so its renewal date moves forward. **Can I choose my billing day, or have all my services renew together on one invoice?** Yes, both are self-service. [Change your billing day](https://vpsdime.com/knowledgebase/client-area/billing/change-billing-day) moves a service's renewal to the day of the month you want (the 1st, or just after payday), and [Sync Due Dates](https://vpsdime.com/knowledgebase/client-area/billing/sync-due-dates) lines several services up on one renewal date, after which they arrive as a single combined renewal invoice. **Can I get a proper invoice or receipt for accounting?** Yes. Download **PDF invoices** from your client area any time, with your VAT/GST number on them if you've added one. See [invoices](https://vpsdime.com/knowledgebase/client-area/billing/invoices). **What happens if I pay late? Is there a grace period?** Yes, there's a grace window. We send reminders around the due date, and a renewal that goes unpaid is first **suspended** (your data is kept), then **terminated** (data deleted) only after further notice. The exact days are in [when invoices are due](https://vpsdime.com/knowledgebase/billing/billing-timeline). **Am I locked into a contract?** No. There's no contract and no minimum term. [Cancel](https://vpsdime.com/knowledgebase/client-area/services/cancellation) whenever you want. ### Trials, guarantee, and refunds **Is there a free trial or a free tier?** We don't run a free trial, but your first order is backed by our 72-hour money-back guarantee. You can also check latency and download speed from your location beforehand with our [Looking Glass](https://vpsdime.com/looking-glass). **Do you offer a money-back guarantee?** Yes. Your **first order** is covered by a **72-hour money-back guarantee** (it applies to your first service with us, not to every order). See [Refunds and money-back guarantee](https://vpsdime.com/knowledgebase/billing/refunds). **Can I get a prorated refund if I cancel mid-cycle?** No. Time you've already paid for on a term isn't refunded, so cancel at the end of your cycle if you want the full period. ### Plans, resources, and specs **How much RAM, CPU, disk, and bandwidth do I get?** It depends on the plan. Our entry Linux VPS starts at **4 GB RAM for $5/month**, and plans scale up from there in RAM, vCPU, NVMe storage, and monthly traffic. Each plan lists its exact resources on the [plans](https://vpsdime.com/linux-vps) pages, and you can top up vCPU, storage, bandwidth, or IPs individually later. **What's the difference between your product lines?** In short: Linux VPS for the best value, Premium VPS for fully dedicated resources, and Windows VPS for Windows. See [Linux VPS vs Premium VPS](https://vpsdime.com/knowledgebase/presales/linux-vps-vs-premium-vps), [Windows VPS](https://vpsdime.com/knowledgebase/presales/windows-vps), and [Choosing the right VPS](https://vpsdime.com/knowledgebase/presales/choosing-the-right-vps). **What is a Storage VPS?** A Storage VPS trades speed for capacity: it uses large **HDDs in RAID10** instead of NVMe, so you get a lot of affordable space. It suits backups, archives, and media libraries where roominess matters more than raw performance. **Is the CPU dedicated or shared? What CPU do you use?** It depends on the product. Premium VPS gives you **fully dedicated** CPU, while Linux and Windows VPS share the node's CPU efficiently, with monitoring that keeps headroom free. Each plan lists its allocation. Under the hood we run **Intel Xeon Gold and Platinum** CPUs on enterprise hardware. **Can I actually use 100% of my RAM 24/7?** Of course, it's fully dedicated to you. **Is storage SSD or NVMe? RAID?** Every plan runs on **write-intensive, high-DWPD NVMe SSDs in RAID10** (a Storage VPS uses HDDs in RAID10 for capacity instead). RAID10 means your data is mirrored, so a single drive failure doesn't take you down. **Do you oversell / overcommit? Will noisy neighbours slow me down?** No, we don't oversell. We keep **headroom on every node** for bursts and monitor our infrastructure closely, so another customer's VPS won't slow yours down. If you want a guarantee in writing, Premium VPS dedicates the resources to you alone. **Can I upgrade or downgrade later, and is there downtime?** Yes, from your client area. On **Linux VPS** it's live and instant with no downtime and the same IP, up or down. On Premium and Windows an upgrade applies with a quick reboot. Note that **Premium VPS is upgrade-only**: it can't be moved to a smaller plan later, so start with the size you need and grow from there. See [Upgrading or downgrading](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade). **Can I add just RAM, disk, or IPs?** You can add **vCPU, storage, and IP addresses** individually from the [Extra Features](https://vpsdime.com/knowledgebase/client-area/services/extra-features) tab. RAM is tied to the plan, so for more of it you move up a plan (live and instant on Linux VPS). **Can I switch product lines (for example Linux to Premium)?** There's no automatic switch between product lines. You'd order the new VPS and move your data across yourself, the same as any migration, the full walk-through is [Migrating a VPS to a new server](https://vpsdime.com/knowledgebase/getting-started/migrating-a-vps). Between **Linux and Windows** there's nothing to migrate in that sense at all, they're different operating systems: order the new VPS, set your applications up on it, copy the data files you need, and cancel the old one. ### Virtualization and operating systems **What virtualization do you use?** Premium VPS runs on **KVM** and Windows VPS on **Hyper-V**, both full hardware virtualization. Linux VPS runs on our own optimized virtualization platform. **Do you offer GPU servers or nested virtualization?** No. We don't offer GPU VPS, and nested virtualization (running a hypervisor inside your VPS) isn't supported. **Can I run Docker?** Yes. You get a clean OS with full root, so Docker and Podman run fine on every product line, install it yourself in seconds. Kubernetes is its own story: **k3s** runs on Linux VPS, while stock full Kubernetes (kubeadm) wants **Premium VPS**. See [Kubernetes on VPSDime services](https://vpsdime.com/knowledgebase/technical-questions/kubernetes-on-vps). **Which operating systems can I choose?** On **Linux VPS**, a wide range of distributions, Ubuntu, Debian, AlmaLinux, Rocky, Arch, and more, plus one-click Applications. On **Premium VPS**, the same distributions or **virtually any non-Windows OS** you like, including BSD or a custom image via ISO. On **Windows VPS**, Windows Server 2025, 2022, or 2019. **Can I install my own custom ISO / any OS?** Yes, on **Premium VPS**, for any **non-Windows** OS. Send us the ISO in a ticket and we'll attach it, then you install it from the console. If it's Windows you're after, that's its own product with the license included, see [Windows VPS](https://vpsdime.com/knowledgebase/presales/windows-vps). (Linux and Windows VPS use our ready-made images rather than custom ISOs.) **Do you offer one-click apps?** Yes, including **Coolify, Traccar, Immich, and Code Server**, with more added over time. Running an open-source project you'd like on the list? Ask us and we'll consider adding it. **Can I reinstall the OS myself, any time?** Yes. [Reinstall](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os) to a fresh OS or one-click app whenever you want, right from the panel. It wipes the VPS, so back up anything you need first. **Do you offer Windows? Which editions, and is the license included?** Yes, on Windows VPS: **Windows Server 2025, 2022, or 2019 (Datacenter edition)**, with the **license included** in the plan price. You connect over RDP. See [Windows VPS](https://vpsdime.com/knowledgebase/presales/windows-vps). ### Control panel and management **Do you provide a control panel?** Yes, a **bespoke control panel built into your client area**. Power on and off, reinstall, resize, open a console, reset your password, and watch resource graphs, all from one place. See [Managing your VPS](https://vpsdime.com/knowledgebase/client-area/services/managing-your-vps). **Is there out-of-band / console access if I lock myself out?** Yes. A browser-based **console** connects straight to your VPS's screen, no SSH or RDP needed, so you can always get back in, even if networking or the firewall is misconfigured. **Does it include a web hosting panel (cPanel/Plesk)? Is a license included?** No. You get a clean OS and full freedom to install any panel you like. We don't bundle a cPanel or Plesk license. **Do you sell cPanel, Plesk, DirectAdmin, or CloudLinux licenses?** No, we don't resell any commercial control-panel or OS licenses, so we can't add one to your invoice. If you want one, buy it directly from the vendor or a license reseller and install it on your VPS yourself. Plenty of customers skip the license cost entirely with a [free, open-source panel](https://vpsdime.com/knowledgebase/getting-started/open-source-control-panels) instead, HestiaCP, CloudPanel, Coolify, and others cover most needs. **Is there an API or Terraform provider?** Yes, we have an API for automating your services (deploy, power, resize, and so on). [Contact us](https://vpsdime.com/open-ticket/) to request access. We don't currently publish a dedicated Terraform provider. ### Location and network **Where are your datacenters, and can I choose?** Yes, you pick your location when you order. We're in the **US (Dallas, Seattle, Los Angeles, New Jersey)** and **Europe (London, Amsterdam)**. The order form shows the locations currently in stock; an out-of-stock location returns as soon as we add capacity. **Which location is best for me?** The one closest to your users gives the lowest latency. Use our [Looking Glass](https://vpsdime.com/looking-glass) to compare ping and download speed from each location before you order. **Can I move my VPS to another location later?** Yes. You order the move from your VPS's manage page for a **$4 fee**; a ticket opens with our team after payment and we perform the migration. The fee is for moving your data with the VPS, if you don't need the data (you ordered the wrong location and haven't used it yet, or you'd reinstall anyway), contact us and we'll **re-provision it in the location you want for free**. The walk-through is [Moving your VPS to another location](https://vpsdime.com/knowledgebase/client-area/services/migrate-location). Your IP changes with the location, so plan to update your DNS afterward. **Do you support floating or reserved IPs? Can I keep my IP if I move locations?** No, we don't offer floating IPs. IP addresses belong to a datacenter, so if your VPS [moves from one location to another](https://vpsdime.com/knowledgebase/client-area/services/migrate-location), **your IP changes**, there's no way to carry it along. Plan around the new-IP checklist (DNS, SPF, rDNS) instead. Within the same location your IP stays with your VPS for the life of the service. **Is bandwidth metered or unmetered? What's the port speed?** Each plan includes a generous **monthly traffic allowance** (metered), delivered over a fast **10 Gbps** uplink. Unused traffic doesn't roll over. **What happens if I exceed my bandwidth?** We email you at 75% and 100% of your allowance. If you don't [add traffic](https://vpsdime.com/knowledgebase/client-area/services/extra-features) or upgrade within 24 hours of hitting 100%, the VPS is suspended until you do, or until your allowance resets on the 1st of the next month. **How many IPv4 addresses do I get, and can I buy more?** One dedicated IPv4 is included. Extra IPv4s are **$2/month each** (with justification), added from [Extra Features](https://vpsdime.com/knowledgebase/client-area/services/extra-features). **Do you offer IPv6?** Yes, IPv6 is available on our network. You can request IPv6 addresses by opening a ticket. **Can I set reverse DNS (rDNS/PTR)?** Yes. Edit reverse DNS for your IPs yourself from the [Network](https://vpsdime.com/knowledgebase/client-area/services/network) tab, which is handy for mail deliverability. **Do you offer private networking or VLANs between my VPSes?** We don't provide a built-in private VLAN. Instead we recommend running your own **encrypted overlay network** (Tailscale, or self-hosted Headscale, work well) between your servers. It's more flexible, more secure, and works across our different locations too. **How good is your network?** It's built for low latency and reliability. We run on **Tier 1 transit providers** and peer directly with major networks, so traffic takes short, well-routed paths. See it for yourself with our [Looking Glass](https://vpsdime.com/looking-glass). ### Email **Can I run a mail server or send email from my VPS?** Yes. **Outbound port 25 is open**, so you can run a mail server and send **low-volume transactional and monitoring email**. **Mass mailing, marketing, and newsletters are not allowed**, so for any real sending volume use a dedicated service such as Amazon SES or Mailgun. **Is your IP space clean / not on blocklists?** Yes. We work hard to keep our network and IP ranges off blocklists by holding customers to high standards, which is exactly why bulk sending isn't permitted. You can also set [reverse DNS](https://vpsdime.com/knowledgebase/client-area/services/network) on your IPs to help deliverability. ### Performance and reliability **What performance can I expect?** Strong across the board. **Linux VPS** runs on NVMe storage and our optimized platform for fast, responsive performance. **Premium VPS** goes further, with fully dedicated resources that hold performance steady even under sustained load. **What's your uptime SLA, and what if you miss it?** We back a **99.9% network uptime SLA** and a **99.99% power uptime SLA**. If we ever fall short, [open a ticket](https://vpsdime.com/open-ticket/) and we'll apply the credit you're owed. **How redundant is your infrastructure?** Very. **Dual power supplies on separate A and B feeds, dual NICs into dual switches, into dual edge routers, into dual fiber paths**, plus RAID10 on every disk. The point is that no single component failing takes your VPS offline. **Have you had major outages?** We engineer against them: redundant power, network, and storage are built to ride out hardware failures without taking your VPS down. When maintenance is planned or an incident happens, we post it to our [service status](https://vpsdime.com/service-status) page, which you can check any time. ### Provisioning and access **How fast is deployment?** Usually **within minutes** of payment. Because we manually verify every order to keep our network clean, a **first** order may take around **15 minutes** before it provisions. **Do I get full root / Administrator access?** Yes, always. Root on Linux, Administrator on Windows. It's your server. **How do I connect?** Over **SSH** (Linux and Premium) or **Remote Desktop** (Windows), and there's always the browser **console** as a fallback if you're locked out. **Can I reboot, rebuild, or reinstall myself?** Yes, all self-service from the panel, any time. ### Backups and data **Do you back up my VPS?** **Premium VPS** includes **free Nightly Backups**. On Linux and Windows VPS you can add **Nightly Backups** whenever you want. See [Nightly Backups](https://vpsdime.com/knowledgebase/client-area/nightly-backups/nightly-backups-overview). **Can I take and restore backups myself?** Yes. Restore your **whole VPS or just individual files** yourself from the client area. Backups are kept for three days. **Are backups off-site? Can I download them?** Yes. Backups are stored **off-site**, away from your VPS's node, and you can **download a full disk image** to keep your own copy or move it elsewhere. See [download a full disk image](https://vpsdime.com/knowledgebase/client-area/nightly-backups/download-full-disk-image). **What happens to my data if I cancel or you terminate the service?** It's deleted once the service ends, so **back up anything you want to keep first**. **Is my data encrypted? Do you look at it?** You can **encrypt your filesystem on Premium VPS**, or use application-level encryption on Linux VPS. We **do not look at your data** in the normal course of business. ### Security and DDoS **Do you provide DDoS protection?** Our network has some mitigation capacity built in, and during a large attack we **null-route** the target IP to protect everyone else on the node. If you expect to be a frequent target, we recommend a dedicated third-party mitigation service, Cloudflare works well for websites, and [our Cloudflare guide](https://vpsdime.com/knowledgebase/getting-started/cloudflare-best-practices) covers setting it up properly. **Do you provide a firewall?** Yes. Linux and Storage VPS include a **managed, network-level firewall** that blocks the most-attacked ports by default, and you're free to run your own firewall inside the VPS as well. See [the VPS firewall](https://vpsdime.com/knowledgebase/client-area/services/firewall). **Is my account protected with 2FA?** Yes, and not optionally: [two-factor authentication](https://vpsdime.com/knowledgebase/client-area/account/two-factor-overview) is **on for every account** and can't be turned off, with email login codes by default and an authenticator-app upgrade if you prefer. **What happens if my VPS gets compromised?** If we spot a compromised VPS (attacking others, sending spam, and so on), we quarantine it to protect the network, then let you either clean it up or back up what you need and reinstall. Since the service is self-managed, the cleanup itself is yours to do, but we'll point you in the right direction. ### Support **Is this managed or unmanaged?** Our service is **self-managed**: the server is yours to run, and we look after the platform underneath it (hardware, network, and virtualization). **What support is included?** A **24/7 staffed** team that typically replies **within minutes**, holidays included. We prioritise anything affecting access to your VPS, and help with other requests on a best-effort basis. **What channels do you offer?** Support is by **ticket**, opened from your account (pre-sales questions can be asked without one). See [Getting help](https://vpsdime.com/knowledgebase/client-area/support/getting-help). **Can you migrate my server, or install and manage software for me?** No, we don't offer full management or done-for-you migrations, since the service is self-managed. For hands-on work, hiring a freelance sysadmin is inexpensive and gets it done properly. **I'm not very technical, can I still use a VPS?** Yes. Modern Linux is well documented, our one-click apps handle much of the setup, and you can hire help for the technical parts if you prefer. ### Migration, scaling, and upgrades **Can I migrate my current server to you?** Yes. You move your data and sites across yourself. We don't perform the migration for you, but it's a common task and a freelance sysadmin can handle it cheaply if you'd rather not. **Can I upgrade without reinstalling or losing data?** Yes. Upgrades keep your data intact, and on **Linux VPS** they're live with no downtime and the same IP. **Can I clone a server to spin up more identical ones?** Yes. We can clone an existing VPS onto a new one for you, free on current distributions, $25 on older ones where the process is manual. The details and how to request it are in [Cloning a VPS into a new VPS](https://vpsdime.com/knowledgebase/client-area/deploy/cloning-a-vps). **Can I scale to many VPSes / a fleet?** Yes. Order as many as you need, all managed from one account. ### Acceptable use **What can I run, and what isn't allowed?** We keep our network fast and our IP space clean for everyone, so a short list of high-abuse activities is off-limits. Nothing here is unusual for a low-cost VPS host. Perfectly fine: websites and web apps, databases, dev and test environments, **game servers**, a **personal VPN for your own use**, Docker and self-hosted apps, **AI inference workloads**, **cryptocurrency staking and validator nodes**, **lawful streaming**, and using every bit of the resources your plan includes. Not allowed: - **Torrents and P2P** (clients, trackers, or seedboxes). - **Tor** relay, exit, entry, or bridge nodes. - **Public VPN or proxy services** run for other people (a private VPN just for yourself is fine). - **Cryptocurrency mining** (staking and validator nodes are fine). - **Bulk or marketing email** (see the Email section above). - **Adult content.** - **Gambling**, casinos, betting, or lotteries. - **Sales of drugs or weapons.** - **Hate speech, terrorism, or content inciting violence.** - **Phishing, malware, or botnet infrastructure.** - **Aggressive web scraping** (denial-of-service-level load, or ignoring robots.txt). - **Copyright infringement** or any unlawful use, including nulled or cracked software. The full policy is in our [Acceptable Use Policy](https://vpsdime.com/aup); you agree to it and our [Terms of Service](https://vpsdime.com/tos) when you order. ### Privacy, legal, and jurisdiction **Do you require ID / KYC / phone verification to sign up?** We don't require ID or KYC, though we do manually verify every order to keep the network clean. **Can I sign up anonymously, with minimal info, a VPN, or a masked email?** No. We need accurate contact and billing details, and orders placed to hide who you are will be declined. **What information do you collect and keep?** Your contact and billing details and the IP addresses you connect from, kept until you ask us to delete your account. See our privacy terms for specifics. **Where is the company based / what law applies?** We're based in the **United Arab Emirates**, so UAE law applies, along with the law of the country your VPS is located in. **Are you GDPR compliant? Can I have my data deleted?** Yes, we comply with GDPR and other data-protection laws for your account data, where we are the controller. Just ask and we'll delete your information. One nuance for businesses: for the content on your VPS we act as raw infrastructure, we don't act as a data processor for your workloads and don't sign DPAs, SCCs, or BAAs. **How do you handle copyright / DMCA?** We respect copyright. Hosting content you don't hold the rights to isn't allowed, and we act on valid infringement complaints. **How is abuse handled?** Report it to `abuse [@] nodisto.com`, and our team acts on reports promptly. **Can I read your TOS, AUP, and SLA before ordering?** Yes. You agree to them when you order: [Terms of Service](https://vpsdime.com/tos) and [Acceptable Use Policy](https://vpsdime.com/aup). Our uptime commitments are set out in those terms. ### Ordering and cancellation **What information do you need to order?** Just your contact and billing details (name, email, and a billing address) plus a payment method. You can create your account during checkout, or sign in with Google or GitHub. See [How to order a VPS](https://vpsdime.com/knowledgebase/presales/how-to-order-a-vps). **Why is my paid order not active yet?** Every paid order gets a quick **human review** before activation, usually minutes. First orders and long-dormant accounts get a closer look, and we may open a ticket with a question, reply to it and you're through. See [My order is under review](https://vpsdime.com/knowledgebase/presales/order-under-review). **Why was my order flagged by fraud screening?** Orders are screened automatically at checkout. The usual triggers are ordering over a **VPN or proxy**, a **billing country that doesn't match your IP's location**, automated ordering tools, or many orders at once. Most are fixable, disconnect the VPN or complete your address, then order again, and false positives are reviewed if you [contact us](https://vpsdime.com/open-ticket/). See [My order was flagged by fraud screening](https://vpsdime.com/knowledgebase/presales/order-flagged-as-fraud). **How do I cancel? Is it self-service?** Yes. Submit a **cancellation request** from your client area and choose **Immediate** or **end of billing period**. See [Cancelling a VPS](https://vpsdime.com/knowledgebase/client-area/services/cancellation). **Will I be charged again after I cancel?** No. Once you submit a cancellation request, any open invoice for that service is cancelled and we won't charge you again, even if auto-renew was on. ### Company and trust **How long have you been in business?** Since **2013**, providing VPS hosting to individuals and businesses for over a decade. **Where can I read reviews?** See our [customer reviews](https://vpsdime.com/customer-reviews). **How do you compare to the big cloud providers?** We give you the **highest resources per dollar**, and we're a leaner, independent company: **self-funded, no investors, and we own our network, IP space, hardware, and software**. We reply in minutes, we treat you as a person rather than a ticket number, and we've **never raised our prices**, while the big names have raised theirs more than once. **Are you a reseller, or do you own your hardware?** We own it all: our network, IP space, hardware, and software. Nothing here is rented from someone else and marked up. ### Affiliate and reselling **Can I host my clients' projects on my VPS?** Yes, hosting your clients' websites and apps on your VPS is perfectly fine. If you'd like to earn by referring customers to us instead, see the [affiliate program](https://vpsdime.com/knowledgebase/client-area/affiliates/affiliate-program). **Do you have an affiliate program?** Yes. You earn a **recurring 10%** on customers you refer, for as long as they stay subscribed. See the [affiliate program](https://vpsdime.com/knowledgebase/client-area/affiliates/affiliate-program). **Do you offer white-label?** No, we don't offer white-label or unbranded reselling. If you'd like to earn from customers you send our way, use the [affiliate program](https://vpsdime.com/knowledgebase/client-area/affiliates/affiliate-program) instead. ### Related questions - "How much is the cheapest VPS, and are there hidden fees?" - "Why is your VPS so cheap, is it legit?" - "Do you oversell, and can I use 100% of my resources?" - "What virtualization do you use, and can I run any OS?" - "Can I run a mail server / send email?" - "Are game servers, torrents, Tor, or a VPN allowed?" - "What's your uptime, redundancy, and DDoS protection?" - "Is it managed or self-managed, and how fast is support?" - "Do you require ID, and where are you based?" - "How do you compare to DigitalOcean, Linode, or Vultr?" - "Can I resell, and do you have an affiliate program?" --- ## Support coverage URL: https://vpsdime.com/knowledgebase/support-coverage Last reviewed: 2026-07-02 Summary: What VPSDime support does and doesn't cover on a self-managed VPS, how software help works and when to hire a sysadmin, and what response times to expect from the 24/7 team. What our support covers, and what to expect from it. For the mechanics of actually opening and tracking a ticket, see [Getting help](https://vpsdime.com/knowledgebase/client-area/support/getting-help) in your client area. - [What support covers](https://vpsdime.com/knowledgebase/support-coverage/what-support-covers). The self-managed model: what's always on us, what's yours with our help, and what isn't offered. - [Software and server management](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management). "Can you install or fix my software?", what we do instead, and when to hire a sysadmin. - [Response times and priorities](https://vpsdime.com/knowledgebase/support-coverage/response-times-and-priorities). The 24/7 team, typical reply times, and what priority really does. --- Still need a person? You can [open a support ticket](https://vpsdime.com/open-ticket/) any time. --- ## What support covers URL: https://vpsdime.com/knowledgebase/support-coverage/what-support-covers Last reviewed: 2026-07-02 Summary: VPSDime services are self-managed. We look after everything underneath your VPS (hardware, network, virtualization, and the client-area platform) and help with your own software on a best-effort basis, but running the server is yours. ### What this is Our services are **self-managed**: the server is yours to run, and we look after everything underneath it. This explains where the line sits in practice, what's always on us, what's yours with our help, and what isn't offered. ### Always on us Anything about the platform your VPS runs on is our job, and we fix it, no "best effort" about it: - The VPS not starting, or the node it lives on having trouble - Network problems on our side (connectivity, routing, packet loss) - Performance issues caused by our infrastructure - Client-area features not working (console, backups, reinstall, graphs, and so on) If you're seeing any of these, [open a ticket](https://vpsdime.com/open-ticket/). If your VPS is unreachable, the [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) page can often fix the cause on the spot before a ticket is even needed. ### Yours, with our help The software you run on the VPS, your web server, database, sites, apps, and their configuration, is your responsibility. But you're not left in the dark: - If the fix is quick and obvious, we'll often just sort it or tell you exactly what to do. - If it's more involved, we'll point you in the right direction, and we'll keep answering your questions. Help with your own software is **best-effort**, a courtesy on top of the service rather than part of it. In practice our team helps with this kind of thing every day. And a privacy note: **we don't access your VPS uninvited.** We only look inside it when you ask us to check something, so your data stays yours. ### Not offered We don't do software installation, done-for-you migrations, or ongoing server administration. If you'd rather hand the server work to someone, see [Software and server management](https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management) for what we suggest instead. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what's wrong, with the exact error if there is one, - whether it looks like a platform problem or something in your own stack. ### Related questions - "What does self-managed or unmanaged mean?" - "Is my VPS managed?" - "What does your support cover?" - "Can you fix an issue on my server for me?" - "Whose responsibility is the software on my VPS?" - "Will you log into my server or look at my data when helping me?" --- ## Software and server management URL: https://vpsdime.com/knowledgebase/support-coverage/software-and-server-management Last reviewed: 2026-07-02 Summary: VPSDime doesn't install, migrate, or manage software for you, the service is self-managed. What we offer instead (guidance, one-click Applications, self-service reinstall), and when hiring a freelance sysadmin makes sense. ### What this is The honest answer to "can you install / configure / migrate / manage ____ for me?", and what your options are instead. ### What we don't do The service is [self-managed](https://vpsdime.com/knowledgebase/support-coverage/what-support-covers), so we don't offer: - **Software installation**, setting up your web server, control panel, app, or stack for you - **Done-for-you migrations**, moving your sites and data from another host - **Ongoing server administration**, maintenance, updates, or monitoring of your software This is part of how the pricing works: you get generous resources at a low price, and the server work is yours. ### What we offer instead - **Direction.** Ask, and we'll point you at the right approach or tutorial, and answer questions along the way. See [what support covers](https://vpsdime.com/knowledgebase/support-coverage/what-support-covers). - **[One-click Applications](https://vpsdime.com/knowledgebase/getting-started/one-click-applications).** Common stacks deploy ready-made from the panel (Coolify, Immich, Traccar, Code Server, and more), which covers a lot of "can you install X" cases with zero setup. - **Self-service reinstall.** A clean OS or application is always one [reinstall](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os) away if you want to start over. ### Doing it yourself Most server tasks are a well-documented tutorial away, modern Linux distributions are extensively documented, and running your own server is very learnable. Start with a current LTS release, follow a reputable guide, and ask us if you get stuck on something specific. **AI chatbots are a genuinely good server helper.** ChatGPT, Claude, Gemini, and the like are very capable at exactly this kind of work: paste the exact error message, or describe what you want to set up, and they'll walk you through it step by step and patiently answer every follow-up. It's like having a sysadmin on call for free. Just sanity-check any destructive command (anything that deletes, formats, or overwrites) before you run it. A step further, **AI agent tools** (Claude Code and the like) run on your own machine and can operate the server over SSH with you approving each step, they don't just tell you the commands, they run them and read the results. Powerful for multi-step work like migrations or debugging, with the same rule applied more strictly: review everything before approving it, especially anything that deletes or overwrites, and keep [backups](https://vpsdime.com/knowledgebase/getting-started/backing-up-your-vps) current before letting any tool loose on a server that matters. The full setup and the safety rules are in [Using Claude Code on your VPS, safely](https://vpsdime.com/knowledgebase/getting-started/claude-code-on-vps). One etiquette note for when self-help ends in a ticket anyway: write the ticket **in your own words with the real errors**, and don't paste the chatbot's output into it, [here's why that slows your fix](https://vpsdime.com/knowledgebase/getting-started/raising-a-support-ticket). ### Hiring help If you'd rather not do the server work, hiring a **freelance system administrator** is inexpensive and effective, one-off tasks (an installation, a migration, a tune-up) are typically cheap hourly work, and ongoing part-time management is easy to find on freelance marketplaces. That gets you real hands-on management, which a low-cost self-managed VPS deliberately doesn't include. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - what you'd like installed, moved, or managed, - whether you want direction to do it yourself, or a pointer for getting it done for you. ### Related questions - "Can you install software on my VPS for me?" - "Do you offer managed services?" - "Can you migrate my sites from my old host?" - "Who can I hire to manage my server?" - "Do you have one-click app installs?" --- ## Response times and priorities URL: https://vpsdime.com/knowledgebase/support-coverage/response-times-and-priorities Last reviewed: 2026-07-02 Summary: VPSDime support is staffed 24/7 including holidays and typically replies within minutes. It's ticket-only (no phone or live chat) and provided in English. Access-affecting problems are prioritised, ticket priority signals urgency rather than jumping the queue, and best-effort software questions can take longer. ### What this is What to expect after you [open a ticket](https://vpsdime.com/open-ticket/): who's on the other end, how fast replies come, and what actually affects the speed. ### Staffing and typical times - Support is **staffed 24/7, holidays included**. There's no "office hours" queue where a Friday-night ticket waits until Monday. - Replies typically come **within minutes**. - **Anything affecting access to your VPS is prioritised**, a server that's down or unreachable goes to the front. - **Best-effort questions can take longer.** Help with your own software is a courtesy on top of the service (see [what support covers](https://vpsdime.com/knowledgebase/support-coverage/what-support-covers)), so at busy times, platform problems come first. ### By ticket, in English - **Support is by ticket**, there's no phone line or live chat. That's deliberate: a ticket reaches the same 24/7 team within minutes, and everything said and done is on record, so nothing gets lost between calls or chat sessions. - **Support is provided in English.** Writing your ticket in English keeps replies fast and precise. ### What priority does The ticket form asks for a **priority** (High, Medium, Low). It signals urgency, it isn't a queue you jump by always picking High: - **High**: genuinely urgent, a VPS that's down, or a suspected security problem. - **Medium**: a normal problem that's blocking you. - **Low**: a question that isn't time-sensitive. Marking routine questions High doesn't get them answered sooner, and it makes real emergencies harder to spot. ### Getting a fast resolution, not just a fast reply Two things shorten the total time to fixed more than anything we do: - **A first message we can act on.** The exact error, the VPS involved, when it started, and what you tried. The full checklist is in [raising a ticket that gets solved fast](https://vpsdime.com/knowledgebase/getting-started/raising-a-support-ticket). - **Your words plus the server's output, never an AI chatbot's.** Paste real errors and command output; don't paste chatbot transcripts, our L3 staff diagnose from actual symptoms, and wading through AI speculation slows the fix. - **The self-service tools.** If your VPS is unreachable, [My VPS is Down](https://vpsdime.com/knowledgebase/client-area/support/vps-troubleshooter) frequently fixes the cause on the spot, faster than any ticket. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what's wrong and how urgent it genuinely is. ### Related questions - "How fast does support reply?" - "Do you have phone or live chat support?" - "Can I get support in my own language?" - "Is support available 24/7, on weekends and holidays?" - "Does setting my ticket to High priority make it faster?" - "Why is my software question taking longer than my outage ticket did?" - "How do I get my problem fixed on the first reply?" --- ## Acceptable use & network policies URL: https://vpsdime.com/knowledgebase/acceptable-use Last reviewed: 2026-07-02 Summary: What you can run on a VPSDime VPS and what isn't allowed, the email sending policy, how DDoS attacks against your VPS are handled, and what happens if you use up your monthly traffic. How your VPS may be used, and how we protect the network everyone shares. The binding documents are the [Acceptable Use Policy](https://vpsdime.com/aup) and [Terms of Service](https://vpsdime.com/tos); these guides explain the rules and what actually happens in practice. - [What you can run, and what isn't allowed](https://vpsdime.com/knowledgebase/acceptable-use/whats-allowed). The allowed and prohibited list, and what happens if a VPS is compromised. - [Sending email from your VPS](https://vpsdime.com/knowledgebase/acceptable-use/email-policy). Low-volume mail is fine, bulk mail is not, and what our monitoring does. - [DDoS attacks and null-routing](https://vpsdime.com/knowledgebase/acceptable-use/ddos-policy). What happens when your VPS is attacked, and what to do if you're a frequent target. - [Security testing, port scanning, and pen testing](https://vpsdime.com/knowledgebase/acceptable-use/security-testing). Authorized testing of your own or consented targets is fine; scanning third parties or us is not. - [Traffic allowance and overages](https://vpsdime.com/knowledgebase/acceptable-use/bandwidth-overage). The warning emails, the 24-hour window, and how suspension and reset work. --- Still need a person? You can [open a support ticket](https://vpsdime.com/open-ticket/) any time. --- ## What you can run, and what isn't allowed URL: https://vpsdime.com/knowledgebase/acceptable-use/whats-allowed Last reviewed: 2026-07-05 Summary: What's allowed on a VPSDime VPS (websites, databases, game servers, a personal VPN, Docker, and more) and the short list of prohibited uses (torrents, Tor, public VPN/proxy services, crypto mining, bulk email, adult content, reselling), plus what happens if your VPS is compromised. ### What this is The practical version of our acceptable-use rules: what you can run on your VPS, and the short list of things you can't. The full, binding policy is the [Acceptable Use Policy](https://vpsdime.com/aup), which you agree to (along with the [Terms of Service](https://vpsdime.com/tos)) when you order. The rules exist to keep the network fast and our IP space clean for everyone. Nothing here is unusual for a VPS host. ### Perfectly fine - Websites, web apps, and APIs - Databases - Development, staging, and test environments - **Hosting your clients' websites and apps** as part of your work (you're the account holder, so what runs on the VPS stays your responsibility) - **Game servers** (Minecraft and the like) - A **personal VPN for your own use** - Docker and self-hosted apps (Nextcloud, media tools, automation, and so on) - **AI inference workloads** - **Cryptocurrency staking and validator nodes** (mining is a different story, see below) - **Lawful streaming** that doesn't infringe anyone's rights - Using every bit of the resources your plan includes ### Not allowed - **Torrents and P2P**: clients, trackers, or seedboxes. - **Tor**: relay, exit, entry, or bridge nodes. - **Public VPN or proxy services** run for other people. A private VPN just for yourself is fine. - **Cryptocurrency mining.** Staking and validator nodes are fine; mining is not. - **Bulk or marketing email.** Low-volume transactional mail is fine; see [Sending email from your VPS](https://vpsdime.com/knowledgebase/acceptable-use/email-policy). - **Adult content.** - **Gambling**: casinos, betting, or lotteries. - **Sales of drugs, controlled substances, or weapons.** - **Hate speech, terrorism, or content inciting violence** against people or groups. - **Phishing, malware, command-and-control, or botnet infrastructure.** - **Aggressive web scraping**: scraping that generates denial-of-service-level load on its targets or ignores robots.txt. - **Copyright infringement** or any unlawful use, including nulled, cracked, or pirated software. We act on valid infringement complaints. - **Reselling.** Selling our servers as your own product isn't permitted. To earn from customers you send our way, use the [affiliate program](https://vpsdime.com/knowledgebase/client-area/affiliates/affiliate-program) instead. ### Suspended for a violation? Here's the way back If your VPS was suspended for breaking one of the rules above (running a Tor node is a common example), the path to reactivation is straightforward, and it runs through a ticket, not a workaround: 1. **[Open a support ticket](https://vpsdime.com/open-ticket/)** about the suspension. 2. **Acknowledge what was running.** Reviews go much faster when the ticket engages with the actual finding rather than disputing something our monitoring observed directly. 3. **Commit to removing the prohibited software and not running it again.** That commitment is what the reactivation is based on. 4. **Staff unsuspends, and you remove it immediately.** While the VPS is suspended you can't get into it, so the removal happens right after reactivation, and it needs to be your **first action**: anything set to start on boot is already running again the moment the VPS comes back, so uninstall or disable the prohibited software before anything else (a clean [OS reinstall](https://vpsdime.com/knowledgebase/client-area/services/reinstall-os) also settles it). The same automated monitoring that caught it the first time keeps watching after reactivation, and if it detects the same software running again, that registers as the violation continuing rather than resolved. Two notes worth taking seriously: a suspended VPS still has its data, so this is recoverable, promptly, and repeat violations after a reactivation are a different conversation, the first one is handled with goodwill, a pattern is not. ### If your VPS is compromised If our monitors spot a compromised VPS (attacking others, sending spam, and so on), our staff verifies it and **suspends the VPS** to stop further damage, to it and to others, then you either clean it up or back up your data and reinstall. The service is self-managed, so the work itself is yours to do, but the full step-by-step is in [My VPS was hacked. Recovery, step by step](https://vpsdime.com/knowledgebase/troubleshooting/compromised-vps-recovery). The best prevention is [securing your VPS](https://vpsdime.com/knowledgebase/getting-started/securing-your-vps) properly and keeping everything on it updated. ### Not sure about your use case? If what you want to run isn't clearly covered here or in the [AUP](https://vpsdime.com/aup), [ask us first](https://vpsdime.com/open-ticket/). A one-line ticket before you deploy beats a suspension after. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - what you'd like to run, - roughly how it will use the network (ports, traffic, mail). ### Related questions - "Do you allow ____?" - "Are game servers like Minecraft allowed?" - "Can I run a VPN on my VPS?" - "Are torrents or Tor allowed?" - "Is crypto mining allowed?" - "Is crypto staking or running a validator node allowed?" - "Is gambling allowed?" - "Can I run AI inference workloads?" - "Is web scraping allowed?" - "Can I host nulled or cracked scripts?" - "Can I resell your services?" - "Can I host my clients' websites on my VPS?" - "What happens if my VPS gets hacked or compromised?" - "My VPS was suspended for a TOS violation, how do I get it back?" - "I was suspended for running Tor, what do I do now?" --- ## Sending email from your VPS URL: https://vpsdime.com/knowledgebase/acceptable-use/email-policy Last reviewed: 2026-07-02 Summary: VPSDime's email policy, outbound port 25 is open and low-volume transactional mail is fine, bulk and marketing mail are forbidden, automated monitoring blocks SMTP on VPSes that emit mass mail, and a $250-per-blacklist charge applies if your IP gets listed. ### What this is What you can and can't do with email on a VPSDime VPS, and how our monitoring enforces it. The short version: run a mail server if you like, send the mail your apps need, but any kind of bulk sending is off-limits. ### What's allowed **Outbound port 25 is open**, so you can [run a mail server](https://vpsdime.com/knowledgebase/getting-started/self-hosting-email) and send **low-volume transactional and monitoring email**: password resets, order confirmations, alerts from your systems, personal correspondence. That covers the mail a normal site or app generates. To help your mail land in inboxes, set **reverse DNS** on your IP from the [Network](https://vpsdime.com/knowledgebase/client-area/services/network) tab so it matches your mail server's hostname. If your mail is landing in spam, the full self-service diagnosis (SPF, DKIM, DMARC, testing tools) is in [Emails from my VPS go to spam](https://vpsdime.com/knowledgebase/troubleshooting/emails-going-to-spam). ### What's not allowed **Mass mailing of any kind is strictly forbidden on our network**: marketing blasts, newsletters, cold outreach, purchased lists, anything sent in bulk. This is what keeps our IP ranges off blocklists, which benefits every customer sending legitimate mail. If you have real sending volume, use a dedicated email service such as **Amazon SES** or **Mailgun**. They're built for it, inexpensive, and your deliverability will be better than from any single VPS. ### How it's enforced - **Automated monitoring.** Our systems watch for mass-mail emission from VPSes. A VPS that starts bulk-sending has its **SMTP ports blocked automatically**. If that happens, deal with the cause (often a compromised site or app), then [open a ticket](https://vpsdime.com/open-ticket/) to get the block reviewed. - **Blacklist charge.** We check our IP space against blocklists frequently. **If your IP gets blacklisted, you'll be charged $250 per blacklist**, and you're required to handle the delisting. You're responsible for the software and usage on your VPS, so "it wasn't me, my site was hacked" doesn't waive this. Keep your VPS and its apps updated and locked down. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - what kind of mail you're sending and roughly how much, - if SMTP was blocked, what you've done to address the cause. ### Related questions - "Can I run a mail server or send email from my VPS?" - "Is port 25 open?" - "Can I send newsletters or marketing email?" - "Why was SMTP blocked on my VPS?" - "What happens if my IP gets blacklisted?" - "What should I use for bulk email instead?" --- ## DDoS attacks and null-routing URL: https://vpsdime.com/knowledgebase/acceptable-use/ddos-policy Last reviewed: 2026-07-05 Summary: How VPSDime handles DDoS attacks against your VPS, built-in mitigation capacity for smaller attacks, null-routing of the target IP during large ones (reviewed every 6 hours), and what to do if you expect to be attacked regularly. Includes protection options for non-website services, since Cloudflare only proxies web traffic. Game proxies (TCPShield, NeoProtect), Cloudflare Spectrum, and protected tunnels (X4B, EvoShield) for everything else including UDP. ### What this is What happens when a DDoS attack is aimed at your VPS, and what your options are. ### How attacks are handled - **Smaller attacks:** our network has some **mitigation capacity built in**, so modest attacks are often absorbed without you noticing. - **Large attacks:** to protect the other customers sharing the network, we **null-route the target IP**. Traffic to that IP is dropped at the edge until the attack subsides. Your VPS itself keeps running, but it's unreachable on the null-routed IP for the duration. - **Null-routes are reviewed every 6 hours.** If the attack has stopped, the null-route is lifted; if it's still going, the null-route stays in place and is checked again at the next review. ### If you expect to be attacked regularly Being attacked doesn't make you a rule-breaker, but a VPS on its own isn't the right tool for absorbing regular DDoS. If you expect to be a frequent target: - **Put the site behind a mitigation service.** For websites, **Cloudflare** works well (the free tier is often enough): it hides your VPS's IP and soaks the attack before it reaches us. Set it up properly, including firewalling your web ports so only Cloudflare can reach them, with [Cloudflare best practices](https://vpsdime.com/knowledgebase/getting-started/cloudflare-best-practices). - **Keep your origin IP secret.** Mitigation only helps while attackers don't know the IP behind it. If the IP has already leaked, see the IP-change policy below. ### IP change requests A request we get during attacks: "just give me a new IP." We don't change IPs on the strength of a suspected attack alone, and the reason is practical, not bureaucratic: **without protection in front, a new IP buys you minutes.** The attacker re-resolves your domain (or re-scans), finds the new address, and the attack resumes, now with one more burned IP in the story. An IP change only helps as the *last* step of the sequence, not the first: 1. **Put mitigation in place first.** Cloudflare for websites ([set up properly](https://vpsdime.com/knowledgebase/getting-started/cloudflare-best-practices), origin locked to their ranges), or the game-server options in the next section for non-web services. 2. **Then, if the old IP is already exposed** and attacks are still hitting it directly, [open a ticket](https://vpsdime.com/open-ticket/) and request the change. A fresh IP issued *behind* active protection stays unknown, which is what makes the change worth doing exactly once. Requested in that order, an IP change is the finishing move that makes mitigation complete. Requested on its own, it's a treadmill, which is why step 1 comes first. ### If the target isn't a website (game servers and other ports) Cloudflare's normal proxy only handles **web traffic** (HTTP and HTTPS). A Minecraft server, a voice server, or anything else on its own TCP or UDP port gets no protection from an orange-clouded DNS record, so this class of service needs a different tool. The self-serve options, roughly in order of how easy they are: - **Minecraft: a game proxy service.** [TCPShield](https://tcpshield.com/) is the standard for Java Edition: a genuinely free tier for small and medium servers, premium plans from **$30/month** (Bedrock needs premium). [NeoProtect](https://neoprotect.net/) is the same model, with a free tier and paid plans from around **€15/month**, including Bedrock/Geyser support. Both work like Cloudflare does for websites: players connect to the proxy's address, and the proxy forwards clean traffic to your VPS. - **Minecraft or SSH, if you're already on Cloudflare: Spectrum.** Cloudflare's **Pro plan ($25/month)** includes [Spectrum](https://www.cloudflare.com/application-services/products/cloudflare-spectrum/) proxying for **Minecraft and SSH** with 5 GB of Spectrum traffic per month included (Business adds RDP and 10 GB), billed per GB beyond that. TCP only, and the per-GB meter makes it a poor fit for high-traffic servers, but it's the shortest path if the domain is already there. - **Anything else, including UDP: a protected tunnel.** Services like [X4B](https://www.x4b.net/) and [Evolution Host's EvoShield](https://evolution-host.com/remote-ddos-protection.php) sell remote protection with **public pricing**: you get a protected IP at their edge, and traffic reaches your VPS through a GRE or similar tunnel, any port, any protocol. This is the answer for UDP games (FiveM, Source engine, and similar) that the proxies above don't cover. Setup is real command-line work on the VPS (a tunnel interface plus routing), but both document it and it's well within one person's reach. Pick the provider location nearest your VPS, since the tunnel adds a network hop. - **What's *not* a customer option: BGP-based mitigation.** Providers in that class (Path.net, Cosmic Guard, Voxility) protect whole IP ranges announced over BGP, which requires owning IP space and an ASN. They mostly sell to hosting companies with pricing on request, so if a guide's setup steps start with "announce your /24", it's written for a different audience. Whichever you pick, the [same rule as Cloudflare](https://vpsdime.com/knowledgebase/getting-started/cloudflare-best-practices) applies: the protection only works if your VPS's own firewall accepts game traffic **only from the protection service** (or only over its tunnel). A protected front door with the origin still answering to the whole internet mitigates nothing. ### Troubleshooting - **My VPS is unreachable and I think it's being attacked.** Check the [service status](https://vpsdime.com/service-status) page first, then [open a ticket](https://vpsdime.com/open-ticket/). If the IP was null-routed, we can tell you and confirm when it was last reviewed. - **How long will the null-route last?** Until the attack stops. Reviews happen every 6 hours, so the typical wait after an attack ends is at most a few hours. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - when the trouble started, - whether you've had attacks against this service before. ### Related questions - "Do you have DDoS protection?" - "My VPS is under a DDoS attack, what happens now?" - "Why is my IP null-routed and how long does it last?" - "My VPS is unreachable during an attack." - "What should I do if my site gets attacked often?" - "How do I protect a game server from DDoS? Cloudflare doesn't cover it." - "What DDoS protection works for Minecraft?" - "How do I protect a UDP service like FiveM from attacks?" - "My VPS is under attack, can I just get a new IP?" - "When will you change my IP because of DDoS?" --- ## Security testing, port scanning, and pen testing URL: https://vpsdime.com/knowledgebase/acceptable-use/security-testing Last reviewed: 2026-07-04 Summary: Running security tools (nmap, Nessus, Metasploit, Burp, and the like) from your VPS is fine when the target is your own systems or something you have explicit authorization to test. What is prohibited is outbound scanning, vulnerability testing, or brute-forcing against third parties who haven't consented, and any attempt against our infrastructure or other customers. This explains the line, drawn straight from our Terms of Service and Acceptable Use Policy. ### The short answer Security work **on systems you own or are authorized to test is allowed**. Security work **aimed at third parties who haven't consented, or at us, is not**. That single distinction, authorized target versus unauthorized target, is the whole policy, and it lines up with how the law treats the same activity. There is no blanket ban on security tools. nmap, Nessus, OpenVAS, Metasploit, Burp Suite, sqlmap, hashcat, a full Kali install, they're ordinary software, and running them is a legitimate use of a VPS. ### What's allowed - **Scanning and testing your own infrastructure**, the VPS itself, your other servers, your own web apps. - **Authorized engagements**: penetration testing a client's systems under a signed contract or written scope, bug-bounty testing within a program's stated rules, a red-team exercise you've been hired for. - **Learning and competition**: CTF challenges, deliberately vulnerable practice targets (HackTheBox, TryHackMe, DVWA, your own lab), and security research against systems you control. - **Defensive tooling**: running scanners against your own services to find your own weaknesses before someone else does. The common thread is **authorization**. If you have the right to test the target, whether because you own it or because its owner gave you permission, our policy isn't aimed at you. ### What's prohibited From our [Terms of Service](https://vpsdime.com/tos) and [Acceptable Use Policy](https://vpsdime.com/aup), the following are not permitted: - **Outbound port scanning, vulnerability scanning, or brute-force activity against third parties** who haven't authorized it. The TOS names this directly, and the AUP treats a port scan or other information-gathering against another party's systems as a precursor to attempted intrusion. - **Any attempt to access, compromise, or subvert the security of our own systems or other customers' services.** Testing your neighbors on the platform, or us, is never in scope, contact us for coordinated disclosure instead (see below). - **Denial-of-service or amplification traffic**, which is a separate prohibition covered under our [DDoS policy](https://vpsdime.com/knowledgebase/acceptable-use/ddos-policy), a "stress test" against a target you don't own is an attack. Unauthorized scanning is also how attackers begin, so it draws abuse reports and, in many jurisdictions, it's a crime independent of our terms. Both the report and the law land on you, not us, when the target didn't consent. ### Practical notes - **Your testing must not generate abuse reports against our network.** A target being scanned doesn't see your authorization letter; it sees probes from our IP and may complain to us. "It was authorized" is your matter with the target's owner, not a shield that makes the complaint our problem. Keep authorized testing **tightly scoped and rate-limited** so it stays between you and the consenting party, hold your written authorization to answer any dispute directly, and understand that **repeated abuse complaints about your traffic can get your service suspended regardless of authorization**. If you can't run an engagement without it spilling into abuse reports to us, it doesn't belong on the VPS. - **Incoming scans against your VPS are just the internet.** Every public IP is scanned constantly; that's [background noise](https://vpsdime.com/knowledgebase/technical-questions/change-ssh-port), not an attack you need to report. Our own [SSH firewall](https://vpsdime.com/knowledgebase/client-area/support/ssh-firewall) blunts the most common brute-force class automatically. - **Found a vulnerability in VPSDime itself?** We welcome responsible disclosure. Don't test it against production or other customers, [open a ticket](https://vpsdime.com/open-ticket/) describing what you found and we'll take it from there. ### Still need help? If you're unsure whether a specific engagement is in bounds, [ask us first](https://vpsdime.com/open-ticket/). A one-line description of the target and your authorization is usually all it takes for a clear yes. So we can answer on the first reply, it's worth mentioning: - what you'll be running and against what, - your basis for testing that target (you own it, or a scope/authorization from its owner), - whether it's a one-off or ongoing. ### Related questions - "Can I run nmap or a port scanner from my VPS?" - "Is penetration testing allowed on VPSDime?" - "Can I use my VPS for bug bounty work?" - "Is it OK to run a vulnerability scanner from my server?" - "Can I test my own website's security from my VPS?" - "Am I allowed to scan other servers?" --- ## Traffic allowance and overages URL: https://vpsdime.com/knowledgebase/acceptable-use/bandwidth-overage Last reviewed: 2026-07-02 Summary: Every VPSDime plan includes a metered monthly traffic allowance. Warning emails go out at 75% and 100% of usage; after hitting 100% you have 24 hours to add traffic or upgrade before the VPS is suspended, and the allowance resets on the 1st of each month. ### What this is Each plan includes a **monthly traffic allowance** (it's metered, not unmetered), delivered over a fast 10 Gbps uplink. This explains what happens as you approach and pass that allowance. ### How the allowance works - Your allowance **resets on the 1st of each month**. Unused traffic doesn't roll over. - You can watch usage any time on your VPS's [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) tab. ### What happens when you run low 1. **At 75% used**, we email you a heads-up. 2. **At 100% used**, we email you again, and you have **24 hours** to either [add traffic](https://vpsdime.com/knowledgebase/client-area/services/extra-features) or [upgrade the plan](https://vpsdime.com/knowledgebase/client-area/services/upgrade-downgrade). 3. **If you do neither within 24 hours**, the VPS is **suspended**. It comes back when you add traffic or upgrade, or automatically when your allowance **resets on the 1st** of the next month. ### Things worth knowing - **Suspension here is about traffic, not payment.** Your data is untouched, and the VPS returns as soon as more traffic is available (added, upgraded, or reset). - **Add traffic ahead of time.** If your usage trends toward the cap mid-month, adding traffic from [Extra Features](https://vpsdime.com/knowledgebase/client-area/services/extra-features) is prorated and avoids the scramble. If you're over the cap most months, a bigger plan is usually the better deal. - **Keep your account email reachable**, the 75% and 100% notices are your early warning. ### Troubleshooting - **My VPS was suspended for traffic.** Add traffic or upgrade from your client area and it comes back; otherwise it returns on the 1st when the allowance resets. - **The VPS came back, but my website or app didn't.** Services not set to start on boot stay down after any reactivation, see [the one-minute fix](https://vpsdime.com/knowledgebase/troubleshooting/services-not-starting-after-reboot). - **My usage seems too high.** Check the [Graphs](https://vpsdime.com/knowledgebase/client-area/services/graphs) for what's consuming it. Unexpected traffic is often a compromised app, a misbehaving bot, or something being scraped, worth investigating rather than just topping up. ### Still need help? You can [open a support ticket](https://vpsdime.com/open-ticket/). So we can help on the first reply, it's worth mentioning: - the VPS hostname or IP, - whether you want more traffic this month or a bigger plan going forward. ### Related questions - "What happens if I run out of bandwidth?" - "Is bandwidth metered or unmetered?" - "My VPS was suspended for exceeding traffic." - "When does my traffic allowance reset?" - "How do I add more bandwidth?" --- # Articles ## The Vercel Experience on Your Own Metal URL: https://vpsdime.com/coolify-one-click-vps-deployment Summary: The Vercel experience on your own metal. Deploy a fully configured, secure-by-default Coolify instance on your VPS in 60 seconds for as little as $5/month. ### One-Click Coolify Deployment is Here ### The Vercel Experience on Your Own Metal: One-Click Coolify Deployment is Here Posted April 15th, 2026 by VPSDime If you've ever used Vercel, Netlify, or Heroku, you know the "magic" feeling: you push code, and a few seconds later, your app is live. No Nginx configurations, no SSL headaches, no manual database setup. It's the gold standard for developer experience. But as any growing startup or side-hustler knows, that magic comes with a "convenience tax." As your traffic scales, those monthly bills transform from a rounding error into a major line item. You start paying for "seats," premium middleware, and bandwidth markups that are 10x the market rate. **Coolify** is the open-source answer to this dilemma. It brings the polished PaaS (Platform as a Service) experience to your own private servers. Because we believe so strongly in this mission, **we are proud to officially sponsor the Coolify project.** Today, we're taking that commitment a step further: **One-click Coolify deployment is now live on our platform.** ### What exactly is Coolify? Coolify isn't just a control panel; it's an infrastructure engine. It uses Docker under the hood to turn a raw Linux VPS into a high-performance application cluster. It gives you a beautiful, unified dashboard to manage your entire digital empire. Whether you are a solo developer or managing a team, Coolify handles the heavy lifting: **Zero-Downtime Deployments:** Your app stays online while the new version spins up. **Automatic SSL:** It talks to Let's Encrypt so you never have to touch a certificate again. **Self-Healing:** If your app crashes, Coolify restarts it automatically. **Database Management:** One-click instances of PostgreSQL, MySQL, Redis, and MongoDB with built-in backup scheduling. **280+ One-Click Apps:** Instantly deploy everything from WordPress and Ghost to Plausible Analytics and n8n. ### Secure-by-Default: Instant Ownership from the First Boot Standard installations usually follow a manual setup phase: you run an install script, wait, and then visit the IP address to create your account. While this is the common path, it often leaves a brief window where the registration page is open to anyone who happens to find your IP before you do. We've optimized our provisioning process to ensure your new instance is yours—and only yours—from the very first second it goes live. When you select Coolify on our order form, you aren't just getting a generic installation; you are setting up your private environment before the server is even active. **By providing your Admin Email and Password during checkout, our automated system injects these credentials directly into the setup process.** **Locked Down from the Start:** The moment the Coolify service initializes, it is already protected by your unique credentials. There is no "open" window for crawlers to find; your admin account is waiting for you the moment the login screen appears. **Zero Terminal Work:** You don't need to log in via SSH to run installation scripts or manage environment variables. We handle the heavy lifting behind the scenes using pre-configured `.env` values. **Ready in 60 Seconds:** From the moment you hit "Order," our system provisions your VPS, applies OS security patches, and deploys a fully configured version of Coolify. You'll receive an email as soon as your private cloud is ready for your first project. ### Enterprise Power at "Practically Free" Prices The biggest hurdle to self-hosting has always been the cost of high-performance hardware. We've fixed that. To run a modern PaaS like Coolify effectively, you need RAM—and we've made that RAM more accessible than ever. **The 4GB Starter Plan:** For just **$5/month**, you can run a full Coolify instance with multiple small apps and a database. **The 6GB Power Plan:** At **$7/month**, you get the extra breathing room needed for heavier Docker builds and staging environments. When you compare this to the $20/month *per seat* or the tiered pricing of traditional PaaS providers, hosting with us is **practically free.** You get 100% of the hardware power for a fraction of the cost of a "managed" service. ### Your Private Cloud is Waiting We sponsor Coolify because we believe developers should have total control over their data and their costs without sacrificing the modern deployment experience. By removing the "Linux barrier" and the high cost of entry, we're making it possible for anyone to run a world-class tech stack. Check the **Applications** tab on your next order, set your credentials, and let us handle the rest. **Your VPS is no longer just a server; it's your own private cloud.** #### A Quick Note on Backups While Coolify is incredibly stable, remember that "Self-Managed" means you are the captain of the ship. We highly recommend enabling our **Nightly Backups** during checkout. For a small additional fee, you get the ultimate peace of mind knowing that your entire private cloud can be restored in an instant if you ever "experiment" a little too hard. ### Comments ### Leave a Reply Your email address will not be published. Required fields are marked * --- ## The Fortress and the Sentry URL: https://vpsdime.com/fortress-and-sentry-vps-security Summary: Transform your vulnerable VPS into an impenetrable fortress. A comprehensive, layered security guide from initial login to advanced monitoring. ### Your Ultimate Guide to Securing a Self-Managed VPS ### The Fortress and the Sentry: Your Ultimate Guide to Securing a Self-Managed VPS Posted Tuesday November 11th, 2025 by VPSDime You just spun up a new, cheap self-managed VPS. It's a pristine, blank canvas brimming with potential. It's also a tiny, anonymous house with no locks, standing on a street with billions of people, and every single one of them is jiggling the doorknob. Welcome to the public internet. A self-managed VPS gives you unparalleled power and value, but it comes with one non-negotiable trade-off: **you are in charge of security.** This isn't a suggestion; it's the core of the contract. The good news is that building a digital fortress is not about some secret, arcane knowledge. It's about applying a series of logical, well-known layers of defense. This guide is your blueprint. We will go layer by layer, from the moment you first log in to the advanced, automated defenses that will guard your server 24/7. ### Layer 1: The First 30 Minutes – Triage and Access Control Before you even think about installing your website or application, you must secure the front door. These are the *very first* actions to take. #### 1. Patch Your System Immediately Your VPS image is likely days, weeks, or even months old. In that time, dozens of security vulnerabilities may have been discovered. Your first command, before all else, is to patch the system. On a Debian/Ubuntu system: ``` sudo apt update && sudo apt upgrade -y ``` On a Red Hat/AlmaLinux/Fedora system: ``` sudo dnf update -y ``` #### 2. Get Off the `root` User The `root` user is the all-powerful administrator. If an attacker compromises this account, the game is over. You should *never* log in as `root` for daily work. Your first task is to create a personal user account and give it `sudo` (administrator) privileges. On a Debian/Ubuntu system: ``` # Log in as root # Create your new user (you will be prompted for a password) adduser your_username # Add this user to the 'sudo' group to grant admin rights usermod -aG sudo your_username ``` ``` # Create your new user useradd your_username # Set a password for the new user passwd your_username # Add this user to the 'wheel' group to grant admin rights usermod -aG wheel your_username ``` Now, **log out and log back in as `your_username`**. You will perform every other step in this guide as this new user. ### Layer 2: Hardening the Gateway – The Modern SSH Defense Your SSH (Secure Shell) port is the main administrative door to your server. 99% of all automated attacks will be directed here. Your goal is to make this door invisible, impenetrable, and heavily alarmed. #### 1. Ditch Passwords for SSH Keys (The Non-Negotiable) Passwords can be guessed, brute-forced, or phished. SSH keys are cryptographically secure. This is the single most effective security upgrade you can make. An SSH key pair consists of a **private key** (which you keep secret on your computer) and a **public key** (which you place on the server). The server will only allow someone to log in if they have the corresponding private key. On your *local computer* (not the VPS), generate a key pair: ``` ssh-keygen -t ed25519 ``` Now, copy the public key to your new server: ``` ssh-copy-id your_username@YOUR_SERVER_IP ``` Try logging in again. You should be logged in automatically without a password. #### 2. Install Fail2Ban (The Automated Sentry) Fail2Ban is a tool that scans your server's logs. If it sees an IP address repeatedly failing to log in (a brute-force attack), it automatically bans that IP at the firewall level. On a Debian/Ubuntu system: ``` sudo apt install fail2ban ``` ``` sudo dnf install fail2ban ``` Then enable and start it: ``` sudo systemctl enable fail2ban sudo systemctl start fail2ban ``` It works out of the box for SSH and is a set-it-and-forget-it lifesaver. #### 3. Change the Default SSH Port Every bot on the planet scans port 22. By simply changing it, you become invisible to 99% of this automated traffic. On modern systemd-based distributions (Ubuntu 22.04+, Debian 12+, Fedora, etc.), SSH uses **socket activation**, which means the listening port is controlled by systemd, not `sshd_config`. To change the port, you need to override the systemd socket unit: ``` sudo systemctl edit ssh.socket ``` This opens an editor for a drop-in override file. Add the following (the empty `ListenStream=` clears the default port 22 before setting the new one): ``` [Socket] ListenStream= ListenStream=23456 ``` Then reload systemd and restart the socket: ``` sudo systemctl daemon-reload sudo systemctl restart ssh.socket ``` You can verify the new port is active with: ``` sudo systemctl status ssh.socket ``` **Note:** On older systems without socket activation, you can instead edit `/etc/ssh/sshd_config`, uncomment the `#Port 22` line, change it to your chosen port, and restart with `sudo systemctl restart sshd`. **Important:** Before you log out, you must **allow your new port through the firewall** (see Layer 3) and confirm you can connect on the new port from a second terminal. #### 4. Set Up Two-Factor Authentication (2FA) For ultimate security, you can require both your SSH key *and* a one-time code from your phone (like Google Authenticator). This is known as "something you have" (your key) and "something you know" (your code). You can set this up by installing the `libpam-google-authenticator` package and configuring your PAM (Pluggable Authentication Modules). #### 5. Lock Down SSH Access with an IP ACL (The Velvet Rope) Why leave your SSH port open to the world? If you have a static IP at your home or office, you can tell your firewall to *only* accept SSH connections from that IP. A more modern and flexible approach is to use a mesh VPN like **Tailscale**. You can install Tailscale on your server and your laptop, which places them both on a secure, private network. You can then configure your server's firewall to **block all public access to your SSH port** but **allow access from your private Tailscale IP**. From the public internet's perspective, your SSH port doesn't even exist. #### 6. Final SSH Configuration Hardening Finally, let's turn off all the old, insecure settings in your `sshd_config` file: ``` sudo nano /etc/ssh/sshd_config ``` Find and change these lines to the following values: ``` # This disables logging in as the root user directly PermitRootLogin no # This forces everyone to use SSH keys PasswordAuthentication no KbdInteractiveAuthentication no # Keep PAM enabled for session setup and 2FA support UsePAM yes ``` **Note:** The listening port is managed by systemd's `ssh.socket` (see step 3 above), so there is no need to set `Port` in this file. Restart the SSH service to apply all your changes: ``` sudo systemctl restart ssh.socket ssh.service ``` ### Layer 3: Building the Fortress – Firewalls and Network Monitoring Now that the admin door is secure, let's build the walls. A firewall's job is to block all network traffic except for what you explicitly permit. #### 1. Configure UFW (Uncomplicated Firewall) UFW is the easiest and most effective firewall for a single server. The strategy is simple: **deny everything by default, then allow only what you need.** ``` # 1. Deny all incoming traffic and allow all outgoing traffic by default sudo ufw default deny incoming sudo ufw default allow outgoing # 2. Allow your new, non-standard SSH port (CRITICAL: Do this first!) sudo ufw allow 23456/tcp # 3. Allow standard web traffic sudo ufw allow 80/tcp # For HTTP sudo ufw allow 443/tcp # For HTTPS # 4. Turn the firewall on sudo ufw enable # Check your rules sudo ufw status ``` Your server is now secure. No traffic can get in except for SSH (on your new port) and web traffic. #### 2. Advanced Monitoring: Suricata and Zeek (The Security Cameras) A firewall blocks traffic, but an **Intrusion Detection System (IDS)** watches it. **Suricata** is a rule-based IDS; it's like a security guard with a binder of known attack signatures (like SQL injection, malware, etc.) and alerts you if it sees one. **Zeek** is different; it's a network analyzer. It's like a security camera that records *every* conversation, giving you a high-level log of all network activity (e.g., "This IP uploaded this file via FTP," "This IP made 50 failed DNS queries"). These are advanced tools, but they provide invaluable insight into what's happening on your network. ### Layer 4: Securing the Interior – System-Level Hardening An attacker who gets past your firewall and SSH shouldn't be given free rein. These steps limit their ability to do damage *inside* your server. **Never Run Services as Root:** Your web server (Nginx, Apache) should *never* run as the `root` user. If an attacker finds a flaw in your website's code, they will gain control of the web server process. If that process is running as `root`, they instantly own your entire server. Run all services as their own unprivileged user (e.g., `www-data`). **Use Mandatory Access Control (SELinux/AppArmor):** These are powerful, kernel-level security systems. They act as a second, internal layer of defense. Even if an attacker compromises your web server *and* finds a way to become `root`, SELinux can still block them from reading your SSH keys or writing to system files because the web server process is not *labeled* for that kind of activity. **Harden `/tmp` and Shared Memory:** The `/tmp` directory is world-writable, making it a favorite spot for attackers to download and run malicious scripts. You can re-mount your `/tmp` partition with `noexec`, `nosuid`, and `nodev` options in `/etc/fstab` to prevent any code from being executed from this directory. ### Layer 5: Securing Your Applications – The Web Stack Most VPSs run a web server. Securing your server is only half the battle; you must also secure your web applications. **Implement a Reverse Proxy:** Don't run your application (Node.js, Python, etc.) directly exposed to the internet. Put **Nginx** in front of it as a reverse proxy. Nginx is a battle-hardened server that will handle SSL/TLS, caching, and rate-limiting, protecting your more delicate application code. **Use a WAF (Web Application Firewall):** A WAF like **ModSecurity** integrates with your web server and actively blocks web-specific attacks like SQL Injection (SQLi) and Cross-Site Scripting (XSS). **SSL/TLS Hardening:** Use **Let's Encrypt** for free, automated SSL certificates. But don't stop there. Configure your web server to only use modern protocols (TLS 1.2 and 1.3) and strong ciphers. This will get you an "A+" on the SSL Labs test. **Use Security Headers:** Instruct browsers to be more secure by adding headers like **HSTS** (forces HTTPS) and **CSP (Content Security Policy)** (prevents XSS attacks). **Database Hardening:** Your database (MySQL, PostgreSQL) should *never* be accessible from the public internet. Configure it to only bind to `127.0.0.1` (localhost). This means only applications running on the *same server* can access it. ### Layer 6: The Long Game – Ongoing Maintenance and Monitoring Security is a process, not a destination. These final steps keep your fortress secure over time. **Set Up Automatic Security Updates:** On Ubuntu/Debian, `unattended-upgrades` is a vital tool. It will automatically apply critical security patches in the background, so your server is never left vulnerable for long. **Secure Your DNS:** Your server needs to look up other domains. By default, it sends these queries in plain text. Configure your server's DNS resolver (e.g., `systemd-resolved`) to use **Encrypted DNS** (like DNS-over-TLS) to prevent eavesdropping. #### Logging and File Integrity **Logwatch:** Installs a daily cron job that scans all your logs and emails you a single, clean summary. It's the best 5-minute security check you can do. **Linux Auditing System (`auditd`):** This is your server's "black box." You can configure it to log *every* action, like file access or system calls, for deep forensic analysis. **Centralized Logging:** For multiple servers, send all your logs to a separate, secure server (an ELK stack or Graylog). This way, if an attacker compromises a server, they can't delete the logs to cover their tracks. **File Integrity Monitoring (FIM):** Tools like **AIDE** or **Tripwire** take a "fingerprint" of your entire system. They run daily and alert you if *any* system file changes, warning you of a potential intrusion. **The Final Safety Net: Pull Backups:** Your backups are your last line of defense. Do not "push" your backups (i.e., have your production server log into your backup server). This places your backup server's keys on your production server. If your prod server is hacked, the attacker will find those keys and delete all your backups. Instead, use **pull backups**: have your *backup server* (e.g., a Storage VPS) log into your production server to "pull" the data. This way, your production server has no idea where its backups are, and they are safe from any compromise. #### Conclusion It may look like a long list, but these layers build on each other, creating a powerful, compounding security posture. By investing a few hours to build this fortress from the start, you can spend the next few years running your project with confidence and peace of mind. At [VPSDime](https://www.vpsdime.com), we provide the reliable, affordable VPS infrastructure that's the perfect foundation for your secure server fortress. Our self-managed servers give you complete control to implement these security best practices while keeping your costs low. ### Comments ### Leave a Reply Your email address will not be published. Required fields are marked * --- ## The Developer's Sandbox URL: https://vpsdime.com/developers-sandbox-throwaway-vps Summary: Your dev machine is sacred. Break things, test sketchy scripts, and experiment fearlessly on a disposable VPS sandbox instead. ### Why Every Coder Needs a Cheap "Throwaway" VPS ### The Developer's Sandbox: Why Every Coder Needs a Cheap "Throwaway" VPS Posted October 28th, 2025 by VPSDime Your local development machine is a sacred temple. It's a masterpiece of careful curation, perfected over hundreds of hours. Your dotfiles are immaculate, your IDE is tuned to perfection, and your specific library versions are all in a delicate, harmonious balance. The thought of installing a rogue package or running a sketchy script that could disrupt this harmony is enough to give any coder nightmares. But innovation is messy. Learning is chaotic. True experimentation requires the freedom to break things, to push limits, and to venture into the unknown. So, where do you make the mess? You don't do it in your temple. You do it in the sandbox. For the modern developer, the ultimate sandbox is a cheap, "throwaway" VPS. ### What is a "Throwaway" VPS? Let's be clear: the server isn't *literally* thrown away after each use (though you could). The power is in the **mentality**. A throwaway VPS is a low-cost server that you treat as completely disposable. Its value is not in its uptime or the data it holds, but in its ability to be instantly created and, more importantly, instantly destroyed and rebuilt. Think of it as a digital Etch A Sketch. You can build the most complex, chaotic system you can imagine, and when you're done or you've made a catastrophic mess, you just shake it clean. That "shake" is the "Reinstall OS" button in your control panel, a feature that transforms a simple server into a developer's superpower. ### The Superpowers of a Disposable Environment For less than the price of a couple of pizzas a month, a throwaway VPS gives you a set of freedoms that will fundamentally accelerate your skills and projects. #### 1. The Freedom to Be Reckless: Your Personal Learning Lab The fear of breaking your primary machine is the biggest barrier to learning new technologies. A disposable VPS eliminates this fear entirely. **Master Docker and Containers:** Want to learn Docker without installing its complex daemons and virtual networks on your pristine Mac or Windows machine? A VPS is a clean, native Linux environment perfect for experimenting with containers. **Explore Entirely New Ecosystems:** Your development world doesn't have to be a monoculture. • **Test Across Distros:** Your main server runs on Ubuntu, but you need to ensure your script works on a Red Hat-based system like AlmaLinux or Fedora? Spin one up in minutes. Test your `dnf` commands, check dependencies, and then throw it away. No need for complicated local VMs. • **Bridge Operating Systems:** As a Mac or Linux user, have you ever needed to test one specific Windows application? Instead of buying a new license or struggling with WINE, a cheap Windows VPS lets you use Remote Desktop to get a native Windows environment, test your app, and then terminate the server. **Install System-Altering Software:** This is where a throwaway VPS truly shines. Curious about virtualization platforms like **Proxmox** that fundamentally take over the host system with their own kernel and networking stack? Trying this on a physical machine is a massive, often irreversible commitment. On a VPS, you can install it, play with nested virtualization, and if you completely mess up the entire networking stack, who cares? Reinstall and start again. #### 2. The Digital Biohazard Suit: Testing the Unknown Have you ever found a fascinating but slightly sketchy script on GitHub? Or wanted to download software from a source you don't fully trust? Running it on your main computer is a massive security risk. **Tackle "Sticky" or Uninstallable Software:** Some software integrates so deeply into an OS with kernel modules, system hooks, and scattered files that a clean uninstall is impossible. It leaves digital residue everywhere. A throwaway VPS is the perfect quarantine zone for testing such applications, ensuring your primary machine remains pristine. **Run Massive, Unattended Compilations:** Need to compile a huge project like the **Unreal Engine**, a custom **Linux kernel**, or a complex application from source that takes hours and maxes out your CPU? Doing this on your laptop not only locks it down and risks overheating, but a failed compile can leave a mess of partial files and dependencies. Offload the entire process to the VPS. If the compile fails spectacularly, it happens in a disposable environment, far from your valuable local data. **Execute Strange Scripts:** That intriguing GitHub repository with a complex `install.sh` script? Don't run it blindly on your machine. Pipe it to `bash` on your throwaway VPS and see what it does without any personal risk. #### 3. The Clean Room: Perfect, Replicable Test Environments The eternal developer curse is the phrase, "But it works on my machine!" A throwaway VPS is the cure. Before you deploy your code to production, you can spin up a fresh VPS with the *exact same* operating system and install *only* the dependencies your application needs. This "clean room" test provides the ultimate confirmation that your deployment scripts are solid and you haven't forgotten a dependency. #### 4. The Ultimate "Undo" Button: The Reinstall Feature Imagine you just spent an hour trying to install Proxmox and have made your server's networking completely unreachable. On a local machine or a dedicated server, this would mean a frustrating support ticket and a long wait. On your throwaway VPS, this is a 60-second problem. You tried something, it failed catastrophically, and you learned what not to do. Your tuition for that lesson was one click of the **"Reinstall OS"** button. It is the most powerful undo button ever created, especially when you're playing with fire. ### Why Not Just a Local Virtual Machine? It's a fair question. Tools like VirtualBox, VMware, and Parallels are powerful and have their place for offline work. But when used as a "throwaway" sandbox, a local Virtual Machine (VM) has several fundamental drawbacks that a cheap VPS completely solves. #### 1. The Performance Leash: Your Laptop is Still Doing the Work A local VM is not a separate computer; it's a resource-hungry application running on *your* machine. When you fire up a VM, you are directly sacrificing a huge chunk of your laptop's precious CPU cores and RAM. The result? Your primary machine slows to a crawl. The fans start screaming, the battery drains, and even simple tasks like browsing the web become sluggish. A VPS, by contrast, uses its own dedicated resources in a datacenter. Your laptop stays cool, quiet, and fast. #### 2. The Artificial Bubble: It's Not the Real Internet This is the most critical difference. A local VM lives in an artificial bubble, hidden behind your home router. A VPS lives on the front lines of the real, public internet. **Public IP Address:** Want to test a webhook from Stripe or GitHub? Need to give a client a live demo link? With a local VM, this is a nightmare of router configuration. With a VPS, it just works. You have a real, static IP address from the start. **Real-World Latency:** Code that runs instantly on `localhost` can break down when faced with real-world network latency. Testing on a VPS forces you to build more resilient applications because you're experiencing the actual conditions of the internet. **A Truly Clean Environment:** A Linux VM running on your Windows or macOS machine is an emulation. A VPS is a pristine, native Linux environment running on a Linux-native hypervisor, a far more accurate mirror of a real production server. #### 3. The Physical Tether: Your Sandbox is Chained to Your Desk Your local VM is a set of massive files that lives on a single physical machine. If you switch to another computer or just want to check a process from your phone, you're out of luck. A VPS is untethered. You can securely SSH into your sandbox from any device, anywhere in the world. #### 4. The Illusion of "Disposable": Digital Clutter Lingers While you can delete a local VM, it never feels truly "throwaway." The multi-gigabyte image files clog up your hard drive, and the virtual networking adapters clutter your host machine's settings. A VPS is truly ephemeral. When you click "Reinstall OS," the entire remote environment is vaporized and replaced, leaving absolutely no trace on your personal machine. ### The Smartest Investment in Your Skills A cheap VPS is one of the most cost-effective investments a developer can make, not in a project, but in *themselves*. It removes fear, friction, and risk from the process of learning and experimentation. It's a dedicated space to be curious, to be messy, and to be wrong without consequence. It's the cheapest, most effective way to buy yourself the freedom to break things. And breaking things is how we learn to build. ### Comments ### Leave a Reply Your email address will not be published. Required fields are marked * --- ## Offloading the Load URL: https://vpsdime.com/windows-vps-build-server Summary: Stop letting builds turn your laptop into a jet engine. Offload heavy compiling and rendering to a cheap Windows VPS and reclaim your productivity. ### Use a Cheap Windows VPS as a Build Server and Keep Your Laptop Fast ### Offloading the Load: Use a Cheap Windows VPS as a Build Server and Keep Your Laptop Fast Posted October 25th, 2025 by VPSDime We've all been there. You're deep in the zone, coding a new feature, editing a video timeline, or designing a 3D model. Then, it's time to compile. It's time to render. It's time to *build*. You press the button, and the transformation begins. Your sleek, quiet laptop, your portal to productivity, turns into a jet engine. The fans scream to life, the chassis becomes scalding hot, and every other application slows to a crawl. Your mouse stutters across the screen. Just trying to answer an email becomes a test of patience. You are a prisoner to the progress bar, your expensive machine held hostage by its own workload. What if you could reclaim your laptop? What if you could delegate all that heavy lifting to a tireless, powerful workhorse that lives in the cloud, all for a tiny monthly cost? You can. It's time to discover your new secret weapon: a cheap Windows VPS as a dedicated build server. ### The Universal Problem: The Overburdened Laptop Your laptop is a marvel of engineering, but it's a master of compromise. It's designed for portability and efficiency, not for sustained, brutal, peak performance. Constantly pushing it to its thermal and processing limits with heavy tasks leads to: **Productivity Collapse:** While a build is running, you can't effectively multitask. Your primary tool is essentially out of commission. **Physical Wear and Tear:** Running at maximum temperature for hours on end shortens the lifespan of your expensive hardware. **A Hostile Work Environment:** The constant, high-pitched whine of fans is distracting and stressful. **Inconsistent Environments:** The classic "it works on my machine" headache is often due to subtle differences in local setups, SDK versions, or environment variables. ### The Dedicated Workshop: A Windows VPS Think of your laptop as your clean, quiet office where you do your thinking and creative work. A Windows VPS is your off-site, heavy-duty workshop. It's a space filled with powerful machinery, designed for one purpose: to do the noisy, demanding work so your office can stay peaceful. When you connect to a Windows VPS using **Remote Desktop (RDP)**, you're greeted with the familiar Windows interface you already know. There's no complex command line to master. You can install your IDEs, your SDKs, your rendering software (everything you need) in a stable, isolated environment. This "workshop" is always on, always connected to the internet's backbone, and always ready for your toughest jobs. ### Your Workflow, Transformed: Who is This For? Offloading your builds is a game-changer for a huge range of professionals. #### Software & Game Developers This is a lifesaver. You can kick off a massive compile for your C++, .NET, or Java application on the VPS. While it churns away, your laptop remains fast and responsive for you to start working on the next feature. For game developers, you can offload hours-long tasks like compiling Unreal Engine, baking lighting, or packaging builds for different platforms, freeing you to continue designing your world. #### Video Editors & Content Creators Stop letting a 4K video render take over your life. Upload your project files to the VPS, start the render in Adobe Premiere or DaVinci Resolve, and disconnect. You can close your laptop and go to dinner. When you return, the render is done, and you can upload the finished file at blistering datacenter speeds. #### Architects, Engineers, & 3D Artists 3D rendering, complex simulations, and CAD processing are notoriously resource-intensive. A Windows VPS acts as your personal render farm, handling these demanding jobs in the background while you continue to design and model on a snappy local machine. #### Data Analysts & Scientists Running a long data processing script, a complex database migration, or training a smaller machine learning model can tie up your machine for hours. A VPS can execute these long-running tasks without interruption, even if your local Wi-Fi drops. ### The Simple, Elegant Workflow **1. Setup Once:** Connect to your VPS via Remote Desktop and install all your necessary tools: Visual Studio, Unity, Blender, your favorite IDEs and SDKs. **2. Sync Your Work:** Use a service like **Git**, Dropbox, or Resilio Sync to keep your project files synchronized between your laptop and the VPS. **3. Offload the Job:** When it's time for a heavy task, simply push your latest changes, connect to the VPS, and start the build or render. **4. Disconnect & Reclaim Your Freedom:** This is the magic step. Close the Remote Desktop connection. Your VPS continues to work at full speed. Your laptop is now completely free, cool, and quiet for you to use. **5. Retrieve the Result:** Once the job is done, simply grab the finished product (the application installer, the MP4 file, the final render) from the VPS. ### The Smartest Upgrade You Can Make Before you spend thousands on a new top-of-the-line laptop just to get a minor performance boost on your builds, consider the economics. A cheap Windows VPS gives you a dedicated, powerful build machine for a tiny fraction of the cost. You're not just buying a server; you're buying back your time, your focus, and the longevity of your primary machine. Stop waiting for the progress bar. Offload the load and set your productivity free. ### Comments ### Leave a Reply Your email address will not be published. Required fields are marked * --- ## Serverless vs. ServerMORE URL: https://vpsdime.com/serverless-vs-servermore-high-ram-vps Summary: The serverless dream becomes a nightmare for predictable workloads. Learn why a high-RAM VPS offers superior performance and cost control. ### Why a High-RAM VPS Crushes Lambda for Predictable Workloads ### Serverless vs. ServerMORE: Why a High-RAM VPS Crushes Lambda for Predictable Workloads Posted October 25th, 2025 by VPSDime The tech world is buzzing with a seductive promise: "serverless." It's the idea of a future where you simply write code, upload it as a function (like AWS Lambda), and it magically runs and scales without you ever thinking about a server. For certain tasks, it's a brilliant innovation. But for a massive number of real-world applications, this "serverless" dream can quickly become a nightmare of unpredictable costs, performance bottlenecks, and vendor lock-in. The truth is, for the vast majority of projects that aren't based on short, random bursts of traffic, you don't need *serverless*. You need **ServerMORE**. You need more control, more predictable performance, and more RAM for your money. You need a high-RAM VPS. ### The Serverless Promise: A Gig Worker for Your Code To understand why a VPS often wins, we first have to be honest about what a serverless function (like Lambda) actually is. Think of it like a gig worker you hire for a single, specific task. • You need a picture resized? You call the worker, they do the job in seconds, and they leave. You only pay for the few seconds they were active. • You don't pay for their downtime, their tools, or their commute. This is great for infrequent, event-driven tasks. But what happens when you need someone on standby, ready to work *instantly*, all day long? What if you need them to remember what they did five minutes ago? Hiring a gig worker for every single task, every single minute, would be absurdly expensive and inefficient. You'd just hire a full-time employee. A **full-time employee** is your high-RAM VPS. It's always on, always ready, and you pay a single, flat, predictable salary for its time, no matter how much or how little work it does in a given hour. ### The Achilles' Heel: Predictable Workloads A **predictable workload** is any application or service that needs to be consistently available and running. This describes the core of most web applications: • Your web server (NGINX, Apache) • Your application backend (Node.js, Python, PHP) • Your database (PostgreSQL, MySQL, Redis) • Your background job queue worker • Any long-running data processing script Running these on a "pay-per-millisecond" serverless model is where the logic breaks down and the costs explode. Here's why the "ServerMORE" approach of a high-RAM VPS is the superior choice. #### 1. The Dirty Secret of Serverless Pricing is Unpredictability Lambda's pay-per-use model sounds cheap until your workload becomes constant. A service that's always running is racking up billable milliseconds *every second of every day*. Your monthly bill becomes a terrifying variable that can spike without warning. A high-RAM VPS has a **fixed monthly cost**. It's the ultimate in predictable pricing. Whether your application serves 10 requests or 10,000 requests in an hour, you pay the exact same, budget-friendly price. You can run your database, web server, and background workers 24/7 for one flat fee, without ever fearing a surprise bill. #### 2. Performance: The "Cold Start" Problem and the Power of RAM Serverless functions suffer from "cold starts." If a function hasn't been used recently, the platform shuts it down. The next request has to wait for a new container to spin up, which can add hundreds of milliseconds or even seconds of latency. A process running on your VPS is always **"hot."** It lives in RAM, ready to respond instantly. This is where a high-RAM VPS becomes a performance beast. You can run your database and use the extra memory for a massive cache (like Redis), keeping your entire application's working set in memory for lightning-fast access. There are no cold starts, ever. Your performance is consistent and fast. #### 3. Freedom from the Straitjacket: No Limits, No Lock-in Serverless platforms impose strict limitations. AWS Lambda functions, for example, can only run for a maximum of 15 minutes. They have memory limits and package size limits. You are locked into their specific way of doing things. A VPS is a blank canvas. It is **stateful** by nature, meaning your applications can hold data in memory and run for as long as you want. • Need to run a data analysis script that takes 3 hours? No problem. • Want to use an obscure programming language or a specific Linux utility? You have root access. Go for it. • Need to open a persistent WebSocket connection? Easy. You are not renting a function; you are commanding a full server. #### 4. The Hidden Drain: Data Egress Costs A major, often overlooked cost of cloud platforms is "data egress", the fee they charge you to send data *out* of their network. If your application serves large files, generates reports, or provides data-heavy API responses, these egress fees can easily eclipse your compute costs. Most VPS providers, in contrast, offer enormous, multi-terabyte bandwidth allowances for a low, fixed price. You can serve terabytes of data without ever worrying about a surprise bill for just letting your users download their own data. ### When Does Serverless Still Win? To be clear, serverless is a powerful tool for the right job. It excels at being the "glue" between other managed services or for tasks that are truly infrequent and spiky: • Running a cron job once an hour to clean a database. • Generating an image thumbnail the moment it's uploaded to storage. • Handling a webhook from a third-party service that is called unpredictably. For these "gig worker" tasks, it's a perfect fit. ### Conclusion: Choose the Right Tool for the Job The "serverless-first" mantra is a great marketing slogan, but it's poor engineering advice. For the vast majority of applications with predictable, always-on workloads, the "ServerMORE" philosophy of a high-RAM VPS is undeniably superior. It offers predictable costs, consistently high performance without cold starts, absolute freedom from limitations, and protection from exorbitant data egress fees. Don't pay by the millisecond for a full-time job. Buy the "full-time employee" (a powerful, cost-effective, high-RAM VPS) and build your application on a foundation of stability and common sense. **Whether you need a solid starting point with 4GB or 6GB of RAM, or the massive power of a 288GB RAM beast, there's a cost-effective plan ready to become your project's permanent home here at VPSDime.** ### Comments ### Leave a Reply Your email address will not be published. Required fields are marked * --- ## How to Host Your Side Hustle Project URL: https://vpsdime.com/host-side-hustle-cheap-vps Summary: Stop letting cost kill your dreams. Launch your side hustle on a powerful VPS for the price of a coffee. Five proven business models included. ### On a Cheap VPS ### How to Host Your Side Hustle Project on a Cheap VPS Posted October 24th, 2025 by VPSDime You have it. That brilliant idea that keeps you up at night. A micro-SaaS to solve a niche problem, a powerful blog to build your brand, a portfolio to showcase your skills, or an online tool for your community. It's a great idea. It could be *the* idea. But then, the voice of doubt creeps in. *"How much is this going to cost me? What if it fails? I can't afford to sink hundreds of dollars into a project that might go nowhere."* And so, the idea is shelved. It joins the graveyard of countless other brilliant side hustles, killed not by a lack of passion, but by the perceived cost of entry. What if that cost wasn't a hundred dollars? What if it wasn't even twenty? What if you could give your dream a real home on the internet, with a real server and a real IP address, for about the price of one fancy coffee a month? You can. It's time to talk about the cheap VPS. ### The Myth of the Expensive Launch Let's get one thing straight: the idea that launching a serious project online is expensive is a relic of the past. We've been conditioned by high-priced "pro" level SaaS plans, complex cloud calculators from giants like AWS, and managed hosting plans that cost a fortune. These tools have their place, but they are often massive overkill for a new side hustle. You don't need a cannon to hunt a rabbit. You need a simple, reliable, and powerful tool that gives you everything you need and nothing you don't. That tool is a low-cost Virtual Private Server (VPS). For around **$5 a month**, you get your own private, blank canvas on the internet. ### The Powerhouse in Your Pocket: What a Cheap VPS *Actually* Is A cheap VPS isn't a "lesser" server. It's a *concentrated* one. It's a private, isolated slice of a much more powerful physical server, running in a professional datacenter with blazing-fast internet speeds. When you buy that $5 plan, you are not getting a toy. You are getting a professional toolkit. Here's what's really in the box: **A Professional-Grade Operating System:** You get to install a mainstream, powerful Linux distribution like Ubuntu or Debian, the same operating systems that power a massive portion of the internet's most serious websites and applications. **Root/Administrator Access: The Keys to the Kingdom:** This is the single most important feature, and it's something you'll never get on shared hosting. Root access means you have 100% control. You can install any software, edit any configuration file, and run any service you want. There are no artificial limits. The only limit is your imagination. **A Dedicated Public IP Address: Your Stake in the Ground:** This isn't a temporary or shared address. It is your project's permanent, unique address on the global internet. This is essential for running professional services, hosting a game server, pointing a domain name cleanly, or ensuring your API is always reachable at the same spot. **Datacenter-Grade Connectivity: The Internet Fast Lane:** Your home internet is slow for uploads. A datacenter is the heart of the internet. Your VPS is connected at incredible gigabit speeds, both for downloads and uploads. This means your website serves pages instantly, your file uploads take seconds instead of hours, and your applications are incredibly responsive. **24/7/365 Availability: Your Tireless Employee:** Your VPS runs on enterprise-grade hardware with redundant power and cooling, designed for constant operation. While your laptop sleeps, your server is awake, running your code, serving your customers, and working for you around the clock. **Total Software Freedom: No Walled Gardens:** On other platforms, you're locked into their ecosystem. On your VPS, you're free. Want to run a specific version of a database? Need a niche programming language? Want to host an obscure open-source application? You can. You don't need to ask for permission. If it runs on Linux, it runs on your VPS. **A Clear Path to Scale: Room to Grow:** What happens if your side hustle explodes in popularity? On a VPS, you're not stuck. You can typically upgrade your plan to add more CPU, RAM, or storage with just a few clicks, often without a complex migration. You can start small and grow seamlessly. ### What Side Hustles Can You *Actually* Build on a $5 Server? You'd be shocked by the power packed into such a small investment. A cheap VPS isn't just for hosting a personal blog; it's a launchpad for automated, money-making engines. The key is to choose a project that is resource-efficient and can work for you in the background. Here are five proven side hustle models that are a perfect fit for a low-cost VPS: #### 1. The Niche Affiliate Blog or Review Site A classic for a reason, the niche affiliate blog is a perfect entry point into online business. You can choose a passion, like "sustainable coffee gear" or "retro gaming accessories," and build a site that generates passive income through affiliate links from places like Amazon Associates. As your library of helpful reviews and articles grows, so does your potential for 24/7 earnings. This model is exceptionally well-suited for a cheap VPS, where a lightweight WordPress setup or a static site generator can handle massive traffic spikes with minimal resources, giving you full control over your brand without the limitations of free platforms. #### 2. A "Micro-SaaS" Monitoring Service The most powerful side hustles solve a small, annoying problem, and a "Micro-SaaS" monitoring service does just that. You can build an automated service that checks other people's websites every few minutes and charges a small monthly subscription fee to send an email or Telegram alert when a site goes down. This is the ultimate "set it and forget it" business, perfectly suited for a cheap VPS. By installing free, open-source software like Uptime Kuma, you can run a reliable service that uses almost no resources, effectively turning your server's own 24/7 uptime into the very product you are selling. #### 3. A Paid Community Newsletter or Forum People will pay for access to exclusive communities and high-value, curated information. By launching a paid newsletter or private forum on your own VPS, you can build a recurring revenue stream from monthly or yearly subscriptions. This approach is far more profitable than using platforms like Substack or Patreon, as you avoid their hefty fees. Efficient, modern software like Ghost for newsletters or Flarum for forums runs beautifully on a low-cost server, allowing you to own the platform, the email list, and the direct relationship with your audience, a truly sustainable business asset. #### 4. A Specialized API as a Service If you have some coding skills, you can turn a simple script into a recurring revenue stream by offering a specialized API as a service. Think of an API that provides a "quote of the day," aggregates local event data, or offers a unique financial data lookup. You can offer a free tier to attract users and then charge a monthly subscription for higher usage, using platforms like RapidAPI to handle the billing. This business model is incredibly efficient for a cheap VPS, as a well-written API endpoint is extremely lightweight and only consumes resources when a request is made, making it a highly profitable use of your server. #### 5. A Niche E-commerce or Dropshipping Store Instead of paying high monthly fees to platforms like Shopify, you can launch your own powerful e-commerce or dropshipping store with complete control. By focusing on a specific niche, you can stand out from the competition and build a dedicated customer base. This model makes money through direct product sales, and with dropshipping, you don't even need to hold your own inventory. Hosting your store on a cheap VPS using free, open-source software like WooCommerce for WordPress is a smart financial move. You completely avoid recurring platform fees, meaning a much larger portion of the profit from every single sale goes directly into your pocket. ### The Mindset Shift: From Renter to Owner Perhaps the biggest benefit isn't the cost savings, but the shift in mindset. When you use a restrictive platform, you are a renter, living by someone else's rules. When you use a VPS, you become an owner. Every task, from setting up a web server to configuring a firewall, teaches you real, valuable, and highly marketable skills. You are not just building a project; you are building your own expertise. You are not locked into an ecosystem. You have the freedom to innovate, to experiment, and to build a solution that is perfectly tailored to your vision. ### The Financial Risk is Gone. What Are You Waiting For? The fear of high running costs is no longer a valid excuse. For just a few dollars, you can remove the biggest barrier to entry and give your idea a fighting chance. If the project fails, you've lost less than the price of a movie ticket. But if it succeeds, you've built the foundation of your future on the most cost-effective platform imaginable. Stop letting your brilliant ideas die on the vine. For the price of a coffee, you can buy a workshop, turn on the lights, and start building. ### Comments ### Leave a Reply Your email address will not be published. Required fields are marked * --- ## Design for Failure, Sleep Through the Night URL: https://vpsdime.com/the-beehive-approach Summary: Stop building monolithic systems that fail catastrophically. Learn how to create resilient, self-healing infrastructure using clusters of cheap VPS. ### The Beehive Approach to High Availability ### Design for Failure, Sleep Through the Night: The Beehive Approach Posted October 21st, 2025 by VPSDime In the world of digital infrastructure, there are two prevailing philosophies for building a reliable service. The first is the Blue Whale. It's an all-in-one, monolithic marvel: the single largest, most powerful, and most expensive server or cloud instance you can afford. It is majestic and immensely capable. But if that one whale gets sick, everything stops. Its sheer size becomes its greatest vulnerability. Then, there is the Beehive. It is a decentralized, resilient collective built from thousands of small, cheap, and expendable units. A worker bee is born, serves a specific purpose, and eventually dies. When one bee fails, the hive doesn't even notice. Another one is born, or another existing worker takes its place, and the core function of the hive (protecting the queen and producing honey) continues without interruption. The system's strength lies in its distributed nature, not in the power of any single component. This is the new paradigm for reliability. Stop trying to build an unsinkable whale. It's time to build a self-healing beehive with a cluster of cheap VPS. ### Do You Have Enough Nines in Your Uptime? In our always-online world, "downtime" is a business-ending word. The reliability of a service is measured in "nines" of uptime. **99% Uptime ("Two Nines"):** This sounds good, but it means your service can be down for over 3.6 days a year. **99.9% Uptime ("Three Nines"):** Better, but still allows for almost 9 hours of downtime annually. **99.99% Uptime ("Four Nines"):** Now we're talking. This is just under 1 hour of downtime per year. **99.999% Uptime ("Five Nines"):** The gold standard. A mere 5 minutes of downtime per year. For an e-commerce store, five minutes of downtime during a holiday sale can mean thousands in lost revenue. For a SaaS application, it means broken workflows and angry customers canceling subscriptions. For a gamer, it means getting kicked from a match-winning moment. Achieving as many nines as possible isn't just a technical goal; it's a critical business necessity. ### Why You Need High Availability Imagine this: It's 3 AM. You're finally in a deep sleep after an exhausting week. Suddenly, your phone erupts with alerts. Your main server is down. Your website, your application, your entire business is offline. You stumble to your computer, heart pounding, adrenaline surging, and begin the frantic, desperate search for a solution while angry customer emails pile up. Now, imagine the alternative. The same server hardware fails at 3 AM. An automated alert gently pings your phone: "Node WEB-03 failed. Health checks failed. Traffic rerouted to WEB-04. System self-healed. Service uptime: 100%." You see the message, roll over, and go back to sleep, confident that the beehive handled the problem on its own. That peace of mind is what high availability (HA) gives you. It's a design philosophy that anticipates failure and makes it irrelevant. ### The Enemy: The Single Point of Failure The goal of high availability is to eliminate any Single Point of Failure (SPOF). A SPOF is any component in your system whose failure will cause the entire system to stop working. Think of an escalator versus a set of stairs. The escalator is a complex, convenient machine, but if the power goes out or a gear breaks (a SPOF), it becomes useless. The stairs, however, are a simple, redundant system. If one step breaks, you can just step over it. The stairs will always get you where you need to go. Your goal is to build digital stairs, not a digital escalator. To do this, you need redundancy, having more than one of everything critical. ### How to Build Your Beehive with a Bunch of Cheap VPS Building a high-availability system sounds complex, but it boils down to creating redundancy at four key layers. Here's how you can do it with a cluster of affordable VPS. #### Load Balancers (The Hive Entrance) This is your traffic controller. A load balancer is a VPS that does nothing but receive incoming user requests and distribute them to a pool of "worker bee" web servers. **How it works:** It constantly runs health checks on your web servers. If one server stops responding, the load balancer instantly stops sending traffic to it and directs it to the healthy ones. **Tools:** HAProxy is a purpose-built, incredibly fast load balancer. NGINX can also be configured to act as a powerful load balancer. #### File-Level Replication (The Shared Mind) All your worker bees need to have the exact same files. If a user uploads a profile picture to one web server, all the other web servers need to see that picture instantly. **How it works:** You create a distributed file system that spans across multiple VPSs, making them all act as one giant, synchronized hard drive. **Tools:** GlusterFS is a powerful tool for this. A simpler, lighter-weight option is lsyncd, which watches for file changes and uses rsync to immediately replicate them to other nodes. #### Database Replication (The Shared Memory) This is often the most critical layer. If your database goes down, your entire application is useless. You need a database that can survive the loss of a server. **How it works:** You create a database cluster where every node contains an identical, up-to-the-second copy of the data. You can write to any node, and the change is instantly replicated to all others. **Tools:** MariaDB Galera Cluster is the gold standard for easy-to-configure, multi-master replication. If one database VPS dies, the other two continue operating without missing a beat. #### DNS Failover (The Emergency Relocation Plan) What if the entire datacenter where your beehive lives goes offline? This is where DNS failover comes in. **How it works:** You run your own redundant DNS servers in different geographic locations. If your primary cluster is unreachable, your DNS system can automatically update your domain's records to point all traffic to a backup "hive" in another datacenter. **Tools:** You can build a resilient DNS cluster using open-source software like PowerDNS with database replication. #### The Beehive Just Works When you combine these layers, you create a truly resilient system. The load balancer acts as the guard bee, directing visitors to healthy workers. The replicated file systems and databases act as the hive's shared consciousness, ensuring every bee has the same information. When a worker VPS inevitably fails (due to a hardware issue, a software bug, or routine maintenance), the system doesn't panic. It was designed for this. The load balancer seamlessly redirects the workload, and the other bees simply pick up the slack. The hive continues to buzz along, producing honey for your users, entirely unaware that a single worker has perished. You can finally stop worrying about that 3 AM phone call and let your beehive do the work. At [VPSDime](https://www.vpsdime.com), we provide the affordable, high-resource VPS infrastructure that's perfect for building your own resilient beehive. Our reliable servers are ideal worker bees: powerful enough to handle production workloads, affordable enough to deploy in clusters, and independent enough to provide true redundancy. ### Comments ### Leave a Reply Your email address will not be published. Required fields are marked * --- ## The Myth of Infallibility URL: https://vpsdime.com/aws-outage-the-myth-of-infallibility Summary: The AWS outage of October 20 proved that vendor lock-in is a critical risk. Learn how a cheap VPS failover strategy can protect your business from downtime. ### Why Today's AWS Outage Proves the Value of Hybrid Infrastructure ### The Myth of Infallibility: Why Today's AWS Outage Proves the Value of Hybrid Infrastructure Posted Monday October 20th, 2025 by VPSDime If your dashboards are red and your support channels are flooded this evening, you're not alone. The massive AWS outage on October 20, 2025, has plunged a significant portion of the internet into a state of digital silence. For countless businesses, today was a brutal lesson in a simple truth: putting all your eggs in one basket, no matter how strong that basket seems, is a recipe for disaster. Many companies that went down today weren't just using AWS for hosting; their entire operation was woven into its ecosystem. When the outage hit, they couldn't serve their website, their app was down, and worse, they couldn't even communicate the problem to their customers because their email service, AWS SES, was also offline. They had no backup plan. No failover. They had total faith in the myth of infallibility. This isn't about blaming AWS. Failures in systems of such immense complexity are inevitable. This is about asking a critical question: What is your Plan B? For a growing number of savvy developers and businesses, the answer isn't a second, equally complex cloud region. It's a simple, robust, and radically independent sleeper failover, often in the form of a cheap VPS. ### The Cascading Failure of the "All-In" Approach Today's outage demonstrated the critical flaw of vendor lock-in. When a core service like networking or authentication fails in a hyperscale cloud, it triggers a domino effect: Your website goes down. Your backend API stops responding. Your database becomes unreachable. Your email provider (SES) can't send status updates. Your logging service (CloudWatch) can't tell you what's wrong. Your entire business is paralyzed by the failure of a single, external vendor. A hybrid infrastructure approach, however, builds resilience by creating intentional separation. ### The Power of a "Sleeper Failover" VPS A "sleeper failover" is a low-cost server that sits outside your primary infrastructure, waiting to be activated in an emergency. It's your digital lifeboat. A high-resource, cheap VPS is the perfect candidate for this role for several key reasons: **True Independence:** It runs on a completely different network, in a different datacenter, under a different provider. It is insulated from your primary system's failures. **Predictable Cost:** A failover VPS costs a simple, flat monthly fee. It's an incredibly affordable insurance policy against the thousands, or even millions, in lost revenue from downtime. **Simplicity and Control:** A standard Linux VPS has no complex dependencies. You have root access and full control to run a lean, reliable emergency stack. ### Four Practical Failover Strategies You Can Set Up This Week Instead of just worrying about the next outage, here's how you can use a cheap VPS to prepare for it. #### 1. The Status Page Hub The most basic and crucial step. Host a simple, static HTML status page on your VPS. When your main site goes down, you can instantly update your customers via social media with a link to a page that actually works, explaining the situation. This alone can save your brand's reputation during a crisis. #### 2. The Email Lifeline Today, companies couldn't email their users because SES was down. By configuring a simple Postfix mail relay on your VPS, you create a backup email route. With a quick configuration change, your application can switch to this relay to send critical password resets and status updates, maintaining communication when it matters most. #### 3. The DNS Failover Target Using a service like Cloudflare, you can set up automated DNS failover. When Cloudflare detects that your primary AWS server is unresponsive, it can automatically redirect all traffic to a scaled-down, "emergency mode" version of your site or application hosted on your VPSDime server. This can happen in under 60 seconds, saving you from a total outage. #### 4. The "Skeleton Crew" Application For mission-critical services, you can host a read-only or limited-functionality version of your application on the VPS. If your main e-commerce site goes down, the failover version could still allow users to browse products and see contact information, which is infinitely better than a blank error screen. #### Stop Believing in Myths, Start Building Resilience Today's AWS outage wasn't a freak accident; it was a predictable event in an unpredictable system. The lesson is clear: reliance is a liability. It's time to stop thinking of your infrastructure as a single choice and start thinking of it as a strategic portfolio. A cheap, high-resource VPS isn't just an alternative to the cloud; it's the perfect partner for it. For a tiny fraction of your monthly cloud spend, you can purchase the one thing a single vendor can never sell you: genuine resilience. At [VPSDime](https://www.vpsdime.com), we understand that reliability doesn't have to come with a premium price tag. Our affordable VPS plans are designed to be your perfect failover partner: simple, powerful, and truly independent from the major cloud providers. ### Comments ### Leave a Reply Your email address will not be published. Required fields are marked * --- ## Benefits of VPS URL: https://vpsdime.com/benefits-of-vps Summary: Find out advantages of using a VPS over a dedicated server ### What are the advantages of VPS over a dedicated server? ### What are the benefits of using a VPS over a dedicated server? Posted Monday September 5th, 2021 by VPSDime Ever since the first computers were introduced to the world, we've been using them to store and process data. As technology has evolved, so have our needs for storage and processing power. The most convenient way of utilizing the power of computers is renting them from hosting providers. With many different kinds of hosting services being available, dedicated servers are the most popular ones among all. This article will explore the benefits of VPS over dedicated servers so that you can make an informed decision about which one best suits your needs! ### Definitions A dedicated server is a type of hosting where the client receives access to a physical server located in a data center. By renting a dedicated server, you are basically committing the management and maintenance of hardware. A VPS, on the other hand, is a completely virtualized service. A VPS acts like a dedicated server and most of the time you won't see any difference. By renting a virtual server service, you are receiving access to a software running on a physical server. ### VPS's are cheaper than dedicated servers. Dedicated servers were the most common service for private hosting before virtualization technologies came along. Virtualization altered everything, making private hosting accessible at an affordable price. You may now rent a VPS for a fraction of the price of a dedicated server these days. Providers like us are able to provide a bare-metal like performance at an inexpensive cost by utilizing virtualization. As a result, you get an inexpensive entry into the industry for your start-up. ### You don't have to deal with hardware layer. When you rent a dedicated server, you are generally expected to troubleshoot hardware issues yourself and let the provider know to come up with a solution. Instead, a VPS entails that the web hosting company takes care of all hardware maintenance. It's provider's responsibility to make sure the VPS you receive is always up and running. This lets you sleep better at night and frees up more time to focus on your business. ### VPS's are scalable. When your application or website starts to attract more audience, you are going to have to upgrade your server to handle the resource demand. Upgrading a dedicated server is not easy and will require scheduled maintenance which means downtime for your visitors. A virtual machine can be easily upgraded or downgraded within a few seconds. One of the greated advantages of our Linux VPS product line allows on-the-fly scaling. This means that the upgrades and downgrades can be done without any interruption or downtime -- even rebooting isn't required! ### Fast deployment and mobility. VPS's can be deployed and relocated quickly. This implies that you may rapidly set up a VPS. They may be transferred to another location in a matter of minutes. It's not cost-effective to relocate a dedicated server. This implies you'll have to establish a new dedicated server in the new location and then restore your data from backups. ### Easy and worry-free backups. Taking a backup of your VPS is also very straight-forward. Because the storage system behind it is also virtualized, a backup of your VPS can be taken without any interruption of your running system. On the other hand, taking a backup of a dedicated server will need more intricate solutions or expensive backup software to avoid the backup process affecting your application. ### VPS's are environment friendly. The topic of eco-friendly technology and green hosting has been gaining popularity for a few years now. In order to reduce our carbon footprint as much as possible, we need to do everything that we can in this regard. Utilizing a VPS instead of a dedicated server can help you with this goal. If you have a dedicated server, it means that your business or personal network is the only one benefiting from all of its power consumption. When you choose a Virtual Private Server, the resources of an actual physical server are shared among several virtual environments. This allows more people to share these important resources, and it ensures that they're being used in an optimal manner. #### Conclusion We hope you have found this information helpful as it provides a lot of insight into the advantages of using a VPS instead of a dedicated server. In conclusion, we would like to say that by purchasing a [cheap VPS](https://www.vpsdime.com), you can save money and be worry-free about your hardware layer. You will also get online faster and upgrade or downgrade easily with less complexity in data backup! By reducing your carbon footprint, you are doing something great for our planet! ### Comments ### Leave a Reply Your email address will not be published. Required fields are marked * --- ## Windows VPS Use Cases URL: https://vpsdime.com/windows-vps-use-cases Summary: Windows VPS Use Cases: What can a cheap Windows VPS do for you? ### What can a cheap Windows VPS do for you? ### Windows VPS Use Cases: What can a cheap Windows VPS do for you? Posted Monday September 4th, 2021 by VPSDime Windows is one of the most popular operating system used for millions of professionals every day. By using a powerful and cheap Windows VPS, you could enjoy a lot of benefits. They can be used for a variety of purposes whether you are a start-up company owner or a university professor. This article will cover some of those Windows VPS use cases so you can decide if you need one. ### A little bit of history. Microsoft has created a server optimized version of Windows operating system in 1993 and called it Windows NT Advanced Server 3.1. This version was mostly used for small office computers providing computing power with the great user interface Microsoft is famous for. Fast forward 7 years, after a few versions in between, Microsoft has announced Windows Server 2000 and introduced technologies like Active Directory and Group Policy which helped increasing productivity in data center and office environments. However it made its big jump in 2008 with the Microsoft's own virtualization technology called Hyper-V. ### What is Hyper-V? Hyper-V is a microkernel based virtualization hypervisor which is natively integrated with Windows. It was first released as a beta in 2008 for Windows Server 2008 and it is available since then on all Windows server editions. ### What is a Windows VPS? A virtual server that arrives with a version of Windows Server operating system is called a Windows VPS. The best platform for this type of service is to use Hyper-V in order to host the machine on top of one more dedicated servers, as they provide better performance and stability than other technologies like KVM as the operating system running on the host integrates with the operating system running on the VM. ### Great for development With its native support for Microsoft technologies like .NET Framework and Microsoft SQL server, Windows VPS acts as an ideal platform for Microsoft oriented development and testing. It is especially useful for big projects with a huge number of Windows components, when the need to deploy and test in real life conditions arises. ### Can be used as a remote office computer By renting a cheap Windows VPS, you can easily create yourself a remote working computer environment. Simply install the required software and connect to it remotely. This is particularly handy if you are working remotely. Your working environment will be available and running at all times in a data center environment with a fast and stable internet connection. Especially if you are a digital nomad, your files will be safe and protected from hackers and viruses. ### A testing bed for Windows updates If you are running Windows on your projects, it is good practice to keep your Windows installation up-to-date with Windows service packs and Windows updates. However, if you do not have a dedicated computer for this purpose or it does not fit into your budget - renting cheap Windows VPS will provide you with the benefit of testing updates before doing them on your regular environment. ### Second computer with Windows If you are using Linux, MacOS or BSD systems on your day to day operations, you know that some applications and software are only designed for Windows operating system. Purchasing a low-cost Windows VPS will let you run Windows-specific applications on your own computer without the need for emulators. ### Windows Web Server (IIS) and Windows Database Server IIS has been one of the most popular hosting systems for websites and applications that are running .NET based backend. Microsoft SQL server is also a great alternative to Oracle. #### As a Backup Server If you are running a business, it is critical that you have an effective backup solution for all your data files and documents in case of disaster recovery scenarios. Many businesses use Windows servers as their primary back-up servers because of their ease of use. #### For Game Servers Many game developers create their multiplayer games on windows based platforms and use windows server to host them on IIS web server layer. There are many benefits of hosting the game servers on Windows environment rather than Linux. #### For Docker Windows Server 2025 ships with the Nano Server container image, a minimalistic headless build of Windows capable of running Docker containers in production grade environments with high density deployments where every MB counts! In this way, windows reduces its attack surface drastically along with resource footprint resulting into much efficient infrastructure compared to Linux counterparts. #### As an Automation Tool Another use case of an economical Windows VPS is the ability to run various automation tools that rely on Windows command line or Powershell extensions. With Windows's amazing GUI, users are always at an advantage for productivity compared to Linux counterparts that are more command line oriented. #### For Forex Trading If you want to operate a completely 24/7 online stock trading business, a Windows VPS is the way to go. You will never have internet difficulties, hardware failure, power outages, or other problems like that when you use a VPS. Anyone can easily install a Forex trading software like MetaTrader and enjoy the benefits of having a stable connection to the trade centers of the world. #### For Running SEO Tools Most SEO tools such as GSA, and Scrape box are built for Windows operating system. With an easily deployable [cheap VPS](https://www.vpsdime.com), your SEO tool business will be running smoothly. #### Conclusion As you can see, Windows VPS has a lot of use cases and we have listed only a few. Microsoft has definitely created a great product with a lot of innovative technologies tied with it. VPSDime offers the best bang for your buck for your Windows VPS needs. Check our [Windows VPS](https://vpsdime.com/windows-vps) product line page to compare our plans and purchase one today. ### Comments ### Leave a Reply Your email address will not be published. Required fields are marked * --- ## Cheap and Reliable VPS URL: https://vpsdime.com/can-a-cheap-vps-be-reliable Summary: Find out if you can get a cheap vps that is also reliable. ### Can a cheap VPS be also reliable? Posted Monday September 3th, 2021 by VPSDime Virtualization is the technology behind VPS's. Hypervisor software takes the physical resources of a server and divide them up so that virtual environments can use them. It simulates a physical server environment to the operating system it runs and the end user faces this interface as it's a real server. ### Argument With the virtualization revolution, the cost of renting a private server reduced quite a bit. With the constant decline of prices for hardware, more and more companies are able to provide VPS hosting at a low cost. Many people are looking for VPS services with the idea that cheap is bad. They think that if it is cheap, then it must be unreliable and not up to their standards. The truth is, [cheap VPS](https://www.vpsdime.com) services can still be reliable and save you a lot of money while performing just like an expensive VPS. ### Challanges There are some challenges for a web hosting company to be able to offer a VPS at an affordable cost while keeping its services reliable and enterprise ready. Owning some or all of the infrastructure can help an organization maintain lower recurring costs in the long term, as it is cheaper than leasing. At first this means that companies will have to spend more money on these items but they are able to make larger profits later on because their expenditures are smaller and predictable. Another expensive asset which increases the costs is IP address space. IP addresses are a limited supply. Like any limited supply in the world, their prices are going up each day. If the hosting company is not renting someone else's IP space, they are going to get affected by the increased costs over time. The software used to provide the VPS hosting service is another important expense which affects the prices. Licensing costs of such software can really set a provider back and add up in costs to pass to its customers. To help with on-going costs, a company save a lot by maintaining this software in-house built on top of an open source software. This way the company can both help the improvement of the open source software while increasing their reputation by offering more advanced features to their customers. This allows them to offer cheaper services than potential competitors who have to pay on-going licensing costs for the software. Manual labor is the most expensive part of a company who offers VPS to its customers. To avoid doing manual labor, the company should work on having most of its operations automated. Installing and configuring of a VPS host system, when done manually takes hours, while having an automated software do it would only take a few minutes and will save the company costs of having this done by a human. The key to provide reliable VPS services is having a smoothly running infrastructure. The hypervisors should be running problem-free and all the issues arise should be taken care of as soon as possible. The systems should not be over-loaded and avoid causing performance issues to the customers. All of this when done with hand would take a lot of resources. When automated monitoring of the systems is utilized, it may save a lot of time and money for the business while also ensuring that the infrastructure is always healthy. #### Conclusion As you can see, when done right, a cheap VPS can be perfectly reliable and help you save a lot of costs. Of course this can be accomplished by a properly managed company with ample capital and highly skilled staff, as well as a software development department that is entirely dedicated to developing solutions. For the past 8 years, we at [VPSDime](https://www.vpsdime.com) have been living proof of it. All of our VPS plans are affordable, highly available and optimized for speed. ### Comments ### Leave a Reply Your email address will not be published. Required fields are marked *