Lets get WHMCS to add a feature to allow both IPv6 and IPv4 addresses. Make it an option within the module if you want to allow that or not. When an IPv4 first connects back, it registers it, same thing happens with the v6 address. Depending on my cell phone service, I sometimes connect to WHMCS in ipv6 which says I'm unlicensed. I have to reissue it and then can login. I did find out if you ask, you can get it manually put in, but that could save me a headache and them time!
Thanks!
Merged Ideas
Allow WHMCS license to contain both an IPv4 and an IPv6 address
When our license only had our IPv4 address allocated, admins could only connect to the admin control panel using IPv4. If they tried to connect using IPv6 (which happens automatically if possible by the user on our website) then they would be presented with an invalid license error. We reissued the license and when it had the IPv6 address allocated then the same problem happened but with anybody connecting using IPv4. Now that both the IPv6 and IPv4 addresses are allocated to our license this issue has gone away. To fix this the only way is to contact licensing to manually add both addresses to your license. As IPv6 becomes more widespread this issue will become a major problem down the road so the best thing to do is to add this feature before that happens.
IPv6 For Licensing
Hi!As IPv4's are to be forgotten about, as less and less are available, I find it very important that WHMCS put's IPv6 upfront.As of right now, we have to contact support to add our IPv6 to our licence. If that could be automatic, that would be great.Also, it would be nice if there was an alert in system health if ipv6 is not enabled.The global transition to V6 starts by IT providers, and WHMCS is the platform for a huge amount of IT and Cloud providers.Cheers,
27 Comments
Login to post a comment.
I think Peter Bin's suggestion would be just fine, please implement! :)
My suggestion is to only store the first IPv4 and the first IPv6 addresses which connect. So If the initial connection is IPv4, store the IPv4 address. When a second connection is IPv4, don't store the IPv4. When a second/fourth/fifth/etc... connection is IPv6, store the IPv6 too, but when the next connection is IPv4 or IPv6, don't store that new address.
Only store the first IPv4 and IPv6 addresses.
What we believe is being requested here is to automatically store both the IPv4 and IPv6 address at the time of the initial check-in for a license. The way it works today is the IP the user connects from is stored. How are you proposing that the other IP be automatically detected?