• Resolved David LeBlanc

    (@davidtleblanc)


    I installed a new site and got a message when I tried to log in for the first time “This website has a redirect loop,” which as I understand it is something in the .htaccess file pointing back at itself.

    This was the third site on this domain at GoDaddy, using it’s app system. I fixed it by slightly changing the name on the .htaccess file in the root directory and WordPress installed a fresh one, I guess.

    What in the old .htaccess was pointing back at itself? How will I avoid this in the future? What bit of code will fix that?

    The slightly changed .htaccess file had all of the security plugin’s info on it and I want to make sure the new one gets that info back.

    The second site installed without a problem and I did it kind of the old fashioned way, I did not use GoDaddy’s app system to install it. Just set up a database, FTP’d a copy of WordPress to the folder, went through the famous five minute install bit and had a second site. It seems to have it’s own .htaccess file.

    The third install did not and adding one did not fix the problem.

    Any information anyone can offer will be greatly appreciated.

Viewing 7 replies - 1 through 7 (of 7 total)
  • My two cents, you should copy-pasted here the contents of each htaccess file, or share a pastebin link in case the files are very long.

    Also, I may be mistaken, but the DEFAULT content of an htaccess shouldn’t, I think, mention the domain name, so you could safely copy one default htaccess file from one site to another (better download it to your disk and reupload it, in case there is a change of ownership – no idea with godaddy and your hosting account.)

    Thread Starter David LeBlanc

    (@davidtleblanc)

    Sabinooo,

    That’s kind of what I thought. I mention GoDaddy because all of the weird stuff seems to happen on accounts they host. It probably is all coincidence, but…

    I suspect a sensible part of Godaddy’s bad reputation with wordpress comes from the fact they’re one of the hosts chosen by the most inexperienced users, so they’re going to be one of the hosts the most associated with reports of website going real bad.
    I’m not sure, GoDaddy uses cpanel for its members, right ? Offering an inexperienced webmaster access to cpanel is as safe as letting a kid play with hand grenades : it’s only a matter of time before it blows up in the face of the unwary victim.

    As for your situation, David, did you try the htaccess files thingy ?
    The default wordpress htaccess file wouldn’t care less about mentioning the domain name, maybe you could try with this, to see if it fixes your situation ?

    # BEGIN WordPress
    
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    
    # END WordPress

    Thread Starter David LeBlanc

    (@davidtleblanc)

    Sabinooo,

    Thanks. Yes, I added back the old data to the new .htaccess file and all is working correctly. Not sure why I had the issue, perhaps a corrupted file.

    When you have no other explanations, corrupted file becomes the go to excuse.

    This website is on GoDaddy’s own proprietary admin. system, not cPanel, but GoDaddy has added cPanel and is urging customers to migrate to it. I think I read that new customers are not given a choice anymore and they have to use cPanel.

    I always found cPanel easy to work. I prefer cPanel myself and don’t seem to have the issues I have had on GoDaddy. I don’t know if it’s the admin system or just series of coincidences or me causing the problems.

    Happily, they all do get resolved.

    I will say GoDaddy’s support has always been helpful and friendly and patient, if occasionally clueless.

    Hi everyone. I am also having this issue and I’ve tried the following

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]  <-- I inserted this line
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    
    # END WordPress

    But it isn’t working. Also, I tried to put the plugins on hold to see if it is one of the plugins that caused the problem… Even though I didn’t install any new plugin as at the last time I logged in.

    Thread Starter David LeBlanc

    (@davidtleblanc)

    It’s possible it’s a cookie issue.

    One way to find out is to either delete all of your cookies or try to access the site from another computer. If it is a cookie issue I think it will clear itself in a day or so. I think that is what it was in my case.

    Whatever the cause and fix, it’s all fine now for. I should also note I did clear the cookies on three different browsers and reported the same problem. Maybe erasing a week’s worth of cookies was not enough.

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

The topic ‘redirect loop’ is closed to new replies.