VestaCP use eventually crashes my EC2 instance

[tbrady85]

As the title says, after a few minutes using the VestaCP panel, whether it be adding a domain, SSL certificates, emails, whatever my VPS will just crash. There doesn't seem to be any specific action I do that causes this but it seems to happen more often while adding SSL certificates. The server will still be running but everything becomes unresponsive. All of my websites, the admin panel, mail, SSH, FTP all become unresponsive. This only happens when editing things in the VestaCP panel itself. Once I manual reboot the server everything works fine until I start changing things within the control panel again. Any ideas of what could be causing this?

Edit: I'm running an AWS EC2 instance with 1 vCPU and 1gb ram and Ubuntu 16.04 and this is a fresh install on a new instance. I used to have my webserver running on the same instance but with Ubuntu 14 and Sentora CP and have never had this issue.

[mehargags]

Can you try this with Debian 8 image ?
I have several 1GB EC2s successfully running VestaCP and running fine. I'm sure many have Ubu 16 as well.

One Issue to keep in mind is that Amazon's EC2s have a default "admin" user already created, you need to take care of it with --force install.

[tbrady85]

Sure I'll try that and see what happens. On a side note, I started a brand new instance and reinstalled vestaCP and still have the same issues. The only other thing I can think of is maybe I have too many services running? This is the bash command I use to install VestaCP:

Code: Select all

bash vst-install.ubuntu.sh --force --nginx yes --apache yes --phpfpm no --named yes --remi yes --vsftpd yes --proftpd no --iptables yes --fail2ban yes --quota no --exim yes --dovecot yes --spamassassin yes --clamav yes --mysql yes --postgresql no

[tbrady85]

I decided to go with a CentOS instance and so far so good with that one. Still not sure what was going on with the Ubuntu instance with vesta.

[mehargags]

ok once you have a fresh Ubuntu before installing vestaCP issue these commands:

Code: Select all

apt-get purge apache* samba* bind9* exim4* postfix* -y

apt-get autoremove --purge -y

and then try to install vestaCP and post results

[tjebbeke]

Maybe it was a good idea to check:
- Log files
- Resource (Top, Load, Memory, ...)

[raiden]

Try minimal installation, i'm using t2.micro too, only nginx + apache, vsftpd, exim + dovecot and mysql, firewall no needed when using aws :))