Problems installing Zabbix Agent on Ubuntu 20.04 VM

[IBP-Service]

Hi everyone,

We have an active 3.2 Server ( migration to 6.0 is in works ) and need to add a new VM to the current monitoring. This needs to be done now so we cant wait on the migration aka has to be v 3.2 for the agent.
The whole initial zabbix server setup was done by people who are no longer with the company, so I am more or less on my own in this.
The new VM is running Ubuntu 20.04 and we thought we could grab the 3.2 for xenial and install it that way ( I am new to linux so please correct me if I am wrong in this assumption )

Before this post I couldnt figure out why the proxy ( which communicates with other agents on the same net fine and also is running on 3.2) couldnt reach the new agent. The agent was logging something about a missing header.
Further investigation showed that the agent was running version 4.0.17 for some reason.

The commands I used to install the agent were the following :

# sudo wget https://repo.zabbix.com/zabbix/3.2/ubuntu/pool/main/z/zabbix-release/zabbix-release_3.2-1+xenial_all.deb 
# sudo dpkg -i zabbix-release_3.2-1+xenial_all.deb
# sudo apt update
# sudo apt install zabbix-agent

Can somebody explain what I am doing wrong in this case and what options I have ?
The problem is that due to the software running on the server and further services of it it needs to run Ubuntu 20.04.
I dont know if I am somehow messing something up with the wget , the repo being drunk or something else.

Thanks in advance.

[Atsushi]

Probably, there is no corresponding Zabbix 3.2 agent on Zabbix official repository, so OS standard package is installed. Even if you install the Ubuntu Xenial (16.04) package on Ubuntu Focal (20.04), there is no guarantee that it will work properly. If you want to start Zabbix 3.2 agent on Ubuntu 20.04, compile and install from the source code.

[IBP-Service]

Forgot to reply but thanks for the comment on that.
It was exactly how you said it that it went straight for the 20.04 Ubuntu version ( Agent v 4.x in this case)
This will be resolved when we migrate from our 3.2 to 6.0 Server.

Thanks again