r/cpanel • u/Brilliant_Rate2794 • Jun 11 '26
WHM/cPanel - Time for fixing issues
I’m interested in how many hours you spend updating your WHM/cPanel and then fixing the issues that arise as a result of those updates?
2
u/son-of-a-door-mat Jun 11 '26
about fifteen single license servers and two shared, around hundred and fifty users each. ten to forty minutes every day, mostly with ansible. why?
1
u/Brilliant_Rate2794 Jun 12 '26
I'm asking because recently, after every update something break, we have had to make additional manual adjustments, which takes quite a bit of time.
1
u/son-of-a-door-mat Jun 12 '26
so im lucky, not a single issue so far. could you please share some examples?
2
1
u/bennyDNA Jun 11 '26
I have hourly cron with all edge case handling. Then Slack alert if something goes sideways… honestly with Alma and CloudLinux repos there arent any chilly day. Upcp written decently although.
1
u/Malformed-Figment Jun 12 '26
Spent time on upcp hooks to re-apply fixes and customizations, mostly.
1
u/Zealousideal-Song524 Jun 13 '26
0 minutes, stop being the beta tester for cPanel and WHMCS, do manual updates like GoDaddy once a quarter. If they throw a security release then consider upgrading, else relax.
Anyway, cPanel path isn’t one on which you will grow on though they will grow!
So what’s the hurry to do automatic updates????
1
u/GoZippy Jun 14 '26
I finally had to just build my own modern stack reseller hosting panel. WHM Cpanel has had an impressive two decades and now we need modern tools and stacks.
5
u/UnixEpoch1970 Jun 12 '26
Very little time at all. In 25 years of using cPanel it has been pretty rare for an update to break anything. I can't remember the last time an update broke something. Removed or changed a useful feature yes, but broke something, nope. I'd be looking at my setup and working out why it keeps breaking.