Links to all content generate a Apache Not Found error on Amazon EC2 Route 53

  • I installed WP on an Ubuntu 11.10 micro instance server.

    I have a the domain: https://www.fedruin.com routed through Amazon’s Route 53 service, which appears to be working well.

    The problem is, an Apache Not Found error is returned on any page other than the title page or a link that refers to a .php file in the root directory of the WP installation. I have consistantly had this problem anytime I have tried to install WP on my own on a Amazon EC2 server, so it make me think it is a config issue.

    I have tried putting WP into it’s own directory under var/www, as well as running the entire site under var/www (that is the root of the WP install is located at var/www)

    Apache is configured with the following mods active:

    alias
auth_basic
auth_n
authz_default
authz_groupfile
authz_host
authz_user
autoindex
cgi
deflate
dir
env
expires
headers
mime
negotiation
php5
reqtimeout
rewrite
setenvif
status

    This is the .htaccess file:

    # BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

    and the index.php file:

    # BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

    Any help would be greatly appreciated as I have been racking my head against this one for quite a while now. Thank you in advance

  • The topic ‘Links to all content generate a Apache Not Found error on Amazon EC2 Route 53’ is closed to new replies.

Tags