Support » Plugin: Solid Security – Password, Two Factor Authentication, and Brute Force Protection » IPv6 support follow up
IPv6 support follow up
-
Hello,
Its been a year since my original inquiry here.I wanted to follow up and see if there is a time table yet for when IPv6 support will be added.
-
Done. This functionality really needs to happen and sooner than later.
On Feb 11th 2016 (last thursday) iThemes released iTSec Pro 2.2.2 which includes IPv6 support.
New Feature: Added support for IPv6 addresses. This includes support for IPv6 in lockouts, ban hosts, and white lists.
So I guess an iTSec plugin release will follow shortly here on WordPress.org …
dwinden
Hey All,
This has just been released in 5.3.0!
Thanks,
Gerroald
Just a heads-up… the update killed one of my sites on Hostgator as they don’t yet support IPv6. Would’ve been nice to have this as an option, and not automatically switched on in a Sync update.
Hey ViscoDesign,
Can you please elaborate as to how it killed your site? Are there any specific errors?
Even if a site doesn’t support IPv6 it shouldn’t cause any issues.
Thanks,
Gerroald
Hi Gerroald.
After the upgrade, iTSec started writing its ‘Quick ban’ IP addresses to the .htaccess file in IPv6 format, and because the server didn’t support IPv6, it threw a 500 internal server error. The site just wouldn’t load. I had to remove the plugin and at the moment it is still deactivated as I’m not sure if I want to switch it back on – because I can’t even get to the Admin area once it’s activated.
That’s the message I got from Hostgator support anyway. Perhaps it’s unique to them? Sorry I can’t elaborate any more, servers aren’t my thing. I just code 🙂
Hope that helps!
JohnHey John,
Just to try to clarify things, IPv4 and IPv6 IPs are treated separately by the plugin. The plugin will only write an IPv6 IP to the .htaccess if it is given an IPv6 IP (which it shouldn’t get if your server doesn’t support IPv6).
The only other reason it would attempt to write an IPv6 address to the htaccess would be if you manually banned an IPv6 address on the settings page.
Would you be able to get us a copy of the htaccess that caused the problem (maybe hostgator would be able to get it for you) as well as what version of Apache you are running?
Thanks for the explanation Aaron. I’m not sure how it all works, but this is the code I had to remove from the top of the htaccess…
# BEGIN iThemes Security - Do not modify or remove this line # iThemes Security Config Details: 2 # Quick ban IP. Will be updated on next formal rules save. SetEnvIF REMOTE_ADDR "^2001:41d0:2:b960:0:0:0:0$" DenyAccess SetEnvIF X-FORWARDED-FOR "^2001:41d0:2:b960:0:0:0:0$" DenyAccess SetEnvIF X-CLUSTER-CLIENT-IP "^2001:41d0:2:b960:0:0:0:0$" DenyAccess <IfModule mod_authz_core.c> <RequireAll> Require all granted Require not env DenyAccess Require not ip 2001:41d0:2:b960:0:0:0:0 </RequireAll> </IfModule> <IfModule !mod_authz_core.c> Order allow,deny Deny from env=DenyAccess Deny from 2001:41d0:2:b960:0:0:0:0 Allow from all </IfModule> # END iThemes Security - Do not modify or remove this line
Once I removed those lines the site popped up again.
Server is running Apache 2.2.31
Hey ViscoDesign,
We’re taking a closer look into this. Would it be possible for you to email me at gerroald @ ithemes . com?
Thanks,
Gerroald
For sure, I’ll send you an email now…
Hey ViscoDesign,
We’ve been working on this. I just wanted to let you know I’ve emailed you back just in case you’ve missed.
Thanks,
Gerroald
Sorry Gerroald, my bad. Will respond to that email now…
- The topic ‘IPv6 support follow up’ is closed to new replies.