dotter Posted July 28, 2015 Share Posted July 28, 2015 I've recently started migrating all internal services my company uses to Docker in order to minimize overhead when dealing with different requirements and maintenance practices. Being a long time subscriber, WHMCS was also on the list of being migrated. Unfortunately the licencing system WHMCS uses makes migrating a WHMCS installation to a container impossible as the internal IP of the container usually changes after a restart. And if the IP changes, the licence has to be reissued. The reissue process is not a problem in itself, but a container can be shutdown and a new one created as part of an automated migration to a healthy host (think AWS). One even better example (not specific to Docker) is upgrading by using a cold-copy where the same licence principle applies. Searching for similar issues resulted in no hits so I assume this will be a new topic on the WHMCS table. I would like to ask the WHMCS team to comment on this as there are ways to maintain the licencing model while at the same time allowing the use of containers and standby deployments. Thanks for reading. 0 Quote Link to comment Share on other sites More sharing options...
sawyerzhang Posted October 7, 2017 Share Posted October 7, 2017 Been trying to to the same thing here, and hope WHMCS can do something about this. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Support Manager WHMCS John Posted October 8, 2017 WHMCS Support Manager Share Posted October 8, 2017 Hi, If you are using WHMCS in a high-availability/cloud hosting environment where the IP address is likely to change frequently, we have a solution for that. Please contact our licensing team who can make the necessary arrangements for you: https://www.whmcs.com/support/ 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.