Home › Forums › WordPress Plugins › Hide My WP › 500 internal error because of two lines in the htaccess

This topic is: not resolved
Viewing 15 posts - 1 through 15 (of 16 total)
1 2
  • Author
    Posts
  • February 11, 2016 at 4:55 pm #7905
    aqt
    Pro
    Post count: 41

    Hi I ‘ve just upgraded to latest PHP 5.6 from latest PHP 5.5. After the upgrade I realized that the I get an error 500 on the w-admin pages. I checked the Apache error log and noticed this ….. AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace….

    I will write down the htaccess lines on the next post

    I have the same HMWP configuration n two websites the other works fine after the upgrade.

    February 11, 2016 at 5:29 pm #7906
    aqt
    Pro
    Post count: 41
    This reply has been marked as private.
    February 12, 2016 at 2:19 am #7913
    Suman M.
    Post count: 12478

    Hi, please let us know your website’s wp-admin login details (as private reply), so that we can have a look at the issue.

    February 25, 2016 at 11:25 am #8141
    aqt
    Pro
    Post count: 41
    This reply has been marked as private.
    February 25, 2016 at 1:45 pm #8154
    Suman M.
    Post count: 12478

    As of now do not set new name for wp-admin path. It will only complicate the issue. Please try this:

    – in HMWP start tab click on “reset settings to wp”
    – in HMWP Start Tab, select “Medium Privacy – More Compatibility” scheme and save the settings
    – goto Permalink & URLs tab and set “rename plugins” option to “all plugins”

    Note: Your new login URL will be http://www.yourdomain.com/wp-login.php?hide_my_wp=1234

    Let us know the result.

    February 25, 2016 at 1:52 pm #8155
    aqt
    Pro
    Post count: 41

    What you said works fine, I have already tested several configurations. The only 1 thing that breaks the wp backend is the PHP restriction which when ticked adds the 2 lines above in the htaccess and breaks only the backend. Either in that case the frontend works fine.

    Doesn’t the fact that I use nginx as a revesre proxy mean that I should use an alternative configuration and not the htaccess rules?

    February 25, 2016 at 2:08 pm #8160
    Suman M.
    Post count: 12478

    The htaccess rules are working fine for you, except those 2 rules, so you need not use an alternative configuration. We recommend you to not use “avoid direct access to php files” option as it’s creating conflict in your case.

    February 25, 2016 at 9:18 pm #8180
    aqt
    Pro
    Post count: 41

    Hi Suman,

    unfortunately that’s not a solution and we must find a fix for this, We have already bought two licenses and I’m thinking about buying for all our wordpress sites. Is there anybody else who can help us with this? or do you need any more information from me? What’s the correct way to debug this?

    I appreciate your time
    thank you

    February 26, 2016 at 5:33 am #8187
    Suman M.
    Post count: 12478

    Can you please let us know your website’s wp-admin login details (as private reply), so that we can have a look at the issue.

    February 26, 2016 at 6:19 am #8189
    aqt
    Pro
    Post count: 41

    As already said in my second post I’m not allowed to give admin access to anybody but I can provide information logs screenshots files and whatever details you may need, just tell me what do you need to debug this

    February 27, 2016 at 8:07 am #8200
    Suman M.
    Post count: 12478
    This reply has been marked as private.
    February 27, 2016 at 10:13 am #8210
    aqt
    Pro
    Post count: 41
    This reply has been marked as private.
    February 28, 2016 at 7:10 am #8219
    Suman M.
    Post count: 12478

    Hi, I’ve assigned this ticket to Sr. support so that he can look further into it.

    February 28, 2016 at 8:43 am #8223
    aqt
    Pro
    Post count: 41

    Hi
    Thank you
    I think what’s left is the nginx configuration as a reverse proxy, the problem has to be somewhere there. Let me know if you need to have a look to any configuration files of nginx

    March 22, 2016 at 3:37 pm #8565
    aqt
    Pro
    Post count: 41

    Hi there has been nearly a month I still haven’t got any answer from Sr. support. So when somebody can can look into this?

    Thank you

  • Author
    Posts
Viewing 15 posts - 1 through 15 (of 16 total)
1 2

You must be logged in to reply to this topic.