Serious Permission Issues with your product when it comes to migrated sites

[adnetza]

Your product has some very serious permission issues when it to comes to migrating sites and im not just talking about file level where a basic chown admin -R would should correct the problem, so let me explain and start at the beginning. I have installed your software on 2 CentOS VMs without issue, so BRAVO on an excellent install script. So after a successful install i proceed to migrate my wordpress sites and DB to the new platform. site files were migrated under admin user, created db under admin_blahblah, ran chown admin -R /home/admin/web/blahblahblah.com/public_html/ and edited the wp-config to reflect the new info to connect to the new db.

All good.

I was able to bring up websites just fine and login as Site Admin user. then I realized i couldnt update ANYTHING in the site such as plugins, permalinks or run scripts. After several hours searching google and of course your forum which i found nothing worth while to correct the problem, i proceeded with a test which might force permissions elsewhere. So, I created a new user in addition to the existing admin and executed the v-change-domain-owner blahblahblah.com newuser which completed with error. i was able to make edits to the plugins and change the permalinks (WHICH WILL TAKE OF THE 404 FOR MIGRATED SITES). I was stoked!

so i continuted my site migratons under the new user with the same process as under the admin user. And GUESS WHAT? it didnt work! i executed the chown and still no joy.

then i realized the issue. the site scripts cant query the DB one way or the other! Wordpress sees DB Server but not the DB. It even gives me the YOUR USER NAME AND PASSWORD ARE FINE but wheres the db!


the only way i can get a 100% working site is if i do the following which is horrible.

1. Migrate site under admin user
2. create db under admin user
3. execute chown admin -R /home/admin/web/blahblahblah.com/public_html/
4. edit wp-config to relate new db information
5. bring up site to insure successful rendering of index page

THEN (this is the best)

6. execute v-change-domain-user blahblahblah.com newuser
7. login to site, go to settings, click permalink and click save.

site is 100%

ridiculous.

this needs to be resolved

i or anyone under any user should be able to migrate an existing site, execute chown and have a working site.

give me some assistance and please correct for others.

[tjebbeke]

In the latest version, there are some bugs. We are working on it to fix this. You can always create a bug report so we can check this out in detail.

[dpeca]

You had on first server site under 'someuser' account (it wasn't 'admin') and then you imported it to other server under 'admin' account?
Am I understood you right?

I'll never imported or put sites under 'admin' account, I'm afraid that PHP scripts can execute binaries under 'admin' account, which is as 'root' (let me correct somebody if I'm wrong).

Also, I'll never import backup as other username (in this case 'admin'), because, logically, by changing username a chance to something goes wrong is many times larger.

[adnetza]

no. all files and users are on the same server. maybe i shouldnt have mentioned the second server BUT the issue can be duplicated on both VestaCP servers!

if you are asking where the migration originated from then the answer is a CPanel server. the user on the Cpanel was the site name. thats how cpanel does it.... /home/blahblah/public_html/

[adnetza]

In the latest version, there are some bugs. We are working on it to fix this. You can always create a bug report so we can check this out in detail.

are you saying this is a bug??

[tjebbeke]

In the latest version, there are some bugs. We are working on it to fix this. You can always create a bug report so we can check this out in detail.

are you saying this is a bug??

I don't say it is a bug, but it is possible.

You say that you have made edits to the v-change-domain-owner script? What kind of changes have you done? Maybe you edit a part and thats why it isn't working.

So, I created a new user in addition to the existing admin and executed the v-change-domain-owner blahblahblah.com newuser which completed with error. i was able to make edits to the plugins and change the permalinks (WHICH WILL TAKE OF THE 404 FOR MIGRATED SITES). I was stoked!

[adnetza]

In the latest version, there are some bugs. We are working on it to fix this. You can always create a bug report so we can check this out in detail.

are you saying this is a bug??

I don't say it is a bug, but it is possible.

You say that you have made edits to the v-change-domain-owner script? What kind of changes have you done? Maybe you edit a part and thats why it isn't working.

So, I created a new user in addition to the existing admin and executed the v-change-domain-owner blahblahblah.com newuser which completed with error. i was able to make edits to the plugins and change the permalinks (WHICH WILL TAKE OF THE 404 FOR MIGRATED SITES). I was stoked!

no. i didnt say i edited the script. i executed the script to change domain users.

[dpeca]

if you are asking where the migration originated from then the answer is a CPanel server. the user on the Cpanel was the site name. thats how cpanel does it.... /home/blahblah/public_html/

you imported site from cPanel?
manually or you used some script for import from cPanel to Vesta?

[adnetza]

if you are asking where the migration originated from then the answer is a CPanel server. the user on the Cpanel was the site name. thats how cpanel does it.... /home/blahblah/public_html/

you imported site from cPanel?
manually or you used some script for import from cPanel to Vesta?

yes i used rsync