Master and Slave cPanel Servers
Hello,
Currently i run 5 cPanel servers. They all have diffrent host names e.g. and of course diffrent login URLS, e.g. server1.domain.com:2087 and server2.domain.com:2087 and of course server 1 login will not work for server2.
Control Panels like SolusVM and HyperVM have something called Slave servers (Not to be confused with DNS Clusters.
The Problem
I can honestly say 70% of my tickets are about clients can't log in and 99.9% of the time is because there logining in to server1.domain but should be logging into server2.domain.
The Solution
Like other softwares we can add servers for clients (Apache. MYSQL, everything e.g.) And can just login to one server. E.g. like HyperVM and Solus.
I think this would be great !
Cheers
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
That is a good idea. But cpanel.net proberbly charge another fee.
if it was free to add slaves and only pay for 1 license then i would use it.
That is a good idea. But cpanel.net proberbly charge another fee.
if it was free to add slaves and only pay for 1 license then i would use it.
why aren't the clients just logging in to (theirdomain)/cpanel
- makes support easier and simpler for them to remember !
why aren't the clients just logging in to (theirdomain)/cpanel
- makes support easier and simpler for them to remember !
1: Clients should know which server their site is hosted on. They should receive a mail when they become a customer, with their hostname, so if they're located on server1, server2, server3 etc.
2: If you have 10000 servers, a Wildcard SSL should be good enough to protect all hostnames.
1: Clients should know which server their site is hosted on. They should receive a mail when they become a customer, with their hostname, so if they're located on server1, server2, server3 etc.
2: If you have 10000 servers, a Wildcard SSL should be good enough to protect all hostnames.
SolusVM Has this e.g. It would just generalrly be easier to manage.
SolusVM Has this e.g. It would just generalrly be easier to manage.
A single login location would be a good idea, if you have more than one server.
We all know it from big sites like https://accounts.google.com/ .
But as long as the users have to remember there correct mail server the single login page won't be only one step to customers heaven. To have one mailserver domain name (FQDN) for different server won't be easy/possible without a clustering approach.
A single login location would be a good idea, if you have more than one server.
We all know it from big sites like https://accounts.google.com/ .
But as long as the users have to remember there correct mail server the single login page won't be only one step to customers heaven. To have one mailserver domain name (FQDN) for different server won't be easy/possible without a clustering approach.
This is a really cool idea, but I think cPanel will and *SHOULD* have us pay for licensing fees per SERVER but rather allow us to cluster multiple cPanel installations into one.
This is a really cool idea, but I think cPanel will and *SHOULD* have us pay for licensing fees per SERVER but rather allow us to cluster multiple cPanel installations into one.
Replies have been locked on this page!