Solution to X10's growth problem

[Smith6612]

thanks for explanation,
that means more than160 users concurrently, commanding in cPanel..or they are engaged(just connected).
Can't we timeout the next logins when more than 160 users are already loged-in in cPanel for free hosting..?

I have been through WHM and cPanel itself (obviously not on x10's servers), but I am not aware of any option to really adjust the timeout on these connections for cPanel. Good chance that is in one of those encrypted files that Corey mentioned that contains the connection limit value. But basically, if cPanel's web server works the same way as Apache does, when you are able to get a hold of an Apache worker thread, it's pretty much your own worker for however long the time out is or for however long you are visiting the website if you do not let the worker time out. No one else will be able to be served by that worker thread, a new one would have to be created. It's why in some cases, people can still browse a website but others cannot connect on and off, yet everything comes from one server. If Keep-Alive is turned off, sure you can basically alleviate this, but it adds additional load to the server.

[jputter17]

Guys I know you add cPanel for the users, and it is great to use, however myself I am not particularly bothered about cPanel as I upload stuff via ftp and then on top of that I install my own php versions of stuff like joomla etc without using cpanel.

What about actually having an option for those that wish not to use cpanel to be able to remove it after an account has been created, surely quite a few people will remove it and thus free up some of your users, that way no one can complain because you are still offering what others don't and they have the option to not use it.

[magnetix.gaming39]

Guys I know you add cPanel for the users, and it is great to use, however myself I am not particularly bothered about cPanel as I upload stuff via ftp and then on top of that I install my own php versions of stuff like joomla etc without using cpanel.

What about actually having an option for those that wish not to use cpanel to be able to remove it after an account has been created, surely quite a few people will remove it and thus free up some of your users, that way no one can complain because you are still offering what others don't and they have the option to not use it.

I'll agree with with the option of using cpanel or not. But cpanel is not just for uploading your files. It includes the necessary tools to maintain your web server. Specially it will be useful for first time users as myself.

[lynnwood]

I agree that we there should be an option for whether or not I would like to have cPanel as part of my account properties. I actually have zero need for it and would much prefer some actual uptime.

[Corey]

Having an option to not have cPanel would not work as it would require a completely different system to manage those accounts and a long time to develop a system to manage them. We already have a new solution that we're in the process of implementing, the results so far are very promising.

I'm going to go ahead and close this thread as I believe it has run its course.