r/webhosting • • 1h ago

News or Announcement Two new nginx exploits (CVE-2026-123007 and CVE-2026-123633)

3 Upvotes

Here's our writeup of two new Nginx vulnerabilities that were released today.

TL;DR- unauthenticated RCE, disable http/2 until the patches land.

https://prostack.uk/blog/critical-nginx-http2-vulnerabilities-november-2026/

Hope it's useful.


r/webhosting • • 11h ago

Technical Questions A €4/Month Alternative to an Expensive VPS Storage Upgrade

1 Upvotes

I recently ran into a shortage of disk space on my VPS. I currently rent a VPS for €7 a month with this configuration: 4 vCPUs, 8 GB of RAM, and a 120 GB NVMe drive. It has 50 GB of free space left. But I need to run a Docker container whose image is 76 GB. I could upgrade my current VPS to get a 240 GB disk, but that would cost €30 a month. That’s steep. I noticed that my hosting provider offers 250 GB of S3 storage for just €4 a month, accessible over its internal network. So I started wondering how I could turn it into a filesystem and have Docker store files there.

First, I tried rclone. It lets you create a FUSE filesystem from your S3 storage. To speed things up, you can cache frequently used files on a local SSD using the --vfs-cache-max-size flag. Unfortunately, Docker uses overlay2, which requires filesystem operations that rclone mount does not guarantee: atomic renames, correct chmod and chown behavior, hard links, and extended attributes. In short, a full POSIX filesystem is needed.

And I found a solution: s3backer. It has 600+ stars on GitHub and provides a full-fledged ext4 filesystem. I set a 20 GB cache on my local SSD using the --blockCacheSize option, mounted it at /mnt/s3, and reconfigured Docker to store images, containers, and volumes there. As a result, the most frequently used files are cached locally instead of being pulled over the network from S3. What do you think? Expanding my virtual machine’s disk space by 250 GB for €4 a month? Pretty great, if you ask me!

By the way, here’s a summary table of the available options:

SolutionHow it worksProsCons
s3backer + ext4S3 as a block deviceFull POSIX filesystem, Docker compatibility, cachingComplex setup, latency, risk of filesystem corruption
rclone mountFUSE over S3Simple setup, local cache, support for multiple cloud providersIncomplete POSIX compatibility, some operations are unsupported
s3fsFUSE over S3Simple mounting, familiar file operationsSlow metadata operations, POSIX limitations
JuiceFSDistributed filesystem on top of S3POSIX, caching, high performanceRequires separate metadata storage
S3QLFilesystem on top of S3POSIX, compression, deduplication, encryptionExtra overhead, complex recovery

Of course, s3backer is far from the only way to turn S3 into a filesystem. There are at least two other interesting projects: JuiceFS and S3QL. Both run on top of S3, support POSIX operations and local caching, but they seemed like overkill for my use case.

JuiceFS is a fairly powerful distributed filesystem. It supports multiple servers working concurrently, caching, POSIX, and much more. But there’s a catch: in addition to S3 itself, it requires a separate metadata store. This could be Redis, PostgreSQL, MySQL, or even a local SQLite database. The last option doesn’t require a separate service, but you still have to keep the metadata database safe and back it up. Overall, it’s an interesting solution, especially if you have a server cluster. But I only have one VPS, and I didn’t want to set up extra infrastructure just to store Docker images.

S3QL is another interesting option. It supports POSIX, local caching, compression, deduplication, and encryption. It doesn’t need a separate database server: metadata is stored in SQLite and synchronized with the object store. But these extra features come at the cost of added complexity. Deduplication requires computing hashes, compression uses CPU time, and recovering the filesystem after a failure may require checking and restoring metadata with specialized tools. These aren’t critical drawbacks, but I didn’t see any particular advantages for my use case, either.

The key difference lies in the approach: JuiceFS and S3QL implement filesystems themselves using FUSE, while s3backer provides virtual block storage on top of which you can create a standard ext4 filesystem. As a result, Docker works with the familiar Linux filesystem, and s3backer translates block operations into requests to S3. No separate metadata databases, no deduplication, and no extra layers of file management.

Of course, this setup has its downsides too. Random reads and writes can be heavily affected by S3 latency, and losing the connection to the storage can bring the containers to a halt. A serious failure could also corrupt the filesystem. So I wouldn’t use this setup for critical databases. But for storing large Docker images that are downloaded once and then mostly read, it seemed perfectly reasonable-especially when S3 is available over the hosting provider’s local network. In short, I wanted an extra 250 GB for €4 a month without building a distributed storage system. From that perspective, s3backer seemed like the best fit.


r/webhosting • • 13h ago

Technical Questions Hoststack VPS – Repeated Maintenance Issues and Extremely Poor Customer Support

1 Upvotes

I've been using Hoststack VPS for our company's production infrastructure, and honestly, the experience has been extremely disappointing.

The VPS keeps experiencing maintenance-related issues and performance inconsistencies. These aren't minor inconveniences when you're running production workloads; they directly affect service availability and business operations.

What's even more frustrating is the customer support.

Whenever we contact support to ask questions or get clarification about the infrastructure, we either receive no response or get responses that don't address the actual problem.

At one point, when we were trying to get serious technical clarification, the response was literally "heheheheh". Seriously, is that how a hosting provider handles customer concerns?

We expect basic things from a VPS provider:

  • Reliable infrastructure and predictable performance.
  • Transparent communication about maintenance and outages.
  • Proper technical explanations when performance issues occur.
  • Responsive and professional customer support.

We're paying for a hosting service, not asking for a favour.

