Vesta Control Panel - Forum

Vulnerability in PHP7 exposes sites to remote hacking risk The problem only applies to NGINX servers with PHP-FPM enabled. image A dangerous vulnerability (CVE-2019-11043) has been identified in the PHP 7 branch, which allows attackers to execute commands on the server using a specially generated UR...

it's just a theory: (untested) Let's Encrypt problem with special chars in domain names happens (possibly) when vestacp installer is customized before installation to not include the DNS system. guess the vestacp people do not have the time to test every combination. did not decide to install the DN...

hello, changing port for vestacp backend will also change port for /phpmyadmin vim /usr/local/vesta/nginx/conf/nginx.conf # find this lines # Vhost server { listen 8083; <- change new port :wq # save and quit # restart vesta service vesta restart what you can do is modify the /url/path/to/phpmyadmin...

argh! seems to be similar problem: https://forum.vestacp.com/viewtopic.php?t=14817 had to reinstall anyway... and now i want to add a domain with special character: ö and the evil "Error: Let's Encrypt new auth status 400" is back! WHAT DOES "status 400" actually mean? Static hostname: webserver2.vm...

alright i might as well answer my own question.

found: which does:
so i would say:
is pretty fine.

Hello, thanks for the great control panel, really love it's simplicity (do not need that softaculous, i use my own script to do wget latest wordpress, unpack, chmod etc.) usually have: /scripts/shutdown.sh /scripts/reboot.sh ... what is the most graceful way to shutdown/reboot vestacp? or is a simpl...

Hello all, update: i do do not know what the "400" is supposed to mean. but it definitely has something to do with a domain name, if you have multiple domain names, try to reduce the list to one domain, see if it works then. i also really love vestacp - its simplicity is just great. (i do not need m...

how can i uninstall it? you should not ship vesta with this enabled/installed per default, less code = more secure. https://www.exploit-db.com/exploits/45584 http://www.tpweb.org/2015/11/06/vestacp-file-manager/ https://nvd.nist.gov/vuln/detail/CVE-2018-10686 https://pastebin.com/raw/phAM8DFH

okay it is getting worse. after running vestacp for several months inside docker... i think i will take a look at OpenVZ or leave the container space at all. why? problems: 1. containers harddisk space once used – does not shrink!? (unless you export/import) i would understand this if all files were...

BIGGEST Problem with docker: it can not free once claimed disk space! X-D

so if you copy big files to your docker instance... and delete them... the disk space is not FREEED!

is it a bug? or a feature?

whatever it is IT SUCKS and forced me to buy a bigger server.