@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+T3s|4
+acetone
+hottuna
+orignal
+postman
+weko
+wodencafe
An0nm0n
Arch
Gid_
Irc2PGuest13599
Irc2PGuest16518
Irc2PGuest45876
Irc2PGuest63393
Minogami
Onn4l7h
Onn4|7h
ProRu
Soni
Teeed
aargh3
b3t4f4c3___
cheddah
eyedeekay_bnc
i2puser
itsjustme
j6
limak
not_bob_afk
profetikla
rapidash
tbqdrn
theglitc1
w8rabbit
x74a6
zer0bitz
Opicaak
Hi, eyedeekay, just pinging you to check if deb.i2p2.de is up or not, it seems unreachable right now.
eyedeekay
Reachable from here to me, I'm logged in on it right now too
eyedeekay
Does deb.i2p2.no work for you?
Opicaak
I can ping this one
Opicaak
But not the first one.
eyedeekay
OK they're the same server, if you need a short-term solution for now then just use deb.i2p2.no
eyedeekay
Anything else you can tell me the re: the unreachability of the other?
Opicaak
It's unpingable, and times out on apt update.
Opicaak
The .no also requires the tls cert?
eyedeekay
Yes
Opicaak
I just noticed that it's not only the deb.i2p2.de, but also packages.microsoft.com
Opicaak
But other apt sources work, interesting.
eyedeekay
That's weird
Opicaak
Can you ping 13.80.99.124? It's packages.microsoft.com
eyedeekay
Sure can
eyedeekay
Azure Western Europe for me
Opicaak
Yes, so you are getting replies?
eyedeekay
No, it's just sitting there spinning in my terminal
Opicaak
So, it is probably down. I just tried deb.i2p2.no again, and it's also stuck now.
eyedeekay
Well just a sec, if I stick that same IP address into my browser, it works just fine
eyedeekay
It's not responding to pings, but it seems to be there just the same
eyedeekay
deb.i2p2.de on the other hand is responding to pings for me
Opicaak
I bet someone cut important fibre somewhere in EU, haha.
Opicaak
Just like you, I can see it in the browser, the MS apt.
Opicaak
And I can also access both i2p debs via browser.
Opicaak
i2p apts*
eyedeekay
Must be one heck of a fiber, deb.i2p2.de isn't anywhere near Azure
Opicaak
It seems like an issue on my PC, maybe a reboot would fix it.
Opicaak
But I have so much work open, I don't feel like rebooting.
Opicaak
Maybe MS switched to TLS apt, and maybe the i2p2.de cert has expired, I haven't checked either.
eyedeekay
I just renewed the deb.i2p2.de certs a week or two ago, it's not that
Opicaak
So weird...
Opicaak
Ok, so, MS did switch to 443 and TLS, they didn't use it previously.
Opicaak
Awesome, that also solved the i2p2 deb issue.
Opicaak
And the blog post is still returning 404 from i2p (127.0.0.1:7657) news section.
Opicaak
It's missing 0 in the URL.
Opicaak
Current URL: /en/blog/post/2023/3/13/new_release_2.2.0 instead of /en/blog/post/2023/03/13/new_release_2.2.0