I have edited my htdocs htaccess file to remove the ?i=1 redirect and now after reading the importance of that redirect I really wish I can undo what I have edited. Is there a way to restore my original htaccess?
Then is it ok to leave it as it is?
I mean with the code that removes ?i=1 redirect, I read that it protects from malicious bots but I already have a security plugin installed that changes the wp-admin in WordPress and 2fa and much more. And added a strong infinityfree password and added 2fa too (two factor authentication)
Should that be enough security for my website and domain from bots?
No, I would remove it or you run the risk of endless redirects occurring if the security system is triggered.
That’s only one part of what the system protects against. It’s also there to help protect the server, which is something no WordPress plugin can do.
You also can’t remove the security system. Your htaccess program is not a solution, all it will do is break your entire website if the system is triggered.
Delete the htaccess code you added. I already told you that.
It’s still triggered, but there’s a period for every successful challenge that the challenge doesn’t perform at all for you, and you don’t see the ?i=1.
After seeing ?i=1 you can actually remove that part from the url and visit the site again, and it won’t show up.
The problem that I can’t remove the code is because I can’t find the same exact code I added so I’m just scared to remove a code that looks like it and corrupt something else.
If there is way to add someone more experienced than me to do that for me, I would be so glad.
The ?i=1 redirect cannot be removed with .htaccess rules. The security challenge is run by our servers before ever reaching your website.
The only thing you can do is do another redirect to remove the ?i=1 fragment from the URL. But that’s just a cosmetic change, it doesn’t affect the security of your site.
All the other measures you’ve taken, like hardening the WordPress login and setting up two factor authentication, are useful regardless of the browser validation though. The browser validation system is helpful but it’s no silver bullet.
Sure, we can help you troubleshoot your .htaccess code. Can you please share the code you have now? Then we can tell you which changes to make.
It’s your call. I don’t see any inherent issues with it, but .htaccess code (especially rewrite rules) tends to be quire cryptic.
If it does what you need it to do, then keep it. If it’s causing problems, remove it.
To remove this code from your .htaccess file, just remove this code from your .htaccess file. Open the file in your file manager and remove the lines. If you can add the code, you can just as easily remove it.