Bottles icon indicating copy to clipboard operation
Bottles copied to clipboard

[Bug]: Bottles fails to detect an internet connection

Open LiberalArtist opened this issue 1 year ago • 4 comments

Describe the bug

Bottles says "You don't seem to be connected to the internet", but there is an internet connection.

To Reproduce

  1. Start Bottles.
  2. Hover over the internet connection icon.
  3. See this message: Screenshot of internet connection error message.
  4. Click the icon (nothing happens).
  5. Attempt to create a bottle.
  6. Get stuck with this dialog (for up to an hour): Screenshot of "Creating a Bottle" dialog.

Package

Flatpak from Flathub

Distribution

Kubuntu 22.04

Troubleshooting Logs

Version: 2022.8.28-brescia-2
Display:
    X.org: true
    X.org (port): :99.0
    Wayland: true
Graphics:
    vendors:
        nvidia: &id002
            vendor: nvidia
            envs:
                __NV_PRIME_RENDER_OFFLOAD: '1'
                __GLX_VENDOR_LIBRARY_NAME: nvidia
                __VK_LAYER_NV_optimus: NVIDIA_only
            icd: ''
        intel: &id001
            vendor: intel
            envs:
                DRI_PRIME: '1'
            icd: /usr/lib/x86_64-linux-gnu/GL/vulkan/icd.d/intel_icd.x86_64.json:/usr/lib/i386-linux-gnu/GL/vulkan/icd.d/intel_icd.i686.json
    prime:
        integrated: *id001
        discrete: *id002
Kernel:
    Type: Linux
    Version: 5.15.0-47-generic
Distro:
    Name: GNOME
    Version: '"42 (Flatpak runtime)"'
Disk:
    Total: 16687243264
    Free: 16687091712
RAM:
    MemTotal: 31.1GiB
    MemAvailable: 11.2GiB
Bottles_envs: null

Display Protocol

Wayland

Display Backend used by Bottles

Wayland

Additional context

I have tried disconnecting and reconnecting from WiFi, but it hasn't worked. I have confirmed that the Flatpak permissions should allow network access. This is a fresh installation with no existing bottles. (I have never used Bottles before, so sorry if I'm missing something really basic!)

The problem happens regardless of whether I start Bottles from the desktop launcher or the command line. Here is some logging:

philip@bastet:~$ flatpak run com.usebottles.bottles --version
2022.8.28-brescia-2
philip@bastet:~$ flatpak run com.usebottles.bottles
23:39:18 (WARNING) Connection status: offline … 
23:39:18 (INFO) Bottles Started! 
23:39:18 (WARNING) Connection status: offline … 
23:39:19 (ERROR) Could not get index for components repository 
23:39:20 (ERROR) Could not get index for dependencies repository 
23:39:20 (ERROR) Could not get index for installers repository 
23:39:20 (INFO) Performing Bottles checks… 
23:39:20 (INFO) Runners found:
         - sys-wine-7.0
 
23:39:21 (WARNING) Connection status: offline … 
23:39:21 (INFO) No components found. 
23:39:21 (WARNING) Connection status: offline … 
23:39:21 (INFO) No dependencies found! 
23:39:22 (WARNING) Connection status: offline … 
23:39:22 (INFO) No installers found! 
23:39:22 (INFO) Library saved 
23:39:28 (INFO) Performing Bottles checks… 
23:39:28 (WARNING) No dxvk found. 
23:39:29 (WARNING) Connection status: offline … 
23:39:29 (WARNING) No vkd3d found. 
23:39:29 (WARNING) Connection status: offline … 
23:39:29 (WARNING) No nvapi found. 
23:39:29 (WARNING) Connection status: offline … 
23:39:30 (WARNING) No latencyflex found. 
23:39:30 (WARNING) Connection status: offline … 
23:39:30 (WARNING) Connection status: offline … 
23:39:30 (INFO) Runners found:
         - sys-wine-7.0
 
23:39:30 (WARNING) No runners found. 
23:39:31 (WARNING) Connection status: offline … 
23:39:31 (INFO) No components found. 
23:39:31 (INFO) No dependencies found! 
23:39:31 (INFO) No installers found! 
23:43:54 (WARNING) Connection status: offline … 
Traceback (most recent call last):
  File "/app/share/bottles/bottles/frontend/views/new.py", line 204, in create_bottle
    dxvk=self.manager.dxvk_available[0],
IndexError: list index out of range

LiberalArtist avatar Sep 13 '22 03:09 LiberalArtist

Bottles pings https://repo.usebottles.com to check the connection. It’s the equivalent of: ping repo.usebottles.com.

Are you able to ping it? If yes, there is probably some system related problems.

mirkobrombin avatar Sep 13 '22 05:09 mirkobrombin

