myVesta

Hockeywain wrote: ↑Mon Jun 24, 2024 7:27 am Hello greetings I have a problem running vestacp on my Linux machine I get this error message


package yum has no installation candidate

yum command is for centos and redhat based distros, are you trying to install myvestacp in any of those? This is Debian only

Problem while installing php 7.4 I did wget -nv -O ./vesta-inst-php.sh https://c.myvestacp.com/tools/multi-php-install.sh mcedit ./vesta-inst-php.sh then at first try i only did inst_56=0 inst_70=0 inst_71=0 inst_72=0 inst_73=0 inst_74=1 inst_80=0 inst_81=0 inst_82=0 which tried to uninstall the alr...

bash vst-install-debian.sh --hostname YOURHOSTNAME.COM --email YOUR@EMAIL.COM --password YOURPASSWORD --secret_url YOURSECRETURL --port YOUPORT This way, it will ask you only to type 'y' at the beginning. But, yes, we can make a parameter to skip that 'y' at the beginning. Also i have noticed now t...

After install, i did a server reboot, the only service that didn't start at startup was iptables, i have opened it manually and it works

Installation was a success, do you want to log into it and check logs?

We didn't test VSFTPD :D Try and give us feedback :) By the way, ProFTPD works just fine. Only remember to start service manually after reboot :D I am testing now in a fresh vm! One thing i wanted to report long time now is that if I use the installer and add my own parameters example other port, s...

myVesta wrote: ↑Mon Jun 19, 2023 12:48 am I think it's ready now.
Only one issue left - and it's on Debian side - it's not our bug - https://bugs.debian.org/cgi-bin/bugrepo ... ug=1038416

This shouldn't be an issue the if we chose the other ftp server during the install right?

Although I have moved my servers into 2 VM, 1 for docker+portainer+nginx for websites and a 2nd vm for mailcow dockerized, I still use myvestacp as a test lab, I would like to ask if you have any ETA for debian 12?
I will try to make a clean install using debian12 cloudimage

I moved my server into 2 vm, 1 running Docker and portainer for websites and a 2nd vm with docker running mailcow dockerized, all problems solved!

I think this is related to the same issue I am facing as well, I do not want to use port 25 at all since this is by far the no1 port bots use to attack my servers, I have changed 4 datacenters in the past years, dedicated>VM>back to dedicated and in every case, on any domain name, I am getting hamme...