Support » Networking WordPress » Newly converted multisite subdomains can't connect to database

  • Resolved newmediaavenues

    (@newmediaavenues)


    Godaddy virtual dedicated server.
    Plesk

    Newly created blogs are showing up in the database in phpadmin but I’m getting “Error establishing a database connection” when I attempt to view them. The main blog works fine.

    I have DNS configured with wildcard subdomains but with Plesk, this isn’t all that clear. Also, Godaddy will not allow an * in their Cname configuration of their own name servers.

    Currently, if I type anything at all such as fakeword.domain.com, it comes back with “Error establishing a database connection” so I’m thinking maybe it’s a vhosts.conf issue or some other wildcard problem.

Viewing 15 replies - 1 through 15 (of 26 total)
  • Yes, I referred to that page as my resource for installation.

    I’m willing to pay someone with WP multisite experience to dig around at this point. Any resources where I might find this individual?

    Another detail to the clues, when creating a new blog, while the entries are showing up in the database, nothing is showing up in blogs.dir. Should there be something in there for each entry?

    No, blogs.dir fills in when you upload images.

    Currently, if I type anything at all such as fakeword.domain.com, it comes back with “Error establishing a database connection” so I’m thinking maybe it’s a vhosts.conf issue or some other wildcard problem.

    Oddly no. That means that WP is ‘catching’ all the subdomains (that is you’re correctly sending anything.domain.com to domain.com’s WP install) so that’s okay.

    Did you by chance move your install from a subfolder AFTER making it multisite?

    Nope, it’s in the top level and always has been. It is, however, under a “webspace” of another domain. This is something I’ve never dealt with since I’ve never dealt with Plesk before.

    There is a little complicated background. The site was first on a shared hosting at Godaddy. I set up multisite assuming I could employ the wildcard dns and found out I couldn’t so I got a virtual dedicated so I could control that. So I downgraded the WP installation back to regular WP and moved it, importing the old database into the new one. Got it up and running and then upgraded back to multisite.

    I also had an issue with the version of mysql not being sufficient for the latest WP so I upgraded that. Now I get the “Your PHP MySQL library version 5.0.90 differs from your MySQL server version 5.1.58. This may cause unpredictable behavior.”

    I’ve read that this shouldn’t be an issue, but I’m willing to entertain any and all potential causes up to and including gremlins and angry unicorns.

    Additional info:

    I created the blogs test1, test2, test3 with same results. The were put in the database but when going to subdomain I get the can’t connect error. Then deleted them from the WP Network Admin and they were removed from the database. So WP can connect and modify the database.

    It is, however, under a “webspace” of another domain.

    I don’t think that’s a problem, but my plesk experience is minimal :/

    The can;t connect error means the db tables were not created.

    I created the blogs test1, test2, test3 with same results. The were put in the database but when going to subdomain I get the can’t connect error.

    How many wp_posts tables are there? DO you get wp_3_posts, wp_4_posts etc…?

    This may be an issue:

    * You can have multiple installations in one database if you give each a unique
    * prefix. Only numbers, letters, and underscores please!
    */
    $table_prefix = ‘wp_1’;

    I set up the database as wp_1 at first because I wasn’t clear on this.

    So now with all the adding and removing test blogs, I currently have wp_19, wp_110, wp_111, wp_112 and wp_113.

    When I look at wp_113_posts there are 2 entries, the welcome and the sample post for those blogs.

    $table_prefix = ‘wp_1’;

    I set up the database as wp_1 at first because I wasn’t clear on this.

    and that particular extension will screw up multisite, because that’s one way it checks for “is this an upgraded wordpress mu site?”

    can you have a do-over? or change the prefix?

    Um, good question. I’d rather not do a total do-over. Can I just duplicate the database, alter it or?

    How might you go about it if it was your problem? 🙂

    I’d do a dump of the db, change the table names, change it prefix in the confgi file, then plop my altered sql back in a new empty db, adjust the config file to point to the new one and there ya go.

    FYI that table prefix comment was not relating to multisite at all. (Hmm, maybe I should file a ticket on that…)

    Okay, I did all that now and all and I created a new blog called newdb.mysite.com and it wrote to the new DB where everything else is. The new table is wp_13.

    Still getting the same “Error establishing a database connection”

    If it is creating the new tables with no problem, that means wp can connect to the db, correct?
    So it has something to do with the subdomain not being able to call up the table that was created. Is this also correct?

    If I type sub.domain.com/wp-admin/ I get the WP dished error page.
    If I type subANYTHING.domain.com/wp-admin/ I still get the WP dished error page.
    If I type sub.domain.com or ANYYTHING.domain.com I get the regular server error in bold black that must be dished from the database server.

    or ANYYTHING.domain.com I get the regular server error in bold black that must be dished from the database server.

    Okay THIS is helpful. If you type anything.domain.com and the install is working correctly, you should just be redirected to the signup page.

Viewing 15 replies - 1 through 15 (of 26 total)
  • The topic ‘Newly converted multisite subdomains can't connect to database’ is closed to new replies.