Hello!
I have recently setup a LAMP stack on a CENTOS 7 staging server.
Currently, whenever I create a directory within /var/ww/html and place the duplicator files in that directory and try to unpack them, it says that there are not sufficient read / write permissions. Please see attached
I have changed the folder owner to apache:apache
Any help would be appreciated!
Unable to use WordPress Duplicator
Re: Unable to use WordPress Duplicator
This is almost certainly selinux trying to protect you since any app running under Apache and trying to write to its own docroot is seen as a hacker attempting to compromise your site. If you can install this from a linux command line then it would work but from within Apache httpd it is - correctly - forbidden. If you MUST run it via apache you could temporarily set selinux to permissive mode using setenforce 0 and then turn it back to enforcing mode afterwards with setenforce 1
And given how often there are wordpress exploits, you really want all the protection you can get on it so really really try to leave it enabled and don't just take the easy route of disabling it permanently.
And given how often there are wordpress exploits, you really want all the protection you can get on it so really really try to leave it enabled and don't just take the easy route of disabling it permanently.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
- KernelOops
- Posts: 428
- Joined: 2013/12/18 15:04:03
- Location: xfs file system
Re: Unable to use WordPress Duplicator
Unfortunately CentOS is not very clear about how to use /var/www/html and many tutorials and guides on the internet are giving incorrect information.
So to make it clear, /var/www/html IS FOR READ ONLY CONTENT unless you create a different ownership structure.
A wordpress site that needs to update itself, install/update themes, plugins and do all sorts of read/write work on files, can't run with the default CentOS configuration under /var/www/html (as the apache user).
Instead, my suggestion is to use /home directories and run Apache and PHP as that user. Thus, /home/domain/public_html can be used to read/write by the domain user and PHP can be restricted with open_basedir.
So to make it clear, /var/www/html IS FOR READ ONLY CONTENT unless you create a different ownership structure.
A wordpress site that needs to update itself, install/update themes, plugins and do all sorts of read/write work on files, can't run with the default CentOS configuration under /var/www/html (as the apache user).
Instead, my suggestion is to use /home directories and run Apache and PHP as that user. Thus, /home/domain/public_html can be used to read/write by the domain user and PHP can be restricted with open_basedir.
--
R.I.P. CentOS
--
R.I.P. CentOS
--
Re: Unable to use WordPress Duplicator
Running a wordpress site that has continual write access to itself is a recipe for compromise. That applies equally if run as the httpd user or as a normal one.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
- KernelOops
- Posts: 428
- Joined: 2013/12/18 15:04:03
- Location: xfs file system
Re: Unable to use WordPress Duplicator
Wordpress needs to maintain itself, install updates on its own, download themes and plugins. For normal usage, read/write access is required.
In rare cases, you can get it to run off a separate read/write area for the admin only but force it to run read-only for the public, or even generate static pages, but that is rather too advanced for most people who just want to run a site.
In rare cases, you can get it to run off a separate read/write area for the admin only but force it to run read-only for the public, or even generate static pages, but that is rather too advanced for most people who just want to run a site.
--
R.I.P. CentOS
--
R.I.P. CentOS
--