Thanks! Trying ping repo.usebottles.com works fine for me outside of the Flatpak sandbox, as does just navigating to that page in my browser (the Firefox Flatpak, in fact, which I'm also using to write this). I don't know how to do a similar check within the Flatpak environment for Bottles.

One thing I noticed is that, in the first screenshot above, both the "Library" tab and the internet connection button are using the same somewhat-blurry caution icon. Is that expected?

I'm sort of at a loss for what might be going wrong ...

LiberalArtist avatar Sep 14 '22 04:09 LiberalArtist

One thing I noticed is that, in the first screenshot above, both the "Library" tab and the internet connection button are using the same somewhat-blurry caution icon. Is that expected?

No, your system/theme/desktop doesn't provide that common named icons.

Thanks! Trying ping repo.usebottles.com works fine for me outside of the Flatpak sandbox, as does just navigating to that page in my browser (the Firefox Flatpak, in fact, which I'm also using to write this). I don't know how to do a similar check within the Flatpak environment for Bottles.

We just download a few Kb from the repo. Is the Steam Manager option enable?

mirkobrombin avatar Sep 14 '22 16:09 mirkobrombin

I tried using Bottles from Nix instead of the Flatpak, and it seems to be working fine! It has successfully connected to the internet and created a new bottle, at least. Using Nix got me version 2022.5.28-trento-3, but when I tried using that version with Flatpak (via sudo flatpak update --commit=5884f32e357cc145e259c9b7713152aaff3b31abf6983a95ebf65a9a228dcb83 com.usebottles.bottles), it still couldn't connect to the internet.

So the problem seems to be something about the Flatpak sandboxing. AFAICT I'm using entirely the default configuration, though, so I don't know what could be going wrong. (I don't have the Steam Manager option enabled.)

LiberalArtist avatar Sep 16 '22 03:09 LiberalArtist

I have similar problem and I tried a few things to understand why it's happening like this. I don't know if my findings will be helpful, but here they are:

  • Bottles was working in the past, unfortunately I don't know when it was because I wasn't using it for some time (few months?)
  • in general Bottles is stuck on "Starting up..." screen for several minutes, sometimes it shows that 1,2 or 3 packages has been fetched and after getting to the "main screen" it shows the icon with "You don't seem connected to the internet..." (on some rare occasions after clicking the icon it reconnects and I can download runners in preferences etc.). FORCE_OFFLINE=1 doesn't speed things up but shows the connection icon immediately
  • Bottles has permissions to network flatpak info --show-permissions com.usebottles.bottles:
...
[Context]
shared=network;ipc;
...
  • non flatpak AUR versions can't find connection too
  • I thought that maybe it's my Arch system configuration and tried installing Bottles flatpak on Ubuntu 22.04.01 LTS, Fedora 37 Beta and Debian 11.5 live disks and on all of them I can freely ping and access https://repo.usebottles.com/ by terminal and browser, but Bottles can't
  • I've tried another flatpak "XIVauncher" to see if it's only Bottles not working and it also couldn't connect to download files required by it's game. However lutris version ("native" wine version) connected and downloaded files just fine
  • I looked at connection.py and saw that line urllib.request.urlopen('https://repo.usebottles.com/components/index.yml', timeout=5) and tried to run this line in native Python and it was returning status 200 OK every time I was running it
import urllib.request  
test = urllib.request.urlopen('https://repo.usebottles.com/components/index.yml', timeout=5)  
print(vars(test))
  • after all of this I tried changing my internet connection by using smartphone hotspot (mobile internet) and it worked - Bottles could connect and download runners almost instantaneously. By using ping I noticed that mobile internet was working on IPv6 and my home internet on IPv4

I don't know what to think about this. It looks like the problem lies in my internet connection, but I can connect to the repo by browser/terminal and download files manually. Maybe something is going on with general flatpak networking configuration/something and IPv6 or IPv4, but that doesn't fully explain why native AUR Bottles doesn't work too.

EDIT: I forgot to mention that I tried changing DNS to 1.1.1.1 or 8.8.8.8 and it did nothing.

pszabunko avatar Sep 24 '22 20:09 pszabunko

I don't think this is IPv6 related. For testing purposes I've disabled AAAA lookups on my local DNS server and I'm still having this issue. I've also tested inside flatpak using curl https://repo.usebottles.com/components/index.yml, the issue occurs randomly after few calls

[📦 com.usebottles.bottles ~]$ curl -v https://repo.usebottles.com/components/index.yml
* STATE: INIT => CONNECT handle 0x5635852e5080; line 1837 (connection #-5000)
* Added connection 0. The cache now contains 1 members
* STATE: CONNECT => RESOLVING handle 0x5635852e5080; line 1883 (connection #0)
* family0 == v4, family1 == v6
*   Trying 194.233.171.195:443...
* STATE: RESOLVING => CONNECTING handle 0x5635852e5080; line 1967 (connection #0)
* connect to 194.233.171.195 port 443 failed: Connection timed out
* Failed to connect to repo.usebottles.com port 443 after 130935 ms: Connection timed out
* multi_done: status: 28 prem: 1 done: 0
* The cache now contains 0 members
* Closing connection 0
curl: (28) Failed to connect to repo.usebottles.com port 443 after 130935 ms: Connection timed out

pgrondek avatar Sep 27 '22 22:09 pgrondek

@pgrondek Who is your ISP? Is it UPC by any chance? Have you tried connecting by mobile internet/different ISP?

pszabunko avatar Sep 28 '22 11:09 pszabunko

@pgrondek Who is your ISP? Is it UPC by any chance? Have you tried connecting by mobile internet/different ISP?

Yes, I have UPC. I've tried VPN (my mobile is in same ISP - play) and it looks like issue does not occur.

pgrondek avatar Sep 29 '22 10:09 pgrondek

Have the same issue, also only the UPC. Any solution for that? Anyone know what is causing the issue?

pbogut avatar Sep 30 '22 20:09 pbogut

Same issue here. I have UPC too. This is from my host:

[jpadilla@fractal-local ~]$ curl -v https://repo.usebottles.com/components/index.yml
*   Trying 194.233.171.195:443...
*   Trying 2a01:7e01::f03c:93ff:fe08:d86f:443...
* Immediate connect fail for 2a01:7e01::f03c:93ff:fe08:d86f: Network is unreachable
^C
[jpadilla@fractal-local ~]$ curl -v https://repo.usebottles.com/components/index.yml
*   Trying 194.233.171.195:443...
*   Trying 2a01:7e01::f03c:93ff:fe08:d86f:443...
* Immediate connect fail for 2a01:7e01::f03c:93ff:fe08:d86f: Network is unreachable
^C
[jpadilla@fractal-local ~]$ curl -v https://repo.usebottles.com/components/index.yml
*   Trying 194.233.171.195:443...
* Connected to repo.usebottles.com (194.233.171.195) port 443 (#0)
[jpadilla@fractal-local ~]$ curl -v https://repo.usebottles.com/components/index.yml
*   Trying 194.233.171.195:443...
*   Trying 2a01:7e01::f03c:93ff:fe08:d86f:443...
* Immediate connect fail for 2a01:7e01::f03c:93ff:fe08:d86f: Network is unreachable

UPDATE: It works when using a VPN with a different provider. So definitely it looks like a problem with UPC.

d3ce1t avatar Oct 05 '22 21:10 d3ce1t

FWIW, I do not have UPC. (I'm in North America.)

LiberalArtist avatar Oct 05 '22 23:10 LiberalArtist

Anyway, I think a workaround could be to just retry after a few seconds. With curl, this works for me most of the time:

curl --retry 3 --connect-timeout 3 -v https://repo.usebottles.com/components/index.yml

d3ce1t avatar Oct 06 '22 00:10 d3ce1t

Anyway, I think a workaround could be to just retry after a few seconds. With curl, this works for me most of the time:

curl --retry 3 --connect-timeout 3 -v https://repo.usebottles.com/components/index.yml

I'll check this

mirkobrombin avatar Oct 06 '22 12:10 mirkobrombin

Hello, I have the identical problem (ISP:UPC), except that I can go and browse https://repo.usebottles.com/ with no problem, curl --retry 3 --connect-timeout 3 -v https://repo.usebottles.com/components/index.yml also working, but at all I can't ping repo.usebottles.com. Bottles starts up dramatically slow and there is no indication of a problem.

My DNS resolves the address correctly as 194.233.171.195. I checked with vpn and everything works. I asked my friend who has also uses UPC and he can ping repo address, wireshark indicates that there is no response to the ping as if it is cut out on the server side. My router is configured corectly. Can You as admin of server where is hosted that domain check if is no block list for certain IP?

(deck@steamdeck ~)$ flatpak run com.usebottles.bottles 13:55:50 (WARNING) Connection status: offline … 13:55:50 (INFO) Bottles Started!

(bottles:2): Gtk-CRITICAL **: 13:55:50.562: Unable to register the application: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying ^C (130)(deck@steamdeck ~)$

Sidroff avatar Oct 08 '22 11:10 Sidroff

I'll add some debug logs

mirkobrombin avatar Oct 08 '22 14:10 mirkobrombin

I'll add some debug logs

Thanks for trying to resolve my problem.

I added IPv6 config to my network and now it's works but only when I use adresses from IPv6

PS C:\Users\Sidroff> ping repo.usebottles.com -t Pinging repo.usebottles.com [2a01:7e01::f03c:93ff:fe08:d86f] with 32 bytes of data: Reply from 2a01:7e01::f03c:93ff:fe08:d86f: time=37ms Reply from 2a01:7e01::f03c:93ff:fe08:d86f: time=37ms Reply from 2a01:7e01::f03c:93ff:fe08:d86f: time=35ms Reply from 2a01:7e01::f03c:93ff:fe08:d86f: time=35ms Ping statistics for 2a01:7e01::f03c:93ff:fe08:d86f: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 35ms, Maximum = 37ms, Average = 36ms Control-C

PS C:\Users\Sidroff> ping -4 repo.usebottles.com -t Pinging repo.usebottles.com [194.233.171.195] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Ping statistics for 194.233.171.195: Packets: Sent = 3, Received = 0, Lost = 3 (100% loss), Control-C

PS C:\Users\Sidroff> ping -4 github.com -t Pinging github.com [140.82.121.4] with 32 bytes of data: Reply from 140.82.121.4: bytes=32 time=28ms TTL=54 Reply from 140.82.121.4: bytes=32 time=29ms TTL=54 Reply from 140.82.121.4: bytes=32 time=30ms TTL=54 Reply from 140.82.121.4: bytes=32 time=31ms TTL=54 Reply from 140.82.121.4: bytes=32 time=27ms TTL=54 Ping statistics for 140.82.121.4: Packets: Sent = 5, Received = 5, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 27ms, Maximum = 31ms, Average = 29ms Control-C

Trafic from my router: SWITCH ipv6-icmp 2001:470:6010:7dfd:9b5f:c1b6:8a74:5494[1] -> 2a01:7e01::f03c:93ff:fe08:d86f[1] NO_TRAFFIC:NO_TRAFFIC 27 / 27 2 KiB / 2 KiB WANV6 ipv6-icmp 2001:470:6010:7dfd:9b5f:c1b6:8a74:5494[1] -> 2a01:7e01::f03c:93ff:fe08:d86f[1] NO_TRAFFIC:NO_TRAFFIC 27 / 27 2 KiB / 2 KiB

Here is how it looks on router side, packet on IPv4 don't return to me, so in my problem bottles have same isues to recive proper handshake from server repo

Sidroff avatar Oct 09 '22 09:10 Sidroff

@francescomasala any thoughts?

mirkobrombin avatar Oct 09 '22 10:10 mirkobrombin

@francescomasala any thoughts?

I am checking the infra, I will send an update as soon as I have news

francescomasala avatar Oct 09 '22 10:10 francescomasala

It should all be fixed, @sidroff check it out if you can

francescomasala avatar Oct 09 '22 10:10 francescomasala

@francescomasala > It should all be fixed, @Sidroff check it out if you can

nope, disabled ipv6 and connecting with ipv4 nothing new same for icmp 194.233.171.195, Request timed out Screenshot_20221009_124638

Sidroff avatar Oct 09 '22 10:10 Sidroff

@francescomasala > It should all be fixed, @Sidroff check it out if you can

nope, disabled ipv6 and connecting with ipv4 nothing new same for icmp 194.233.171.195, Request timed out Screenshot_20221009_124638

I've updated caddy and fixed IPv6 stuff image Tell me if now is working

francescomasala avatar Oct 09 '22 11:10 francescomasala

@francescomasala > 3 Tell me if now is working

This time it looks like something has changed, on terminal I run debug and got random messages like connection staus: offline (not on startup where i got it in previous states), and two line: No dependencies found! No installers found!

On icmp I have no answer, DMZ for device from 194.233.171.195, its stops little longer on Fetched 2/3 or 3/3 Downloading ~20kb of packages...

A few second ago it started up (~2 min loading), almost as it should and I can see the dependencies and installers, in the terminal I do not get any connection error

And i have one error what i cant rid of @mirkobrombin, its hould be there? Gtk-CRITICAL crit

Sidroff avatar Oct 09 '22 11:10 Sidroff

And now i get new error "Could not get index for components repository"

Sidroff avatar Oct 09 '22 11:10 Sidroff

I checked again only ipv6, and there is no problem here, fast startup and no connection errors *only Gtk-Critical left. IPv4 alone still nothing, I changed the dns to these 8.8.4.4, 1.1.1.1, 9.9.9.9 for sure.

It seems that the problem lies with the "partial"? blocking of my public IPs 31.178.36.87

Sidroff avatar Oct 09 '22 12:10 Sidroff

I tried connecting/testing the various web servers from different Tier 1 ISPs but did not encounter any problems, and I can see your connections from netstat being made successfully

francescomasala avatar Oct 09 '22 12:10 francescomasala

Try to connect from a different network

francescomasala avatar Oct 09 '22 12:10 francescomasala

@francescomasala 👍 Thank you for your input, it remains for me to connect via ipv6 or vpn or also mobile data LTE for now (form this device) all mentioned works for me, only UPC ipv4 has a problem for now

Sidroff avatar Oct 09 '22 12:10 Sidroff

For me (using UPC ISP), ping was never a problem:

[jpadilla@fractal-local ~]$ ping -4 repo.usebottles.com
PING repo.usebottles.com (194.233.171.195) 56(84) bytes of data.
64 bytes from Bottles-Web-FRA-0.usebottles.com (194.233.171.195): icmp_seq=1 ttl=50 time=25.6 ms
64 bytes from Bottles-Web-FRA-0.usebottles.com (194.233.171.195): icmp_seq=2 ttl=50 time=28.9 ms
64 bytes from Bottles-Web-FRA-0.usebottles.com (194.233.171.195): icmp_seq=3 ttl=50 time=26.8 ms
64 bytes from Bottles-Web-FRA-0.usebottles.com (194.233.171.195): icmp_seq=4 ttl=50 time=26.1 ms
64 bytes from Bottles-Web-FRA-0.usebottles.com (194.233.171.195): icmp_seq=5 ttl=50 time=25.5 ms

When using traceroute with ICMP ECHOs I get consistently the same route every time:

[jpadilla@fractal-local ~]$ traceroute -4 -I repo.usebottles.com
traceroute to repo.usebottles.com (194.233.171.195), 30 hops max, 60 byte packets
 1  * * *
 2  10.209.128.1 (10.209.128.1)  5.892 ms  10.190 ms  10.107 ms
 3  89-75-12-193.infra.chello.pl (89.75.12.193)  11.060 ms  11.127 ms  11.191 ms
 4  pl-waw26b-rc1-ae-8-2150.aorta.net (84.116.252.201)  11.277 ms  11.353 ms  11.411 ms
 5  pl-waw26b-ri1-ae-24-0.aorta.net (84.116.138.73)  10.165 ms  10.225 ms  10.294 ms
 6  ae-13.r01.wrswpl01.pl.bb.gin.ntt.net (129.250.9.109)  11.456 ms  8.863 ms  8.926 ms
 7  ae-22.r20.frnkge13.de.bb.gin.ntt.net (129.250.5.18)  27.619 ms  27.612 ms  27.563 ms
 8  ae-0.a03.frnkge07.de.bb.gin.ntt.net (129.250.7.16)  33.518 ms  32.765 ms  32.717 ms
 9  ae-0.akamai.frnkge07.de.bb.gin.ntt.net (168.143.105.105)  33.389 ms  33.371 ms  33.317 ms
10  a23-210-54-17.deploy.static.akamaitechnologies.com (23.210.54.17)  30.255 ms  30.197 ms  31.156 ms
11  * * *
12  * * *
13  * * *
14  Bottles-Web-FRA-0.usebottles.com (194.233.171.195)  27.222 ms * *

However, when using TCP the route is slightly different after 6th hop:

[jpadilla@fractal-local ~]$ sudo traceroute -4 -T repo.usebottles.com
traceroute to repo.usebottles.com (194.233.171.195), 30 hops max, 60 byte packets
 1  * * *
 2  10.209.128.1 (10.209.128.1)  13.062 ms  13.143 ms  13.193 ms
 3  89-75-12-193.infra.chello.pl (89.75.12.193)  13.289 ms  13.355 ms  18.565 ms
 4  pl-waw26b-rc1-ae-8-2150.aorta.net (84.116.252.201)  24.352 ms  24.339 ms  18.523 ms
 5  pl-waw26b-ri1-ae-24-0.aorta.net (84.116.138.73)  21.131 ms  20.988 ms  21.013 ms
 6  ae-13.r01.wrswpl01.pl.bb.gin.ntt.net (129.250.9.109)  21.222 ms  12.534 ms  12.508 ms
 7  ae-8.r20.amstnl07.nl.bb.gin.ntt.net (129.250.3.133)  33.624 ms  33.654 ms  37.025 ms
 8  ae-3.r00.frnkge13.de.bb.gin.ntt.net (129.250.6.14)  28.441 ms ae-0.a01.amstnl07.nl.bb.gin.ntt.net (129.250.7.87)  33.503 ms ae-3.r00.frnkge13.de.bb.gin.ntt.net (129.250.6.14)  30.916 ms
 9  ae-3.akamai.amstnl07.nl.bb.gin.ntt.net (168.143.105.177)  90.035 ms ae-0.akamai.amstnl09.nl.bb.gin.ntt.net (168.143.105.181)  34.545 ms ae-0.akamai.frnkge07.de.bb.gin.ntt.net (168.143.105.105)  30.729 ms
10  ae12.r02.ams01.icn.netarch.akamai.com (23.197.69.40)  33.905 ms ae13.r01.fra02.icn.netarch.akamai.com (23.210.52.46)  45.202 ms a23-210-54-17.deploy.static.akamaitechnologies.com (23.210.54.17)  30.019 ms
11  ae11.r01.fra03.icn.netarch.akamai.com (95.100.192.161)  37.480 ms  27.655 ms  46.961 ms
12  ae1.r02.fra03.ien.netarch.akamai.com (23.210.54.37)  30.562 ms  27.318 ms  46.776 ms
13  * * *
14  * * Bottles-Web-FRA-0.usebottles.com (194.233.171.195)  24.638 ms

[jpadilla@fractal-local ~]$ sudo traceroute -4 -T repo.usebottles.com
traceroute to repo.usebottles.com (194.233.171.195), 30 hops max, 60 byte packets
 1  * * *
 2  10.209.128.1 (10.209.128.1)  14.103 ms  14.236 ms  14.162 ms
 3  89-75-12-193.infra.chello.pl (89.75.12.193)  14.317 ms  21.497 ms  21.487 ms
 4  pl-waw26b-rc1-ae-8-2150.aorta.net (84.116.252.201)  21.747 ms  21.593 ms  21.956 ms
 5  pl-waw26b-ri1-ae-24-0.aorta.net (84.116.138.73)  21.705 ms  21.896 ms  21.781 ms
 6  ae-13.r01.wrswpl01.pl.bb.gin.ntt.net (129.250.9.109)  30.517 ms  16.435 ms  16.446 ms
 7  ae-22.r20.frnkge13.de.bb.gin.ntt.net (129.250.5.18)  32.405 ms  35.753 ms  28.530 ms
 8  ae-0.a00.amstnl09.nl.bb.gin.ntt.net (129.250.2.163)  37.595 ms ae-3.r00.frnkge13.de.bb.gin.ntt.net (129.250.6.14)  32.712 ms ae-0.a03.frnkge07.de.bb.gin.ntt.net (129.250.7.16)  32.488 ms
 9  ae-0.akamai.frnkge07.de.bb.gin.ntt.net (168.143.105.105)  32.712 ms  32.570 ms ae-0.akamai.amstnl09.nl.bb.gin.ntt.net (168.143.105.181)  58.329 ms
10  a23-210-54-17.deploy.static.akamaitechnologies.com (23.210.54.17)  37.334 ms ae12.r02.ams01.icn.netarch.akamai.com (23.197.69.40)  32.303 ms  32.267 ms
11  ae5.r01.fra03.icn.netarch.akamai.com (95.100.192.138)  41.829 ms  31.077 ms ae11.r01.fra03.icn.netarch.akamai.com (95.100.192.161)  25.978 ms
12  ae1.r02.fra03.ien.netarch.akamai.com (23.210.54.37)  34.529 ms  30.410 ms  35.407 ms
13  * * *
14  Bottles-Web-FRA-0.usebottles.com (194.233.171.195)  29.518 ms * *


[jpadilla@fractal-local ~]$ sudo traceroute -4 -T repo.usebottles.com
traceroute to repo.usebottles.com (194.233.171.195), 30 hops max, 60 byte packets
 1  * * *
 2  10.209.128.1 (10.209.128.1)  13.633 ms  13.707 ms  13.695 ms
 3  89-75-12-193.infra.chello.pl (89.75.12.193)  13.854 ms  13.918 ms  19.874 ms
 4  pl-waw26b-rc1-ae-8-2150.aorta.net (84.116.252.201)  19.986 ms  20.058 ms  19.893 ms
 5  pl-waw26b-ri1-ae-24-0.aorta.net (84.116.138.73)  20.109 ms  20.192 ms  20.222 ms
 6  ae-13.r01.wrswpl01.pl.bb.gin.ntt.net (129.250.9.109)  20.279 ms  15.892 ms  15.911 ms
 7  ae-8.r20.amstnl07.nl.bb.gin.ntt.net (129.250.3.133)  48.736 ms ae-22.r20.frnkge13.de.bb.gin.ntt.net (129.250.5.18)  35.210 ms  35.159 ms
 8  ae-0.a01.amstnl07.nl.bb.gin.ntt.net (129.250.7.87)  33.977 ms ae-3.r00.frnkge13.de.bb.gin.ntt.net (129.250.6.14)  29.221 ms ae-0.a03.frnkge07.de.bb.gin.ntt.net (129.250.7.16)  29.247 ms
 9  ae-2.akamai.frnkge13.de.bb.gin.ntt.net (168.143.105.113)  33.833 ms ae-0.akamai.amstnl09.nl.bb.gin.ntt.net (168.143.105.181)  37.410 ms  37.349 ms
10  a23-210-54-17.deploy.static.akamaitechnologies.com (23.210.54.17)  37.025 ms  36.974 ms ae13.r01.fra02.icn.netarch.akamai.com (23.210.52.46)  46.335 ms
11  ae5.r01.fra03.icn.netarch.akamai.com (95.100.192.138)  35.819 ms ae11.r01.fra03.icn.netarch.akamai.com (95.100.192.161)  26.529 ms ae5.r01.fra03.icn.netarch.akamai.com (95.100.192.138)  35.991 ms
12  ae1.r02.fra03.ien.netarch.akamai.com (23.210.54.37)  34.287 ms  38.220 ms  35.213 ms
13  * * *
14  * * *
15  * * *
16  * Bottles-Web-FRA-0.usebottles.com (194.233.171.195)  29.874 ms *

[jpadilla@fractal-local ~]$ sudo traceroute -4 -T repo.usebottles.com
traceroute to repo.usebottles.com (194.233.171.195), 30 hops max, 60 byte packets
 1  * * *
 2  10.209.128.1 (10.209.128.1)  9.544 ms  11.698 ms  11.609 ms
 3  89-75-12-193.infra.chello.pl (89.75.12.193)  11.924 ms  12.087 ms  13.887 ms
 4  pl-waw26b-rc1-ae-8-2150.aorta.net (84.116.252.201)  11.826 ms  12.008 ms  17.862 ms
 5  pl-waw26b-ri1-ae-24-0.aorta.net (84.116.138.73)  17.659 ms  17.551 ms  17.733 ms
 6  ae-13.r01.wrswpl01.pl.bb.gin.ntt.net (129.250.9.109)  17.904 ms  12.351 ms  10.348 ms
 7  ae-8.r20.amstnl07.nl.bb.gin.ntt.net (129.250.3.133)  37.406 ms ae-22.r20.frnkge13.de.bb.gin.ntt.net (129.250.5.18)  30.848 ms ae-8.r20.amstnl07.nl.bb.gin.ntt.net (129.250.3.133)  37.308 ms
 8  ae-0.a01.amstnl07.nl.bb.gin.ntt.net (129.250.7.87)  32.706 ms  32.587 ms  30.884 ms
 9  ae-0.akamai.amstnl09.nl.bb.gin.ntt.net (168.143.105.181)  58.965 ms ae-2.akamai.frnkge13.de.bb.gin.ntt.net (168.143.105.113)  29.713 ms ae-0.akamai.amstnl09.nl.bb.gin.ntt.net (168.143.105.181)  58.923 ms
10  ae12.r02.ams01.icn.netarch.akamai.com (23.197.69.40)  31.342 ms  35.431 ms *
11  ae5.r01.fra03.icn.netarch.akamai.com (95.100.192.138)  34.515 ms * ae11.r01.fra03.icn.netarch.akamai.com (95.100.192.161)  28.345 ms
12  ae1.r02.fra03.ien.netarch.akamai.com (23.210.54.37)  29.752 ms  31.987 ms  29.329 ms
13  * * *
14  * * *
15  * Bottles-Web-FRA-0.usebottles.com (194.233.171.195)  29.192 ms *

Curl continues to fail when retry is not used:

For IPv4 (without retry):

[jpadilla@fractal-local ~]$ curl -4 -v https://repo.usebottles.com/components/index.yml
*   Trying 194.233.171.195:443...
* connect to 194.233.171.195 port 443 failed: Connection timed out
* Failed to connect to repo.usebottles.com port 443 after 132359 ms: Connection timed out
* Closing connection 0
curl: (28) Failed to connect to repo.usebottles.com port 443 after 132359 ms: Connection timed out

My router doesn't support IPv6 so I get Network unreachable error when trying curl -6 -v https://repo.usebottles.com/components/index.yml

Note that this works most of the time for me: curl -4 --retry 3 --connect-timeout 3 -v https://repo.usebottles.com/components/index.yml.

Trying to put it all together, it looks like TCP traffic is routed through different paths in a very short time and this somehow causes requests not to reach the destination (repo.usebottles.com) or replies not to reach the source (my computer) for some of these paths.

Maybe we can conduct a test using iperf3 to measure packet loss?

d3ce1t avatar Oct 10 '22 12:10 d3ce1t

So, the problem seems like is from Akamai side, I'll try to fix and maybe add a couple of new nodes inside our infrastructure, I'll keep you updated!

francescomasala avatar Oct 11 '22 06:10 francescomasala

Today first time I recived sucesfull icmp from server, also Bottles works as should on ipv4

Sidroff@vm:~$ ping google.com -4
PING  (216.58.208.206) 56(84) bytes of data.
64 bytes from waw07s02-in-f14.1e100.net (216.58.208.206): icmp_seq=1 ttl=57 time=18.1 ms
64 bytes from par10s21-in-f14.1e100.net (216.58.208.206): icmp_seq=2 ttl=57 time=20.3 ms
64 bytes from waw07s02-in-f14.1e100.net (216.58.208.206): icmp_seq=3 ttl=57 time=14.8 ms
64 bytes from par10s21-in-f206.1e100.net (216.58.208.206): icmp_seq=4 ttl=57 time=13.5 ms
64 bytes from par10s21-in-f206.1e100.net (216.58.208.206): icmp_seq=5 ttl=57 time=13.9 ms
64 bytes from waw07s02-in-f14.1e100.net (216.58.208.206): icmp_seq=6 ttl=57 time=13.2 ms
64 bytes from waw07s02-in-f14.1e100.net (216.58.208.206): icmp_seq=7 ttl=57 time=13.8 ms
64 bytes from waw07s02-in-f14.1e100.net (216.58.208.206): icmp_seq=8 ttl=57 time=14.8 ms
64 bytes from par10s21-in-f14.1e100.net (216.58.208.206): icmp_seq=9 ttl=57 time=14.6 ms
^C
---  ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8012ms
rtt min/avg/max/mdev = 13.163/15.224/20.314/2.257 ms
Sidroff@vm:~$ sudo traceroute -I repo.usebottles.com
traceroute to repo.usebottles.com (194.233.171.195), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  0.392 ms  0.474 ms  0.471 ms
 2  * * *
 3  89-75-11-65.infra.chello.pl (89.75.11.65)  11.467 ms  16.598 ms  16.821 ms
 4  pl-stg01a-ra2-be-1-2190.aorta.net (84.116.253.98)  21.916 ms  22.451 ms  22.745 ms
 5  pl-waw10a-rc1-ae-35-0.aorta.net (84.116.253.185)  26.419 ms  26.712 ms  27.013 ms
 6  pl-waw26b-ri1-ae-3-0.aorta.net (84.116.138.102)  21.498 ms  19.752 ms  20.067 ms
 7  ae-13.r01.wrswpl01.pl.bb.gin.ntt.net (129.250.9.109)  20.544 ms  14.091 ms  16.064 ms
 8  ae-8.r20.amstnl07.nl.bb.gin.ntt.net (129.250.3.133)  37.730 ms  37.836 ms  37.986 ms
 9  ae-0.a01.amstnl07.nl.bb.gin.ntt.net (129.250.7.87)  35.983 ms  35.975 ms  39.866 ms
10  ae-3.akamai.amstnl07.nl.bb.gin.ntt.net (168.143.105.177)  37.629 ms  37.520 ms  37.570 ms
11  * * *
12  * * *
13  ae1.r02.fra03.ien.netarch.akamai.com (23.210.54.37)  34.733 ms  34.528 ms  35.514 ms
14  a23-210-54-19.deploy.static.akamaitechnologies.com (23.210.54.19)  31.867 ms  31.820 ms  31.859 ms
15  * * *
16  * * *
17  * * *
18  Bottles-Web-FRA-0.usebottles.com (194.233.171.195)  35.128 ms  32.958 ms  31.376 ms
Sidroff@vm:~$ sudo traceroute -T repo.usebottles.com
traceroute to repo.usebottles.com (194.233.171.195), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  0.280 ms  0.258 ms  0.340 ms
 2  * * *
 3  89-75-11-65.infra.chello.pl (89.75.11.65)  18.248 ms  17.864 ms  15.528 ms
 4  pl-stg01a-ra2-be-1-2190.aorta.net (84.116.253.98)  19.950 ms  23.891 ms  23.371 ms
 5  * * *
 6  pl-waw26b-ri1-ae-3-0.aorta.net (84.116.138.102)  22.959 ms  21.067 ms  29.956 ms
 7  ae-13.r01.wrswpl01.pl.bb.gin.ntt.net (129.250.9.109)  21.494 ms  16.522 ms  19.048 ms
 8  ae-22.r20.frnkge13.de.bb.gin.ntt.net (129.250.5.18)  31.835 ms ae-8.r20.amstnl07.nl.bb.gin.ntt.net (129.250.3.133)  38.036 ms  40.390 ms
 9  ae-0.a03.frnkge07.de.bb.gin.ntt.net (129.250.7.16)  29.626 ms  30.882 ms ae-0.a00.amstnl09.nl.bb.gin.ntt.net (129.250.2.163)  40.725 ms
10  ae-2.akamai.frnkge13.de.bb.gin.ntt.net (168.143.105.113)  35.205 ms ae-3.akamai.amstnl07.nl.bb.gin.ntt.net (168.143.105.177)  37.804 ms ae-0.akamai.amstnl09.nl.bb.gin.ntt.net (168.143.105.181)  39.753 ms
11  ae11.r02.fra02.icn.netarch.akamai.com (23.210.52.50)  33.971 ms a23-210-54-17.deploy.static.akamaitechnologies.com (23.210.54.17)  29.785 ms ae11.r02.fra02.icn.netarch.akamai.com (23.210.52.50)  35.939 ms
12  * * *
13  ae1.r02.fra03.ien.netarch.akamai.com (23.210.54.37)  34.722 ms  28.115 ms *
14  * a23-210-54-19.deploy.static.akamaitechnologies.com (23.210.54.19)  30.035 ms  33.018 ms
15  * * Bottles-Web-FRA-0.usebottles.com (194.233.171.195)  33.928 ms

Connection state on router also looks correct WAN_RE0_UPC icmp 31.178.36.xx:60848 -> 194.233.171.195:60848 0:0 6 / 6 504 B / 504 B

Thanks for helping

Sidroff avatar Oct 12 '22 13:10 Sidroff