Symptoms
The domains hosted on the server have all had Alias domains added similar to the following:
domain.tld.cpanel.site
domain.tld.cprapid.com
Description
cPanel version 124 introduced the "Autodomain" feature, which adds a domain alias per-VirtualHost that is associated with the "cprapid.com"/"cpanel.site" hostname tied to your server. These are added to the Apache configuration automatically, and are not intended to be "real" Alias domains that are managed by your users. The intention of this "Autodomain" is to provide a ready-to-use domain name to begin building your website while propagation occurs, or when a domain is still pointed to a different host.
When the "userdata_upgrade" script is called, these "Autodomain" aliases are added to the cPanel userdata for all domains hosted on the server which makes these visible to all accounts, adds them to AutoSSL coverage, and counts against a user's Alias Domain limit.
We've opened an internal case for our development team to investigate this further. For reference, the case number is CPANEL-46965. Follow this article to receive an email notification when a solution is published in the product.
Workaround
The "userdata_upgrade" is only called when certain action is taken on the server, such as when the Apache ports are changed or the EA-NGINX service is installed on the server. There is no method to prevent this from occurring when these tasks are performed.
If the server has been impacted by this, the following one-liner will iterate over all users and remove these aliases:
while read -r line; do line=$(echo "$line" | grep -E "cprapid.com|cpanel.site"); [ ! -z "$line" ] && cpapi2 --user=$(echo $line | cut -d':' -f2 | tr -d ' ') Park unpark domain=$(echo $line | cut -d':' -f1); done < /etc/userdomains
Comments
1 comment
Update: We would like to thank you for your interest in this article/case and encourage your submissions as they are valuable to the ever-expanding development of cPanel & WHM. At this time, this particular issue has not been selected for action from our Development Team, as it may require more development resources than we can allot, or alters the direction cPanel envisions for the product. Submissions persist in our Issue Tracking System in the event the impact of the related issue grows or product direction changes. If you feel that this defect requires direct action, we strongly encourage you to submit a Feature Request to allow the cPanel Community to vote and support your cause.
Thank you again for helping us make cPanel & WHM the hosting platform of choice.
Article is closed for comments.