Originally posted by wiedehopf
View Post
Announcement
Collapse
No announcement yet.
FR24 server disconnected , could not connect
Collapse
X
-
Hi,
I have the same issue (in France).
Would be interesting to share our ISPs to understand if there is an issue with one of them there.
My ISP is Orange.
Thanks
Leave a comment:
-
Ah that makes tracerouting easier:
Pilax and anyone having the problem, use the following command for a trace:
Code:traceroute 185.218.24.23 -T -p 8099
This might help to narrow down where exactly the problem is.
This information could in turn be be forwarded by FR24 to their hosting provider.
Or the users with the problem might be able to contact their ISP with the the trace command and output.
I'm in Germany, somewhere between EDDF and EDDN, and it works fine for me, i'm just trying to help narrow down the source of the problem.
traceroute described above for me looks like this
Code:7 kbn-bb3-link.telia.net (213.155.130.101) 26.903 ms 25.996 ms 26.128 ms 8 kbn-b3-link.telia.net (213.155.135.179) 26.545 ms kbn-b3-link.telia.net (62.115.121.17) 27.198 ms kbn-b3-link.telia.net (80.91.252.23) 27.008 ms 9 iponly-ic-319310-kbn-b3.c.telia.net (62.115.151.47) 27.927 ms 27.688 ms 28.934 ms 10 * * * 11 185.218.24.1 (185.218.24.1) 39.654 ms 34.206 ms 34.745 ms 12 185.218.24.23 (185.218.24.23) 35.000 ms 38.599 ms 38.700 ms
Last edited by wiedehopf; 2019-02-14, 11:11.
Leave a comment:
-
I couldn't easily find a german based server to test from online, But a
telnet 185.218.24.22 8099
(or 185.218.24.23) should also produce a bit of garbage onscreen meaning successful connection to server.
Anything else is a timeout/unable to connect
Leave a comment:
-
Doesn't necessarily mean it's bad, it seems popular to block any attempt to debug network connections in some places.
For me it goes via Telia and then it vanishes (but the feed is working for me):
Code:4 ffm-b4-link.telia.net (213.248.93.186) 15.417 ms 15.462 ms 15.710 ms 5 ffm-bb4-link.telia.net (62.115.120.7) 16.033 ms ffm-bb3-link.telia.net (62.115.120.1) 16.321 ms ffm-bb4-link.telia.net (62.115.120.7) 16.568 ms 6 hbg-bb4-link.telia.net (62.115.138.173) 26.888 ms hbg-bb1-link.telia.net (62.115.123.77) 18.489 ms 19.755 ms 7 kbn-bb3-link.telia.net (213.155.130.101) 25.803 ms kbn-bb4-link.telia.net (213.155.135.121) 25.518 ms kbn-bb3-link.telia.net (213.155.130.101) 25.755 ms 8 kbn-b3-link.telia.net (213.155.135.179) 35.211 ms kbn-b3-link.telia.net (62.115.121.15) 32.134 ms 32.650 ms 9 iponly-ic-319310-kbn-b3.c.telia.net (62.115.151.47) 32.905 ms 33.671 ms 33.564 ms 10 * * * [.....]
Anyway such problems in my experience are normally fixed after a couple of days.
Let's just hope this is the case here.
(If they wouldn't block any attempt at tracerouting, one could at least confirm the most likely problematic hop, but like this it is hard to see anything useful)
You can try adding --icmp or -T to the traceroute command, maybe that is less blocked along your route.Last edited by wiedehopf; 2019-02-14, 09:42.
Leave a comment:
-
not good it seems...
traceroute -n 185.218.24.22 -m20
traceroute to 185.218.24.22 (185.218.24.22), 20 hops max, 60 byte packets
1 192.168.1.1 1.741 ms 3.401 ms 8.345 ms
2 80.10.237.125 7.171 ms 8.581 ms 8.753 ms
3 193.253.92.162 8.808 ms 10.227 ms 10.397 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
Leave a comment:
-
Originally posted by pilax View PostIs there a way to change server IP ?
How do you contact support ?
Leave a comment:
-
If it is a routing problem what i kinda suspect, there isn't much you can do but wait for the ISPs to figure it out.
Their actual feed servers (not feed.flightradar24.com) don't respond to ping so you can't even properly check if the connection to them is the problem.
Anyway the output of the following command might be interesting:
traceroute 185.218.24.22 -m20
(And if multiple people with the problem maybe a common pattern can be identified)
Leave a comment:
-
yes thanks I try that two, I try also to disable IPv6 even my conf does not change...
I don't know what to check now...
Leave a comment:
-
i don't think you can.
have you tried adding this:
Code:use-http=yes http-timeout=20
probably the cases it solved were a different problem from the current one.
Leave a comment:
Leave a comment: