WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Getting redirect loop error for new domain (4 posts)

  1. zzzmuzz
    Member
    Posted 2 years ago #

    I added a new site to my multisite (which has 6 subsites all working well).

    When I set up the new site I had something of a problem when I went to put in the "Domain" under edit site, as the new site was a .org of a domain name I already have on the multisite.
    ie I have a domain on the multisite: extendincome.com which is on the multisite as extendincome.entereos.com and extendincome.com redirects to it.

    But now, with extendincome.org what should the domain be called in WP? I set it up as extendincomeorg.entereos.com and after the host did the DNS changes, extendincome.org redirected to extendincomeorg.entereos.com. But not now. I then thought perhaps it should be in WP as extendincome.org.entereos.com but that doesn't work.

    The error I have ended up with is below. I have also contacted the host for comment.

    This web page has a redirect loop
    The web page at http://extendincomeorg.entereos.com/ has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
    Here are some suggestions:
    • Reload this web page later.
    • Learn more about this problem.
    Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.

    I have cleared cached and cookies etc.

  2. Did you install a domain mapping plugin and activate it yet? That's what you need to do this.

  3. zzzmuzz
    Member
    Posted 2 years ago #

    Yes, have done this, as I have also done it with the other sites on the network.

    Hmmm, I can't get into the Dashboard for this site. Trying to access it from the superadmin sites list. A user is set up. I can use Edit but when I click on Dashboard I get:

    404 Not Found
    The resource requested could not be found on this server!

  4. zzzmuzz
    Member
    Posted 2 years ago #

    I seem to have this sorted now thanks. It was to do with an incorrect document root.

Topic Closed

This topic has been closed to new replies.

About this Topic