Skip to main content

Proxy Subdomains unsecured domains

Comments

11 comments

  • cPanelMichael
    :56:36 AM WARN The domain "www.mail.domain.com" failed domain control validation: You do not have a document root for the domain "www.mail.domain.com".

    Hello, It looks like AutoSSL is failing to validate the domain name due to a custom configuration for the mail subdomain on this account. Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome. Thank you.
    0
  • Nirjonadda
    Support Request ID is: 8355187
    0
  • cPanelMichael
    Hello, To update, removing the custom "www.mail" subdomain entries allowed the AutoSSL process to succeed. Thank you.
    0
  • Nirjonadda
    Hello, To update, removing the custom "www.mail" subdomain entries allowed the AutoSSL process to succeed. Thank you.

    Now proxy subdomains are not loading? Also mail. subdomains are not SSL certificates Work. cpanel.mysite.com mail.mysite.com webdisk.mysite.com webmail.mysite.com
    0
  • cPanelMichael
    Hello, To update, it looks like the issue was addressed after reinstalling the Mod Proxy EA4 RPM on the system (some of the existing proxy configuration values were missing). Thank you.
    0
  • morrow95
    I also stumbled upon this same error for the www.mail.domain.com on all accounts that are using autossl. Can you elaborate on your answer "To update, removing the custom "www.mail" subdomain entries allowed the AutoSSL process to succeed." and how to correct/remove this error? We have one subdomain setup on the entire server which has nothing to do with mail whatsoever (blog.domain.com). I thought maybe this was referring to dns entries for the domains, but those look perfectly fine as well. Where exactly is this error coming from and what do we do to correct it?
    0
  • cPanelMichael
    Hello @morrow95, The original poster's issue related to the use of custom "www.mail" alias entries in the account's cPanel userdata files (they were manually added). For the issue you are facing, the first step is to determine how the "www.mail" alias was added, as that's not a default configuration. Have you added a custom "mail.domain.com" subdomain or addon domain name on the affected account? Thank you.
    0
  • morrow95
    Hello @morrow95, The original poster's issue related to the use of custom "www.mail" alias entries in the account's cPanel userdata files (they were manually added). For the issue you are facing, the first step is to determine how the "www.mail" alias was added, as that's not a default configuration. Have you added a custom "mail.domain.com" subdomain or addon domain name on the affected account? Thank you.

    No, we have not. 3 out of 4 domains on this server have the problem. Why there is a single one without it I do not know, but coincidentally that was also the last domain/account we created in WHM as well and within the last year. The other three would have been created somewhere during 2015'ish I believe. We have always had WHM set to update on RELEASE tier.
    0
  • cPanelMichael
    Hello, You can manually remove the "www.mail" alias for each account from the corresponding userdata files. The userdata files are located within the following directory:
    /var/cpanel/userdata/$username/
    To know which files to edit, run a command such as:
    grep www.mail /var/cpanel/userdata/$username/*
    Note that you don't have to edit the "cache" files, but you should update them after making changes with the following command:
    /scripts/updateuserdatacache
    Then, once you save the changes, rebuild the Apache configuration file with the following command:
    /scripts/rebuildhttpdconf
    Thank you.
    0
  • morrow95
    Michael, Thanks - that did the trick. Appreciate it.
    0
  • cPanelMichael
    Hello, I'm glad to see that helped. Thank you for updating us with the outcome.
    0

Please sign in to leave a comment.