SolusVM

Actually try this: rm -rf /usr/local/svmstack/letsencrypt/store That will delete the old registration data. Then run: /usr/local/svmstack/letsencrypt/letsencrypt -i

Try this: yum clean all yum update svmstack-letsencrypt That should fix it.

Hi, Do you have port 80 open on the master? it needs it to connect to the letsencrypt servers.

I think this was due to you trying to use CentOS 6 and the OpenVZ kernel. As it stands now we won't be supporting OpenVZ on CentOS 7 until it is officially supported. https://openvz.org/Releases

Try a simple reboot of the node. If the issue continues please submit a ticket.

Find this line in /etc/vz/vz.conf: CONFIGFILE="basic" That tells me the generic config file is called "basic", however it will be named in a different format in /etc/vz/conf/: ve-basic.conf-sample Edit that file and add the following line: QUOTAUGIDLIMIT="1000" Each VM now built will use that setting.

Yes solusvm will resize the partition when the vps builds to the size of the vps you specify. The templates in the TDN are general templates that have a mix of filesystems. This means solusvm will only extend the logical volume (HDD) not the partitions of filesystems inside them. We also have a set of BSD and windows templates in the works that auto resize on build. So your saying that virtualizor expands the disk, partitions and filesystem inside an active vps? If thats the case then i make sure you take plenty of backups because you will corrupt data at some point.. it's only a matter of time. You have to understand that keeping data safe always ends in limitations of what you can do. We would never dream of mounting a live virtualized logical volume period.

I've also reqested a photograph of him with his new Air once he receives it.

The lucky winner of the MacBook Air is James Havery from Arizona USA! Contact has been made with the client and mailing address confirmed.

Just to make you aware we are changing the templating system.... Smarty is proving to be a massive overhead on some busy systems so we have been testing the reseller area on our own custom system that doesn't need to compile The results are great! The next step is the client area!

That is correct. We are still adding features to the reseller area, including language support.

You copy the default template folder from /usr/local/solusvm/templates/client and give it a custom name. You then edit the files in that. I would hold off though, We have a new template out soon that is easy to customize.

Table sorting will be put in asap. The bandwidth is collected evey 5 minutes, collecting it in a lower interval is not advised..

It's not a bug. Once you add an ip to the whitelist it will only allow that ip. If no ip's are in the white list it will allow any ip.