Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-22252

Zabbix repo unavailable on the network for me

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Commercial support required
    • Icon: Trivial Trivial
    • None
    • None
    • Packages (C)
    • None
    • Linux, but does not matter, it seems to be a networking problem

      Dear Zabbix Team,

       

      I have some server instances on AWS, using Lightsail services. Zabbix repos are not available for a while on one of the servers, they used to work before.

      This seems to be a networking issue on your end, I have no firewall blocking traffic on my side, nor in the VPC. You can see traceroute is dying on us halfway.

      My src ip is: 18.184.191.113

      I tried to telnet to port 443 from the specified host and it does not work. Random host is working. I even inserted allow filter into the firewall to avoid possible blockage, but did not help. All these are working without problem from my other hosts.

      Somehow it seems there is filtering on your end.

      Please advise.

       

      Best

       

      Pal Vig

      -- 

      root@shs-eu-01:~# telnet repo.zabbix.com 443
      Trying 178.128.6.101...
      ^C
      root@shs-eu-01:~# route -n
      Kernel IP routing table
      Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
      0.0.0.0         172.26.0.1      0.0.0.0         UG    100    0        0 eth0
      172.26.0.0      0.0.0.0         255.255.240.0   U     0      0        0 eth0
      172.26.0.1      0.0.0.0         255.255.255.255 UH    100    0        0 eth0
      root@shs-eu-01:~# traceroute repo.zabbix.com
      traceroute to repo.zabbix.com (178.128.6.101), 30 hops max, 60 byte packets
       1  ec2-54-93-0-75.eu-central-1.compute.amazonaws.com (54.93.0.75)  4.611 ms ec2-99-150-19-93.eu-central-1.compute.amazonaws.com (99.150.19.93)  2.172 ms ec2-54-93-0-83.eu-central-1.compute.amazonaws.com (54.93.0.83)  8.462 ms
       2  240.0.88.15 (240.0.88.15)  0.677 ms 240.0.88.14 (240.0.88.14)  0.311 ms 240.0.88.12 (240.0.88.12)  0.414 ms
       3  240.0.88.31 (240.0.88.31)  0.426 ms 240.0.88.24 (240.0.88.24)  0.444 ms 240.0.88.25 (240.0.88.25)  0.452 ms
       4  240.0.88.31 (240.0.88.31)  0.503 ms 240.0.88.30 (240.0.88.30)  0.500 ms 240.0.88.31 (240.0.88.31)  0.496 ms
       5  242.1.84.241 (242.1.84.241)  6.848 ms 242.1.85.241 (242.1.85.241)  1.171 ms 242.1.84.97 (242.1.84.97)  0.544 ms
       6  100.95.20.140 (100.95.20.140)  1.747 ms 100.95.20.133 (100.95.20.133)  0.811 ms 100.95.4.140 (100.95.4.140)  0.994 ms
       7  100.100.2.8 (100.100.2.8)  0.840 ms 100.100.2.14 (100.100.2.14)  0.888 ms 100.100.4.124 (100.100.4.124)  1.368 ms
       8  ffm-b10-link.ip.twelve99.net (62.115.51.84)  3.980 ms ffm-b5-link.ip.twelve99.net (62.115.57.136)  1.222 ms ffm-b11-link.ip.twelve99.net (62.115.48.54)  1.553 ms
       9  ffm-bb2-link.ip.twelve99.net (62.115.121.6)  1.606 ms ffm-bb1-link.ip.twelve99.net (62.115.121.0)  1.724 ms ffm-bb2-link.ip.twelve99.net (62.115.142.4)  1.899 ms
      10  prs-bb2-link.ip.twelve99.net (62.115.122.138)  10.129 ms prs-bb1-link.ip.twelve99.net (62.115.123.13)  9.984 ms *
      11  ldn-bb4-link.ip.twelve99.net (62.115.133.238)  14.625 ms ldn-bb1-link.ip.twelve99.net (62.115.135.24)  18.300 ms *
      12  nyk-bb2-link.ip.twelve99.net (62.115.113.20)  86.786 ms nyk-bb1-link.ip.twelve99.net (62.115.112.244)  87.372 ms  86.989 ms
      13  sjo-b23-link.ip.twelve99.net (62.115.119.229)  157.665 ms  158.672 ms  158.400 ms
      14  saca-b1-link.ip.twelve99.net (62.115.138.103)  159.222 ms  159.116 ms  156.253 ms
      15  digitalocean-svc069868-ic355392.ip.twelve99-cust.net (62.115.191.29)  155.830 ms * *
      16  * * *
      17  * * *
      18  * * *
      19  * * *
      20  * * *
      21  * * *
      22  * * *
      23  * * *
      24  * * *
      25  * * *
      26  * * *
      27  * * *
      28  * * *
      29  * * *
      30  * * *
      root@shs-eu-01:~# ping hwsw.hu
      PING hwsw.hu (185.43.207.157) 56(84) bytes of data.
      64 bytes from 185.43.207.157 (185.43.207.157): icmp_seq=1 ttl=47 time=17.9 ms
      64 bytes from 185.43.207.157 (185.43.207.157): icmp_seq=2 ttl=47 time=16.4 ms
      ^C
      — hwsw.hu ping statistics —
      2 packets transmitted, 2 received, 0% packet loss, time 1001ms
      rtt min/avg/max/mdev = 16.405/17.190/17.976/0.796 ms
      root@shs-eu-01:~# iptables -I INPUT -d 178.128.6.101 -j ACCEPT
      root@shs-eu-01:~# telnet repo.zabbix.com 443
      Trying 178.128.6.101...
      ^C

       

      OTHER MACHINE, WORKS OUT OF THE BOX

      root@shs-eu-02:~# telnet repo.zabbix.com 443
      Trying 2604:a880:2:d0::2062:d001...
      Connected to repo.zabbix.com.
      Escape character is '^]'.
      ^]
      telnet> quit
      Connection closed.
      root@shs-eu-02:~# telnet -4 repo.zabbix.com 443
      Trying 178.128.6.101...
      Connected to repo.zabbix.com.
      Escape character is '^]'.
      ^]
      telnet> quit
      Connection closed.

            zabbix.support Zabbix Support Team
            overlordhu Vig Pal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: