Error While fresh install

[xorro]

I just ran simple bash vst-install.sh on CentOS 7 and came up with this error.

Code: Select all

Error: Package: phpMyAdmin-5.0.0~alpha1-1.el7.remi.noarch (remi-test)
           Requires: php-symfony4-config >= 4.2.8
           Available: php-symfony4-config-4.1.12-1.el7.remi.noarch (remi)
               php-symfony4-config = 4.1.12-1.el7.remi
           Available: php-symfony4-config-4.1.13-1.el7.remi.noarch (remi)
               php-symfony4-config = 4.1.13-1.el7.remi
Error: Package: phpMyAdmin-5.0.0~alpha1-1.el7.remi.noarch (remi-test)
           Requires: php-symfony4-expression-language >= 4.2.8
           Available: php-symfony4-expression-language-4.1.12-1.el7.remi.noarch (remi)
               php-symfony4-expression-language = 4.1.12-1.el7.remi
           Available: php-symfony4-expression-language-4.1.13-1.el7.remi.noarch (remi)
               php-symfony4-expression-language = 4.1.13-1.el7.remi
Error: Package: phpMyAdmin-5.0.0~alpha1-1.el7.remi.noarch (remi-test)
           Requires: php-symfony4-yaml >= 4.2.8
           Available: php-symfony4-yaml-4.1.12-1.el7.remi.noarch (remi)
               php-symfony4-yaml = 4.1.12-1.el7.remi
           Available: php-symfony4-yaml-4.1.13-1.el7.remi.noarch (remi)
               php-symfony4-yaml = 4.1.13-1.el7.remi
Error: Package: phpMyAdmin-5.0.0~alpha1-1.el7.remi.noarch (remi-test)
           Requires: php-symfony4-dependency-injection >= 4.2.8
           Available: php-symfony4-dependency-injection-4.1.12-1.el7.remi.noarch (remi)
               php-symfony4-dependency-injection = 4.1.12-1.el7.remi
           Available: php-symfony4-dependency-injection-4.1.13-1.el7.remi.noarch (remi)
               php-symfony4-dependency-injection = 4.1.13-1.el7.remi
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

anyone know how to resolve this?

[xorro]

Not even working on ubuntu 19

Code: Select all

Get:5 http://nginx.org/packages/mainline/ubuntu disco InRelease [2,111 B]
Ign:6 http://apt.vestacp.com/disco disco InRelease 
Err:7 http://apt.vestacp.com/disco disco Release   
  404  Not Found [IP: 104.236.66.100 80]
Get:8 http://nginx.org/packages/mainline/ubuntu disco/nginx amd64 Packages [11.5 kB]
Reading package lists... Done
E: The repository 'http://apt.vestacp.com/disco disco Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
N: Skipping acquire of configured file 'nginx/binary-i386/Packages' as repository 'http://nginx.org/packages/mainline/ubuntu disco InRelease' doesn't support architecture 'i386'
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package rssh is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'rssh' has no installation candidate
E: Unable to locate package vesta
E: Unable to locate package vesta-ioncube
E: Unable to locate package vesta-nginx
E: Unable to locate package vesta-php
E: Unable to locate package vesta-softaculous
Error: apt-get install failed

After trying several times with multiple operating systems i think it's time for me to move on to another solution. It's been a very good journey with vestacp which i used to run on my all servers and also for all clients but today i think vestacp team is not longer cares about their product anymore. As they did not even implemented Other PHP versions or even did not bothered to add ioncube loader to be installed by default. And what i have been gone through it is very hard but i have to say. Good Bye

[liamgibbins]

Exactly the same as I am getting with CentOS 7 64bit

wish I never decided to reinstall my server now..

[xorro]

Some how i was able to install vestacp on Ubuntu 18.04 with several errors.

The other issue which i have been facing on my old centos 7 and current fresh installed ubuntu server is when ever i try to activate ssl support via let's encrypt i get this error "Error: Let's Encrypt validation status 400" no matter what i do this error is not going away even with CLI i get this error on ubuntu

Code: Select all

v-add-letsencrypt-domain: command not found

when it try to run (sudo apt-get install --reinstall vesta) i get this error

Code: Select all

Preparing to unpack .../vesta_0.9.8-25_amd64.deb ...
Unpacking vesta (0.9.8-25) over (0.9.8-25) ...
Setting up vesta (0.9.8-25) ...
/usr/local/vesta/bin/v-add-user-notification: line 19: /func/main.sh: No such file or directory
/usr/local/vesta/bin/v-add-user-notification: line 20: /conf/vesta.conf: No such file or directory
/usr/local/vesta/bin/v-add-user-notification: line 27: check_args: command not found
/usr/local/vesta/bin/v-add-user-notification: line 28: is_format_valid: command not found
/usr/local/vesta/bin/v-add-user-notification: line 29: is_object_valid: command not found
grep: /user.conf: No such file or directory
sed: can't read /user.conf: No such file or directory
/usr/local/vesta/bin/v-add-user-notification: line 19: /func/main.sh: No such file or directory
/usr/local/vesta/bin/v-add-user-notification: line 20: /conf/vesta.conf: No such file or directory
/usr/local/vesta/bin/v-add-user-notification: line 27: check_args: command not found
/usr/local/vesta/bin/v-add-user-notification: line 28: is_format_valid: command not found
/usr/local/vesta/bin/v-add-user-notification: line 29: is_object_valid: command not found
grep: /user.conf: No such file or directory
sed: can't read /user.conf: No such file or directory
/usr/local/vesta/bin/v-add-user-notification: line 19: /func/main.sh: No such file or directory
/usr/local/vesta/bin/v-add-user-notification: line 20: /conf/vesta.conf: No such file or directory
/usr/local/vesta/bin/v-add-user-notification: line 27: check_args: command not found
/usr/local/vesta/bin/v-add-user-notification: line 28: is_format_valid: command not found
/usr/local/vesta/bin/v-add-user-notification: line 29: is_object_valid: command not found
grep: /user.conf: No such file or directory
sed: can't read /user.conf: No such file or directory
/usr/local/vesta/bin/v-add-user-notification: line 19: /func/main.sh: No such file or directory
/usr/local/vesta/bin/v-add-user-notification: line 20: /conf/vesta.conf: No such file or directory
/usr/local/vesta/bin/v-add-user-notification: line 27: check_args: command not found
/usr/local/vesta/bin/v-add-user-notification: line 28: is_format_valid: command not found
/usr/local/vesta/bin/v-add-user-notification: line 29: is_object_valid: command not found
grep: /user.conf: No such file or directory
sed: can't read /user.conf: No such file or directory

[liamgibbins]

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. :)

[xorro]

Finally i think it's time to move instead spending more time on this. Going to try ISPConfig.

Just another vestacp fork https://www.hestiacp.com/

[liamgibbins]

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

https://github.com/serghey-rodin/vesta/ ... -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 clean all;
yum install epel-release -y;
wget http://rpms.famillecollet.com/enterpris ... ease-6.rpm; rpm -Uvh remi-release-6.rpm;
yum clean all

[sysdop]

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

[liamgibbins]

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

then try install again

[krooze]

remi test disable on /repos.d

Works for me

tkns

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

then try install again