Why is our Multiple Network install not accesible via its IP address?

  • Hey there,
    after several days of trying and searching around let me see if someone here can help. The problem is:

    We have a WordPress Network with the plugins WP-Multiple-Network and WP-Domain-Mapping installed. It is working nearly as expected.
    We can access all sites via it’s domains and all the admin and mapping works fine. Also the different networks are working correctly.

    The issue is:
    If we enter the IP address of the server then it directs to the error:

    No site defined on this host. If you are the owner of this site, please check Debugging a WordPress Network for help.

    .

    The database tables seem to be correct and include all the domains for sites and also the domains for the different networks.

    We think that the server is working ok and also correctly redirecting the IP address to the WordPress install, but there is some last step missing somewhere inside WordPress to point the ip to the right site.

    Usually we would not really care much about that, but it creates the following issue. Our Plesk installation has the watchdog module running to check all services on the server and restart them if needed. While checking the apache server it tries to reach the server-ip-address. The error message somehow makes it believe that apache is down and has it restarted. This happens (depending on the interval we set) every 5 minutes.

    We are probably just looking too deep into it to find the proper way of fixing that, this is why we hope for your help ??

    Thanks so much…

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

  • no, this works as expected.

    there *is no* record of the IP address in the database. that’s how it should be. Because you have no blogs with that web address.

    If the server is set up properly to redirect requests for that IP to the domain name, what *should* happen is you’ll see your multisite new blog signup page. THAT woudl be correct behavior.

    Thread Starter bigcityinformer

    (@bigcityinformer)

    Hmmm, that’s a good news then I guess – as expected ??

    Will have to check why the error comes up then. Sign-ups are disabled for all the blogs, it’s all manual only. Will check this out tomorrow, thanks for the hint Andrea_r, really appreciated ??

    Strangely the *.domainname.com is working as it should, also all the other redirects and domainmappings. So not really sure why it is directing to that error-page. Server setup seems all right.
    Hay, those pesky little server-setup issues ??

    Thread Starter bigcityinformer

    (@bigcityinformer)

    Just realized, the IP address somehow does link properly to the WordPress install, it’s a WordPress error message after all. And debugging shows that some parts of WordPress are loaded already. So it is going well all the way until it reaches the point that sign-ups are disabled probably, and then it spits out the error.
    Unfortunately the error-site also gives a 500 Error in the page-header so the server thinks something is wrong…

    So it has the IP somewhere in the db enough for WP to think there’s a blog at that address.

    And unless you had installed it on the IP address first, then switched it over to a full domain name, the IP address is never stored.

    Thread Starter bigcityinformer

    (@bigcityinformer)

    Hmm, figured something out ??

    We had some directives in the wp-config disabled, and that caused the problem. It was recommended in the setup for the plugin (have to correct the plugin name, it is networks-for-wordpress, not wp-multiple-network – but these are apparently based on the same code).

    So after enabling those again the problem seems fixed.

    Now we are of course wondering if this will cause some new issues or has side-effects on the multi-network functionality of our install???

    There is another thread with the same issue, the author of the plugin can’t really tell if the directives should stay or not ??

    Ron and I also have amulti network plugin called Networks+ (it;s paid).

    and yes, you have to take those out. No, it won;t be a problem.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Why is our Multiple Network install not accesible via its IP address?’ is closed to new replies.