Been running cloudmin/virtualmin Deb12 love it question about liscensing domains liability

Cloudmin
1

I have run into a specific issue where I have a user that wants to do commerce on their website. Now I’ve given it some thought but it has me reeling a bit as I am not really certain how licensing works verbatim.

With virtualmin it states “10 domains” lets just say.

How is that defined does that mean exactly:

10 virtual servers each having their own domain on any number of servers?
10 servers each hosting virtual min with an unlimited amount of virtual websites?
And do subdomains count as another domain if I have a separate virtual server for that.

I have one cloudmin liscense and one virtual min liscense I pay for per year I think that is sufficient for my needs but I need to know how to structure my bill based upon this information.

The problem I am encountering is I can’t see a way to remove myself from liability of customer data if I allow them access to the website thus I would like to have a separate virtual server and make them wholey responsible for everything that were to happen on that subdomain if they wish to use woo commerce.

I am looking for the most bullet proof method to remove myself from potential liabilities if they were to say sell something that wasn’t illegal while I was not watching or the retention of personal data getting leaked in the event of a hack to the woo commerce software or virtual min software bug lets say. I surely don’t want to be the target of a data leak lawsuit. Although it will be a 3rd party payment processor being square there is still a lot of data stored with woo commerce so in the best case I am hoping to setup a virtual server on a subdomain that is specific to that individual so if they mess something up or don’t backup their data or what have you or customer data is leaked it is their responsibility for not keeping their server secure or doing updates etc… I mean there would have to be a contractual agreement of course as well. But that only goes so far so I’d like to insulate myself from potential damages due to their potential ignorance. I’d love to say with certainty it could all be handled contractually but I’m not a legal scholar I don’t know the proper verbiage nor the past cases and litigation on this topic and how it should be handled best. I can only think isolation with a subdomain and a separate server they would pay for with a link from their main site would be the most appropriate then they can be responsible for all of those things as they should I could simply give them wordpress administrative access and they would be 100% responsible for the integrity of that data and server and so forth I would just setup and install woocommerce to that server and word press and they could take the reigns from there.

It would be one thing if there was a way of doing checkout implicitly as a guest where the woo commerce plugin didn’t collect data other than to generate an email with the user and shipment data and order and details in which case no customer data was stored on my server.

Maybe someone who already does this has some info on this from a liability standpoint. Maybe it is best to go with an offsite host all together and just use them and the subdomain for optimal insulation.

But the license info is also important to understand to know what I need in general I may have to upgrade to say 50 domains or I may not it depends.

2

No.

One Virtualmin installation on a system with up to ten domains (Virtual Servers in Virtualmin terminology). Whether that is a virtual system or a physical one is irrelevant to the license. You get one installation of Virtualmin per license.

Cloudmin licenses are wholly unrelated to Virtualmin licenses. Cloudmin manages virtual machines (KVM instances, usually), and is license based on the number of virtual machines you’re managing. If you want Virtualmin Pro on every Cloudmin VM, you’d need a license for each virtual machine, with an appropriate number of domains.

1 Like
3

I presume a subdomain such as Shop.Website.com would count then as a domain even though it is technically a subdomain? If I were to use a separate virtual server for that subdomain?

So technically speaking in which case it would be limited to the number of virtual servers rather than domains so might want to change that if this is the case in the license info.

So it is the number of virtual servers this is most excellent I reread your comment. Oh hell well I guess I might have to up the anti and get another licesnse so I can have virtual servers on separate virtualmin instance to provide isolation where folks can set up their own shopping subdomains at best case I mean I presume I could do just GPL and just backup the server as I think wordpress is available with GPL if I wanted to do it on the cheap. But IDK I’d kinda like to have them on the pro update stream. Just in case after all it is commerce and customer data we are dealing with.

4

A subdomain is just a name. If you create a new virtual server or sub-server for it, then it counts against the domain (virtual server) total. If you create an alias it does not. The name is irrelevant to license consumption.

It used to say “virtual servers (domains)”. I don’t know when that changed. But, everybody else in the industry calls it “domains”, so we’re kind of fighting an uphill battle trying to convince people to call it something else.

But, to be extremely clear/concise: If you create a virtual server or a sub-server it counts against the license limit. If you create an alias it does not.

1 Like
5

Let’s be clear here the “10 domains” limit ONLY applies to the PRO licence. with the GPL version the sky is your limit.

However, your legal concerns apply whatever and wherever.

1 Like
6

Yeah the legal stuff I get it it’s all opinion not advice I have legal console just was curious how others are handling.

7

Uphill or Downhill clarity wins the fight in the long run. But I get it now! No problem. I also understand I could use GPL but I’d prefer to be on the upgrade cycle of pro for the safest possible operation.