• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Issue WHMCS Plesk Plugin

TobiasP

Regular Pleskian
Hi,

I found a problem in the WHMCS Plesk Plugin on github.

I noticed that even though I had set "shared ipv4, shared ipv6" the hosting never got assigned an ipv6 address.
after looking through the code I noticed that before the "IP Mode" setting is honoured, the username that is used to connect to the plesk panel is compared to "admin".

And of course I had not entered my regular admin credentials into WHMCS but created an additional admin user for WHMCS. So there was the problem. Why the check for the username admin is important is beyond me because any additional admin user has the same priviliges as the original "admin".

So please remove this check and tell the whmcs guys to pull the updated plugin.

Here is the piece of code I mean:
whmcs-plugin/V1000.php at master · plesk/whmcs-plugin · GitHub

isAdmin() function
whmcs-plugin/Api.php at master · plesk/whmcs-plugin · GitHub

I already created a pull request:
Fixed: IP-Assigning when user is not "admin" by tofuSCHNITZEL · Pull Request #28 · plesk/whmcs-plugin · GitHub

Cheers,
Tobias
 
unfortunately with these changes following error is produced when terminating a hosting:
Error code: 1017. Error message: IPv6 addresses are not support in protocols below 1.6.3.2
in particular it comes from the "webspaces_get_by_owner_id" api call
it only happens when the customer has another subscription.

I don't know how to fix that.
 
Back
Top