We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
A Suggestion...
A Suggestion...
Perhaps a Features Requests or Suggestions subforum can be added?
Incidentally, I see that while VestaCP still has Debian-based support in the works, I'm happy to know that this is the case.
That said, here's a few things I'd like to request in addition to the features request/suggestions subforums:
1. Support for CSF within the admin panel so the admin can see CSF and not just edit CSF's configuration via CLI.
2. Support for Softaculous.
3. Support for Hostbill.
4. Support for Pure-FTPD.
5. Support for disabling SSH access to customers. I do not see this as an option available in the control panel admin section.
6. Possibly change the way public_html is set up? I'm aware that you can change this yourself through specific configurations in the nginx/apache configs... but I'd like to see the option of setting it to /home/USER/public_html much like cPanel currently has their setup going.
7. Last but not least: A wiki hosted on VestaCP's website documenting the way VestaCP works in respective languages. I've set up an internal wiki for my company documenting what I've learned about VestaCP, but I'd love to see documentation directly from the creators of VestaCP.
Edit: 8. Support for BoxBilling would be amazing as well.
Edit2: 9. I would consider ensuring compatibility with Blesta to be of the highest priority at this time. /edit on oct 23rd 2013
This is looking to be a very awesome control panel. I will most likely end up rolling it out across all shared hosting servers that we have and retain cPanel for reseller hosting.
Incidentally, I see that while VestaCP still has Debian-based support in the works, I'm happy to know that this is the case.
That said, here's a few things I'd like to request in addition to the features request/suggestions subforums:
1. Support for CSF within the admin panel so the admin can see CSF and not just edit CSF's configuration via CLI.
2. Support for Softaculous.
3. Support for Hostbill.
4. Support for Pure-FTPD.
5. Support for disabling SSH access to customers. I do not see this as an option available in the control panel admin section.
6. Possibly change the way public_html is set up? I'm aware that you can change this yourself through specific configurations in the nginx/apache configs... but I'd like to see the option of setting it to /home/USER/public_html much like cPanel currently has their setup going.
7. Last but not least: A wiki hosted on VestaCP's website documenting the way VestaCP works in respective languages. I've set up an internal wiki for my company documenting what I've learned about VestaCP, but I'd love to see documentation directly from the creators of VestaCP.
Edit: 8. Support for BoxBilling would be amazing as well.
Edit2: 9. I would consider ensuring compatibility with Blesta to be of the highest priority at this time. /edit on oct 23rd 2013
This is looking to be a very awesome control panel. I will most likely end up rolling it out across all shared hosting servers that we have and retain cPanel for reseller hosting.
Last edited by KeiroD on Thu Oct 24, 2013 6:23 am, edited 2 times in total.
Re: A Suggestion...
SSH can be disabled globally in hosting package or after user creation in the editing mode. Just set SSH Access to "nologin". If you want to provide sftp/scp only without real shell access then select rssh.
We are going to launch wiki documentation portal very soon.
Thanks for your valuable suggestions.
We are going to launch wiki documentation portal very soon.
Thanks for your valuable suggestions.
Re: A Suggestion...
Not in the Ubuntu version, it seems, see below:skid wrote:SSH can be disabled globally in hosting package or after user creation in the editing mode. Just set SSH Access to "nologin". If you want to provide sftp/scp only without real shell access then select rssh.
We are going to launch wiki documentation portal very soon.
Thanks for your valuable suggestions.
-
- Posts: 25
- Joined: Mon Sep 30, 2013 8:42 am
Re: A Suggestion...
For the number 1 question you can also use Webmin and the CSF module, there you can edit it via the web.1. Support for CSF within the admin panel so the admin can see CSF and not just edit CSF's configuration via CLI.
Re: A Suggestion...
Here is hotfix for SSH Access disabling
Code: Select all
echo "/sbin/nologin" >> /etc/shells
Re: A Suggestion...
Nice one, works beautifully. It showed up immediately in the option. Thanks for the quick fix.skid wrote:Here is hotfix for SSH Access disablingCode: Select all
echo "/sbin/nologin" >> /etc/shells
I'm aware Webmin exists. However, I'd like to note that Webmin and VestaCP shouldn't really be used together. Most of the time, I do my management of servers via SSH, but from time to time, I'll decide to be lazy and do it through the web interface.ricardo777 wrote:For the number 1 question you can also use Webmin and the CSF module, there you can edit it via the web.1. Support for CSF within the admin panel so the admin can see CSF and not just edit CSF's configuration via CLI.
It's simply an option I'd like to see added at some point in the feature. Not just for myself, but for resellers that need to clear out the IP of a end-user having trouble accessing the server. See where I'm going here?
Incidentally, skid: More of a question than a suggestion, really right now: Why are you disallowing root login via VestaCP? I am aware that "admin" is the system administrator, but in all honesty, it is root that is the system administrator and that is what should be used. Are you not using the PAM module for authentication of users?
Re: A Suggestion...
We already thinking about integration with CSF, but I can't give you exact date at this moment.
As for the admin user it was made for security reasons. Authentication is handled by PAM and actually you can login as root user, but your session will be switched to admin user account.
The idea is that admin use a sudo to call vesta scripts and his sudo permissions are tied to a /usr/local/vesta/bin directory. So in case if someone find a security hole in vesta it won't give him a root privileges anyway because /usr/local/vesta/bin is not writable for admin.
As for the admin user it was made for security reasons. Authentication is handled by PAM and actually you can login as root user, but your session will be switched to admin user account.
The idea is that admin use a sudo to call vesta scripts and his sudo permissions are tied to a /usr/local/vesta/bin directory. So in case if someone find a security hole in vesta it won't give him a root privileges anyway because /usr/local/vesta/bin is not writable for admin.
Re: A Suggestion...
Understood on the CSF integration.skid wrote:We already thinking about integration with CSF, but I can't give you exact date at this moment.
As for the admin user it was made for security reasons. Authentication is handled by PAM and actually you can login as root user, but your session will be switched to admin user account.
The idea is that admin use a sudo to call vesta scripts and his sudo permissions are tied to a /usr/local/vesta/bin directory. So in case if someone find a security hole in vesta it won't give him a root privileges anyway because /usr/local/vesta/bin is not writable for admin.
I tried logging into it as root, but it simply gave me invalid username or password, so that doesn't quite work in the way you suggested it.
However, with regards to the event of a root-level escalation exploit, that is a good idea. I take it that when root installs VestaCP, "admin" is added to sudoers in Ubuntu automatically? If so, that's a great way of adding the admin user. Means I can disable root access via SSH and su/sudo to root via admin.
I am liking how VestaCP is working out, so far. The lack of documentation is a bit of an issue, but fortunately, given that I'm testing VestaCP and writing my own documentation, that's not too much of an issue.
Another question for you: I'm not sure if you're the one maintaining the Ubuntu installer script... but if you are, would it be possible to integrate it into the installer found at http://vestacp.com/pub/vst-install.sh?
It'd simplify me updating the central server that has the installer and sending the installer to the new server and having it install via a clustered SSH system.
Basically, what I'm trying to say is that you should integrate the Ubuntu installer into the main installer so that all one needs to do is download it to the central server. This permits them to pull it from the central server to the new server being provisioned and run the installer from there.
Re: A Suggestion...
This Monday we are releasing new unified installer together with the Debian 7 support. So it will work the way you described it.
Re: A Suggestion...
Win. Good to know. Thanks for the awesome work thus far. :)skid wrote:This Monday we are releasing new unified installer together with the Debian 7 support. So it will work the way you described it.