Latest Hosting News on Reddit

If a web app is just a static file, could browsers sync data directly with each other over WebRTC instead of a server, so the data lives in each browser and the app stays alive as long as one person has it open (like BitTorrent seeding)? I think you’d still need a tiny signaling server for peers to find each other, but it’d hold no data. How would you actually build this, and where does it break (durability when everyone closes the tab, NAT)? Does a project like this already exist? submitted by /u/Superb_Yesterday5588 [link] [comments]

[ Removed by Reddit on account of violating the content policy. ] submitted by /u/Asicona_Hsoalbd [link] [comments]

Which option would u pick for a Laravel app db: Postgresql It’s my first time choosing a panel for a cloud hetzner vps thanks submitted by /u/FeeKey3471 [link] [comments]

I’ve been running WHM servers for client hosting for years now, and I keep seeing the same pattern. Everyone locks down SSH and sets up CSF, then calls it a day. That’s fine for baseline security, but there’s a whole layer of WHM-specific attack surface that barely gets mentioned in the standard hardening guides. The things that actually bit me: Tweak Settings has a public access toggle buried in there. Go to Tweak Settings > Stats programs and make sure Awstats and Webalizer aren’t publicly accessible. I found out the hard way that default installs sometimes leave these exposed, and they leak way more server info than you’d want visible. Directory structure, bandwidth patterns, the works. cPHulk is not just “that brute force thing.” The default config tracks root login attempts but doesn’t block at the WHM port level. You need to actually enable protection for the 2087 port explicitly, or you’re just logging attacks without stopping them. Also, whitelist your own IP before you lock yourself out. Yes, I’ve done this. Compiler access is enabled by default for all accounts. Security Center > Compiler Access lets you restrict gcc and other compilers to root only. If you’re running shared hosting or reseller accounts, there is zero reason a random cPanel user needs to compile binaries on your server. This is how you end up with IRC botnets you didn’t know you were hosting. Email authentication (SPF/DKIM/DMARC) isn’t just for deliverability. It also stops your server from being used as a spam relay if an account gets compromised. Email Deliverability in WHM will show you which domains are misconfigured. Fix them. A compromised WordPress site sending 10k emails an hour will get your entire IP range blacklisted. I actually documented the full list of things I check on every new WHM setup here after the third time I had to explain it to a new team member. It covers the less obvious stuff like TLS cipher restrictions and the ModSecurity ruleset gotchas. The big one people sleep on: regularly audit your actual package list in WHM. Go to Packages > Feature Manager and look at what you’re giving resellers and end users by default. If “Shell Access” is enabled in your default package, you’ve basically handed SSH to everyone who signs up. I’ve seen this on way too many servers. What’s the weirdest security issue you’ve run into on a WHM box? I’m curious if anyone else has dealt with the Softaculous auto-update thing causing version conflicts that break security patches. submitted by /u/Veduis [link] [comments]

submitted by /u/No_Island_1309 [link] [comments]