Fresh installation of VestaCP on Ubuntu 16.04 failed, why?
-
- Posts: 301
- Joined: Tue Dec 22, 2015 2:06 pm
Fresh installation of VestaCP on Ubuntu 16.04 failed, why?
Today I did a fresh installation of VestaCP on Ubuntu 16.04, but failed soon after the installation started. Following is my steps and results:
1. I reset my VPS to re-install the OS: Ubuntu 16.04 64-bit.
2. On this clean and fresh Ubuntu, I run "apt-get update" first and got no updates (seems everything is the latest).
3. I ran VestaCP install command (the default one on the homepage of vestacp.com)
4. I got following error after some successful installation information:
Thank you.
1. I reset my VPS to re-install the OS: Ubuntu 16.04 64-bit.
2. On this clean and fresh Ubuntu, I run "apt-get update" first and got no updates (seems everything is the latest).
3. I ran VestaCP install command (the default one on the homepage of vestacp.com)
4. I got following error after some successful installation information:
Why? How can I fix this?
...
Installation will take about 15 minutes ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
linux-generic linux-headers-generic linux-image-generic
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
--2017-01-15 11:11:42-- http://nginx.org/keys/nginx_signing.key
Resolving nginx.org (nginx.org)... 206.251.255.63, 95.211.80.227, 2001:1af8:4060:a004:21::e3, ...
Connecting to nginx.org (nginx.org)|206.251.255.63|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1561 (1.5K) [text/plain]
Saving to: ‘/tmp/nginx_signing.key’
/tmp/nginx_signing.key 100%[===========================================>] 1.52K --.-KB/s in 0s
2017-01-15 11:11:44 (196 MB/s) - ‘/tmp/nginx_signing.key’ saved [1561/1561]
OK
--2017-01-15 11:11:44-- http://c.vestacp.com/deb_signing.key
Resolving c.vestacp.com (c.vestacp.com)... 104.236.66.100
Connecting to c.vestacp.com (c.vestacp.com)|104.236.66.100|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1719 (1.7K) [text/plain]
Saving to: ‘deb_signing.key’
deb_signing.key 100%[===========================================>] 1.68K --.-KB/s in 0s
2017-01-15 11:11:46 (180 MB/s) - ‘deb_signing.key’ saved [1719/1719]
OK
Ign:1 http://nginx.org/packages/mainline/ubuntu xenial InRelease
Hit:2 http://mirrors.aliyuncs.com/ubuntu xenial InRelease
Hit:3 http://mirrors.aliyun.com/ubuntu xenial InRelease
Hit:4 http://mirrors.aliyun.com/ubuntu xenial-security InRelease
Hit:5 http://mirrors.aliyun.com/ubuntu xenial-updates InRelease
Hit:6 http://mirrors.aliyun.com/ubuntu xenial-proposed InRelease
Hit:7 http://mirrors.aliyun.com/ubuntu xenial-backports InRelease
Hit:8 http://mirrors.aliyuncs.com/ubuntu xenial-security InRelease
Hit:9 http://mirrors.aliyuncs.com/ubuntu xenial-updates InRelease
Hit:10 http://mirrors.aliyuncs.com/ubuntu xenial-proposed InRelease
Hit:11 http://mirrors.aliyuncs.com/ubuntu xenial-backports InRelease
Ign:12 http://nginx.org/packages/mainline/ubuntu xenial Release
Ign:13 http://apt.vestacp.com/xenial xenial InRelease
Ign:14 http://nginx.org/packages/mainline/ubuntu xenial/nginx amd64 Packages
Ign:15 http://apt.vestacp.com/xenial xenial Release
Ign:16 http://apt.vestacp.com/xenial xenial/vesta amd64 Packages
Ign:17 http://nginx.org/packages/mainline/ubuntu xenial/nginx i386 Packages
Ign:18 http://nginx.org/packages/mainline/ubuntu xenial/nginx all Packages
Ign:19 http://apt.vestacp.com/xenial xenial/vesta i386 Packages
Ign:20 http://nginx.org/packages/mainline/ubuntu xenial/nginx Translation-en_US
Ign:21 http://apt.vestacp.com/xenial xenial/vesta all Packages
Ign:22 http://nginx.org/packages/mainline/ubuntu xenial/nginx Translation-en
Ign:23 http://apt.vestacp.com/xenial xenial/vesta Translation-en_US
Ign:14 http://nginx.org/packages/mainline/ubuntu xenial/nginx amd64 Packages
Ign:24 http://apt.vestacp.com/xenial xenial/vesta Translation-en
Ign:17 http://nginx.org/packages/mainline/ubuntu xenial/nginx i386 Packages
Ign:16 http://apt.vestacp.com/xenial xenial/vesta amd64 Packages
Ign:18 http://nginx.org/packages/mainline/ubuntu xenial/nginx all Packages
Ign:19 http://apt.vestacp.com/xenial xenial/vesta i386 Packages
Ign:20 http://nginx.org/packages/mainline/ubuntu xenial/nginx Translation-en_US
Ign:21 http://apt.vestacp.com/xenial xenial/vesta all Packages
Ign:22 http://nginx.org/packages/mainline/ubuntu xenial/nginx Translation-en
Ign:23 http://apt.vestacp.com/xenial xenial/vesta Translation-en_US
Ign:14 http://nginx.org/packages/mainline/ubuntu xenial/nginx amd64 Packages
Ign:24 http://apt.vestacp.com/xenial xenial/vesta Translation-en
Ign:17 http://nginx.org/packages/mainline/ubuntu xenial/nginx i386 Packages
Ign:16 http://apt.vestacp.com/xenial xenial/vesta amd64 Packages
Ign:18 http://nginx.org/packages/mainline/ubuntu xenial/nginx all Packages
Ign:19 http://apt.vestacp.com/xenial xenial/vesta i386 Packages
Ign:20 http://nginx.org/packages/mainline/ubuntu xenial/nginx Translation-en_US
Ign:21 http://apt.vestacp.com/xenial xenial/vesta all Packages
Ign:22 http://nginx.org/packages/mainline/ubuntu xenial/nginx Translation-en
Ign:23 http://apt.vestacp.com/xenial xenial/vesta Translation-en_US
Ign:14 http://nginx.org/packages/mainline/ubuntu xenial/nginx amd64 Packages
Ign:24 http://apt.vestacp.com/xenial xenial/vesta Translation-en
Ign:17 http://nginx.org/packages/mainline/ubuntu xenial/nginx i386 Packages
Ign:16 http://apt.vestacp.com/xenial xenial/vesta amd64 Packages
Ign:18 http://nginx.org/packages/mainline/ubuntu xenial/nginx all Packages
Ign:19 http://apt.vestacp.com/xenial xenial/vesta i386 Packages
Ign:20 http://nginx.org/packages/mainline/ubuntu xenial/nginx Translation-en_US
Ign:21 http://apt.vestacp.com/xenial xenial/vesta all Packages
Ign:23 http://apt.vestacp.com/xenial xenial/vesta Translation-en_US
Ign:24 http://apt.vestacp.com/xenial xenial/vesta Translation-en
Ign:22 http://nginx.org/packages/mainline/ubuntu xenial/nginx Translation-en
Ign:14 http://nginx.org/packages/mainline/ubuntu xenial/nginx amd64 Packages
Ign:17 http://nginx.org/packages/mainline/ubuntu xenial/nginx i386 Packages
Ign:16 http://apt.vestacp.com/xenial xenial/vesta amd64 Packages
Ign:18 http://nginx.org/packages/mainline/ubuntu xenial/nginx all Packages
Ign:19 http://apt.vestacp.com/xenial xenial/vesta i386 Packages
Ign:20 http://nginx.org/packages/mainline/ubuntu xenial/nginx Translation-en_US
Ign:21 http://apt.vestacp.com/xenial xenial/vesta all Packages
Ign:22 http://nginx.org/packages/mainline/ubuntu xenial/nginx Translation-en
Ign:23 http://apt.vestacp.com/xenial xenial/vesta Translation-en_US
Ign:24 http://apt.vestacp.com/xenial xenial/vesta Translation-en
Err:14 http://nginx.org/packages/mainline/ubuntu xenial/nginx amd64 Packages
403 Forbidden [IP: 112.124.140.210 80]
Err:16 http://apt.vestacp.com/xenial xenial/vesta amd64 Packages
403 Forbidden [IP: 112.124.140.210 80]
Ign:17 http://nginx.org/packages/mainline/ubuntu xenial/nginx i386 Packages
Ign:19 http://apt.vestacp.com/xenial xenial/vesta i386 Packages
Ign:18 http://nginx.org/packages/mainline/ubuntu xenial/nginx all Packages
Ign:21 http://apt.vestacp.com/xenial xenial/vesta all Packages
Ign:20 http://nginx.org/packages/mainline/ubuntu xenial/nginx Translation-en_US
Ign:23 http://apt.vestacp.com/xenial xenial/vesta Translation-en_US
Ign:22 http://nginx.org/packages/mainline/ubuntu xenial/nginx Translation-en
Ign:24 http://apt.vestacp.com/xenial xenial/vesta Translation-en
Reading package lists... Done
W: The repository 'http://nginx.org/packages/mainline/ubuntu xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://apt.vestacp.com/xenial xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch http://nginx.org/packages/mainline/ubun ... 4/Packages 403 Forbidden [IP: 112.124.140.210 80]
E: Failed to fetch http://apt.vestacp.com/xenial/dists/xen ... 4/Packages 403 Forbidden [IP: 112.124.140.210 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package vesta
E: Unable to locate package vesta-nginx
E: Unable to locate package vesta-php
Error: apt-get install failed
Thank you.
Re: Fresh installation of VestaCP on Ubuntu 16.04 failed, why?
The problem seems to be that the vesta repo servers hasent accepted your request. Can't detect any problem, they are online on my side. Try it again, maybe it was just temporary.
Code: Select all
...
E: Failed to fetch http://nginx.org/packages/mainline/ubun ... 4/Packages 403 Forbidden [IP: 112.124.140.210 80]
E: Failed to fetch http://apt.vestacp.com/xenial/dists/xen ... 4/Packages 403 Forbidden [IP: 112.124.140.210 80]
...
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: Fresh installation of VestaCP on Ubuntu 16.04 failed, why?
this is the problem... the repos are not updated and so can't find Vesta Repo. Pls talk to your provider if you can't do "apt update"2. On this clean and fresh Ubuntu, I run "apt-get update" first and got no updates (seems everything is the latest).
who is your provider ? and your server specs ? just be sure you are on an x86/x64 and not ARM server
-
- Posts: 301
- Joined: Tue Dec 22, 2015 2:06 pm
Re: Fresh installation of VestaCP on Ubuntu 16.04 failed, why?
Thanks for your help.
My server is "cloud VPS" from aliyun.com , which is the largest cloud server provider in China. I have no idea if this server is "ARM server", but I remember that I had successfully installed VestaCP on this same server a month ago. Today I just want to clean everything up and re-install everything ( I am not satisfied with former VestaCP installation on this same server because that one can not run Let's Encrypt to enable SSL for my domains).
Well, I tried again after reading above replies. But still failed with the same error message.
I noticed that in the error message, there is an IP address:
Thank you.
My server is "cloud VPS" from aliyun.com , which is the largest cloud server provider in China. I have no idea if this server is "ARM server", but I remember that I had successfully installed VestaCP on this same server a month ago. Today I just want to clean everything up and re-install everything ( I am not satisfied with former VestaCP installation on this same server because that one can not run Let's Encrypt to enable SSL for my domains).
Well, I tried again after reading above replies. But still failed with the same error message.
I noticed that in the error message, there is an IP address:
But 112.124.140.210 is not the IP address of my server. Why this IP is there?Err:8 http://nginx.org/packages/mainline/ubuntu xenial/nginx amd64 Packages
403 Forbidden [IP: 112.124.140.210 80]
Thank you.
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: Fresh installation of VestaCP on Ubuntu 16.04 failed, why?
Can you PM me your SSH details ?
-
- Posts: 301
- Joined: Tue Dec 22, 2015 2:06 pm
Re: Fresh installation of VestaCP on Ubuntu 16.04 failed, why?
Thank you very much, I am very willing to provide the SSH account to let you help me solve this issue.mehargags wrote:Can you PM me your SSH details ?
I had PM you the SSH account. Did you get it?
I will wait for your good news. :-)
Last edited by baijianpeng on Sun Jan 15, 2017 7:51 pm, edited 1 time in total.
-
- Posts: 301
- Joined: Tue Dec 22, 2015 2:06 pm
Re: Fresh installation of VestaCP on Ubuntu 16.04 failed, why?
Maybe the "Ubuntu server installer" provided by the hosting company is not the original Ubuntu install ISO, maybe they had removed/changed something in Ubuntu ?
I can not install the Operating System of my server with official Ubuntu ISO file because my hosting company does NOT allow this, they only let me choose OS versions from a list of "public images" provided by them.
I can not install the Operating System of my server with official Ubuntu ISO file because my hosting company does NOT allow this, they only let me choose OS versions from a list of "public images" provided by them.
-
- Posts: 301
- Joined: Tue Dec 22, 2015 2:06 pm
Re: Fresh installation of VestaCP on Ubuntu 16.04 failed, why?
Ok, finally under the help of support staff from my hosting provider, I solved this issue.
The reason is very simple: They (the hosting company) had added a line of proxy code into apt.conf, this proxy caused installing of VestaCP failed.
Open this file:
/etc/apt/apt.conf
the content is only one line:
Comment this line out and reboot my server, then re-install VestaCP from beginning, everything is OK now.
Thank you for all your help.
The reason is very simple: They (the hosting company) had added a line of proxy code into apt.conf, this proxy caused installing of VestaCP failed.
Open this file:
/etc/apt/apt.conf
the content is only one line:
Code: Select all
Acquire::http::Proxy "http://mirrors.aliyun.com/";
Thank you for all your help.
Re: Fresh installation of VestaCP on Ubuntu 16.04 failed, why?
this detail helped me to install vestacp on alibaba cloud.
baijianpeng wrote: ↑Sun Jan 15, 2017 9:04 pmOk, finally under the help of support staff from my hosting provider, I solved this issue.
The reason is very simple: They (the hosting company) had added a line of proxy code into apt.conf, this proxy caused installing of VestaCP failed.
Open this file:
/etc/apt/apt.conf
the content is only one line:
Comment this line out and reboot my server, then re-install VestaCP from beginning, everything is OK now.Code: Select all
Acquire::http::Proxy "http://mirrors.aliyun.com/";
Thank you for all your help.
-
- Posts: 301
- Joined: Tue Dec 22, 2015 2:06 pm
Re: Fresh installation of VestaCP on Ubuntu 16.04 failed, why?
hi, @rkhyd, I had abandoned the "ubuntu + vestacp" method , now I am running VestaCP on CentOS, because I noticed that the former combination will produce some weired 500 Errors but I can not fix them. After switching to CentOS, those errors never happened.