Can't reach store-repository.jolla.com and update my SailfishOS (Cloudflare issue)

asked 2019-07-20 05:37:40 +0300

Collider gravatar image

updated 2019-07-20 15:26:39 +0300

Hello. I have encountered some really weird network issue.

[root@Sailfish nemo]# ssu re 3.1.0.11 && version —dup
Changing release from 3.1.0.11 to 3.1.0.11
Your device is now in release mode!
[D] unknown:0 - "No carrier"
REFRESHING CACHE AND DOWNLOADING PACKAGES
Refreshing: 0%
Error: Timeout exceeded when accessing 'https://store-repository.jolla.com/rele
ases/3.1.0.11/jolla-hw/adaptation-qualcomm-p4903/armv7hl/repodata/repomd.xml?cr
edentials=store'.

I tried to ping it, but it didn't respond. Ok, I did traceroute.

[root@Sailfish nemo]# traceroute store-repository.jolla.com
traceroute to store-repository.jolla.com (34.240.77.117), 30 hops max, 38 byte
packets
1  *  *  *
2  10.3.245.81 (10.3.245.81)  49.088 ms  10.3.245.89 (10.3.245.89)  37.199 ms
10.3.245.81 (10.3.245.81)  42.289 ms
3  10.226.0.65 (10.226.0.65)  36.700 ms  10.226.9.33 (10.226.9.33)  45.788 ms
10.226.0.65 (10.226.0.65)  174.270 ms
4  10.226.9.46 (10.226.9.46)  41.155 ms  10.226.9.33 (10.226.9.33)  32.825 ms
10.226.9.46 (10.226.9.46)  47.263 ms
5  10.226.9.46 (10.226.9.46)  43.225 ms  10.226.5.90 (10.226.5.90)  44.672 ms
10.226.9.46 (10.226.9.46)  44.496 ms
6  217.169.83.2 (217.169.83.2)  41.875 ms  10.226.5.90 (10.226.5.90)  34.271 m
s  217.169.83.2 (217.169.83.2)  45.108 ms
7  217.169.83.2 (217.169.83.2)  36.690 ms  m9-r5.inet2.net (85.112.122.5)  75.
970 ms  217.169.83.2 (217.169.83.2)  39.247 ms
8  amsix01-ams1.amazon.com (80.249.210.100)  88.502 ms  m9-r5.inet2.net (85.11
2.122.5)  88.250 ms  decix.amazon.com (80.81.194.152)  85.130 ms
9  decix.amazon.com (80.81.194.152)  84.312 ms  54.239.107.232 (54.239.107.232
)  87.699 ms  decix.amazon.com (80.81.194.152)  76.143 ms
10  54.239.107.131 (54.239.107.131)  82.453 ms  54.239.107.226 (54.239.107.226)
88.978 ms  54.239.107.63 (54.239.107.63)  79.829 ms
11  54.239.107.23 (54.239.107.23)  106.591 ms  *  54.239.107.45 (54.239.107.45)
105.883 ms
12  52.93.128.2 (52.93.128.2)  115.897 ms  *  *
13  52.93.128.48 (52.93.128.48)  154.668 ms  *  176.32.106.248 (176.32.106.248)
110.692 ms
14  *  52.93.128.166 (52.93.128.166)  111.058 ms  *
15  *  52.93.6.160 (52.93.6.160)  145.440 ms  *
16  52.93.101.47 (52.93.101.47)  110.469 ms  52.93.6.144 (52.93.6.144)  116.277
ms  52.93.130.80 (52.93.130.80)  116.223 ms
17  52.93.101.27 (52.93.101.27)  116.363 ms  52.93.128.93 (52.93.128.93)  116.1
12 ms  52.93.101.49 (52.93.101.49)  116.325 ms
18  52.93.7.57 (52.93.7.57)  116.610 ms  52.93.101.46 (52.93.101.46)  119.340 m
s  52.93.7.73 (52.93.7.73)  116.266 ms
19  52.93.7.53 (52.93.7.53)  111.334 ms  *  54.239.47.4 (54.239.47.4)  110.428
ms
20  *  *  52.93.6.158 (52.93.6.158)  105.240 ms
21  52.93.6.180 (52.93.6.180)  116.045 ms  *  *
22  *  52.93.101.11 (52.93.101.11)  98.548 ms  *
23  52.93.101.54 (52.93.101.54)  111.398 ms  *  52.93.133.220 (52.93.133.220)
110.913 ms
24  *  *  *
25  *  *  *
26  *  *  *
27  *  *  *
28  *  *  *
29  *  *  *
30  *  *  *
[root@Sailfish nemo]#

