Moving domain from one user to another causes "the new home is blank"

bluesteam

Verified User
Joined
Jan 28, 2021
Messages
66
Hi,

I have followed the following process to move a domain from one user to another user:


and this one:


so my first step was to create the new user with fakedomain.com and then I ran the script with the necessary parameters from old user to the new user but I get the following message:

[root@admin scripts]# ./move_domain.sh georgesplace.com theolduser thenewuser
the new home is blank
[root@admin scripts]#

Obviously I replaced theolduser and thenewuser with the correct values.

So what could be wrong that I cannot move this domain between the two users?
 
So what could be wrong that I cannot move this domain between the two users?
Seems there is a redirect in place at the moment from georgesplace.com to another restaurant site.

Anyway, did the old user have a mysql database working?
If yes, check if that is moved. If no, you have to move it manually.
If it is moved, then you probably have to change the credentials in the config of the php/mysql website.
Probably olduser_dbname and olduser_dbuser need to be changed to newuser_dbname and newuser_dbuser.
 
Thanks Richard but georgesplace.com was actually just a random name I pulled out of the air to protect privacy! :ROFLMAO:

The domain is setup on the reseller account as the parent. I want to move it from the reseller user to another user that also belongs to the same reseller. The site is a very simple set up. It has a website with a database on the domain with 3 email accounts.

I simply want to move the domain from the parent reseller user to another user on the same reseller.

So I ran the move_domain.sh script and that was the result I got above.

I would have moved the databases afterwards had anything else actually moved but nothing moved at all.

Any ideas?
 
name I pulled out of the air
Oh LoL. Wel next time best is to use domain.com or example.com if you want to keep your domain hidden. :)

had anything else actually moved but nothing moved at all.
Oh that's odd. You didn't say that before. Since you only said you got a white page I was under the impression it was moved, but just gave a blank page.

I simply want to move the domain from the parent reseller user to another user on the same reseller.
Why using the second link then? Creating the fake user is no need for if you want to move to an existing user. Confusing. :)
I presume you want to split domains from 1 user to 2 user accounts from which 1 is a new user you made, right?

Oke lets see, so everything is still present on the old user's account?
Is it only the notice or is the /home/newuser/domains/domain.com/public_html really empty?
 
Oh that's odd. You didn't say that before. Since you only said you got a white page I was under the impression it was moved, but just gave a blank page.
I never said anything about a white page. Not sure where you read that.

Why using the second link then? Creating the fake user is no need for if you want to move to an existing user. Confusing. :)

Just a misunderstanding. The current domain is not on its own separate user. It is linked directly to the reseller user and I want to move this domain on to it's own user account.

So, the instructions tell me to create a new user for the domain where I need to move the domain to so that's what I did.

I presume you want to split domains from 1 user to 2 user accounts from which 1 is a new user you made, right?
No. I want to move a domain linked to a reseller user to it's own user.

Oke lets see, so everything is still present on the old user's account?
Correct. After running that script, nothing actually moved. Instead the output of the script was:

"the new home is blank"

Is it only the notice or is the /home/newuser/domains/domain.com/public_html really empty?

I assume you're referring to the new account/user, it's Empty even after running the script.
 
Not sure where you read that.
You stated the new home is blank. So I thought this ment the new home page had a blank page.

No. I want to move a domain linked to a reseller user to it's own user.
So yes then. Because it must be on some user now too. Admin and reseller are also users too. ;)

Anyway, it's clear now what the intention is and why you used the method with the fake domain.

Is the domain still working on the old user or not? If not, is it possible to run the move_domain script again, the other way around (so from new user to old user) to see if it starts working again then?

Is in fact the domainname transferred (without content) or is the domain name not transferred to the new user?

Are you using plain apache or something like Litespeed? No custom apache scripts?

The script should at least move the content to the new user, so there must be a bug, maybe due to some changes in DA itself.
If you are on a license with ticket support, it might be wise to send in a ticket about this.

P.s. which OS and version are you on? Maybe I can test too.
 
You stated the new home is blank. So I thought this ment the new home page had a blank page.
No I didnt state that. What you read was the actual response message that came back from when I ran the move_domain.sh script. It was the output of the script. my text showed it was between 2 command line entries ;-)

So yes then. Because it must be on some user now too. Admin and reseller are also users too. ;)

Anyway, it's clear now what the intention is and why you used the method with the fake domain.

Is the domain still working on the old user or not? If not, is it possible to run the move_domain script again, the other way around (so from new user to old user) to see if it starts working again then?

Is in fact the domainname transferred (without content) or is the domain name not transferred to the new user?
Still works fine as nothing was moved at all.

Are you using plain apache or something like Litespeed? No custom apache scripts?
apache

The script should at least move the content to the new user, so there must be a bug, maybe due to some changes in DA itself.
If you are on a license with ticket support, it might be wise to send in a ticket about this.
yh I think Ill open a ticket :-)

P.s. which OS and version are you on? Maybe I can test too.
Cloudlinux 7.9
 
Seems to be caused by Cloundlinux.

Just tested to be sure on our Centos 7.9 server with a fake domain. That worked without issues, only errors notices on non existing pointers and awstats which is normal because there were not stats yet. Content was transferred.

Ticket is best solution then I guess.
 
Seems to be caused by Cloundlinux.

Just tested to be sure on our Centos 7.9 server with a fake domain. That worked without issues, only errors notices on non existing pointers and awstats which is normal because there were not stats yet. Content was transferred.

Ticket is best solution then I guess.
Thank you so much for your time and effort :-D
 
Back
Top