Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] We can't access archive/debuginfod.artixlinux.org (Read 1190 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

[SOLVED] We can't access archive/debuginfod.artixlinux.org

So, I and (and multiple people throughout Poland) have a problem. We can't access archives or debuginfod. I know the service works, I can access it with proxy. This has been going on for about 3-4 weeks now,. Could you please check what's wrong and fix it? Thanks.

 

Re: We can't access archive/debuginfod.artixlinux.org

Reply #1 –
Hello Shoun2137,

I have tried accessing the site from my location in Poland to the same effect.  My traceroute shows a successful connection until it moves from my Poland server to the Artix archive.  Does the same thing happen when you do this?

Re: We can't access archive/debuginfod.artixlinux.org

Reply #2 –
Quote from: Danny – on
Hello Shoun2137,

I have tried accessing the site from my location in Poland to the same effect.  My traceroute shows a successful connection until it moves from my Poland server to the Artix archive.  Does the same thing happen when you do this?
Yep, exact thing. People from various places in Poland can't connect to those services. It must be something from Artix's side of things.

Re: We can't access archive/debuginfod.artixlinux.org

Reply #3 –
The Debian package archives are available on various mirrors, there could be a reason for this approach:
https://www.debian.org/distrib/archive
Earlier threads say  Artix isn't blocking anyone either. Imperfections in the internet? If too many users try to access the same thing some won't get through, web hosting I've seen usually has usage limits (user / download) somewhere in the small print.

Re: We can't access archive/debuginfod.artixlinux.org

Reply #4 –
I would like to point out, these reported problems seem to all come from either Poland, Ukraine and area.
What is the chance, somewhere in the routing, some server who or whatever blocks traffic because there is a useless war going on?
It could be a possible explanation.

Re: We can't access archive/debuginfod.artixlinux.org

Reply #5 –
Well, i poked around, just googled the last server traceroute address which was b99.pop104-asr.ipv4.wtnet.de, and it pointed to this thread https://forum.artixlinux.org/index.php/topic,6252.msg39224.html#msg39224

b99.pop104-asr.ipv4.wtnet.de (which is not associated with cloudflare) is owned by wilhelm-tel.de which seems like a normal german ISP, so the war argument should be thrown out the window.

Well, if that's the case then the entire system is unusable, because I can't even update the distro anymore since yesterday. Too bad, I guess, I'll just use Devuan instead it seems.

Re: We can't access archive/debuginfod.artixlinux.org

Reply #6 –
It is simply beyond our influence.
We do not block as artix.

Re: We can't access archive/debuginfod.artixlinux.org

Reply #7 –
Quote from: Danny – on
Hello Shoun2137,

I have tried accessing the site from my location in Poland to the same effect.  My traceroute shows a successful connection until it moves from my Poland server to the Artix archive.  Does the same thing happen when you do this?


Since when is the problem occurring?
We moved roughly maybe 2 months ago gitea, archive and debuginfod instance to a vps.
Probably related to the problem occurring?

Re: We can't access archive/debuginfod.artixlinux.org

Reply #8 –
Quote from: artoo – on
It is simply beyond our influence.
We do not block as artix.
yeah, well no hard feelings, sometimes stuff is just life

Quote from: artoo – on
Quote from: Danny – on
Hello Shoun2137,

I have tried accessing the site from my location in Poland to the same effect.  My traceroute shows a successful connection until it moves from my Poland server to the Artix archive.  Does the same thing happen when you do this?


Since when is the problem occurring?
We moved roughly maybe 2 months ago gitea, archive and debuginfod instance to a vps.
Probably related to the problem occurring?

As i said, I noticed it being unavailable a month~ ago, maybe even less, but as there were reports about that at the end of January, then I don't know really what's going on, but I remember the last time I could access archive exactly at 2th of February, cos of this https://forum.artixlinux.org/index.php/topic,6428.msg39356.html Maybe we're being ratelimited at some point.

