Possible reasons and solutions i) SELinux settings enforcing a file serve $ /etc/selinux/config Change SELINUX = disabled within the file and check if this is the cause for the error ii) Application directory under restricted user permission folder path For example, configuring the django project inside /root folder and trying to serve those files via apache server (apache user). Try changing the folder to a path that you think is good for allowing public access such /var/www or /opt/sites . (more…)

SELinux is a feature that may be turned on certain servers and it can restrict access to certain ports. In order to gain access and make the ports work, you need to open those ports. To see if SELinux is set, type $ sestatus To list all port, try the semanage command $ semanage port -l To check for a specific port that is opened $ semanage port -l | grep 8085 To allow access to a specific port $ semanage port -a -t http_port_t -p tcp 8085

Some possible solutions to this problem: i) Check if .htaccess file is making any redirections ii) Check if /LocalSettings.php have any invalid reference to root ii) If you have freshly installed the server, check if AppArmor or SELinux is installed on the machine. If it is try to remove those software and try you website url. To remove appArmor follow the below steps: $ /etc/init.d/apparmor stop $ update-rc.d -f apparmor remove $ apt-get remove apparmor apparmor-utils

How to find the status of SELinux? $ cat /selinux/enforce The above command will print 0 or 1 which means, 0 – permissive mode 1 – enforcing mode (more…)