Let's assume a single ISPConfig installation. Can we use this single installation to manage multiple VPS/Dedicated Servers of different customers without installing one ISPConfig on each? For example: vps1 with mail+db+web => customer1 vps2 with mail+db+web => customer2 customer1 and customer2 access to our domain: cp.mydomain.com to manage their own server without affecting each other. Is this possible?
Yes, thats possible. Just create your customers as usual (client or reseller) and set the default server for web, db and mail on the limizts tab to the server or vps that they shall use.
Cool. I'll try immediatly. In this way, we can use a single panel install with multiple and totally different customers.
As wrote on another post, i'm having trouble using ISPConfig. I've tried with many machines (2GB RAM, QuadCore) and every now and then ISPConfig starts to slow down until it crashes. I have to reload the whole apache. It's pretty unusable right now.
I run several VMs with about 2 GB and current ispconfig version on debian 6 without a problem here, so your problem is not ispconfig. ISPconfig is not even a service or long running process, so it can not slow down. I guess you mix up ispconfig with one of the services that are configured by ispconfig here like apache. But as long as you dont specify any problem or post a lonk to which thread you refer, nobody can help you to fix your setup.
I've changed apache with nginx and now I don't see any issue. Just a question: is possibile to hide some section to a single users? For example, we would like a mail-only customers, actually I have to set "0" to any service, but we would like to hide the menu.
Ok. I use apache on all of my ispconfig production servers and dont had any issues with it in the past few years. Yes: See System > CP Users, there you can set the modules for each login individually and in the confih.inc.php file you can set the default modules for new users.
Perfect. Exactly what i was looking for. This doesn't prevent me to configure a website, right? Only that user will not be able to access site module.....
