Zabbix Frontend won't open

[Trixter89]

Hi all,

I am new to Zabbix, my girlfriend has a task from her boss to spin 2 VM's in AWS, one with Zabbix and one with MariaDB and the Zabbix Frontend needs to be in a Docker container.

Before even attempting to do the whole thing, we first wanted to do a quick install to go through the steps of Installation and setup the whole thing (Zabbix Server+Agent+MariaDB) on 1 VM. We've been hitting our heads in the wall for the past 12 hours literally, not being able to figure out why http://172.31.24.49/zabbix returns This site can’t be reached 172.31.24.49 took too long to respond.

OS is RHEL 8 on AWS EC2 and installing Zabbix 5.0. Tried following multiple sites with steps, last time I followed this https://bestmonitoringtools.com/how-...entos-or-rhel/ and https://www.zabbix.com/download?zabb...ysql&ws=apache, but with the same result.

Logs of Httpd, MariaDB, Zabbix-Sever and Zabbix-agent do not have any issues at all. All of the services mentioned are running and enabled. php_value[date.timezone] is set for the frontend in /etc/php-fpm.d/zabbix.conf. I've watched over 15 videos in youtube and I am following the steps perfectly, until we reach checking if http://172.31.24.49/zabbix resolves. I have no idea what I am missing and I would be extremely grateful if someone could help, cause I am about to flip the table.

If you need to see any of the conf files, just let me know.

Thanks and kind regards,
Chris

[incama]

Is the VM pingable?

[snuffy]

Apache or Nginx?

[Trixter89]

Hey. VM is pingable

[root@zabbixfml php-fpm.d]# ping 172.31.24.49
PING 172.31.24.49 (172.31.24.49) 56(84) bytes of data.
64 bytes from 172.31.24.49: icmp_seq=1 ttl=64 time=0.020 ms
64 bytes from 172.31.24.49: icmp_seq=2 ttl=64 time=0.040 ms
64 bytes from 172.31.24.49: icmp_seq=3 ttl=64 time=0.037 ms
64 bytes from 172.31.24.49: icmp_seq=4 ttl=64 time=0.029 ms

It's Apache (Httpd+Php Fpm). If the frontend works on port 80, should i be able to telnet 172.31.24.49 80?. Hmm....

[Trixter89]

bump please

[Atsushi]

If you can ping the host, is there a firewall function that restricts access on port number 80 on the network route? It could be firewalld on RHEL 8 or security groups on AWS.