Re: We can't access archive/debuginfod.artixlinux.org

Reply #9 –
Quote from: Shoun2137 – on
So, I and (and multiple people throughout Poland) have a problem. We can't access archives or debuginfod. I know the service works, I can access it with proxy.
The archive server is located in Germany, behind a strict firewall for reasons which won't be explained here (read: security by obscurity). What can be said though is Artix doesn't control that firewall and our host may be blocking certain IP ranges.
The debuginfod server is in the US and runs without any IP blacklisting on HTTPS. If I were you, I'd check your ISP.

Re: We can't access archive/debuginfod.artixlinux.org

Reply #10 –
Quote from: nous – on
Quote from: Shoun2137 – on
So, I and (and multiple people throughout Poland) have a problem. We can't access archives or debuginfod. I know the service works, I can access it with proxy.
The archive server is located in Germany, behind a strict firewall for reasons which won't be explained here (read: security by obscurity). What can be said though is Artix doesn't control that firewall and our host may be blocking certain IP ranges.
The debuginfod server is in the US and runs without any IP blacklisting on HTTPS. If I were you, I'd check your ISP.
'Security by obscurity' or 'Broken by design' ?
I'm not affected. But neither should anyone be unless they are behind a state based firewall which forces the use of a vpn, imho.
If I had website / service which was blocking legitimate users due to a host implemented firewall over which I had no control I'd be switching hosts.

Re: We can't access archive/debuginfod.artixlinux.org

Reply #11 –
Quote from: Shoun2137 – on
Well, if that's the case then the entire system is unusable, because I can't even update the distro anymore since yesterday.

There is a working Artix mirror in Warsaw, so that's your problem.

Code: [Select]
# Artix mirrors
...
# Poland
# https://artix.sakamoto.pl/$repo/os/$arch ... 0.368225
...
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

Re: We can't access archive/debuginfod.artixlinux.org

Reply #12 –
Quote from: lq – on
Quote from: Shoun2137 – on
Well, if that's the case then the entire system is unusable, because I can't even update the distro anymore since yesterday.

There is a working Artix mirror in Warsaw, so that's your problem.

Code: [Select]
# Artix mirrors
...
# Poland
# https://artix.sakamoto.pl/$repo/os/$arch ... 0.368225
...
Whenever i polled from any of the mirrors provided, packages were outdated and pacman tried to downgrade the system.

Edit: I just checked, and yeah, that mirror was already at the top of the list.

Re: We can't access archive/debuginfod.artixlinux.org

Reply #13 –
Quote from: Shoun2137 – on
Whenever i polled from any of the mirrors provided, packages were outdated and pacman tried to downgrade the system.

Edit: I just checked, and yeah, that mirror was already at the top of the list.
This thread has morphed quite a bit.
You started of by saying you could not access archive.artixlinux.org (which several users have reported) and debuginfod.artixlinux.org, the latter seemed odder as traceroute show it's a different server than the archive server.
But it's escalated to supposedly outdated mirrors and pacman downgrading packages.
If the mirror is not updated try using another. But pacman does not downgrade packages unless you specifically tell it to (-uu).
I'm a bit confused.

Re: We can't access archive/debuginfod.artixlinux.org

Reply #14 –
I use yay to do all of updates, and by default when you type just plain `yay` its `yay -Syu`.


Edit: Aight, I can update/upgrade just fine now, so that might be a fart on either my end/mirror's end. But the crux of the matter which is archive/debuginfod not working, well those still don't work. Which begs the question. Do you mirror your debuginfod symbols somewhere else where I could redirect those? I'll live with downgrading by downloading archives with proxy/vpn, but for debuginfod, it'll be somewhat pain in the ass to do.

Edit 2: oh ffs, I just check from VPN exactly which packages are available in debuginfod, I was debugging qt6.7.0 and the last packages you have available are qt6.4.2, no wonder it failed to download. Guess it's only archives that are problematic it seems.