The MU forums have moved to WordPress.org

DNS issue or otherwise (3 posts)

  1. robbo64
    Member
    Posted 17 years ago #

    Have had MU running in domain xyz.com without issues for some time using wildcard dns and subdomains.

    Due to user login authentication plugin issues I have recently had to set up a number of standalone (ie plain Wordpress not MU) blogs via Fantastico in subdomains eg blog1.xyz.com, blog2.xyz.com.

    This worked fine until a couple of days ago when the client reported the following was happening:

    * trying to access any of the standalone blogs (ie not created through MU but through Fantastico) sends you to

    http://xyz.com.au/wp-signup.php?new=blog1

    and the page gives the following error message:

    Greetings Site Administrator! You are currently allowing 'none' registrations. To change or disable registration go to your Options page.
    Registration has been disabled.

    The Options page link goes to xyz.com/wp-admin/wpmu-options.php

    I can't understand how this is occurring since they are completely separate installs - the main domain is WP-MU, the subdomains in question are installed via CPanel - Fantastico.

    calling blogs1.xyz.com/wp-admin/ sends you to the top level domain and of course the registration currently disabled message. Very frustrating.

    Could this be to do with the wildcard dns settings on the server? No changes have been made in any of the installs with regard to registrations or admin options in either WP-MU or the standalone Wordpress installs.

    I am at a loss as to how to proceed. Hopefully someone has an idea as to how this may have arisen.

    Thanks.

    Needless to say the client wants a fix asap as there are paying customers using these blogs and they can't get in

  2. robbo64
    Member
    Posted 17 years ago #

    If relevant, I should add that trying to go directly to any of the subdomain blogs' admin panel url's eg blog1.xyz.com/wp-admin/ also redirets to the signup url for the top-level domain and the reg disabled message quoted above.

  3. robbo64
    Member
    Posted 17 years ago #

    Resolved: In case others have this happen :-

    As I suspected turns out this was due to the wildcard virtualhost entry in httpd.conf file.

    The wildcard virtualhost entry apparently needed to be moved to the end of httpd.conf file following an update from PHP4 to PHP 5 as default on the Linux/cPanel server.

    Hope this helps.

About this Topic