500 Error in subdomain admin only

  • Resolved trigger571

    (@trigger571)


    13 years, 3 months ago

    Hi all,

    Newbie on Multisites. I have configured and installed multisites without a problem (or so I thought) Front end main domain and subdomains working, backend as SuperAdmin all works. Even the Dashboard for the main site works. However, when I go to click on the sub-domain dashboard I get an internal error.

    My error logs show the following:

    [Tue Aug 30 03:10:42 2011] [warn] RewriteCond: NoCase option for non-regex pattern '-f' is not supported and will be ignored.
[Tue Aug 30 03:10:44 2011] [error] [client 118.173.86.244] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.

    Other than that, I have no errors in the log.

    My wp_config.php looks like this:

    * in their development environments.
 */
define('WP_DEBUG', false);
define( 'MULTISITE', true );
define( 'SUBDOMAIN_INSTALL', true );
$base = '/';
define( 'DOMAIN_CURRENT_SITE', 'nameofmysite.com' );
define( 'PATH_CURRENT_SITE', '/' );
define( 'SITE_ID_CURRENT_SITE', 1 );
define( 'BLOG_ID_CURRENT_SITE', 1 );

/* That's all, stop editing! Happy blogging. */

    while .htaccess looks like this:

    # Use PHP5 Single php.ini as default
AddHandler application/x-httpd-php5s .php

# BEGIN WordPress

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]

# END WordPress

    Any ideas anyone? Thanks

Viewing 9 replies - 1 through 9 (of 9 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Did the subdomain work before WordPress was applied?

    Thread Starter trigger571

    (@trigger571)

    No I did not have any subdomains before that. But as I said, subdomains using WordPress multisite does work on the front end, but not in the dashboard of the subdomain.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    I would guess that your .htaccess isn’t being read correctly, and that allowoverride isn’t set to All on your httpd.conf

    On the front end of your subdomains, does the CSS look right?

    Thread Starter trigger571

    (@trigger571)

    Actually there is nothing on the front end of the subdomain other than the host page parked page:

    https://test.thailandhotelmarketing.com/

    Thanks for your BTW input Ipstenu.

    then you do not have wildcard subdomain set up correctly. they should point to the main install, not a new folder.

    Thread Starter trigger571

    (@trigger571)

    Yep – that was the issue.

    Basically, for the benefit for anyone to make this silly mistake, here is what happened.

    In CPanel, I created the wildcard * .domain.com

    The problem is that by default, CPanel interprets that * as a folder and thus created a new folder called wildcard.

    So, if you do set this up and have problems, check your subdomain again. If you see it created a folder called wildcard, delete the subdomain, then re-create it. Before saving your subdomain, make sure the field in Document Root is empty.

    Thanks for your help Andrea_r and Ipstenu.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    What version of cPanel are you on? It’s supposed to pick up that’s a wildcard (it did on mine). Bleah for cpanel bugs.

    Thread Starter trigger571

    (@trigger571)

    I am on 11.30.2 (build 1). The thing is it did pick up the wirldcard all too well. In fact it automatically created a folder called ‘wildcard’ – Silly server!

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Yeah, that’s the thing ?? When I set it up on my 11.30 build, and put in * it goes “OH! That’s supposed to go to /public_html/ for ya!”

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘500 Error in subdomain admin only’ is closed to new replies.

Tags