A reseller wants the customer-facing cPanel to look like theirs, not yours. The WHM cobranding interface lets them upload a logo, change colours, set a branded hostname, and the work is roughly an hour. Two upgrades later, the logo is broken, the favicon is back to cPanel’s, and the customer is getting account-creation emails signed by your support address. Cobranding works, but only when you understand which assets cPanel preserves and which ones get clobbered every time /usr/local/cpanel/scripts/upcp runs.
What’s happening
cPanel cobranding lives in three places that behave differently. Logo and theme images go under /var/cpanel/customizations/brand/<reseller>/ — these survive upgrades. The cPanel theme settings (colour, layout, fonts) are stored in the reseller’s user file and propagate to their accounts via the theme reference; these also survive. Account-creation emails (the welcome message a customer receives) live in /var/cpanel/templates/cpanel/account_creation_emails/ and are owned by the root admin, not the reseller; resellers cannot customize these through their WHM. Webmail branding uses a separate set of files under /var/cpanel/webmail/ and the Roundcube theme is overwritten on Roundcube updates.
How to verify
For any reseller, audit which cobranding bits are actually in place:
ls /var/cpanel/customizations/brand/acmevpn/
whmapi1 list_resellers
whmapi1 get_reseller_data user=acmevpn
cat /var/cpanel/users/acmevpn | grep -E 'STYLE|THEME|BRAND'
tail -f /usr/local/cpanel/logs/error_log | grep brand
The customizations/brand directory should contain cpanel_logo.png, cpanel_favicon.ico, and any per-area overrides. The reseller’s user file shows STYLE= and THEME= references. If either pointer is missing, the customer sees the default cPanel chrome regardless of what the reseller set in the cobranding tool.
The fix
- Pin the branded hostname’s SSL cert explicitly. Resellers often set
cpanel.acmevpn.comas their branded entrypoint; that hostname needs an AutoSSL coverage entry or a manually installed cert. Without it, customers see browser warnings the day after install. - For account-creation emails, edit
/var/cpanel/templates/cpanel/account_creation_emails/as root and copy the per-reseller variant into a subdirectory the reseller’s accounts read. Document the file paths in your reseller onboarding doc — these are the most-asked questions during reseller calls. - Webmail branding goes in
/var/cpanel/webmail/<webmail_app>/styled/<reseller>/and survives webmail updates only if you stay inside that path. Editing the Roundcube core CSS will be reverted at the next webmail update — every time. - Make a backup of
/var/cpanel/customizations/brand/before any major cPanel version upgrade. cPanel does preserve this directory, but a corrupted upgrade has been known to nuke individual files inside it.
Reseller cobranding done right is part of why customers stay — Stack Harbor’s agency partner program includes the full cobranding setup, the SSL plumbing for branded hostnames, and the customer email templates as part of every reseller onboarding.