Has anyone else experienced similar issues with Hoststack? I'd particularly like to hear from customers running production workloads on their VPS infrastructure.

I'm genuinely disappointed with the service so far.


r/webhosting • • 6h ago

News or Announcement We analyzed 97.3% of all the domains to map the web hosting market

0 Upvotes

We've been working on something at webhosting(.)today for the last few months that I thought might be useful to this community. We analyzed 97.3% of all registered domains and mapped over 8,300 hosting providers to understand what's actually happening in the web hosting market.

You can use it to:

  • Check any hosting provider's market position, how many domains they manage and their growth
  • Find out who's involved, who owns whom, including hosting groups and all the brands they control
  • Track domain migrations, see exactly which competitors a provider is gaining or losing domains to
  • Compare hosting companies and see who's actually gaining market share
  • Explore local markets, see who's leading in different countries

Instead of relying on what hosting companies say about their market position, you can look at the actual DNS data. All in one place.

You can browse it here: https://webhosting.today/market-insights/

We would love to get some feedback from you. What else would you like to see in a tool like this?

Disclosure: There is no affiliate links, we are not dependent on any web hosting provider. We also offer premium access for more detailed analysis, but a lot of the data is available for free.


r/webhosting • • 7h ago

Advice Needed Is the EU Digital Services Act actually on your radar as a hoster, or is it a non-issue in practice?

0 Upvotes

I’ve been digging into the EU Digital Services Act lately. On paper it applies to pretty much every hoster serving EU customers: notice-and-action for illegal content, telling customers why you took something down, a point of contact for authorities, and so on. Small companies get a few exemptions, but the core stuff still applies.

But from what I can see, nobody’s really losing sleep over it. Most smaller hosters seem to keep doing what they’ve always done: an abuse@ inbox, a ticket system, and someone who handles it when there’s time.

So I’m curious:

  • Have you actually changed anything because of the DSA?
  • Has a customer, upstream or authority ever asked you about it?
  • Real risk, or a paper tiger that only matters for the big platforms?

Full disclosure: I’ve worked in abuse handling for years and I’m toying with building something to help smaller hosters with this. If the honest answer is “nobody cares,” I’d rather hear it now than after building it.


r/webhosting • • 12h ago

Advice Needed I want to just host websites and not have to also build them for my clients, how should I go about finding new clients? Any tips?

0 Upvotes

I operate a small web hosting company and the only clients I've ever been able to get are the ones whom I've also built the website for. I much rather host the website for clients than build it. I've tried cold emails and advertising without much success because I'm not a big name even though I can offer comparable pricing. It makes sense that clients tend to trust the person who built the website for them to also host it. But that can't be the only way, there's gotta be other ways to get clients, appreciate any tips.


r/webhosting • • 21h ago

Technical Questions Help a dumb dumb out... difference between domain hosting and wider Cloudflare services?

0 Upvotes

Trying to de-Google my life. I should caveat that I understand certain things in very simple terms but am not super technical so feel free to explain like I'm a child!

I own a couple of currently dormant domains - mostly on Squarespace after Google Domains stopped. One is connected to Google Workspace that I use for email that I'll be switching over to Tuta. The rest bar one are not in active use. The remaining one is connected to a Jellyfin server which I had help setting up - which I have a Cloudflare account for with tunnels set up (I understand the rough concept of this but not much else!)

I have found a new domain host (I think 'host' is the correct term?) in Krystal and am slowly transferring domains over. All of this explanation is to ask - if currently my only use case for having my custom domain is email (e.g. having hello@customdomain.com to use on Tuta), is there any reason to add it to my Cloudflare account? Is there anything else I should be doing for extra security here? Or is just setting up the MX records as Tuta instructs enough for what I want?


r/webhosting • • 23h ago

Rant Web Hosting Canada (WHC) suspended my domain and closed my account over a phishing allegation without giving me a chance to explain

0 Upvotes

I wanted to share my recent experience with Web Hosting Canada (WHC).

I registered a domain through WHC and used it for a simple landing page promoting my Tangerine Bank referral code.

On November 13, 2026, PhishLabs reported my domain to WHC, alleging that it had been registered for the sole purpose of malicious activity and was targeting Scotiabank/Tangerine Bank.

However, my website was simply a referral landing page. I was not attempting to steal anyone's banking credentials or conduct phishing activities.

Rather than contacting me to request clarification or giving me an opportunity to address the complaint, WHC quickly suspended my domain and closed my account.

I contacted customer service to explain the situation and requested that they unlock my domain and provide the transfer authorization (EPP) code so I could transfer it to another registrar.

Customer service told me they were unable to help, including with the domain unlock and authorization code, and instructed me to email abuse@whc.ca instead.

I understand that hosting companies and domain registrars need to take phishing reports seriously. However, I find it concerning that WHC would take such drastic action based on an allegation without first giving the customer a meaningful opportunity to respond.

Even if WHC no longer wants me as a customer, I should at least be given a clear explanation of the decision and the process for recovering or transferring my domain.

My biggest concerns are:

  • The apparent lack of investigation or opportunity to respond before my account was closed.
  • The immediate suspension of my domain based on a third-party allegation.
  • Customer service being unable to provide meaningful assistance.
  • The lack of a clear process for obtaining my domain's transfer authorization code and having it unlocked.

I am extremely disappointed with how WHC handled this situation. I would caution anyone considering registering domains with them to understand how they handle abuse complaints, account suspensions, and domain transfers.

Has anyone else experienced something similar with WHC? Were you eventually able to obtain your transfer authorization code and move your domain to another registrar?