• wp-questions

    (@wp-questions)


    Hi,

    I have a 3.5.1 subdomain multisite network with 2 subdomains and 3 websites (using MU plugin)
    The site is hosted on AWS EC2 (Bitnami) with an elastic static IP.

    Up until this morning all the sites including the root site were working ok. Then when I tried to access my root site I was getting redirected to the AWS hostname!

    I checked the wp-config file and sure enough there was a change on this line:
    define( ‘DOMAIN_CURRENT_SITE’, ‘mydomain.net’ );
    TO THIS: define( ‘DOMAIN_CURRENT_SITE’, ‘ec2-xx-xx-xx-xx.compute-1.amazonaws.com’ );

    I reverted back to the original config: define( ‘DOMAIN_CURRENT_SITE’, ‘mydomain.net’ );
    but now I get an error page:
    This webpage has a redirect loop
    Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.

    I’ve looked for an .htaccess file but could not find any on my Bitnami AWS instance (checked all folders uner htdocs). The only thing remotely close to .htaccess was wordpress.conf:

    <IfVersion < 2.3 >
    NameVirtualHost *:80
    </IfVersion>

    <VirtualHost *:80>
    ServerAdmin mail@example.com
    DocumentRoot “/opt/bitnami/apps/wordpress/htdocs”

    <Directory “/opt/bitnami/apps/wordpress/htdocs”>
    Options +MultiViews +FollowSymLinks
    AllowOverride None
    <IfVersion < 2.3 >
    Order allow,deny
    Allow from all
    </IfVersion>
    <IfVersion >= 2.3>
    Require all granted
    </IfVersion>

    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]

    # uploaded files
    RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]

    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ – [L]
    RewriteRule . index.php [L]
    </Directory>
    </VirtualHost>

    Please help me!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter wp-questions

    (@wp-questions)

    any input? :/

    Steve Blackwood

    (@bluesplinter)

    I don’t see a “ServerName mydomain.com” directive in your VirtualHost block. Do you have an old version from when it worked to compare it to?

    Thread Starter wp-questions

    (@wp-questions)

    not sure if I have an older version but will check.

    So I changed my wp-config.php to have DOMAIN_CURRENT_SITE as ec2-xx-xx-xx-xx.compute-1.amazonaws.com and now when I login to the network through the Amazon EC2 domain name it works and I can see all the sites and have all the network dashboard functions.

    Under Sites it looks like the main site is also now ec2-xx-xx-xx-xx.compute-1.amazonaws.com (I assume this is due to the change in wp-config?)

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Root network domain not working’ is closed to new replies.