Wow, it looks strange. However, I can open Jolla's site jolla.com in Browser. But! I can't ping jolla.com, and traceroute to jolla.com looks pretty strange too:

[root@Sailfish nemo]#  ping jolla.com
PING jolla.com (34.247.145.123): 56 data bytes
^C
—- jolla.com ping statistics —-
9 packets transmitted, 0 packets received, 100% packet loss
[root@Sailfish nemo]# traceroute jolla.com
traceroute to jolla.com (34.247.145.123), 30 hops max, 38 byte packets
1  *  *  *
2  10.3.245.89 (10.3.245.89)  45.804 ms  10.3.245.81 (10.3.245.81)  43.348 ms
10.3.245.89 (10.3.245.89)  35.938 ms
3  10.226.9.33 (10.226.9.33)  33.175 ms  10.226.0.65 (10.226.0.65)  39.256 ms
10.226.9.33 (10.226.9.33)  39.303 ms
4  10.226.9.33 (10.226.9.33)  38.559 ms  10.226.9.46 (10.226.9.46)  43.051 ms
10.226.9.33 (10.226.9.33)  33.430 ms
5  10.226.5.90 (10.226.5.90)  44.158 ms  10.226.9.46 (10.226.9.46)  39.027 ms
10.226.5.90 (10.226.5.90)  43.959 ms
6  10.226.5.90 (10.226.5.90)  39.236 ms  217.169.83.2 (217.169.83.2)  35.149 m
s  10.226.5.90 (10.226.5.90)  44.297 ms
7  m9-r5.inet2.net (85.112.122.5)  40.797 ms  217.169.83.2 (217.169.83.2)  39.
234 ms  m9-r5.inet2.net (85.112.122.5)  41.108 ms
8  m9-r5.inet2.net (85.112.122.5)  41.387 ms  decix.amazon.com (80.81.194.152)
83.451 ms  m9-r5.inet2.net (85.112.122.5)  46.443 ms
9  54.239.107.230 (54.239.107.230)  71.499 ms  decix.amazon.com (80.81.194.152
)  75.909 ms  52.93.0.150 (52.93.0.150)  86.660 ms
10  52.93.0.70 (52.93.0.70)  77.915 ms  54.239.107.153 (54.239.107.153)  79.488
ms  54.239.107.226 (54.239.107.226)  75.979 ms
11  *  54.239.107.109 (54.239.107.109)  113.300 ms  *
12  *  52.93.128.48 (52.93.128.48)  105.033 ms  *
13  54.239.42.175 (54.239.42.175)  111.921 ms  *  111.161 ms
14  54.239.41.124 (54.239.41.124)  119.572 ms  *  *
15  52.93.6.206 (52.93.6.206)  112.302 ms  *  52.93.6.236 (52.93.6.236)  110.75
9 ms
16  52.93.6.196 (52.93.6.196)  116.605 ms  52.93.101.33 (52.93.101.33)  119.904
ms  52.93.6.246 (52.93.6.246)  115.932 ms
17  52.93.101.58 (52.93.101.58)  116.176 ms  52.93.101.45 (52.93.101.45)  119.3
13 ms  52.93.101.42 (52.93.101.42)  116.100 ms
18  52.93.101.12 (52.93.101.12)  119.271 ms  52.93.7.151 (52.93.7.151)  119.056
ms  52.93.101.8 (52.93.101.8)  111.706 ms
19  *  52.93.7.153 (52.93.7.153)  111.186 ms  *
20  *  *  *
21  *  *  *
22  *  52.93.101.56 (52.93.101.56)  116.511 ms  *
23  *  *  52.93.7.139 (52.93.7.139)  104.569 ms
24  *  *  *
25  52.93.6.236 (52.93.6.236)  104.146 ms  *  *
26  *  *  *
27  *  *  *
28  *  *  *
29  *  *  *
30  *  *  *
[root@Sailfish nemo]# ping google.com
PING google.com (173.194.73.101): 56 data bytes
64 bytes from 173.194.73.101: seq=0 ttl=44 time=39.858 ms
64 bytes from 173.194.73.101: seq=1 ttl=44 time=35.028 ms
^C
—- google.com ping statistics —-
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 35.028/37.443/39.858 ms
[root@Sailfish nemo]#

