Vesta Control Panel - Forum

you might also want to try what is happening if you remove one of those databases. my guess would be your db user is getting removed as well, which may break things for the second database and so on...

really great write up! suggestion/things to consider: - you could also use lighttpd or nginx on the remote db server instead of apache - there is also a mariadb-client package you could go with on the vestacp server instead of mysql-client. this was installed by default through the vestacp setup scr...

add --mysql no to the install command of vestacp and it doesn't install mysql in the first place. also there will be no phpmyadmin. after you did add your remote mysql like @Lidocaine described you can add and use mysql on that vesta box. it will adjust the phpmyadmin-url for those databases to the ...

https://vestacp.com/docs/#how-to-add-re ... ase-server

be aware of correct privileges on the remote server for the user your are adding with this (needs GRANT) ;-)

Hi skamasle, Thanks for the info, I have already tried this and the issue still persists. its weird, i also connected a newly installed remote database server running 5.6 and i have the same issue.. it will create a database but no users. im not sure where to even start with this just a quick follo...

Hi there, I prefer to use MPM_ITK over ruid2 and recently noticed that Apache2.4 on Debian 8.7 doesn't recognize the check for <IfModule itk.c> in the vhosts correctly. therefore the AssignUserID doesn't work properly and Apache continues to run as www-data hence a lot of permission problems occur. ...

you're welcome. as it seems the same problem is mentioned here: https://github.com/serghey-rodin/vesta/issues/1035 , I will put a backlink there...

just had another look into /usr/local/vesta/bin/v-backup-user where the things are done... there you'll find two blocks: # Backup proxy config if [ ! -z "$PROXY_SYSTEM" ] && [ ! -z "$PROXY" ]; then tpl_file="$WEBTPL/$PROXY_SYSTEM/$PROXY.tpl" conf="$HOMEDIR/$user/conf/web/$PROXY_SYSTEM.conf" get_web_...

yes, I can reproduce that. it seems that this is caused if you have nginx+apache2 installed, then deactivate proxy for a (sub)domain but have ssl enabled. haven't found it yet, but it looks like if there is a check missing when grepping the the templates throughout backup-process, because proxy off ...

apt-get update && apt-get dist-upgrade