I have been trying to setup cakephp on an Amazon EC2 (Ubuntu) instance ..
however when i try running the code .. it shows no color, no
styles, no layout etc.
I have updated the httpd.conf with the following content ..
Options Indexes FollowSymLinks
AllowOverride All
It still doesnt seem to work.
What is it that am doing wrong ???
Regards
Abhishek Jain
I had the same problem. Found out that my .htaccess files didn't have the permission to override anything, because AllowOverride was set to none.
I looked for the value in my httpd.conf file under /etc/httpd/conf/ and changed it to All
<Directory "/var/www/html">
AllowOverride All
</Directory>
Not EC2 related but I had a simmilar issue on the Mac when installing CakePHP on Mamp. A complete delete of all the CakePHP files and a re-install solved the issue for me.
I don't have much too much experience installing Cake, but you should probably check the following anyway:
a) Do you have the correct .htaccess files in the correct directories? Linux treats anything that starts with '.' as a system file, so you have to do
ls -a
to check if they are present. If you moved the files into the directories manually, instead of unpacking the Cake download in the location you wanted it, the .htaccess files may not have been moved.
b) Check your Apache error logs (I assume you're using apache) for errors, especially errors loading mod_rewrite. Make sure LoadModule rewrite_module libexec/httpd/mod_rewrite.so and AddModule mod_rewrite.c are specified in httpd.conf.
c) Where did you put this?
Options Indexes FollowSymLinks AllowOverride All
Without seeing more of your httpd.conf, there's no way of telling whether the Cake document root is inheriting these settings correctly.
Related
I am trying to set up Apache2 on my Ubuntu system. It's has been installed and working. The problem is that I'm working on an AngularJS project and I need a server for my html pages. Right now the directory is set to:
<Directory /var/www/html>
Options FollowSymLinks
AllowOverride None
Require all granted
</Directory>
When ever I try to change it to a specific path I always get the 403 Forbidden error. The path I want it changed to is:
/home/michael/dev/JavaScript/AngularJS/Quiz App
When the system is set to the default path and I reload my html page using Sublime Text and I get a 404 error. The html page is:
http://localhost/01_01/index.html
I've been up all night trying to fiqure this out and did the best I could to resolve it. I'm open to any possible solutions you guys may have.
It is because Apache2 does not have permission to access path within your home directory. One thing you can do is to create a symbolic link in /var/www/html and pointing it to your code directory.
ln -s "/home/michael/dev/JavaScript/AngularJS/Quiz App" /var/www/html/quizApp
No open the browser and type localhost/quizApp and you should be able to open your app in the browser
I installed Nagios on my system (Fedora 21) but when I start it from the browser it throws the error:
Unable to get process status error.
I have added the following lines in my httpd.conf file
ScriptAlias /nagios/cgi-bin/ "/usr/local/nagios/sbin/"
AllowOverride AuthConfig
Options ExecCGI
Order allow,deny
Allow from all
Alias /nagios/ "/usr/local/nagios/share/"
<Directory "/usr/local/nagios/share/">
Options None
AllowOverride AuthConfig
Order allow,deny
Allow from all
</Directory>
nagios.log entries:
[1423829856] Warning: Return code of 127 for check of service 'Total Processes' on host 'localhost' was out of bounds. Make sure the plugin you're trying to run actually exists.
In my case the resolution was sinply to start the Nagios service as
sudo systemctl start nagios.service
after which the error that you were seeing as
Unable to get process status error.
should now look something like
Daemon running with PID 9027
I think there is an issues with the nagios-plugins, You will have to reinstall it. Please try with the following command.
yum reinstall nagios-plugins
I was facing the same issue while upgrading to the newer version of Nagios Core.
After adding the following two lines into nagios.conf:
state_retention_file=/usr/local/nagios/var/retention.dat
status_file=/usr/local/nagios/var/status.dat
the problem doesn't persist anymore!
Thanks to Pety's answer above, I found that my issue was that the ownership of the directory where the "status_file" and "state_retention_file" did not allow nagios account to read/write files. Correcting ownership seemed to fix my issue.
When using the Views admin panel, it appears completely mispresented. Looking at the files being accessed, it turns out that the needed css files are not loaded. My Drupal installation is within a /drupal/ subfolder, and when the module is trying to access domain.com/sites/all/modules/views/css/views.css a 404 is received.
I tried browsing manually to domain.com/drupal/sites/all/modules/views/css/views.css and it works, therefore the file is there and can be accessed from the web.
The strange thing is that for other folders there is no problem, for example both domain.com/modules/user/user.css and domain.com/drupal/modules/user/user.css work. It seems like a problem with sites/ only...
I do not have CSS optimization enabled, and all folders within sites/ have a 755 permission. Is there some configuration setting I'm missing?
Apparently, the domain I'm concerned about is a parked domain (or whatever this is called) for another one, and contained in a subfolder of public_html. Drupal installation, thus, is a subfolder of that subfolder (say, /home/user/public_html/my_domain/drupal) and all requests for my domain are redirected via an .htaccess and MOD_REWRITE, to the Drupal subfolder. For some reason, it didn't have the sites/ in its regexp (modules/ and themes/ were...).
You may have incorrect vhost configuration. In order to check if this is the reason, try accessing the site without the vhost i.e. localhost/drupal and see if this works.
If it loads correctly, then you need to set up the correct document root:
<VirtualHost *:80>
DocumentRoot /www/drupal
ServerName domain.com
</VirtualHost>
Then restart apache.
For more information about how to set up vhost, visit http://httpd.apache.org/docs/2.2/vhosts/examples.html
I am trying to get my OSX MacPorts install of Apache to NOT show directory listings. I have tried various configurations of the "options" directive in the httpd.conf file with no luck. When I go to the site, it still lists the root directory (there is no index file at the moment.)
Apache has been restarted after each change.
There is no .htaccess file in the / directory, so there shouldn't be anything overriding.
This is driving me crazy!
So basically something is overriding your config. From the documentation of apache we can read that Options is can be placed in various context: server config, virtual host, directory, .htaccess.
httpd.conf is read first, so if You provided the configuration properly there, it means that it is overridden somewhere else
How did You do enter the options in the config ? In the most basic variant it should be.
<Directory /path>
Options -Indexes
</Directory>
Here what you should do:
check module configurations in modules for Options Indexes
check the main virtualhost definition, probably called default or 000-default
If it still does not help, add Options -Indexes to your virtualhost directly (provided you have not done it already). Or add it to the .htaccess file in your directory (allowing Options in .htaccess needs to be switched on)[as suggested in comments]
I am trying to install typo3 as per the instructions but I have a bit of a puzzle to solve.
It seems apache denies access to any files I try to access via any symbolic link in the site root directory. I have changed permissions from SymLinksIfOwnerMatch to FollowSymLinks and no joy.
I'm working on mac OSX (SL) and installing in my user's "Sites" directory. I can access any files in this CMS directory via the web browser just not anything through symbolic links.
I hope konsolenfreddy's comment was helpful already. I am trying to round things up here:
First check if the symlinks work from terminal and/or the filesystem in general.
Also, if you use absolute paths, the whole path from root to the file in question must be readable by the Apache user. *
If yes, check if the AllowOverride option is set for your webserver (or if applyable for the virtual host) For debugging you can set AllowOverride All in either apache2.conf, httpd.conf or in sites-available/default
If yes, check if FollowSymlinks is aktivated in any of the files responsible for your webroot, starting with apache2 working yourself down to the .htaccess files.
Try changing file permissions on the symlink file and the target directory (or files)
Try creating your own symlink and see what happens when you call it in the browser.
* Check this answer at askubuntu.com for more hints.
Ok I eventually solved it. In OSX the final file that governs access of sites installed in user directories is the last Include line in the apache2/conf/extra/httpd-userdir.conffile. Once I changed that my problems went away.
Thanks to all the people that replied my questions.