Vesta Control Panel - Forum

Sorry to drag up an old thread but I see people asking about this on proxmox etc.

The op wants a server that is the users endpoint but Vesta to hold webspace etc on server 2 and 3.

This would basically be a rewrite of the panel.

There is an alternative mind you that I have been thinking about ...

I would like to know a work around as well, I installed PHP7 and it still doesnt work.

this problem has been known for a while now and they are working on it I guess..
Its with the new version of phpmyadmin not been compatible or something.

you can use a cron job..

Sorry for late reply, I got it installing and working after going on github but the issue I am now having is that I get 500 error when trying to {domain name}/phpmyadmin/

I followed the advice here https://github.com/serghey-rodin/vesta/issues/1938#issuecomment-533895464
now i can not access ...

I see your having issues installing vestacp, the workaround is on other treads...

mgilank commented 6 days ago
This happen because in remi repo push phpmyadmin 5 alpha to it.
you can disable remi test repo by editing file in /etc/yum.repos.d/remi.repo
and find [remi-test], make enabled=0

then try ...

Disable the remi*-test repositories. If you have the active tests it won't let you.


mgilank commented 6 days ago
This happen because in remi repo push phpmyadmin 5 alpha to it.
you can disable remi test repo by editing file in /etc/yum.repos.d/remi.repo
and find [remi-test], make enabled=0 ...

Try dropping a issue report in github, there looked at very fast

There is a fix up on github, awesome speed..

https://github.com/serghey-rodin/vesta/issues/1938#issuecomment-531159435

Or a copy paste here..

kammi321 commented:
I fixed this issue by first executing the following commands prior to Installation:

yum -y install ca-certificates openssl nss;
yum ...

I tried to roll back the changes form the last update and tried to install on CentOS 7 64bit with vesta-0.938-23 and still get the same errors.

Going to run webmin until its sorted out, also reported the issue on github so hopefully they pick it up & fix it quickly. :)

I had something similar, do you have enough disk space on the server, mine started playing up like that when I ran out of disk space..
try login via ssh and delete a backup or two and see if it improves the situation, that fixed it for me..:P