Open `serverinfo` tab provokes ip ban by apps.nextcloud.com

The appstore seams to be down since ± 5:30

Is it because of maintenance or disruption?

ernolf

Hey, working fine here?

No issues here, the Appstore is working fine for me.

ping ok:

root@optiplex:~# ping -c 3 apps.nextcloud.com
PING apps.nextcloud.com (176.9.217.53) 56(84) bytes of data.
64 bytes from apps.nextcloud.com (176.9.217.53): icmp_seq=1 ttl=57 time=12.5 ms
64 bytes from apps.nextcloud.com (176.9.217.53): icmp_seq=2 ttl=57 time=11.2 ms
64 bytes from apps.nextcloud.com (176.9.217.53): icmp_seq=3 ttl=57 time=11.0 ms

--- apps.nextcloud.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 10.983/11.567/12.499/0.665 ms

traceroute ok:

root@optiplex:~# traceroute --resolve-hostnames apps.nextcloud.com
traceroute to apps.nextcloud.com (176.9.217.53), 64 hops max
  1   192.168.188.1 (fritzbox-7580.fritz.box)  0,947ms  0,602ms  0,516ms
  2   62.155.246.85 (p3e9bf655.dip0.t-ipconnect.de)  3,533ms  1,783ms  1,520ms
  3   217.5.75.90 (n-ea9-i.N.DE.NET.DTAG.DE)  8,999ms  7,696ms  7,580ms
  4   62.157.248.138 (62.157.248.138)  9,190ms  7,674ms  7,548ms
  5   213.239.252.250 (core24.fsn1.hetzner.com)  10,631ms  25,279ms  11,903ms
  6   213.239.224.6 (ex9k2.dc13.fsn1.hetzner.com)  11,363ms  9,989ms  9,959ms
  7   88.198.19.60 (s2.nextcloud.com)  10,633ms  9,051ms  9,059ms
  8   176.9.217.53 (apps.nextcloud.com)  11,443ms  9,822ms  9,709ms

http(s) respone not ok:

root@optiplex:~# curl -L apps.nextcloud.com
curl: (7) Failed to connect to apps.nextcloud.com port 80 after 16 ms: Connection refused
root@optiplex:~# curl -L https://apps.nextcloud.com
curl: (7) Failed to connect to apps.nextcloud.com port 443 after 16 ms: Connection refused

Looks like webserver is down.

Or is my IP been blocked maybe?


EDIT: It was my IP that obviously has been blocked :woozy_face:

I’ll mark this as solved. Sorry for the confusion

I got to the bottom of the matter and it looks like the ApstoreFetcher, as called by serverinfo, is the cause of the problem.

I opened an issue: