The server’s hostname conflicts with domain ownership for the user “nobody”

The Emperor

Member
May 9, 2018
16
1
3
Greece
cPanel Access Level
Root Administrator
I have the same problem for my.hostname.com for which I get notifications

The server’s hostname conflicts with domain ownership for the user “nobody”.
.

Some facts
.
  • /var/cpanel/users/nobody is empty

  • There is no file for my.hostname.com in /var/cpanel/users


  • It exists only in /var/cpanel/users/system

  • In WHM there is no Account (domain) for my.hostname.com , there is only for hostname.com


  • There is no DNS Zone for my.hostname.com , there is only for hostname.com with an A Record pointing to my.hostname.com 14400 IN A public_IP

  • my.hostname.com has been assigned an AutoSSL without issues

  • my.hostname.com has Reverse DNS working without issues
.
Unfortunately I have not seen a specific answer about that from cPanel support in this thread which started 2 years ago. It seems like they suggested to turn off notifications with the cost of getting in bigger troubles.

I created a new one since the system suggested me not to reply but create a new one instead because the thread was more than 1 year old.

This thread is more than 1 year old.
It is very likely that it does not need any further discussion and thus bumping it serves no purpose. Please feel free to start a new thread on this topic if needed.
 

dstana

Well-Known Member
Jul 6, 2016
109
19
68
Phoenix, AZ
cPanel Access Level
Root Administrator
That can't be right, there needs to be a cPanel account to run autossl. There also has to be an A record for the domain that resolves to the requesting server for autossl to work.

What's the output from
Code:
cat /etc/domainusers | grep my.hostname.com
 
Last edited:

The Emperor

Member
May 9, 2018
16
1
3
Greece
cPanel Access Level
Root Administrator
That can't be right, there needs to be a cPanel account to run autossl. There also has to be an A record for the domain that resolves to the requesting server for autossl to work.
First of all , cPanel provides AutoSSL for setup hostnames (for ex. my.hostname.com) without having to have a cPanel account for the my.hostname.com itself. 56 Release Notes - Version 56 Documentation - cPanel Documentation.

Also if you read the facts again you'll see that I mention that the main domain hostname.com (not the my.hostname.com which is set as system hostname) does have an A record that points to my.hostname.com , it couldn't be different from that.

What's the output from
Code:
cat /etc/domainusers | grep my.hostname.com
Secondly the result is nothing, of course.
 
Last edited:

cPanelLauren

Product Owner II
Staff member
Nov 14, 2017
13,266
1,301
363
Houston
Hello


The Hostname SSL certificate is different than the AutoSSL process, no account is needed to provision the hostname SSL and the process runs completely separately from the AutoSSL process.


@The Emperor what is present in /var/cpanel/users/system?
Code:
cat /var/cpanel/users/system
also what is the output when you run the following:

Code:
/scripts/updateuserdomains
 

The Emperor

Member
May 9, 2018
16
1
3
Greece
cPanel Access Level
Root Administrator
@cPanelLauren

Code:
cat /var/cpanel/users/system
Code:
BWLIMIT=unlimited
DEMO=0
DNS=
DNS1=my.hostname.com
FEATURELIST=default
HASCGI=0
HASDKIM=0
HASSPF=0
IP=127.0.0.1
LEGACY_BACKUP=1
LOCALE=en
MAILBOX_FORMAT=maildir
MAXADDON=0
MAXFTP=unlimited
MAXLST=unlimited
MAXPARK=0
MAXPOP=unlimited
MAXSQL=unlimited
MAXSUB=unlimited
MAX_EMAILACCT_QUOTA=unlimited
MTIME=1509319890
OWNER=root
PLAN=undefined
RS=paper_lantern
STARTDATE=0000000000
USER=system
__LOCALE_MISSING=1
.

Code:
/scripts/updateuserdomains
Nothing
 

cPanelLauren

Product Owner II
Staff member
Nov 14, 2017
13,266
1,301
363
Houston
Hi @The Emperor


There's the issue:

Code:
DNS1=my.hostname.com
Can you change that line to look like this:

Code:
# grep DNS /var/cpanel/users/system
DNS=
Then run:

Code:
/scripts/updateuserdomains
/scripts/updateuserdatacache
and let me know if the issue persists?
 

The Emperor

Member
May 9, 2018
16
1
3
Greece
cPanel Access Level
Root Administrator
Hello @cPanelLauren

There's no typo that line should NOT have the hostname on it. The DNS line should be
Code:
DNS=
.

But the line

Code:
DNS=
is already as you suggest, with no value, and certainly it has not the hostname.

Do you mean to remove the line below which is for DNS1 and does have the hostname?

I am certain you write it wrong and you possibly mean to empty the DNS1 line
.

 
Last edited:

cPanelLauren

Product Owner II
Staff member
Nov 14, 2017
13,266
1,301
363
Houston
Hello @The Emperor


Again, I'm indicating that you need to modify that line, not add an additional line. The line:

Code:
DNS1=my.hostname.com
Needs to be modified to

Code:
DNS=
The hostname should NOT be included in this file. The output I provided came directly from my own server. You can even remove the line:

Code:
DNS1=my.hostname.com
 

The Emperor

Member
May 9, 2018
16
1
3
Greece
cPanel Access Level
Root Administrator
So in a few words I delete (or comment out) the DNS1 line since only this one needs to do something with and not the DNS line which does not need modification.

And that is why the following command could not change anything, since DNS= was already empty and it did not help to remove DNS1=my.hostname.com line which was the actual mistake.

Code:
# grep DNS /var/cpanel/users/system
DNS=
.

Glad that we make it clear by the easiest way. So, I commented out DNS1=..

I run without issues or notifications

Code:
/scripts/updateuserdomains
/scripts/updateuserdatacache
I will update the thread in the next few days because I was getting the warning only every few days, except if you know a way to push this check.

Thank you @cPanelLauren
 

cPanelLauren

Product Owner II
Staff member
Nov 14, 2017
13,266
1,301
363
Houston
Hi @The Emperor

I'm glad we got that figured out and I'm sorry for the confusion. Please do let us know if it persists now with the hostname reference removed from /var/cpanel/users/system

Thanks!
 

cPanelLauren

Product Owner II
Staff member
Nov 14, 2017
13,266
1,301
363
Houston
Hi @Solodeji

Yes there does need to be an A record, but this has nothing to do with what I'm requesting he remove. The A record should exist in the DNS Zone file.
 
Last edited:

The Emperor

Member
May 9, 2018
16
1
3
Greece
cPanel Access Level
Root Administrator
Hi @Solodeji

Yes there does need to be an A record, but this has nothing to do with what I'm requesting you remove. The A record should exist in the DNS Zone file.
@cPanelLauren

Just for the record, I am the one that you were instructing me how to fix it and certainly I am not the user @Solodeji whom you just replied to his post.

By the way, now that a few days have been passed, I haven't yet received that warning again so I suppose that issue is solved.

Thanks again
 

cPanelLauren

Product Owner II
Staff member
Nov 14, 2017
13,266
1,301
363
Houston
HI @The Emperor

I'm glad to hear that you haven't received the warning again and everything now seems to be in order. I also fixed my response as it should have noted "he" not "you"