Certificate configuration fails over IPv6

[orudge]

Hello,

If running WHMCS on an IPv6-capable server, and attempting to configure a certificate from an IPV6-capable client, an error is received along the lines of "ClientIP is invalid" (unfortunately I didn't note the exact warning). Disabling IPv6 in Firefox "fixes" this, but as IPv6 is becoming more common, NameCheap should really support IPv6 addresses in the client IP field, even if they don't offer IPv6 access themselves.

[fuzzbawl]

We've experienced the exact same problem. The full error is: string(39) "[1011105] Parameter ClientIP is invalid"

If you look at the Namecheap API error code list, 1011105 is in there indicating that the ClientIP is indeed the issue but it appears to be a problem on Namecheap's side of this. There's nothing we can do to fix it from a settings perspective outside of disabling IPv6 on the client, but that's just not possible. Looks like we'll have to move SSL to another registrar.

[orudge]

I guess as a workaround we could alter the _getClientIp function to detect an IPv6 address and, if found, return the server's own IPv4 address. Not ideal but should allow the order to proceed until NameCheap can fix their systems...

[ggrigon]

2020 and namecheap still without support for ipv6 on the API :(