sojo
August 16, 2021, 2:58am
1
One of My server cannot connect to apps.nextcloud.com
NC (snap)19.0.4
Ubuntu 18.04
It cannot ping to apps.nextcloud.com
and this is traceroute results
traceroute to apps.nextcloud.com (176.9.217.53), 30 hops max, 60 byte packets
9 122.155.226.41 (122.155.226.41) 1.436 ms 5.271 ms 5.353 ms
10 61.19.9.226 (61.19.9.226) 178.413 ms 178.483 ms 61.19.9.221 (61.19.9.221) 187.267 ms
11 195.66.227.209 (195.66.227.209) 183.706 ms 182.847 ms 182.573 ms
12 core6.par.hetzner.com (213.239.252.169) 184.718 ms 195.66.227.209 (195.66.227.209) 231.216 ms 185.477 ms
13 core6.par.hetzner.com (213.239.252.169) 185.396 ms 185.441 ms 185.411 ms
14 core11.nbg1.hetzner.com (213.239.252.173) 210.436 ms core12.nbg1.hetzner.com (213.239.252.253) 204.854 ms core11.nbg1.hetzner.com (213.239.252.173) 210.273 ms
15 core24.fsn1.hetzner.com (213.239.245.30) 207.704 ms core23.fsn1.hetzner.com (213.239.245.226) 219.882 ms ex9k2.dc13.fsn1.hetzner.com (213.239.224.2) 220.637 ms
16 s2.nextcloud.com (88.198.19.60) 206.217 ms ex9k2.dc13.fsn1.hetzner.com (213.239.224.6) 231.741 ms 219.608 ms
17 s2.nextcloud.com (88.198.19.60) 208.408 ms 208.463 ms 209.306 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Another server can ping and traceroute.
Is it possible to be blocked form apps.nextcloud.com ?
tflidd
August 16, 2021, 9:19am
2
4 ex9k2.dc13.fsn1.hetzner.com (213.239.224.2) 1.399 ms 1.395 ms 1.390 ms
5 s2.nextcloud.com (88.198.19.60) 0.297 ms 0.288 ms 0.421 ms
6 apps.nextcloud.com (176.9.217.53) 0.516 ms 0.346 ms 0.334 ms
I can tracert through all hosts. Perhaps it was down for maintenance? Can you open in your browser?
sojo
August 16, 2021, 3:35pm
3
I have 2 servers but 1 can not reach apps.nextcloud.com
Server 1
12 core6.par.hetzner.com (213.239.252.169) 183.186 ms 182.462 ms 182.912 ms
13 core6.par.hetzner.com (213.239.252.169) 185.334 ms core11.nbg1.hetzner.com (213.239.252.173) 203.814 ms core6.par.hetzner.com (213.239.252.169) 185.297 ms
14 core11.nbg1.hetzner.com (213.239.252.173) 207.730 ms * 207.588 ms
15 * ex9k2.dc13.fsn1.hetzner.com (213.239.224.2) 205.502 ms 209.582 ms
16 ex9k2.dc13.fsn1.hetzner.com (213.239.224.2) 209.249 ms ex9k2.dc13.fsn1.hetzner.com (213.239.224.6) 219.429 ms s2.nextcloud.com (88.198.19.60) 205.399 ms
17 s2.nextcloud.com (88.198.19.60) 208.590 ms * *
18 * * *
19 * * *
20 * * *
Server2
12 core6.par.hetzner.com (213.239.252.169) 195.350 ms 195.66.227.209 (195.66.227.209) 188.916 ms 191.196 ms
13 core6.par.hetzner.com (213.239.252.169) 194.627 ms 194.010 ms 194.049 ms
14 core12.nbg1.hetzner.com (213.239.252.253) 207.326 ms 206.648 ms core24.fsn1.hetzner.com (213.239.203.126) 217.298 ms
15 * core23.fsn1.hetzner.com (213.239.245.226) 199.844 ms ex9k2.dc13.fsn1.hetzner.com (213.239.224.6) 206.130 ms
16 s2.nextcloud.com (88.198.19.60) 216.307 ms ex9k2.dc13.fsn1.hetzner.com (213.239.224.2) 221.793 ms 220.312 ms
17 s2.nextcloud.com (88.198.19.60) 219.145 ms 219.915 ms 219.848 ms
18 apps.nextcloud.com (176.9.217.53) 217.342 ms 218.205 ms 217.495 ms
2 server with different public IP prefix (/24)
server 1 YY.155.197.XX
server2 YY.155.196.XX
sojo
August 16, 2021, 3:38pm
5
Just 1 of my servers can’t reach.
Another server can ping and traceroute.
j-ed
August 16, 2021, 4:39pm
6
DNS answers are sometimes cached by a device. USe nslookup Use e.g. "nslookup " to check the resolved ip address and make sure that you clear any DNS cache and try again.
sojo
August 17, 2021, 2:10am
7
DSN answer correct IP (176.9.217.53)
But traceroute stuck at s2.nextcloud.com
traceroute to apps.nextcloud.com (176.9.217.53), 30 hops max, 60 byte packets
16 s2.nextcloud.com (88.198.19.60) 206.216 ms ex9k2.dc13.fsn1.hetzner.com (213.239.224.6) 219.830 ms 219.732 ms
17 * s2.nextcloud.com (88.198.19.60) 208.145 ms 208.867 ms
18 * * *
19 * * *
j-ed
August 17, 2021, 3:54pm
8
It might have been a temporary problem. I’ve just tested it and I was able to access the server without any problem:
...
8 s2.nextcloud.com (88.198.19.60) 18.089 ms 16.871 ms 14.170 ms
9 apps.nextcloud.com (176.9.217.53) 19.564 ms 20.409 ms 17.399 ms
BTW, your general latency seems to be extremely high (>200ms)?!