We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Upgrade Ubuntu 16.04 to 18.04
Upgrade Ubuntu 16.04 to 18.04
Hi,
There's been a looong discussion on how Ubuntu 18.04 is kinda, sorta supported, but kinda sorta doesn't quite work here: viewtopic.php?f=41&t=16849
I thought I'd split this out into a separate topic. Given that Ubuntu 16 is fine, has anyone tried installing onto Ubunutu 16, at which pint its working fine, and then doing a do-release-upgrade to 18.04.
I'm just wondering if this is an option, and whether there are different results between the fresh install and upgrade.
There's been a looong discussion on how Ubuntu 18.04 is kinda, sorta supported, but kinda sorta doesn't quite work here: viewtopic.php?f=41&t=16849
I thought I'd split this out into a separate topic. Given that Ubuntu 16 is fine, has anyone tried installing onto Ubunutu 16, at which pint its working fine, and then doing a do-release-upgrade to 18.04.
I'm just wondering if this is an option, and whether there are different results between the fresh install and upgrade.
Re: Upgrade Ubuntu 16.04 to 18.04
18.04 is super flakey - I wouldn't even considered it supported by VestaCP.
The VestaCP team should really remove it from the 'supported OS list' in the meantime.
Too many reports about users having issues with 18.04 - giving new (and a smaller degree, old) users a bad taste of Vesta when 18.04 install fails.
Fairly bad PR imho.
The VestaCP team should really remove it from the 'supported OS list' in the meantime.
Too many reports about users having issues with 18.04 - giving new (and a smaller degree, old) users a bad taste of Vesta when 18.04 install fails.
Fairly bad PR imho.
Re: Upgrade Ubuntu 16.04 to 18.04
can you maybe share some sources, why ubuntu 18.04 should be so bad? So we can take a deeper look.ivanh wrote: ↑Sat Oct 13, 2018 2:43 am18.04 is super flakey - I wouldn't even considered it supported by VestaCP.
The VestaCP team should really remove it from the 'supported OS list' in the meantime.
Too many reports about users having issues with 18.04 - giving new (and a smaller degree, old) users a bad taste of Vesta when 18.04 install fails.
Fairly bad PR imho.
-
- Posts: 4
- Joined: Tue Oct 16, 2018 1:41 am
- Contact:
- Os: CentOS 6x
- Web: apache + nginx
Re: Upgrade Ubuntu 16.04 to 18.04
hi i have successfully installed vestacp nginix+php on Ubuntu 18.04 and its working fine
login as root on fresh install
generate your installation command from here https://vestacp.com/install/
the generated command will be like this
bash vst-install.sh --nginx yes --phpfpm yes --apache no --named yes --remi yes --vsftpd no --proftpd yes --iptables yes --fail2ban yes --quota no --exim yes --dovecot yes --spamassassin yes --clamav no --softaculous yes --mysql yes --postgresql no --hostname localhost --email youremail --password password
replace bash vst-install.sh with bash vst-install-ubuntu.sh --force
it will be like this
bash vst-install-ubuntu.sh --force --nginx yes --phpfpm yes --apache no --named yes --remi yes --vsftpd no --proftpd yes --iptables yes --fail2ban yes --quota no --exim yes --dovecot yes --spamassassin yes --clamav no --softaculous yes --mysql yes --postgresql no --hostname localhost --email youremail --password password
run the script vesta cp will install without any problem
this is my first post here hope it will be a help for those with Ubuntu 18
login as root on fresh install
generate your installation command from here https://vestacp.com/install/
the generated command will be like this
bash vst-install.sh --nginx yes --phpfpm yes --apache no --named yes --remi yes --vsftpd no --proftpd yes --iptables yes --fail2ban yes --quota no --exim yes --dovecot yes --spamassassin yes --clamav no --softaculous yes --mysql yes --postgresql no --hostname localhost --email youremail --password password
replace bash vst-install.sh with bash vst-install-ubuntu.sh --force
it will be like this
bash vst-install-ubuntu.sh --force --nginx yes --phpfpm yes --apache no --named yes --remi yes --vsftpd no --proftpd yes --iptables yes --fail2ban yes --quota no --exim yes --dovecot yes --spamassassin yes --clamav no --softaculous yes --mysql yes --postgresql no --hostname localhost --email youremail --password password
run the script vesta cp will install without any problem
this is my first post here hope it will be a help for those with Ubuntu 18
Last edited by pramod7770 on Mon Jan 04, 2021 8:14 pm, edited 3 times in total.
Re: Upgrade Ubuntu 16.04 to 18.04
What changes did you make to the installer script?
Re: Upgrade Ubuntu 16.04 to 18.04
I have now compared your code with the original ubuntu installer. It doesn't seem that you addressed the numerous issues users have reported with Ubuntu 18.04
Re: Upgrade Ubuntu 16.04 to 18.04
Dear SCiT, can you please check this thread?ScIT wrote: ↑Sat Oct 13, 2018 4:55 amcan you maybe share some sources, why ubuntu 18.04 should be so bad? So we can take a deeper look.ivanh wrote: ↑Sat Oct 13, 2018 2:43 am18.04 is super flakey - I wouldn't even considered it supported by VestaCP.
The VestaCP team should really remove it from the 'supported OS list' in the meantime.
Too many reports about users having issues with 18.04 - giving new (and a smaller degree, old) users a bad taste of Vesta when 18.04 install fails.
Fairly bad PR imho.
viewtopic.php?f=41&t=16849
Re: Upgrade Ubuntu 16.04 to 18.04
Tried it, same fail to install on fresh ubuntu 18.04:
Code: Select all
Installation will take about 15 minutes ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
--2018-10-28 00:46:12-- http://nginx.org/keys/nginx_signing.key
Resolving nginx.org (nginx.org)... 2001:1af8:4060:a004:21::e3, 2606:7100:1:69::3f, 95.211.80.227, ...
Connecting to nginx.org (nginx.org)|2001:1af8:4060:a004:21::e3|: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
2018-10-28 00:46:12 (243 MB/s) - ‘/tmp/nginx_signing.key’ saved [1561/1561]
E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation
--2018-10-28 00:46:12-- 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
2018-10-28 00:46:13 (382 MB/s) - ‘deb_signing.key’ saved [1719/1719]
E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation
Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
Get:2 http://nginx.org/packages/mainline/ubuntu bionic InRelease [2,115 B]
Err:2 http://nginx.org/packages/mainline/ubuntu bionic InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ABF5BD827BD9BF62
Hit:4 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Hit:5 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
Get:3 http://apt.vestacp.com/bionic bionic InRelease [2,184 B]
Err:3 http://apt.vestacp.com/bionic bionic InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 42C5B2130A1F7714
Hit:6 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease
Reading package lists... Done
W: GPG error: http://nginx.org/packages/mainline/ubuntu bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ABF5BD827BD9BF62
E: The repository 'http://nginx.org/packages/mainline/ubuntu bionic InRelease' is not signed.
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.
W: GPG error: http://apt.vestacp.com/bionic bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 42C5B2130A1F7714
E: The repository 'http://apt.vestacp.com/bionic bionic InRelease' is not signed.
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.
Reading package lists... Done
Building dependency tree
Reading state information... Done
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