Is vesta suitable to web hosting?

[chirag]

Is ist suitable for web hosting business?
Alternative to CPanel?

[skurudo]

Cpanel is older and more mature, community and bisuness bigger.
But, yes and yes. More and more hosting providers and frelancers use Vesta as server CP.

[Clouseau]

With all do respect for effort, I beg to deffer, Vesta is nice panel but is buggy and is not production ready, especially if you are not a sysadmin. I have wrote few bugs here and I have zero reponse for it. Clamav after installation is using 100% of cpu unless you mkdir /var/run/clamav dir and chown it properly, it is killing perfomance - that has been reported over a year and still not fixed (three lines of code, the fix is allready in pull requests in git). If you pick different template for website it breaks nginx and php-fpm configuration, nginx wont start - %backend% variable is probably the problem because GUI want use it. In production this is a fail, nginx stops and you need to fix the stuff manually. Statistics do not work anymore because "stats.inc" in /etc/nginx/conf.d is no longer exists or is generated after installation or adding the webiste - I had to add vstats alias in hosting templates... The changes in gui do not propagate, you need to run v-rebuild-user every time (ie. you change shell of a user, switch to another template in website etc...) And there was a hack in recent version allowing admin access...

This is a nice panel with lot of potential but I think the dev team is to small to follow the large code. If I where you, I would pick one distro and use it a base - there is really no need, a linux sysadmin can make his way on any distro but if you ask me I would choose CentOS or Debian - but CentOS would give a more professional and acustomed look :)

[mehargags]

CentOS is for the masses who need support and Tutorials aplenty...
Debian is for the more refined sysadmins who want a more granular control of their systems...with lesser resource load and higher performance.

Both OSes have their own place and liking and DO NOT INTERSECT each other anywhere.

Secondly,
we have had atleast a 100 discussion already on this:
VestaCP is abolutely production ready... depends if you want to use it for 1) yourself or to 2) resell hosting services to other customers.

For yourself, if you manage all your sites single handedly, its absolutely fine to use it! I use it for more than 30 Servers.
However if you are resell to other customers and you don't have tight control on what they run and host, better get cPanel or DirectAdmin or else you may have hard time tracking problems if you don't know Linux management

[Clouseau]

CentOS, Debian whatever... Been using both for over 10 years and after all that time CentOS rules :) Debian has apt with space powers but most of the time don't need them. Only benefit of debian are upgrades between releases which go seamessly most of the time... Ubuntu on the other hand was crap at the time I used it and never went back to try it... Ok, enough of this, choose Debian :) But would be better to choose one distro and support it so the bugs can be lower :)

Regarding Vesta - it really is not production ready ie. I have on one server news portal with high traffic, I upgraded to latest version, changed the template in gui for that web when I changed something and the nginx wont run afterwards. Good I noticed promptly because I could just change the template and logout... The problem is that %backend% does not get written and the parts are missing in conf. Rebuilding of user fixed the problems. The same is with php-fpm pool, you switch from socket to default and the domain.conf does not update, the file .conf is generated in /etc/php-fpm.d/ which brakes php-fpm. Really, I do not know how noone notices this, it is present on latest version and freshly installed panel on CentOS 7 :)

Vesta is cool, it is very light and smart, it is not powerfull like ispconfig but the vesta installs under 15min :) And for most of the users the options in Vesta are enough :) I am not a developer so I cannot help with the code, I could fill the bugs in, but I cannot fix them...

EDIT: I USE Vesta on few production servers with few websites but I need to do manuall work in cli regarding Vesta actions which are available in GUI. I would not recommend the panel for a newbie, you need some knowledge of linux administration...

[durjoy]

Kudos to VestaCP developers for amazing work. certainly, this control panel has bright future ahead.
IMHO right now developers need to focus on weeding out all the major bugs, instead of adding more new features.
Vesta has all the essential features to manage hosting services. I don't think it needed any more features

As a frequent user of VestaCP, I would love to see "hosting template changing" bug go away. (whenever users change hosting templates, it breaks the system, NGINX stops working).

[mehargags]

Yes absolutely...
VestaCP is full of features for an Average "self hosting" control panel. I think the devs really should focus on cleaning UI bugs and other bugs after the code refactoring in 9.8.16 and iron out the problems. Stability is way more important than feature set!

[deanhills]

VestaCP is VERY fast, particularly if one uses the apache/nginx combo from the bash commands that VestaCP offers.

There are now hosts who offer VestaCP shared hosting because of how light and fast the panel is.

Here is an example of a Webhost who is offering free hosting on a Vesta Control Panel:
https://afreecloud.com/

The hosting is provided by Joe Dougherty, co-founder of Secure Dragon and also a previous administrator of FreeWebHostingTalk.com.

It's the fastest hosting I've had so far in my shared hosting history. If you like you can sign up there to get a feeling of what VestaCP is like as a Website.

[dpeca]

For now, Vesta is production ready only if you are sysadmin that reads /var/log logs and know how to fix problems or Vesta bugs that comes when you install Vesta.

I believe that v17 will fix all that big bugs, many people (including me) are made a pull requests on github in order to fix main bugs (I made a 6 pull requests, mostly for Debian, and reported 2-3 more bugs on bug-tracker).
I love VestaCP, and I believe in her future, so I do efforts to help Vesta developers to fix all known bugs. I know that everyone will do that if his programming skills are enough to fix a bugs.

When I install VestaCP, firstly I fix all bugs that I found (6-7 bugs, all bugs I reported, and made a fix for them in github pull-requests).
So, I can use VestaCP on production machine, because I can handle those bugs (and I already use it on 6 production servers, my company recommends VestaCP as main hosting panel on my company's site).

But, some people don't know how to fix the bugs.

So, I think the people with no-programming and no-sysadmin skills should wait for next release, I believe that VestaCP developers will fix all big bugs.

[dpeca]

IMHO right now developers need to focus on weeding out all the major bugs, instead of adding more new features.

Totally agree!
They need to slow down with new feautures, and fix reported bugs first.
Because it is better to have bugs free and production ready hosting panel, than to have hosting panel with cool new features but with ten bugs that makes VestaCP not production ready.