I did all above over the mobile network, but I've tried it on my Wi-Fi, it's the same. How can I fix it or is it a Jolla issue?

edit retag flag offensive close delete

Comments

Have you tried again as noticed yesterday couldn't access server before 05.00GMT, as expect some down-time is scheduled for the early hours?

aspergerguy ( 2019-07-20 08:41:52 +0300 )edit

Yes, I tried to update several times for past half-year :)

And results for my home broadband connections are the same. I can't ping neither jolla.com nor store-repository.jolla.com, traceroute stuck somewhere in the jolla-amazon infrastructure. And I can open jolla.com in my web-browser. IMHO, it looks like there are some weird firewall rules applied on the Jolla's side.

Collider ( 2019-07-20 14:29:37 +0300 )edit

It looks it's Cloudflare issue:

[root@Sailfish nemo]#  curl -v http://releases.jolla.com
* Rebuilt URL to: http://releases.jolla.com/
*   Trying 52.16.118.154...
* TCP_NODELAY set
* Connected to releases.jolla.com (52.16.118.154) port 80 (#0)
> GET / HTTP/1.1
> Host: releases.jolla.com
> User-Agent: curl/7.61.1-DEV
> Accept: */*
>
< HTTP/1.1 302 Moved Temporarily
< Content-Type: text/html
< Date: Sat, 20 Jul 2019 12:12:36 GMT
< Location: https://dvvwui2qyedk6.cloudfront.net/
< Content-Length: 154
< Connection: keep-alive
<
<html>
<head><title>302 Found</title></head>
<body bgcolor="white">
<center><h1>302 Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
[root@Sailfish nemo]#  curl -vL http://releases.jolla.com
* Rebuilt URL to: http://releases.jolla.com/
*   Trying 34.250.22.92...
* TCP_NODELAY set
* Connected to releases.jolla.com (34.250.22.92) port 80 (#0)
> GET / HTTP/1.1
> Host: releases.jolla.com
> User-Agent: curl/7.61.1-DEV
> Accept: */*
>
< HTTP/1.1 302 Moved Temporarily
< Content-Type: text/html
< Date: Sat, 20 Jul 2019 12:14:53 GMT
< Location: https://dvvwui2qyedk6.cloudfront.net/
< Content-Length: 154
< Connection: keep-alive
<
* Ignoring the response-body
* Connection #0 to host releases.jolla.com left intact
* Issue another request to this URL: 'https://dvvwui2qyedk6.cloudfront.net/'
*   Trying 13.33.96.186...
* TCP_NODELAY set
* Connected to dvvwui2qyedk6.cloudfront.net (13.33.96.186) port 443 (#1)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* Operation timed out after 300295 milliseconds with 0 out of 0 bytes received
* Closing connection 1
curl: (28) Operation timed out after 300295 milliseconds with 0 out of 0 bytes
received
Collider ( 2019-07-20 15:24:40 +0300 )edit

You have in the log:

Your device is now in release mode!
[D] unknown:0 - "No carrier"

Turn on WLAN and try again. There is a bug such that WLAN must be enabled even if you used mobile data for the actual connection.

Furthermore, we warmly recommend using the UI for getting updates - the command line way does not have all the necessary checks.

jovirkku ( 2019-07-23 16:45:06 +0300 )edit

@jovirkku I turned on WLAN and "No carrier" have disappeared, but anyway I can't connect to https://dvvwui2qyedk6.cloudfront.net/. It looks like that Cloudflare have banned a wide range of IP-addresses of Tele2 Saint-Petersburg.

Yeah, I'd like to use UI too, but I can't. When I tap to "SailfishOS updates", everything I see is "Can't open the page".

Collider ( 2019-07-24 14:48:10 +0300 )edit