Nginx Amplify Agent Install Failed

[shrigabhishek]

Error when i try to install nginx amplify agent in ubuntu 22.04

Hit:1 https://deb.nodesource.com/node_16.x jammy InRelease
Hit:2 https://repos.insights.digitalocean.com/apt/do-agent main InRelease
Hit:3 https://repos-droplet.digitalocean.com/apt/droplet-agent main InRelease
Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:5 http://mirrors.digitalocean.com/ubuntu jammy InRelease
Hit:6 http://mirrors.digitalocean.com/ubuntu jammy-updates InRelease
Hit:7 http://mirrors.digitalocean.com/ubuntu jammy-backports InRelease
Ign:8 https://packages.amplify.nginx.com/ubuntu jammy InRelease
Err:9 https://packages.amplify.nginx.com/ubuntu jammy Release
  404  Not Found [IP: 52.24.210.11 443]
Reading package lists... Done
W: https://repos.insights.digitalocean.com/apt/do-agent/dists/main/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
E: The repository 'https://packages.amplify.nginx.com/ubuntu 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.

[srigit]

Error when i try to install nginx amplify agent in ubuntu 22.04

Hit:1 https://deb.nodesource.com/node_16.x jammy InRelease
Hit:2 https://repos.insights.digitalocean.com/apt/do-agent main InRelease
Hit:3 https://repos-droplet.digitalocean.com/apt/droplet-agent main InRelease
Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:5 http://mirrors.digitalocean.com/ubuntu jammy InRelease
Hit:6 http://mirrors.digitalocean.com/ubuntu jammy-updates InRelease
Hit:7 http://mirrors.digitalocean.com/ubuntu jammy-backports InRelease
Ign:8 https://packages.amplify.nginx.com/ubuntu jammy InRelease
Err:9 https://packages.amplify.nginx.com/ubuntu jammy Release
  404  Not Found [IP: 52.24.210.11 443]
Reading package lists... Done
W: https://repos.insights.digitalocean.com/apt/do-agent/dists/main/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
E: The repository 'https://packages.amplify.nginx.com/ubuntu 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.

I ran into the same issue. Use the script steps instead of the manual install.

[f1dz]

I tried both, the script and the manual way. Both failed. It seems that the package was not found because the server was down or something

[srigit]

What error do you get?

[f1dz]

@srigit I'm using Docker Amplify eventually https://github.com/nginxinc/docker-nginx-amplify

[joaopcm]

Got the same error 🤔

[mreho]

Hello, apparently Nginx team forgot to mention that the repository has moved for newer versions of Ubuntu (>= 18.04) and Python (>= 3.x).

Here is the command you should use to setup the repo :

#> codename=`lsb_release -cs` && \
os=`lsb_release -is | tr '[:upper:]' '[:lower:]'` && \
echo "deb http://packages.amplify.nginx.com/py3/${os}/ ${codename} amplify-agent" > \
/etc/apt/sources.list.d/nginx-amplify.list

As you can see py3 has been added inside the URI.

Hope this helps :)

[triplesixman]

Didn't work for me on Debian 12. I hope an update will add it soon.

[achawla2012]

Didn't work for me on Debian 12. I hope an update will add it soon.

@triplesixman There is an existing issue for adding support for Debian 12 in the NGINX Amplify Agent repo: https://github.com/nginxinc/nginx-amplify-agent/issues/100.

[achawla2012]

Hello, please make sure you have up-to agent version installed https://amplify.nginx.com/docs/guide-installing-and-managing-nginx-amplify-agent.html#updating-the-agent

[mhannan]

I was facing a similar issue, then I came across following solution which worked for me: https://askubuntu.com/questions/1385440/ubuntu-sudo-apt-get-update-404-not-found-problem