Write permission fix
https://www.opencart.com/index.php?route=marketplace/extension/info&extension_id=31130
Add JSON SUPPORT for PHP
sudo yum install php-pecl-json
Permission issue:
sudo semanage fcontext -a -t httpd_sys_rw_content_t "/var/www/html/.*?"
sudo semanage fcontext -a -t httpd_sys_rw_content_t "/var/www/html/load/opencart/htdocs"
sudo restorecon -Rv /var/www/html/
Source:
https://stackoverflow.com/questions/36577020/php-failed-to-open-stream-no-such-file-or-directory
If you are running Security-Enhanced Linux, then it might be the reason for the problem, by denying access to the file from the server.
To check whether SELinux is enabled on your system, run the sestatus
command in a terminal. If the command does not exist, then SELinux is not on your system. If it does exist, then it should tell you whether it is enforced or not.
To check whether SELinux policies are the reason for the problem, you can try turning it off temporarily. However be CAREFUL, since this will disable protection entirely. Do not do this on your production server.
setenforce 0
If you no longer have the problem with SELinux turned off, then this is the root cause.
To solve it, you will have to configure SELinux accordingly.
The following context types will be necessary :
httpd_sys_content_t
for files that you want your server to be able to read
httpd_sys_rw_content_t
for files on which you want read and write access
httpd_log_t
for log files
httpd_cache_t
for the cache directory
For example, to assign the httpd_sys_content_t
context type to your website root directory, run :
semanage fcontext -a -t httpd_sys_content_t "/path/to/root(/.*)?"
restorecon -Rv /path/to/root
If your file is in a home directory, you will also need to turn on the httpd_enable_homedirs
boolean :
setsebool -P httpd_enable_homedirs 1
In any case, there could be a variety of reasons why SELinux would deny access to a file, depending on your policies. So you will need to enquire into that. Here is a tutorial specifically on configuring SELinux for a web server.
No comments:
Post a Comment