I can't update my system {...InRelease is not (yet) available...}

Ad · 2024-08-01 07:06

I get this error message from the Discover app:

E: https://q4os .org/q4repo q4os-5-0-cn InRelease is not (yet) available (Cannot initiate the connection to q4os.org:443 (2a02:4a8:ac24:108::96:231). - connect (101: Network is unreachable) Could not connect to q4os.org:443 (81.95.96.231), connection timed out)
E: https://q4os .org/qextrepo bookworm-chrome-cn InRelease is not (yet) available (Cannot initiate the connection to q4os.org:443 (2a02:4a8:ac24:108::96:231). - connect (101: Network is unreachable))

When I ignore the message and click 'update all' it doesn't start.

Also, why does each software in the updating list show the number of KiB/MiB and only "linux-amd-64..." pakage shows 'unknown'? Did the problem start from there?

q4osteam · 2024-08-01 09:18

We can't reproduce the issue, so it seems to be a problem specific to your location.
- What is your geographic location ?
- How long have you been observing the problems ?
- Does anyone else notice connection issues ?

Last edited by q4osteam (2024-08-01 09:20)

Ad · 2024-08-01 15:38

q4osteam wrote:

We can't reproduce the issue, so it seems to be a problem specific to your location.
- What is your geographic location ?
- How long have you been observing the problems ?
- Does anyone else notice connection issues ?

My location is Egypt (North Africa, UTC+02:00).
I observe the problem for a month nearly.

q4osteam · 2024-08-01 15:53

Please run the following commands in terminal and paste their output here for us to analyze:
$ get-q4os-version
$ qrepolist
$ ping -c4 q4os.org
$ sudo apt update

Ad · 2024-08-01 16:26

q4osteam wrote:

Please run the following commands in terminal and paste their output here for us to analyze:
$ get-q4os-version
$ qrepolist
$ ping -c4 q4os.org
$ sudo apt update

OK
$ get-q4os-version >>

5.5.1-n1

$ qrepolist >>

deb http://q4os.org/q4repo q4os-5-0-cn main
deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
deb http://security.debian.org/ bookworm-security main contrib non-free non-free-firmware
deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
deb [arch=amd64] http://q4os.org/qextrepo bookworm-chrome-cn main
deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian bookworm stable
deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
deb [arch=amd64,arm64,armhf] https://packages.microsoft.com/repos/code stable main

$ ping -c4 q4os.org >>

PING q4os.org (81.95.96.231) 56(84) bytes of data.

--- q4os.org ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3075ms

$ sudo apt update >>

Hit:1 http://deb.debian.org/debian bookworm InRelease
Get:3 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]                              
Hit:5 http://security.debian.org bookworm-security InRelease                                                 
Hit:6 https://download.docker.com/linux/debian bookworm InRelease                                            
Hit:2 https://q4os.org/q4repo q4os-5-0-cn InRelease                                                          
Get:4 https://q4os.org/qextrepo bookworm-chrome-cn InRelease [1,844 B]                                       
Hit:7 https://dl.google.com/linux/chrome/deb stable InRelease                                                
Ign:8 https://packages.microsoft.com/repos/code stable InRelease                                             
Ign:8 https://packages.microsoft.com/repos/code stable InRelease                                             
Ign:8 https://packages.microsoft.com/repos/code stable InRelease
Err:8 https://packages.microsoft.com/repos/code stable InRelease
  Cannot initiate the connection to packages.microsoft.com:443 (2620:1ec:bdf::43). - connect (101: Network is unreachable) Could not connect to packages.microsoft.com:443 (13.107.246.43), connection timed out
