[Fresh install] Failed to download AMP on Ubuntu Serverer

OS Name/Version: ubuntu 22.04 live server amd64

Product Name/Version: AMP Instance Manager v2.3.2.10 built 21/04/2022

Problem Description:

GetAMP v2.7.8
AMP QuickStart installation script for Debian, Red-Hat and Arch based GNU/Linux distributions
This installer will perform the following:

 * Install any pending system updates
 * Install any prerequisites and dependencies via your systems package manager
 * Add the CubeCoders repository to your system to keep AMP updated
 * Install AMP and create a default management instance on port 8080
 * Create any firewalls necessary to allow you to connect to AMP
 * Configure the default AMP instance to start on boot

Press CTRL+C to cancel installation.

It is safe to cancel this installation at any point. You can run the install
script again, and the script will skip any steps it has already completed.

Distribution        : ubuntu 22.04
Platform            : x86_64
Internal IP address : 192.168.3.12
External IP address : 79.112.49.96
Network type        : NAT
Gateway IP address  : 192.168.3.1
Detected Firewall   : ufw
System Locale       : en_US.UTF-8
Package Manager     : apt-get

Enter new login details for use with AMP.
Alphanumeric (a-Z and 0-9) only. No special characters - you can change this later.

The password must not be the same as the system password!
Username [admin]:
Password:
Confirm Password:

Will you be running Minecraft servers on this installation?
If selected, this installs the required versions of Java.
[Y/n] y

Will you be running applications that rely on SteamCMD? (Rust, Ark, CSGO, TF2, etc) on this installation?
If selected, this will install the required additional 32-bit libraries.
[Y/n] y

Would you like to isolate your AMP instances by running them inside Docker containers?
This provides an additional layer of protection at the expense of a minor performance impact.
It is strongly recommended if you are going to allow untrusted users access to AMP
but if it's just yourself or trusted users accessing it then it may not be necessary.
[y/N] n

Would you like AMP to be configured for use with HTTPS?

This will install nginx on your system and requires that you do not use any
other web servers such as Apache on this system.

This will create firewall rules to open ports 80 (HTTP) and 443 (HTTPS)
You also must own a domain name that resolves to 79.112.49.96 (Your external IP)

Do not choose this option if you do not already own a domain.

Using this facility requires that you read and accept the LetsEncrypt terms at
https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf

Enable HTTPS?
[Y/n] n


Installation Summary:

AMP System user:                Already exists
Instance Manager:               Already installed
HTTPS setup:                    No
Install Java:                   Yes
Install 32-bit libraries:       Yes
Install Docker:                 No

Ready to install AMP. Press ENTER to continue or CTRL+C to cancel.


Installing AMP...
amp already exists. Skipping...
Updating System...



