Article ID: 121027, created on Apr 11, 2014, last review on May 11, 2014

  • Applies to:
  • Plesk 11.0 for Linux
  • Plesk 11.5 for Linux


Source server runs Debian or Ubuntu, the destination runs RedHat, CentOS or CloudLinux, or conversely. Permission problems on websites after Plesk migration/transfer are appeared.


If Apache user name from the source server does not exist on the destination server, the data created by Apache modules such as PHP or Python have numeric ownership instead of Apache user. This is because rsync cannot assign correct ownership.


Apache user name from source server should be created on destination server with ID of destination Apache user.

Destination: Ubuntu or Debian
Source: RedHat, CentOS or CloudLinux

  1. Get "www-data" GID:

    # id -g www-data
  2. Create "apache" group with this GID:

    # groupadd apache -og 33
  3. Get "www-data" UID:

    # id -u www-data
  4. Create "apache" user with this UID:

    # useradd apache -u 33 -c www-data -og www-data -G www-data,psaserv,psasb -d /var/www -s /sbin/nologin
  5. Check the result:

    # id apache
    uid=33(www-data) gid=33(www-data) groups=33(www-data),1003(psaserv),2523(psasb)

Destination: RedHat, CentOS or CloudLinux
Source: Ubuntu or Debian

  1. Get "apache" GID:

    # id -g apache
  2. Create "www-data" group with this GID:

    # groupadd www-data -og 48
  3. Get "apache" UID:

    # id -u apache
  4. Create "www-data" user with this UID:

    # useradd www-data -u 48 -c apache -og apache -G apache,psaserv,psasb -d /var/www -s /sbin/nologin
  5. Check the result:

    # id www-data
    uid=48(apache) gid=48(apache) groups=48(apache),504(psaserv),506(psasb)

The same method can be applied to SuSE, but default apache user:group is wwwrun:www. Also User name and user ID can be different from default values, so this migration issue can occur even if OS is the same on both servers.

Search Words



a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 01bc4c8cf5b7f01f815a7ada004154a2 29d1e90fd304f01e6420fbe60f66f838 0a53c5a9ca65a74d37ef5c5eaeb55d7f aea4cd7bfd353ad7a1341a257ad4724a

Email subscription for changes to this article
Save as PDF