Vesta Control Panel - Forum

Github link: https://github.com/cdgco/vestawebinterface Looks slick and modern... though I could not use the functionality much. Let me know if you need any help in testing further. Wish you good luck!!! Thanks! I'm trying to achieve the same functionality as the current interface, just with a clean...

Hey everyone! I built a PHP interface and control panel for VestaCP featuring themes, integrations and simple customizations. Vesta Web Interface allows you to rebrand the control panel, change the theme, install it wherever you want, restrict access to users, easily edit options and offers integrat...

After about a week of not even touching my server, I rebooted it and when rebooting I noticed that apache could no start. After looking into the problem, I found that Apache and Nginx were both trying to run on port 8080, and if I stopped Nginx I could start Apache and vise versa. The errors I am re...

I know its much past December, but I have been in contact with the CEO of Site.Pro and he said that they are still working on the plugin, and should have it done this spring, or sooner depending on if they get help from the Vesta team. On the other hand, I have successfully integrated Site.Pro Build...

I just noticed that if one domain is set to VestaCP's nameservers, any user could register a subdomain to that domain. For example, user 1 has domain.com registered to their account, user 2 could register sub.domain.com without any protection / authentication. This then means that a customer to a si...

When will 1.0.3 be released?

Okay, so first off, if I replace vsftpd with proftpd, all my users will still work correct?
Also I would like to know are there any major differences between the two?

I feel that it is necessary enough to have a simpler user interface for clients. I had a conversation over a stackoverflow question I posted about doing this, but there was either a .htaccess error or DNS problem. It seems easily possible, but it may have just been a problem with my servers. Here's ...

Its odd though, it only cuts off part of a domain's nginx config section and it never even occurred to any of the domains of which had their aliases changed

This fixed the problem, but what caused this and how can I prevent this in the future?