Fetched 57.3 kB in 37s (1,530 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
17 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch https://packages.microsoft.com/repos/code/dists/stable/InRelease  Cannot initiate the connection to packages.microsoft.com:443 (2620:1ec:bdf::43). - connect (101: Network is unreachable) Could not connect to packages.microsoft.com:443 (13.107.246.43), connection timed out
W: Some index files failed to download. They have been ignored, or old ones used instead.

q4osteam · 2024-08-01 17:26

The repository

https://packages.microsoft.com/repos/code

seems to be unavailable. So the first step would be disable this repository from sources.list and run again:
$ sudo apt update
and post back the output here

Ad · 2024-08-01 18:51

q4osteam wrote:

The repository
https://packages.microsoft.com/repos/code
seems to be unavailable. So the first step would be disable this repository from sources.list and run again:
$ sudo apt update
and post back the output here

I'm sorry for late. It seems that I can't find sources.list, I run:

sudo nano /etc/apt/sources.list

to comment on the line

deb https://packages.microsoft.com/repos/code

as I learnt from my search of how to disable a repository but nothing appeared and I get a blank black scene in the terminal text editor. I also can't get sources.list file by using the search function in my OS.

q4osteam · 2024-08-01 20:17

You need to go through

/etc/apt/sources.list.d/*.list

files.

Ad · 2024-08-01 20:51

q4osteam wrote:

You need to go through
/etc/apt/sources.list.d/*.list
files.

I did it. This is the result of sudo apt update:

Hit:3 http://security.debian.org bookworm-security InRelease                                                 
Hit:4 http://deb.debian.org/debian bookworm InRelease                                                        
Hit:5 http://deb.debian.org/debian bookworm-updates InRelease                                                
Hit:6 https://dl.google.com/linux/chrome/deb stable InRelease                                         
Hit:7 https://download.docker.com/linux/debian bookworm InRelease                                          
Ign:1 https://q4os.org/q4repo q4os-5-0-cn InRelease                                                        
Ign:2 https://q4os.org/qextrepo bookworm-chrome-cn InRelease
Ign:1 https://q4os.org/q4repo q4os-5-0-cn InRelease
Ign:2 https://q4os.org/qextrepo bookworm-chrome-cn InRelease
Ign:1 https://q4os.org/q4repo q4os-5-0-cn InRelease
Ign:2 https://q4os.org/qextrepo bookworm-chrome-cn InRelease
Err:1 https://q4os.org/q4repo q4os-5-0-cn InRelease
  Cannot initiate the connection to q4os.org:443 (2a02:4a8:ac24:108::96:231). - connect (101: Network is unreachable) Could not connect to q4os.org:443 (81.95.96.231), connection timed out
Err:2 https://q4os.org/qextrepo bookworm-chrome-cn InRelease
  Cannot initiate the connection to q4os.org:443 (2a02:4a8:ac24:108::96:231). - connect (101: Network is unreachable)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
17 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://q4os.org/q4repo/dists/q4os-5-0-cn/InRelease  Cannot initiate the connection to q4os.org:443 (2a02:4a8:ac24:108::96:231). - connect (101: Network is unreachable) Could not connect to q4os.org:443 (81.95.96.231), connection timed out
W: Failed to fetch http://q4os.org/qextrepo/dists/bookworm-chrome-cn/InRelease  Cannot initiate the connection to q4os.org:443 (2a02:4a8:ac24:108::96:231). - connect (101: Network is unreachable)
W: Some index files failed to download. They have been ignored, or old ones used instead.

crosscourt · 2024-08-01 21:02

Ive done quite a few installs and updates this week with Q4OS and havent had any connection issues.

q4osteam · 2024-08-01 22:22

Please run a web browser from the machine in question and point to "q4os.org". Are you seeing Q4OS website ?
It would be also helpful, if you could check the connection to q4os.org form any other computer near your location. Either from Linux or Windows, just check from web browser or run ping command:
$ ping q4os.org
and post back the results. If you will not be able to reach Q4OS, we will need some more debug info via e-mail, we will let you know.

Ad · 2024-08-02 05:49

q4osteam wrote:

Please run a web browser from the machine in question and point to "q4os.org". Are you seeing Q4OS website ?
It would be also helpful, if you could check the connection to q4os.org form any other computer near your location. Either from Linux or Windows, just check from web browser or run ping command:
$ ping q4os.org
and post back the results. If you will not be able to reach Q4OS, we will need some more debug info via e-mail, we will let you know.

It opens from browsers but

~$ ping q4os.org
PING q4os.org (81.95.96.231) 56(84) bytes of data.

give no response.

~$ ping q4os.org
PING q4os.org (81.95.96.231) 56(84) bytes of data.
^C
--- q4os.org ping statistics ---
179 packets transmitted, 0 received, 100% packet loss, time 182259ms

I tried it many times and checked that internet is working.

hchiper · 2024-08-02 07:02

Things happen differently from here (Q4OS 4.12, Belgium)
Don't know if this helps to tackle the issue.

ping displays an ipv6 address:

$ ping q4os.org
PING q4os.org(ipv6.uvirt25.active24.cz (2a02:4a8:ac24:108::96:231)) 56 data bytes
...

Microsoft repository is responding:

$ sudo apt update
...
Réception de :11 https://packages.microsoft.com/repos/code stable/main arm64 Packages [17,7 kB]
Réception de :12 https://packages.microsoft.com/repos/code stable/main amd64 Packages [17,7 kB]
Réception de :13 https://packages.microsoft.com/repos/code stable/main armhf Packages [17,8 kB]
...

Edit:
Could it be that some form of restriction / blocking on the Internet exists in Egypt?

Last edited by hchiper (2024-08-02 07:10)

q4osteam · 2024-08-02 09:54

@Ad
Please run the following commands in terminal and post back:
$ traceroute q4os.org
$ cd /tmp/ && wget q4os.org

It would be also helpful, if you could check the connection to q4os.org, with the ping command, from any other computer near your location, but outside of your local network. Either from Linux or Windows.

Thanks others for the hints too.

Ad · 2024-08-02 13:03

$ traceroute q4os.org

traceroute to q4os.org (81.95.96.231), 30 hops max, 60 byte packets
 1  csp1.zte.com.cn (192.168.1.1)  22.273 ms  22.209 ms  28.847 ms
 2  100.74.0.1 (100.74.0.1)  36.468 ms * *
 3  * * *
 4  * 10.38.153.182 (10.38.153.182)  45.240 ms 10.38.153.186 (10.38.153.186)  45.215 ms
 5  * 10.45.28.66 (10.45.28.66)  47.239 ms  47.216 ms
 6  TELECOM-EGY.edge4.Marseille1.Level3.net (213.19.202.178)  47.193 ms  24.222 ms *
 7  213.242.116.21 (213.242.116.21)  56.635 ms 213.19.202.177 (213.19.202.177)  62.379 ms  62.336 ms
 8  ae2.9.ear1.prg1.neo.colt.net (171.75.8.113)  83.651 ms  84.095 ms  84.904 ms
 9  COMSOURCE-S.ear1.Prague1.Level3.net (212.133.51.18)  86.842 ms  87.390 ms  87.333 ms
10  * * *
11  * * *
12  uvirt25.active24.cz (81.95.96.231)  87.167 ms  102.180 ms  83.229 ms

$ cd /tmp/ && wget q4os.org

--2024-08-02 12:31:05--  http://q4os.org/
Resolving q4os.org (q4os.org)... 81.95.96.231, 2a02:4a8:ac24:108::96:231
Connecting to q4os.org (q4os.org)|81.95.96.231|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://q4os.org/ [following]
--2024-08-02 12:31:06--  https://q4os.org/
Connecting to q4os.org (q4os.org)|81.95.96.231|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9451 (9.2K) [text/html]
Saving to: ‘index.html’

index.html                  100%[=========================================>]   9.23K  --.-KB/s    in 0s      

2024-08-02 12:31:07 (182 MB/s) - ‘index.html’ saved [9451/9451]

I did what you asked me and it seems the problem was from my WiFi network provider. I connected the device to my mobile network via hotspot and here is the result:

~$ ping q4os.org
PING q4os.org (81.95.96.231) 56(84) bytes of data.
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=1 ttl=46 time=174 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=2 ttl=46 time=229 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=3 ttl=46 time=186 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=4 ttl=46 time=208 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=5 ttl=46 time=230 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=6 ttl=46 time=150 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=7 ttl=46 time=173 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=8 ttl=46 time=195 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=9 ttl=46 time=217 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=10 ttl=46 time=240 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=12 ttl=46 time=263 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=13 ttl=46 time=286 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=14 ttl=46 time=311 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=15 ttl=46 time=333 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=16 ttl=46 time=254 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=17 ttl=46 time=276 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=18 ttl=46 time=300 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=19 ttl=46 time=221 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=20 ttl=46 time=243 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=21 ttl=46 time=266 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=22 ttl=46 time=187 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=23 ttl=46 time=312 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=24 ttl=46 time=336 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=25 ttl=46 time=257 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=26 ttl=46 time=178 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=27 ttl=46 time=200 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=28 ttl=46 time=223 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=29 ttl=46 time=245 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=30 ttl=46 time=268 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=31 ttl=46 time=291 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=32 ttl=46 time=212 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=33 ttl=46 time=234 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=34 ttl=46 time=257 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=35 ttl=46 time=179 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=36 ttl=46 time=201 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=37 ttl=46 time=224 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=38 ttl=46 time=144 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=39 ttl=46 time=154 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=40 ttl=46 time=188 ms
64 bytes from uvirt25.active24.cz (81.95.96.231): icmp_seq=41 ttl=46 time=210 ms
^C
--- q4os.org ping statistics ---
41 packets transmitted, 40 received, 2.43902% packet loss, time 40067ms
rtt min/avg/max/mdev = 143.964/231.364/335.829/49.127 ms

q4osteam · 2024-08-02 15:25

Ad wrote:

I did what you asked me and it seems the problem was from my WiFi network provider. I connected the device to my mobile network via hotspot ...

So it seems, your provider is blocking some network traffic. We recommend you to ask them to explain and fix the problem. If they resolve it, we would appreciate you post here the root of issues, so we can see, if such problems may be more common or just rare specific.

crosscourt · 2024-08-02 17:27

Thats really odd, why would they be blocking network traffic?

Ad · 2024-08-02 17:55

q4osteam wrote:

Ad wrote:
I did what you asked me and it seems the problem was from my WiFi network provider. I connected the device to my mobile network via hotspot ...
So it seems, your provider is blocking some network traffic. We recommend you to ask them to explain and fix the problem. If they resolve it, we would appreciate you post here the root of issues, so we can see, if such problems may be more common or just rare specific.

Sure. I'll ask them and see their answer.

Thank you for following up with me! I'm grateful for your help and grateful for the existence of Q4OS in my life

crosscourt · 2024-08-02 19:36

After doing some research it appears you arent the only one having this issue in Egypt with Linux. It may be due to governmental policies affecting ISPs, that have been an issue since 2019. Reaching repositories and updating with a variety of Linux distros have had issues, particularly since April of this year.

Last edited by crosscourt (2024-08-02 19:47)

Q4OS Forum

#1 2024-08-01 07:06

I can't update my system {...InRelease is not (yet) available...}

#2 2024-08-01 09:18

Re: I can't update my system {...InRelease is not (yet) available...}

#3 2024-08-01 15:38

Re: I can't update my system {...InRelease is not (yet) available...}

#4 2024-08-01 15:53

Re: I can't update my system {...InRelease is not (yet) available...}

#5 2024-08-01 16:26

Re: I can't update my system {...InRelease is not (yet) available...}

#6 2024-08-01 17:26

Re: I can't update my system {...InRelease is not (yet) available...}

#7 2024-08-01 18:51

Re: I can't update my system {...InRelease is not (yet) available...}

#8 2024-08-01 20:17

Re: I can't update my system {...InRelease is not (yet) available...}

#9 2024-08-01 20:51

Re: I can't update my system {...InRelease is not (yet) available...}

#10 2024-08-01 21:02

Re: I can't update my system {...InRelease is not (yet) available...}

#11 2024-08-01 22:22

Re: I can't update my system {...InRelease is not (yet) available...}

#12 2024-08-02 05:49

Re: I can't update my system {...InRelease is not (yet) available...}

#13 2024-08-02 07:02

Re: I can't update my system {...InRelease is not (yet) available...}

#14 2024-08-02 09:54

Re: I can't update my system {...InRelease is not (yet) available...}

#15 2024-08-02 13:03

Re: I can't update my system {...InRelease is not (yet) available...}

#16 2024-08-02 15:25

Re: I can't update my system {...InRelease is not (yet) available...}

#17 2024-08-02 17:27

Re: I can't update my system {...InRelease is not (yet) available...}

#18 2024-08-02 17:55

Re: I can't update my system {...InRelease is not (yet) available...}

#19 2024-08-02 19:36

Re: I can't update my system {...InRelease is not (yet) available...}

Board footer