<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Richard Detering on Medium]]></title>
        <description><![CDATA[Stories by Richard Detering on Medium]]></description>
        <link>https://medium.com/@richarddetering?source=rss-90b1ad79f0ba------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*t6o-SaXCdp52vnhXCKdtzg.png</url>
            <title>Stories by Richard Detering on Medium</title>
            <link>https://medium.com/@richarddetering?source=rss-90b1ad79f0ba------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:26:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@richarddetering/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Liquid Web’s Cancellation Trap: The Nightmare Behind Leaving Them!]]></title>
            <link>https://richarddetering.medium.com/liquid-webs-cancellation-trap-the-nightmare-behind-leaving-them-65ee7e20467d?source=rss-90b1ad79f0ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/65ee7e20467d</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Richard Detering]]></dc:creator>
            <pubDate>Thu, 05 Nov 2026 12:56:31 GMT</pubDate>
            <atom:updated>2026-11-05T12:56:31.640Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*armBbMV2gwUYtpAI" /><figcaption>Photo by <a href="https://unsplash.com/@tvick?utm_source=medium&amp;utm_medium=referral">Taylor Vick</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Mark had been running a small online business for several years. Nothing fancy, just a website selling outdoor equipment and camping supplies. It was doing reasonably well, but things had changed. Sales were down, expenses were going up, and he was spending too much money on hosting.</p><p>He was paying $200 a month for a dedicated server at Liquid Web. It had been a good solution when his business was bigger, but these days he didn’t really need that much power.</p><p>He found another hosting company that offered a suitable server for less money. The decision was easy. He would move his website and cancel Liquid Web.</p><p>At least, that’s what he thought.</p><p>On Friday evening, he logged into his LiquidWeb account and started looking for the cancellation option. He found his server, opened the menu and saw something called “Destroy Server.”</p><p>Destroy? That sounded a bit dramatic just to cancel a hosting subscription.</p><p>He stopped and decided to investigate before clicking anything.</p><p>That was probably the best decision he made all week.</p><p>First, he discovered that destroying a server is permanent. Once removed, the files and databases stored on it cannot be recovered through the normal account portal. Any websites, customer information, emails and other important data on that server are at risk.</p><p>He also discovered that associated services, including certain backup and DDoS protection add-ons, can be removed along with the server.</p><p>Mark had been keeping backups on the same server. Suddenly, that didn’t seem like such a clever idea.</p><p>It’s like keeping your spare house key inside the house. It won’t help much when you’re locked out.</p><p>He contacted his new hosting company and arranged the transfer. He downloaded his website files, exported the databases and saved his important emails. He also made another backup and stored it somewhere completely separate.</p><p>Then he transferred a copy of his website to the new server and tested everything. The website worked, the shopping cart was fine, and his email was receiving messages.</p><p>Only then did he feel comfortable moving on.</p><p>But there was another problem waiting for him.</p><p>While checking his Liquid Web contract, Mark discovered that cancellation wasn’t quite as simple as stopping a monthly payment. The company had specific rules about automatic renewals and early termination.</p><p>According to the Terms of Service, customers must provide at least 30 days’ written notice before the end of their current service term if they don’t want the contract to renew automatically.</p><p>There was also something more unpleasant.</p><p>If a customer terminates a flat-rated service early, the charges can include 100 percent of the remaining monthly fees.</p><p>Mark sat back in his chair and did some calculations.</p><p>Imagine paying $200 every month with six months still remaining on your contract. That would mean another $1,200 in monthly charges alone.</p><p>That’s a nasty surprise when you’re trying to save money by changing hosting companies.</p><p>He wasn’t ready to pay that kind of money just to leave.</p><p>He contacted the Billing Department and asked for an exact calculation of his remaining contractual obligations. He also checked his original order because individual service agreements can contain terms that take priority over the general Terms of Service.</p><p>With six months still remaining on his contract, Mark realized that canceling immediately could cost him another $1,200. He wasn’t willing to throw that kind of money away. Instead, he decided to move his website to the new hosting company but keep his Liquid Web account active until the contract expired. He could then avoid the early termination charges by allowing the existing contract to run its course and making sure Liquid Web received his non-renewal notice at least 30 days before the expiration date.</p><p>But then Mark discovered something that really annoyed him.</p><p>The Terms of Service contained a requirement stating that formal termination notices had to be sent by U.S. mail or commercial courier.</p><p>Yes, a physical letter.</p><p>In 2026!</p><p>He could order hosting online, manage his server online, pay his bills online and communicate with Support online. But when it came to formal termination notices, Liquid Web specified a postal letter.</p><p>The address was:</p><p>Liquid Web, LLC<br>2703 Ena Drive<br>Lansing, MI 48917<br>USA</p><p>Attention: General Counsel.</p><p>Mark couldn’t believe it. He had never experienced anything like that with an online service before.</p><p>He also discovered that Liquid Web’s Help Center instructed customers to use an online Support case to close their entire account. The contract and the online instructions didn’t clearly explain how these two procedures worked together.</p><p>He wasn’t going to take any chances.</p><p>He prepared a written cancellation notice, explaining that he didn’t want his services renewed. He sent it by tracked mail and kept the delivery receipt. At the same time, he opened a Support case and asked for written confirmation of the cancellation date and any remaining charges.</p><p>He also made sure that the request was treated as non-renewal rather than early termination. There is a big difference between the two.</p><p>There was still one more thing to take care of.</p><p>His domain name was registered through Liquid Web. He didn’t want to lose it just because he was changing hosting companies.</p><p>He started the outgoing domain transfer through the customer portal. Liquid Web unlocked the domain and provided an EPP authorization code. That’s simply a special code that allows another registrar to accept the transfer.</p><p>Once the new registrar had control of the domain, Mark felt much better.</p><p>A few days later, he received confirmation from Support. He checked his billing information, saved the correspondence and made sure there were no other active services he had forgotten about.</p><p>It had taken considerably more work than he expected, but at least he now knew where he stood.</p><p>Looking back, Mark thought the whole process could have been much easier. A hosting company should not make cancellation more difficult than purchasing its services. Customers shouldn’t have to send physical letters across the world to cancel online services.</p><p>And automatic renewals and cancellation fees should be clearly explained before people commit to a contract, not become an expensive surprise when they decide to leave.</p><p>In the end, Mark moved his website successfully, kept his domain name and avoided the unexpected early termination bill.</p><p>He also learned something he wouldn’t forget: Never click a cancellation button before reading the contract and protecting your data.</p><p>For anyone facing a similar situation, he found a <a href="https://hostiful.net/how-to-cancel-liquid-web-please-note-risks-involved/">useful explanation of the LiquidWeb cancellation process</a> that helped him understand what to check before making the final move.</p><p>This time, Mark knew exactly what he was up against, protected his data, and escaped the costly cancellation trap Liquid Web had deliberately built into its contract.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65ee7e20467d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[She almost lost a $2,400 order by canceling her web hosting]]></title>
            <link>https://richarddetering.medium.com/she-almost-lost-a-2-400-order-by-canceling-her-web-hosting-4a6db64fe3a2?source=rss-90b1ad79f0ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a6db64fe3a2</guid>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[web-hosting]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[website-design]]></category>
            <category><![CDATA[internet]]></category>
            <dc:creator><![CDATA[Richard Detering]]></dc:creator>
            <pubDate>Thu, 29 Oct 2026 12:16:45 GMT</pubDate>
            <atom:updated>2026-10-29T12:16:45.263Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7N7w45gQZ_qnlIXe" /><figcaption>Photo by <a href="https://unsplash.com/@howardbouchevereau?utm_source=medium&amp;utm_medium=referral">Howard Bouchevereau</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Julie was sitting at her kitchen table when she decided she’d had enough of HOSTAFRICA.</p><p>She ran a small business selling handmade wedding decorations. Most of her customers found her website through Google, looked at the pictures, and then sent her a message asking about prices. It wasn’t a big business, but it paid some bills, and she had worked hard to get it going.</p><p>The problem was that she had become unhappy with her hosting. She found the website slow at times, and she wasn’t very happy with the service either. So she started looking around for another company.</p><p>A few days later, she found a new host with a price she liked. She bought a hosting package and was ready to get rid of the old one.</p><p>Julie logged into HOSTAFRICA, found her hosting account, and started looking for the cancellation button. She wanted to get the job done and forget about it.</p><p>Then a message arrived in her email.</p><p>A couple was planning a wedding and wanted decorations for the ceremony and reception. The order was worth about $2,400, which was a lot of money for Julie. They wanted to discuss a few details before placing the order.</p><p>She replied to the message and went back to the cancellation page.</p><p>Just before submitting the request, she had second thoughts. What if something went wrong with the new website? And what about the email address she had used to answer that couple?</p><p>She decided to leave the cancellation for another day.</p><p>That turned out to be a good decision.</p><p>First, Julie made a backup of her WordPress website. She used a backup plugin to save the files and database, then downloaded a copy to her computer. She also saved another copy somewhere outside the hosting account. It might sound like overkill, but having two copies is better than discovering that your only backup is missing something important.</p><p>She moved the website to her new host and opened it in her browser. The homepage looked all right, so she thought she was nearly finished.</p><p>But then she tried to send a message through the contact form. Nothing arrived.</p><p>She tried again. Still nothing.</p><p>Julie wasn’t happy about that, because the contact form was one of the main ways customers reached her. She went back to the new hosting account and checked the settings. After a little fiddling around, she got the form working.</p><p>She tested it once more, and this time the message arrived.</p><p>There was another thing she nearly forgot. Her business email was also connected to the old hosting package. Moving the website didn’t automatically move the email service, so she had to sort that out separately. She made sure she could send messages and receive them before going any further.</p><p>If you’ve ever waited for an important email that never arrived, you know how annoying that can be. Julie didn’t want to find out that a customer had been trying to contact her while she was busy thinking everything was taken care of.</p><p>Next, she checked her domain name. She had registered it through HOSTAFRICA, but she didn’t actually have to move it just because she was leaving the hosting service. She could keep the domain there and point it to the new website.</p><p>She decided to do that for the time being. She checked the renewal date too, because she didn’t want to be surprised by a renewal bill later.</p><p>Only then did Julie return to the cancellation form.</p><p>She found her hosting package, clicked Manage, opened Billing, and selected Request Cancellation. The form offered immediate cancellation or cancellation at the end of the billing period.</p><p>She chose the second option. She wanted a little more time to make sure the new website was working properly, and there was no point in rushing things now.</p><p>After submitting the request, she saved the confirmation email. She also checked the refund terms for her package. She had paid in advance, but she knew that canceling didn’t automatically mean she’d get money back for the unused time. She sent Billing a message asking what applied to her account.</p><p>A reply came a few days later, and she finally knew where she stood.</p><p>There was just one more thing Julie did. She checked that the cancellation request was recorded and made a note of the date the old service was supposed to end. If the normal cancellation process hadn’t worked, she would have opened a support ticket, saved a screenshot, and kept a copy of the message. You never know when you’ll need that information.</p><p>Meanwhile, the wedding couple got back to her. They liked her designs and wanted to go ahead with the order.</p><p>Julie was relieved. Her website was working, the contact form was sending messages, and her email was still getting through. She hadn’t lost the customer, and she hadn’t lost the information she needed to run her business.</p><p>Looking back, she laughed at how close she had come to making a mess of things just because she wanted to cancel an account quickly.</p><p>She had thought the difficult part was clicking the right button. It wasn’t. The real job was making sure everything she needed was safe and working somewhere else before the old service ended.</p><p>If you’re in the same situation with HOSTAFRICA, take a little time before you cancel. Save your website files and database, check your email, and decide what you want to do with your domain. If you’re moving to another host, test the new website first. It’s much easier to fix a problem while you still have access to the old account.</p><p>Julie also kept the <a href="https://hostiful.net/how-to-cancel-hostafrica/">HostAfrica cancellation instructions</a> handy while sorting things out. That helped her deal with the account itself, but she still had to check the website and email on her own.</p><p>In the end, she got everything moved without losing that $2,400 order. And the next time she changed hosting, she knew what to do before she even started.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a6db64fe3a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[He was about to cancel his hosting and nearly lost his business.]]></title>
            <link>https://richarddetering.medium.com/he-was-about-to-cancel-his-hosting-and-nearly-lost-his-business-5b36c9e271fc?source=rss-90b1ad79f0ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b36c9e271fc</guid>
            <category><![CDATA[web-hosting]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[website-design]]></category>
            <category><![CDATA[website-development]]></category>
            <category><![CDATA[wordpress]]></category>
            <dc:creator><![CDATA[Richard Detering]]></dc:creator>
            <pubDate>Thu, 22 Oct 2026 14:43:55 GMT</pubDate>
            <atom:updated>2026-10-22T14:43:55.030Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y3N_bihH3dTUDqDm" /><figcaption>Photo by <a href="https://unsplash.com/@cgower?utm_source=medium&amp;utm_medium=referral">Christopher Gower</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Tom was sitting at his kitchen table when he decided he’d had enough of his web hosting bill. His small repair business had been running for years, and most of his customers found him through his website. Still, he thought the time had come to move to a cheaper hosting company.</p><p>He opened his laptop, logged in to HostPapa, and started looking for the cancellation button.</p><p>It seemed easy enough. A few clicks and he could stop paying for the service. What he hadn’t thought about was everything connected to that account.</p><p>His website was built with WordPress. It had photos of his work, prices, customer reviews, and a contact form. He also used an email address with his domain name. Customers sent him repair questions through that address almost every day.</p><p>If he closed the account without taking care of those things, he could lose much more than a website.</p><p>Luckily, his friend Mike stopped by that afternoon. Mike had moved a website before and asked Tom a simple question.</p><p>“Have you backed everything up yet?”</p><p>Tom hadn’t. He thought that canceling hosting simply meant stopping the next payment. He had no idea that files and email stored on the old account could be deleted when the service ended.</p><p>So they put the cancellation on hold for a while.</p><p>The first job was saving the website. Since Tom used WordPress, Mike suggested a backup plugin called UpdraftPlus. It could save the website files and database, then send the backup to online storage.</p><p>Tom connected the plugin to his Google Drive account and started the backup.</p><p>He wasn’t sure what a database was, so Mike explained it in a way he could understand. Think of the website files as the parts of a filing cabinet, and the database as the information stored inside it. Having one without the other can leave you with an incomplete copy.</p><p>When the backup finished, Tom checked Google Drive to make sure the files were there. He felt much better after seeing them. He also kept the backup instead of deleting it once the new website was working.</p><p>Next came the email problem.</p><p>Tom had used the same business email address for years. He couldn’t afford to miss customer messages just because he changed hosting companies. Mike told him to set up the replacement mailbox first and deal with his old messages before closing HostPapa.</p><p>They checked the new hosting plan and created the email account there. Tom also saved the old messages he wanted to keep. He sent a test email to the new address and replied to it. Both messages arrived.</p><p>That was a relief. But there was still the domain name.</p><p>Tom had assumed that his domain and hosting were the same thing. Mike explained that they were separate. The domain was the address customers typed into their browsers. The hosting was the place where the website files lived.</p><p>Tom could keep his domain at HostPapa and use another company to host the website. He didn’t need to transfer the domain registration just to move the site.</p><p>The new host gave him the DNS settings needed to connect the domain. DNS is a bit like an address book. It tells the internet where to find a website. They also checked the email settings so that customer messages would keep reaching the right place.</p><p>It took some time for the changes to show up everywhere. Tom didn’t cancel the old hosting while they were still testing things. He wanted to be sure the new website and email worked first.</p><p>Once everything was ready, he returned to the HostPapa Dashboard.</p><p>This time, he knew what he was doing. He opened My Services, found his hosting plan, clicked Details, and selected Request Cancellation. He checked the service name, chose to cancel at the end of his current term, and reviewed the form before confirming the request.</p><p>He also took a screenshot of the confirmation and saved it.</p><p>Tom had one last question about the money he’d already paid. Could he get some of it back?</p><p>Mike told him not to count on a refund until he’d checked the rules. HostPapa has a money-back guarantee for certain hosting purchases, but it comes with conditions. Domain registration and some extra services are not refundable. Tom read the policy and found out what applied to his account.</p><p>Then he waited for the cancellation confirmation. HostPapa said its Billing Department reviews requests within three to five business days. Tom kept an eye on his email and saved the message when it arrived.</p><p>A few days later, a new customer used the contact form on his replacement website. The message arrived in the right inbox, and Tom could reply without any trouble.</p><p>He leaned back in his chair and smiled. The website was working, his email was working, and the old hosting cancellation had been confirmed. He hadn’t lost his photos, customer information, or years of work.</p><p>Looking back, he realized that finding the cancellation button had been the easy part. The real job was making sure he could leave without losing something important.</p><p>He also kept his backup files for about a year. Storage was cheap, and he had no desire to rebuild his website from scratch if something went wrong.</p><p>For anyone planning to leave HostPapa, Tom would give the same advice: save your website, sort out your email, decide what to do with your domain, and only then cancel the hosting. A <a href="https://hostiful.net/how-to-cancel-hostpapa-hosting-caution-risks-involved/">practical guide on how to cancel HostPapa</a> can help you check the steps before you start.</p><p>Tom had wanted to get rid of a hosting bill. In the end, he also learned how to protect his business from an expensive mistake. And that was worth far more than the money he hoped to save.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b36c9e271fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[He clicked cancel on Hostwinds and almost lost 11 years of work]]></title>
            <link>https://richarddetering.medium.com/he-clicked-cancel-on-hostwinds-and-almost-lost-11-years-of-work-89fb55a3cfbd?source=rss-90b1ad79f0ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/89fb55a3cfbd</guid>
            <category><![CDATA[web-hosting]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[web-hosting-provider]]></category>
            <dc:creator><![CDATA[Richard Detering]]></dc:creator>
            <pubDate>Sat, 10 Oct 2026 10:45:00 GMT</pubDate>
            <atom:updated>2026-10-10T10:45:00.301Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-nEoz_WWvmhU7zkA" /><figcaption>Photo by <a href="https://unsplash.com/@markuswinkler?utm_source=medium&amp;utm_medium=referral">Markus Winkler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Martin wanted to save some money. That was all.</p><p>On Friday morning, he received a renewal charge for his Hostwinds hosting account. He wasn’t happy about it. He ran a small online store selling spare parts for old motorcycles, and the hosting bill was eating into his profits.</p><p>He had already found another hosting company. The price looked reasonable, and he had signed up for a new plan. Moving the website should be manageable, he thought. He could cancel Hostwinds that evening and finish the move over the weekend.</p><p>What could possibly go wrong?</p><p>That evening, Martin logged in to his Hostwinds account, opened his services, clicked Manage, and found the cancellation option. Everything looked straightforward until he read the warning.</p><p>The service would be terminated immediately. The data stored on it would be permanently deleted.</p><p>Martin stared at the screen.</p><p>“Hang on. I only want to stop the next payment.”</p><p>He had canceled plenty of subscriptions before. Usually, he expected to keep using a service until the period he had paid for ended. But Hostwinds made it clear that cancellation worked differently.</p><p>His online store contained thousands of product photos, customer orders, database records, and years of changes he had made himself. He thought he had a backup somewhere. The problem was, he couldn’t remember when he had last checked it.</p><p>He closed the cancellation page.</p><p>For once, waiting was the smart move.</p><p>The backup he almost forgot</p><p>On Saturday morning, Martin started making a proper backup.</p><p>His website ran on a virtual private server, or VPS. Unlike ordinary shared hosting, a VPS gave him more control over the server. Over the years, he had adjusted settings, installed software, and created scheduled tasks to keep his store running the way he wanted.</p><p>He downloaded the website files and exported the database separately. He also checked his email accounts. Some customer inquiries went back years, and he didn’t want to lose those either.</p><p>Then he remembered all the little server changes he had made along the way.</p><p>Copying the website files wouldn’t recreate everything. There were custom PHP settings, scheduled jobs, security rules, and other things that he might need when setting up the new server.</p><p>He wrote down what he could remember and saved his backups on his computer and an external storage device.</p><p>Next, he began moving the website to his new hosting account.</p><p>The first test failed because of a database setting. He fixed it, tried again, and got further. Later, the order notification emails stopped arriving. That took another round of testing.</p><p>It was frustrating, but he was glad he had started before canceling the old service. If he had pressed that button on Friday evening, he could have been trying to solve these problems with no working copy of his website.</p><p>The storage that didn’t disappear</p><p>By Sunday, Martin’s website was running on the new hosting account. But before canceling Hostwinds, he decided to check his account one more time.</p><p>He had used its cloud storage to keep backups and had also created a snapshot before a major software update.</p><p>A snapshot is a saved image of a server at a particular moment. It can be useful when you need to restore a system or create another server from that saved state.</p><p>Martin had assumed those resources would disappear when he canceled the main VPS.</p><p>They wouldn’t.</p><p>Hostwinds’ instructions explained that separately stored resources, including object storage, volumes, snapshots, and ISOs, were not automatically deleted when the main hosting service was canceled. Those resources could continue generating charges.</p><p>So he could lose the server while still paying for storage associated with it.</p><p>Martin opened the Cloud Control Portal and checked what was there. He found two backups and a snapshot. One backup was old and no longer needed. The other contained files he wanted to keep.</p><p>He downloaded the useful backup and checked that he could open it. Only then did he remove the resources he no longer needed.</p><p>It reminded him of moving out of a house. Handing over the keys doesn’t mean everything in the garage automatically disappears.</p><p>The refund had a deadline, too</p><p>There was still the renewal charge to consider.</p><p>Martin checked Hostwinds’ refund policy and found another detail he couldn’t afford to ignore. Eligible refund requests had to be made within 72 hours of the payment transaction. The service also had to be canceled before requesting the refund.</p><p>Not every product or payment qualified, but Martin believed his recent charge might be eligible.</p><p>There was no point waiting until the following week.</p><p>He saved the invoice and noted the payment time. He also knew that sending a support message asking someone to cancel the service wouldn’t replace the official cancellation process. He needed to submit the request through his account.</p><p>By Sunday evening, he had finished testing the new website. The database worked, customer emails arrived, and the important pages loaded correctly. He checked the domain settings and made the necessary DNS changes.</p><p>Everything appeared to be working.</p><p>Martin went through his notes one last time. The backups were safe, the replacement website was running, and he had dealt with the storage resources he no longer needed.</p><p>Then he returned to Hostwinds.</p><p>He opened Services, selected My Services, clicked Manage beside the old VPS, and chose Actions followed by Request Cancellation. He read the warning again, selected his reason, and confirmed the request.</p><p>This time, he knew exactly what he was doing.</p><p>The old service was terminated, just as Hostwinds had warned. Martin then submitted his refund request within the 72-hour window. He kept the confirmation and payment records rather than assuming the refund would be automatic.</p><p>A much better Monday</p><p>On Monday morning, Martin checked his online store again.</p><p>It was still working. Customers could browse products and place orders, and the notification emails were arriving. The old Hostwinds server was gone, but the business hadn’t missed a beat.</p><p>He had spent most of his weekend on a job he thought would take a few minutes. Still, he hadn’t lost eleven years of work, and he wasn’t left wondering why another storage charge had appeared.</p><p>The experience taught him something he wouldn’t forget.</p><p>Canceling a server is not like canceling a magazine subscription. It’s more like demolishing a workshop. Before the building disappears, you need to take your tools, records, and anything valuable out of it. You also need to check whether you’ve left anything in a separate storage room.</p><p>Later, Martin came across <a href="https://hostiful.net/how-to-cancel-hostwinds-subscription-warning-risks-involved/">a practical guide to the Hostwinds cancellation process</a>. He wished he’d found it before that Friday evening. It would have saved him a fair bit of worrying and time.</p><p>Still, he had moved his website safely, completed the cancellation, and dealt with the potential extra charges before they became another headache.</p><p>Martin had started the weekend wanting to save money.</p><p>He ended it with something more valuable: the knowledge that his business was safe, and that he wouldn’t make the same mistake twice.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89fb55a3cfbd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[He bought a cheap VPS but also gave himself a second job]]></title>
            <link>https://richarddetering.medium.com/he-bought-a-cheap-vps-but-also-gave-himself-a-second-job-2797d400a1f9?source=rss-90b1ad79f0ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/2797d400a1f9</guid>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[web-hosting]]></category>
            <category><![CDATA[vps]]></category>
            <category><![CDATA[vps-hosting]]></category>
            <category><![CDATA[vps-server]]></category>
            <dc:creator><![CDATA[Richard Detering]]></dc:creator>
            <pubDate>Mon, 05 Oct 2026 13:47:02 GMT</pubDate>
            <atom:updated>2026-10-05T13:47:02.251Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="VPS server, laptop and links to control panels" src="https://cdn-images-1.medium.com/max/1024/1*TmjzatQejMAotguxapPvqA.png" /></figure><p>Tom thought he had found a bargain.</p><p>His new VPS cost only a few dollars a month, and for once he felt he had beaten the hosting companies at their own game. The specifications looked decent. The server was his. He had root access. Nobody was going to tell him what he could install.</p><p>He ordered it on a Tuesday evening.</p><p>By Wednesday night, he was already annoyed with it.</p><p>The first problem was not the server.</p><p>It was the server software.</p><p>Tom had assumed there would be some nice dashboard where he could create a website, add a database, set up email and look around without having to remember a collection of Linux commands. Instead, he was looking at a terminal window.</p><p>He stared at it for a while.</p><p>Then he searched for VPS control panels.</p><p>That opened another can of worms.</p><p>He discovered that he could run the VPS without a control panel at all. Plenty of experienced Linux administrators do exactly that. They use SSH, work from the command line and edit configuration files directly.</p><p>Tom was not one of those people.</p><p>He wanted to run websites, not become a part-time system administrator.</p><p>So he started looking at paid panels.</p><p>cPanel caught his attention first. It was well known and looked familiar, but then he saw the license price. His little VPS suddenly did not look so little anymore. A server costing around $8 a month could end up costing far more once the control panel was added.</p><p>That was the moment Tom understood something rather important.</p><p>The number on the VPS sales page was not necessarily the price of the solution.</p><p>It was just the price of the server.</p><p>He kept digging.</p><p>Plesk came next. Then DirectAdmin. Their pricing was different, and some were much less expensive than cPanel depending on what he needed. But the same basic question kept coming back.</p><p>What exactly am I paying for?</p><p>Tom made a little spreadsheet.</p><p>Nothing fancy. Just four columns.</p><p>Server. Control panel. Management. Everything else.</p><p>The spreadsheet was starting to make more sense than the advertising pages.</p><p>Then he discovered the free control panels.</p><p>There was HestiaCP. ISPConfig. Virtualmin GPL. CyberPanel. CloudPanel. Webmin. Froxlor.</p><p>That made him feel better.</p><p>At least he could avoid the extra license.</p><p>He installed a free panel on a test VPS and played with it for an evening. It worked. He could manage websites from a browser instead of typing every instruction by hand.</p><p>For about ten minutes, Tom thought he had solved the whole problem.</p><p>Then the server needed an update.</p><p>He did it.</p><p>Then something stopped working.</p><p>He fixed it.</p><p>Then he discovered he needed to understand what the control panel was actually doing underneath the nice buttons.</p><p>That was the part nobody had really explained to him.</p><p>A free control panel can save you money. It does not magically make server administration free.</p><p>The software might cost nothing.</p><p>Your time still costs something.</p><p>Tom thought about that while sitting at his kitchen table at 11:40 at night, staring at a server log he barely understood.</p><p>He had bought the VPS because he wanted cheaper hosting.</p><p>Instead, he was spending his evening reading about Linux services.</p><p>That is when he learned another distinction that changed his thinking: a control panel is not the same thing as managed hosting.</p><p>The panel makes the server easier to operate.</p><p>Managed hosting means somebody else takes responsibility for some of the technical work.</p><p>Those two things are often lumped together, but they are not the same.</p><p>A control panel might let you create a database with a few clicks. It does not necessarily mean somebody will help when the database server fails.</p><p>It might let you create an SSL certificate. That does not mean somebody is maintaining the operating system underneath it.</p><p>It might even give you backup controls. You still need to understand what is being backed up and whether you can actually restore it.</p><p>Tom had been looking at the wrong thing.</p><p>He was comparing server prices.</p><p>What he really needed to compare was the whole arrangement.</p><p>He went back and looked at the control panels again. cPanel was a mature commercial option. Plesk had several editions. DirectAdmin was considerably cheaper at the low end. The free panels offered some impressive features too, especially for technically capable people.</p><p>But Tom was beginning to realize that “free” and “easy” were two completely different words.</p><p>He also kept one useful <a href="https://hostiful.net/blog/how-a-vps-control-panel-changes-the-real-cost/"><strong>VPS control panel comparison</strong></a> bookmarked, mostly because it had helped him see the actual costs side by side.</p><p>A few days later, Tom changed his approach.</p><p>Instead of buying the cheapest bare VPS he could find and assembling everything himself, he looked for hosting where the control panel was already included.</p><p>Eventually he found a managed setup using Hepsia. It was a semi-dedicated hosting plan.</p><p>There was no separate control-panel bill staring back at him. More importantly, the service was managed, so he was not expected to become the person responsible for every server-side problem.</p><p>Tom still had plenty of control over his websites.</p><p>He just stopped trying to control the wrong things.</p><p>The funny part was that his original idea had not been completely wrong.</p><p>A cheap VPS really can be a good deal.</p><p>A free control panel really can save money.</p><p>A paid control panel really can be worth the cost.</p><p>The mistake is assuming that the cheapest server is automatically the cheapest way to run a website.</p><p>Sometimes the cheapest thing you can buy is also the thing that gives you the most work.</p><p>Tom finally got what he wanted: a server environment he could actually use, without spending every other evening maintaining it.</p><p>And that, he decided, was a much better bargain.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2797d400a1f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The $8 VPS That Wasn’t Really an $8 VPS]]></title>
            <link>https://richarddetering.medium.com/the-8-vps-that-wasnt-really-an-8-vps-2d00050bea3b?source=rss-90b1ad79f0ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d00050bea3b</guid>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[web-hosting]]></category>
            <category><![CDATA[web-hosting-provider]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Richard Detering]]></dc:creator>
            <pubDate>Fri, 02 Oct 2026 15:07:16 GMT</pubDate>
            <atom:updated>2026-10-02T15:07:16.077Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ihRWyYvKPIa_toPW" /><figcaption>Photo by <a href="https://unsplash.com/@kevinache?utm_source=medium&amp;utm_medium=referral">Kevin Ache</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Maya was sitting at the kitchen table late one Tuesday evening, trying to solve a problem she had been putting off for months.</p><p>Her small online store had grown. The shared hosting plan she started with was fine when she had a few dozen products. Now there were more images, more database activity, and more visitors. Pages were not always as quick as they used to be.</p><p>She decided it was time to look at a VPS.</p><p>The first prices she saw looked almost too good to ignore.</p><p>One provider offered a VPS for $8 a month.</p><p>Maya stared at the screen.</p><p>Eight dollars sounded easy.</p><p>Then she started reading the details.</p><p>The VPS was the server itself. The control panel was separate.</p><p>That was the first surprise.</p><p>Maya had always logged into hosting through a graphical dashboard. She used it to manage websites, domains, email, files, databases, and DNS. She had never needed to think much about what was happening underneath.</p><p>Now she was being asked to decide whether she wanted a control panel and, if so, whether it cost extra.</p><p>She learned about SSH too. It was a standard way to connect to a remote server and manage it with commands.</p><p>She could see why a developer might like that. There was a lot of control.</p><p>But Maya was not trying to become a server administrator.</p><p>She ran an online store.</p><p>She knew how to photograph products, answer customers, update prices, and pack orders. Learning server administration was not on her list for the weekend.</p><p>Still, the $8 price kept bothering her.</p><p>She made a little note on a sheet of paper.</p><p>VPS: $8</p><p>Then she started adding the things that might be needed around it.</p><p>In one purely hypothetical example she found while researching, an extra $10 for a control panel, $12 for management, and $4 for backups would turn an $8 server into a $34 monthly setup.</p><p>The numbers were only an example, but the idea stayed with her.</p><p>The cheap server was not necessarily cheap hosting.</p><p>That night she began looking into what managed actually meant.</p><p>She found out that the word could mean different things from one provider to another. Some services might handle server maintenance and security updates but leave other work to the customer. Others might offer more hands-on administration.</p><p>That meant she had to ask better questions.</p><p>Who handles operating-system updates?</p><p>Who deals with security work?</p><p>Who watches the server?</p><p>Who handles troubleshooting?</p><p>What happens when something breaks?</p><p>And what about backups?</p><p>Maya had always assumed that the word backup meant she was covered. Then she realized there was more to it.</p><p>How often were backups made?</p><p>How long were they kept?</p><p>Where were they stored?</p><p>Could the website and database actually be restored?</p><p>She also learned that a power backup was not the same thing as a website backup. A UPS or generator can help keep equipment running. It does not give you a separate copy of your website.</p><p>The longer Maya looked, the more the monthly price seemed like only one part of the decision.</p><p>There could also be extra IP addresses, storage limits, traffic limits, migration charges, and renewal pricing.</p><p>Renewal was another one she had almost missed.</p><p>A low introductory price could change later.</p><p>She wrote down three numbers this time: the starting price, the price during the first term, and the renewal price.</p><p>That made the comparison much clearer.</p><p>A week later, Maya had a short list of what she actually needed.</p><p>She wanted more room than ordinary shared hosting.</p><p>She wanted a graphical control panel.</p><p>She wanted server management included.</p><p>She wanted a clear backup arrangement and real technical support.</p><p>She wanted to know the long-term price.</p><p>And she did not want to spend her evenings learning how to maintain a server.</p><p>Before making a decision, she found a useful explanation of the <a href="https://hostiful.net/blog/the-hidden-costs-of-cheap-vps-hosting/">hidden costs of VPS hosting</a> and read through the different costs one more time.</p><p>Then she looked at another type of hosting she had not taken seriously at first: semi-dedicated hosting.</p><p>It was not a VPS. It was still a shared physical server, but with only a very small number of customers compared with ordinary shared hosting.</p><p>That interested her.</p><p>She would get more resources than she had on regular shared hosting, while the underlying server would remain fully managed.</p><p>There was no root access, but Maya realized she did not actually need root access.</p><p>She needed a website that worked.</p><p>She eventually chose a fully managed semi-dedicated plan with a graphical control panel, included migration, fixed monthly pricing, and a free trial.</p><p>The move was not exciting.</p><p>In fact, it was pretty ordinary.</p><p>And that was exactly what Maya wanted.</p><p>Her website was moved. She could still manage her store from a familiar control panel. She did not have to spend her evenings applying server updates or figuring out why some system setting had suddenly stopped working.</p><p>A few months later, she found the old piece of paper in a kitchen drawer.</p><p>At the top it still said:</p><p>VPS: $8</p><p>Maya laughed.</p><p>The number had not really been wrong.</p><p>She had just been asking the wrong question.</p><p>The better question was how much the whole hosting setup would cost in money, technical work, and her own time.</p><p>Once she started looking at it that way, the decision became much easier.</p><p>And for the first time in a long while, Maya could concentrate on her business instead of her VPS.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d00050bea3b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The $50 Server That Wasn’t Really $50]]></title>
            <link>https://richarddetering.medium.com/the-50-server-that-wasnt-really-50-7e0b2760f1c3?source=rss-90b1ad79f0ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e0b2760f1c3</guid>
            <category><![CDATA[web-hosting-company]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[web-hosting]]></category>
            <category><![CDATA[web-hosting-provider]]></category>
            <category><![CDATA[web-hosting-services]]></category>
            <dc:creator><![CDATA[Richard Detering]]></dc:creator>
            <pubDate>Fri, 02 Oct 2026 14:45:13 GMT</pubDate>
            <atom:updated>2026-10-02T14:45:13.010Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OzkynypLuEKvzrzB" /><figcaption>Photo by <a href="https://unsplash.com/@noa69?utm_source=medium&amp;utm_medium=referral">Yuriy Vertikov</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When Mark first saw the dedicated server offer, he thought he had finally found the answer.</p><p>$50 a month.</p><p>A real physical server. His own machine. Plenty of room for his growing websites.</p><p>He stared at the price on his screen and smiled.</p><p>“For fifty bucks, why not?” he said.</p><p>Mark ran three websites for small businesses and one online store of his own. His shared hosting account had started to feel cramped. Some pages were getting slower when traffic picked up, and he was tired of wondering whether another account on the server was using more than its share of resources.</p><p>A dedicated server seemed like the obvious next step.</p><p>He placed the server in his budget at $50 a month.</p><p>Then he started reading the small print.</p><p>The first surprise was the control panel.</p><p>The server came without one. Mark knew how to use a computer pretty well, but managing several websites entirely from a command line was not what he had in mind. He wanted something where he could see his domains, files, databases and email in one place.</p><p>A control panel would cost extra.</p><p>“Okay,” he thought. “Still probably cheaper.”</p><p>Then he noticed that the server was unmanaged.</p><p>The provider would supply the machine, but Mark would have to deal with much of the administration himself.</p><p>Operating system updates.</p><p>Security updates.</p><p>Software installation.</p><p>Configuration.</p><p>Troubleshooting.</p><p>Monitoring.</p><p>He read the list twice.</p><p>Mark had never actually administered a server before.</p><p>He could learn, of course. People learn all sorts of things. But he pictured himself sitting at his desk late at night, trying to remember which command fixed what, while one of his customers was waiting for a website to come back online.</p><p>He looked at the $50 price again.</p><p>It suddenly seemed smaller.</p><p>Then came backups.</p><p>The data center had power protection and a backup generator, which was reassuring. But Mark realized that protecting the building from a power failure was not the same as having a separate backup of his website data.</p><p>He would need a backup arrangement of his own.</p><p>Another expense.</p><p>Then support.</p><p>The server company offered support, but the level of help for an unmanaged machine was not the same thing as having someone take care of the server for him. Mark imagined needing outside help during a serious problem.</p><p>That help would cost money too.</p><p>Or time.</p><p>Sometimes time was worse.</p><p>He opened a spreadsheet and made a simple list.</p><p>Server: $50.</p><p>Control panel: extra.</p><p>Management: extra if he wanted someone else handling administration.</p><p>Backups: possibly extra.</p><p>Technical help: possibly extra.</p><p>Security work: someone had to do it.</p><p>He sat back.</p><p>The funny thing was that none of these costs were necessarily unfair. The provider wasn’t doing anything wrong. A cheap unmanaged server was still a legitimate product. It simply wasn’t the same product as a fully managed service.</p><p>Mark had been comparing two things that only looked similar because both had the word “server” in them.</p><p>Then he made another mistake.</p><p>He had compared the introductory price but hadn’t checked what happened at renewal.</p><p>The first few months looked attractive. The normal recurring price was higher.</p><p>That was when the $50 server finally stopped being a $50 server in his head.</p><p>It reminded him of buying a cheap car and discovering later that you still needed insurance, tires, maintenance and repairs. The car wasn’t fake. The price wasn’t fake either. He had just been looking at one part of the cost.</p><p>Mark decided not to order it.</p><p>Instead, he asked himself what he actually needed.</p><p>Did he need root access?</p><p>Not really.</p><p>Did he need to personally maintain the operating system?</p><p>Definitely not.</p><p>Did he need a dedicated physical machine?</p><p>Maybe. But what he really wanted was more room for his websites and less hassle.</p><p>That changed the question completely.</p><p>He started looking at semi-dedicated hosting.</p><p>The idea was different. The server was shared, but only among a small number of customers, so it wasn’t ordinary crowded shared hosting. At the same time, the service could be fully managed.</p><p>That sounded much closer to what Mark had originally wanted.</p><p>He found a plan with a control panel included, so he didn’t have to add another license to the monthly bill. He also found another important detail: the pricing was fixed instead of jumping after an introductory period.</p><p>The numbers were easier to understand.</p><p>More importantly, the job was easier to understand.</p><p>The hosting company would handle server maintenance, security updates, software installations and routine optimizations. Mark could concentrate on the websites instead of becoming an unwilling systems administrator.</p><p>He still understood the trade-off. Semi-dedicated hosting was not the same as a dedicated server. He would not have root access, and the server would still be shared.</p><p>But that was fine.</p><p>He wasn’t looking for control just because control sounded impressive. He was looking for a practical way to run his websites.</p><p>A few weeks later, Mark moved his sites.</p><p>The first Monday morning after the move, he made coffee, opened his laptop and checked his customer sites.</p><p>Everything was running.</p><p>No server updates waiting for him.</p><p>No mysterious command-line problem.</p><p>No separate control-panel bill.</p><p>No late-night argument with a machine he barely understood.</p><p>Mark smiled.</p><p>He opened his spreadsheet and deleted the line that said “dedicated server: $50.”</p><p>Under it he wrote something more useful:</p><p>“What does the whole service actually cost?”</p><p>That question saved him more money than the cheap server ever promised.</p><p>And when he told his friend David what he had chosen, Mark explained why the $50 server had turned out to be a very different deal once all the other costs were considered. He also sent David a guide about the <a href="https://hostiful.net/blog/hidden-costs-of-cheap-dedicated-hosting/">hidden costs of dedicated hosting</a> that he had found useful.</p><p>For Mark, that was the happy ending.</p><p>He hadn’t bought the cheapest server.</p><p>He had finally bought the service he actually needed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e0b2760f1c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>