falazvahid
New member
- Joined
- Feb 14, 2026
- Messages
- 1
Hello,
I’m experiencing an issue with updating WHMCS on DirectAdmin that doesn’t happen on cPanel.
When I try to update WHMCS by moving the update files into public_html, DirectAdmin behaves differently than expected:
<span><span>statx (root=/home/username) domains/example.com/public_html/whmcs841/admin: no such file or directory<br>statx (root=/home/username) domains/example.com/public_html/whmcs841/install: no such file or directory<br></span></span>
<span><span><span>File</span></span><span> domains/example.com/public_html/aff.php already exists, file skipped<br></span><span><span>File</span></span><span> domains/example.com/public_html/clientarea.php already exists, file skipped<br></span><span><span>File</span></span><span> domains/example.com/public_html/templates already exists, file skipped<br></span></span>
…meaning that DirectAdmin skips existing files instead of merging or overwriting them, which causes the update to fail or leaves the installation in an inconsistent state.
The main problem is that I have a custom WHMCS template and some customizations, and they risk being overwritten or skipped during the update. On cPanel, this same update works perfectly because the upload/merge process handles existing files safely.
My question:
Thanks in advance for any advice!
I’m experiencing an issue with updating WHMCS on DirectAdmin that doesn’t happen on cPanel.
When I try to update WHMCS by moving the update files into public_html, DirectAdmin behaves differently than expected:
- Some directories (e.g., whmcs841/admin or whmcs841/install) show errors like:
<span><span>statx (root=/home/username) domains/example.com/public_html/whmcs841/admin: no such file or directory<br>statx (root=/home/username) domains/example.com/public_html/whmcs841/install: no such file or directory<br></span></span>
- Most files show messages like:
<span><span><span>File</span></span><span> domains/example.com/public_html/aff.php already exists, file skipped<br></span><span><span>File</span></span><span> domains/example.com/public_html/clientarea.php already exists, file skipped<br></span><span><span>File</span></span><span> domains/example.com/public_html/templates already exists, file skipped<br></span></span>
…meaning that DirectAdmin skips existing files instead of merging or overwriting them, which causes the update to fail or leaves the installation in an inconsistent state.
The main problem is that I have a custom WHMCS template and some customizations, and they risk being overwritten or skipped during the update. On cPanel, this same update works perfectly because the upload/merge process handles existing files safely.
My question:
- How can I safely update WHMCS on DirectAdmin without losing custom templates or modules?
- Is there a way to force DirectAdmin to merge and overwrite files like cPanel does?
- Any recommended workflow for WHMCS updates on DA to avoid this issue?
Thanks in advance for any advice!