Multisites Work actual subdomains being redirected

  • Hi there
    This has had both me and my host going around in circles for the last 3 days
    I have got ( just updated) WordPress .3 RC3 multisites enabled.
    I have added the wildcard *.mysite.com A record.
    My host has added the ServerAlias *mysite.com
    I have the basic htaccess file in place
    I am on a Linux Server using Plesk 9.3
    Ok so here goes. I have a couple of actual subdomains which work just fine until my host adds the ServerAlias to the Apache file and then my WordPress multisite works just fine creating and accessing my multiple blogs but when I try and access an actual suddomain it is redirected to this https://www.mysite.com/wp-signup.php?new=mysubdomain.mysite.com
    Removing the server alias and my WordPress stops working and my subdomains are fine
    Any will help will be greatly appreciated
    Brad

    Copy of my htaccess

    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]

Viewing 3 replies - 16 through 18 (of 18 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    gazouteast, man … You’re misunderstanding what WordPress, or ANY web app, does.

    WPMS 3.0.1 has completely banjaxed the mail-based subdomains (hosts) set in DNS and made them inaccessible.

    WordPress does not have the ability to redirect wildcard subdomains. It has the ability to interpret any wildcards that are set to it.

    Your SERVER setup says ‘Any time *.domain.com comes in, send it to /public_html/’

    WordPress says ‘Hey, I got a request for jimbo.domain.com!’

    Your SERVER is what says to pass the data to WordPress or not. WordPress has ZERO control over that.

    Basic laws of servers.

    What is the BIG change in WPMS compared to WPMU? The one that leaps out at me is that for some reason Automattic deprecated the WPMU VHOSTS function in favour of is_multisite() in the wp-config.php settings – I am certain it is related to that now.

    There is no VHOST funtion. There is a VHOST constant

    VHOST = virtual hosts, aka ServerAlias, aka PARSING Wildcard DNS

    If “no” blog urls look like https://mysite.tld/blog1 aka “sub-directories”. If “yes” blog urls look like https://blog1.mysite.tld aka “sub-domains”

    So … that’s exactly what is_multisite() parses. And by the way, it’s not is_multisite() in the wp-config, it’s a CONSTANT.

    define( 'SUBDOMAIN_INSTALL', true );

    Much easier to understand for most of us, I think ??

    Look, I’m not saying you’re wrong, but you’re running down a path that is premature at best, and certainly a fair game at over-reacting.

    The number of people having this problem are VERY few. A handful on the forums (out of the probably 100k people using MultiSite). Occam’s Razor being what it is, the problem is most likely in how you configured your server to parse wildcard domains.

    This works for a LOT of people. Windows and *nix, cPanel and Plesk, etc etc.

    If you REALLY think this is a BUG in WordPress, don’t be a dink and threaten with a Press Release. Man up and do the right thing by the open community. Open a Bug report. List the details of your server info, provide your http.conf (or whatever you have) so people can see what it’s set up as. If you’re using brad1004’s fix (renaming the vhost files so they are called before each other), list what yours are, complete with each file’s content.

    But a theeat, man? That doesn’t help anyone, least of all you.

    I am also now getting it on cPanel installs that were working under WPMU and under 3.0, but since 3.0.1 are now exhibiting the same behaviour re: fixed subdomains being redirected to WPMS login or blog creation –

    you need some old threads where the same thing was happening to a few people under mu?

    WordPress cannot manipulate the server for you. end of story.

    If it could do what you’re claiming, then it could add the wildcard itself.

    Why did Automattic “fix” something that was not broken?

    Less than half of the core developers who worked on 3.0 work for Automattic. The rest are *volunteers*.

    those constants were renamed, but again, they do not mess with your server. they can’t. If you tried it on cpanel and it did the same thing, again, we go back to your host.

    I have a few of my own installs on cpanel and they do not do this. Nobody but you is reporting this issue.

    Ipstenu is correct in everything she said.

    And if you cannot control your temper, I’ll remind you of the forum rules posted here.

    I’m uncertain as to why this thread has been hijacked into a discussion about wildcard hosting for email. If your email collection is being in any way affected by WordPress then you have a seriously messed up set of DNS entries. You don’t need wildcard MX entries for WordPress, WordPress has nothing to do with MX entries. Your MX entry handler system would probably even be a completely different set of servers.

Viewing 3 replies - 16 through 18 (of 18 total)
  • The topic ‘Multisites Work actual subdomains being redirected’ is closed to new replies.

Tags