Installing prerequisites...
Installing Java for Minecraft...
Installing Adoptium Java 17...
Installing 32-bit dependencies for srcds...
AMP instance manager already installed. Skipping...
Adding firewall rules...
Adding firewall rule for port 8080 (AMP Management Instance) via ufw...
Skipping adding existing rule
Skipping adding existing rule (v6)
Creating default instance...
[Info] AMP Instance Manager v2.3.2.10 built 21/04/2022 15:10
[Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV
[Notice] AMP Service port ranges have not been specified, using any available...
[Notice] Application Service port ranges have not been specified, using any available...
[Activity] Audit: Unknown/None [CreateInstance] Created instance ADS01 using ADS module on port 8080.
[Error] Failed to download AMP (Operation Cancelled). Possible cause: Improper IPv6 configuration.
[Error] OperationCanceledException
[Error] [0] (OperationCanceledException) : The operation was canceled.
[Error]   at InstanceManagerPlugin.LocalInstanceManager.DownloadAndUnpack (InstanceManagerPlugin.LocalAMPInstance Spec, Boolean SkipCache)
[Info] Instance creation failed. Reason: "The core archive failed to download or unpack"

Installation complete. Thanks for using AMP!

You can now reach AMP at http://192.168.3.12:8080/
or at http://79.112.49.96:8080/

Steps to reproduce:

  • Run bash <(wget -qO- getamp.sh)
  • Wait about 1 ~ 2 minutes for the process to start (quad core i3 processor with gigabit Ethernet )
  • Complete the basic installation info (username, password, Minecraft yes, steam yes, docker & https no)
  • Wait again for the installer to proceed to the shared error.

Actions taken to resolve so far:
So far I’ve tried flushing the DNS, checking my ipv6 settings ( I’m not sure though if the error is caused by my pc trying to use ipv6 or the installer requiring functional ipv6 in order to work)

I’ve tried reinstalling the OS, & general google browsing on the issue.

What can I do to fix this.
In the past I used AMP on normal versions of ubuntu (Not the server one, the user friendly one) and it worked.
Now I decided to try using the server version as its more lightweight and I don’t need the UI.

http://192.168.3.12:8080/ is not acessible.
I had a similar issue on this in the past where the problem was the proxy manager of ubuntu.
Now i can say for a fact that amp instance manager is not running


root@gilgamesh:~# sudo lsof -i -P -n | grep LISTEN
systemd-r  683 systemd-resolve   14u  IPv4  24710      0t0  TCP 127.0.0.53:53 (LISTEN)
sshd       778            root    3u  IPv4  24879      0t0  TCP *:22 (LISTEN)
sshd       778            root    4u  IPv6  24881      0t0  TCP *:22 (LISTEN)
Xtightvnc 8005         eoancea    0u  IPv4  42020      0t0  TCP *:6001 (LISTEN)
Xtightvnc 8005         eoancea    3u  IPv4  42022      0t0  TCP *:5901 (LISTEN)
root@gilgamesh:~#

So far as IPv6 goes, if it’s present it has to work. I’m guessing this is home hosted?

1 Like

Yes it is home hosted.
I’m planning to use a dynamic DNS with it provided by my ISP as I see it works quite well.

Any hints for what I can try ?

Thanks.

Try doing a general apt update and upgrade then running the script again. If that doesn’t work there’s a little hack we can do.

1 Like
  • apt update returned one 404 warning
Ign:1 https://ookla.bintray.com/debian generic InRelease
Hit:2 http://ro.archive.ubuntu.com/ubuntu jammy InRelease
Get:3 http://ro.archive.ubuntu.com/ubuntu jammy-updates InRelease [109 kB]
Hit:4 https://download.docker.com/linux/ubuntu jammy InRelease
Hit:5 http://ro.archive.ubuntu.com/ubuntu jammy-backports InRelease
Get:6 http://ro.archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:7 http://ro.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages [26.9                                                                                                                                     kB]
Get:8 http://ro.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [79.                                                                                                                                    5 kB]
Get:9 http://ro.archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [22.                                                                                                                                    6 kB]
Get:10 http://ro.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packag                                                                                                                                    es [50.7 kB]
Get:11 http://ro.archive.ubuntu.com/ubuntu jammy-updates/restricted i386 Package                                                                                                                                    s [720 B]
Get:12 http://ro.archive.ubuntu.com/ubuntu jammy-updates/universe i386 Packages                                                                                                                                     [17.7 kB]
Get:13 http://ro.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages                                                                                                                                     [63.5 kB]
Ign:14 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb jammy InRelease
Hit:15 https://repo.cubecoders.com debian/ InRelease
Err:16 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb jammy Release
  404   [IP: 34.139.10.89 443]
Ign:1 https://ookla.bintray.com/debian generic InRelease
Ign:1 https://ookla.bintray.com/debian generic InRelease
Err:1 https://ookla.bintray.com/debian generic InRelease
  Could not handshake: The TLS connection was non-properly terminated. [IP: 18.195.160.223 443]
Reading package lists... Done
E: The repository 'https://adoptopenjdk.jfrog.io/adoptopenjdk/deb jammy 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.
  • apt upgrade ran fine
  • bash <(wget -qO- getamp.sh) had the same results
Installation Summary:

AMP System user:                Already exists
Instance Manager:               Already installed
HTTPS setup:                    No
Install Java:                   Yes
Install 32-bit libraries:       Yes
Install Docker:                 No

Ready to install AMP. Press ENTER to continue or CTRL+C to cancel.


Installing AMP...
amp already exists. Skipping...
Updating System...
Installing prerequisites...
Installing Java for Minecraft...
Installing Adoptium Java 17...
Installing 32-bit dependencies for srcds...
AMP instance manager already installed. Skipping...
Adding firewall rules...
Adding firewall rule for port 8080 (AMP Management Instance) via ufw...
Skipping adding existing rule
Skipping adding existing rule (v6)
Creating default instance...
[Info] AMP Instance Manager v2.3.2.12 built 05/05/2022 18:14
[Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV
[Notice] AMP Service port ranges have not been specified, using any available...
[Notice] Application Service port ranges have not been specified, using any available...
[Activity] Audit: Unknown/None [CreateInstance] Created instance ADS01 using ADS module on port 8080.
[Error] Failed to download AMP (Operation Cancelled). Possible cause: Improper IPv6 configuration.
[Error] OperationCanceledException
[Error] [0] (OperationCanceledException) : The operation was canceled.
[Error]   at InstanceManagerPlugin.LocalInstanceManager.DownloadAndUnpack (InstanceManagerPlugin.LocalAMPInstance Spec, Boolean SkipCache)
[Info] Instance creation failed. Reason: "The core archive failed to download or unpack"

Installation complete. Thanks for using AMP!

It froze for a while on this step [Activity] Audit: Unknown/None [CreateInstance] Created instance ADS01 using ADS module on port 8080. then it threw the error.

The port 8080 is not in use.

Can you try disabling IPv6 on the system and seeing if that allows it to run normally? Otherwise you can do this:

sudo su -l amp
wget https://cubecoders.com/Downloads/AMP_Latest.zip
mv AMP_Latest.zip ~/.ampdata/instances/AMPCache-23212.zip
ampinstmgr quick

Some of the repositories don’t work because 22.04 is too new and not everything supports it right now. Namely the Adoptium/AdoptOpenJDK repo for Java. You can remove those repositories for now.

1 Like

Disabling ipv6 →

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 90:1b:0e:2a:e1:4b brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.12/24 metric 100 brd 192.168.3.255 scope global dynamic enp2s0
       valid_lft 86217sec preferred_lft 86217sec
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:0f:46:d9:7c brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
root@gilgamesh:/home/eoancea#
  • bash <(wget -qO- getamp.sh)
    Execution started much faster (usually I had to wait bout 5 mins for it to start)
    And it worked :smiley:

I suppose some servers/proxy’s don’t respond well to ipv6 requests.

Our systems all support IPv6, but you can end up with weirdness if you have a system that has an IPv6 address but no reachable IPv6 DNS for example. It’s usually correct if it says in the message that there’s an issue with the IPv6 setup :wink:

1 Like