Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fastly Repository #658

Open
clefebvre opened this issue Apr 8, 2024 · 175 comments
Open

Fastly Repository #658

clefebvre opened this issue Apr 8, 2024 · 175 comments
Assignees

Comments

@clefebvre
Copy link
Member

clefebvre commented Apr 8, 2024

Hi everyone,

pngwing com

We're currently testing the Fastly CDN, which has the potential to really boost the performance of our repositories.

How to test

  1. Launch the Software Sources tool.
  2. Click on Restore the default settings to ensure you're using the official mirror.
  3. Edit /etc/apt/sources.list.d/official-package-repositories.list with:

sudo xed /etc/apt/sources.list.d/official-package-repositories.list

  1. In this file, replace:

http://packages.linuxmint.com

with:

http://fastly.linuxmint.io

  1. Update your APT cache with:

apt update

What to expect

  • Faster response times. Unlike our repositories which are located in Chicago, this is a global CDN, with servers all over the World.
  • Consistent speeds. Packages are cached. When more people download them, the speeds should not go down.
  • High availability.

How long is this test

One month, two months maybe? It's hard to predict.

We're testing load, pricing, updates..

HTTPS

You can also test the Fastly repositories via HTTPs.

Instead of:

http://fastly.linuxmint.io

Use:

https://fastly.linuxmint.io

How to give us Feedback

We expect the Fastly CDN to be fast, consistent and highly available.

If you're testing it and you're happy with it, simply react to this issue with the rocket emoji 🚀.

If you are experiencing problems, let us know with a comment.

Long term

We're hoping to be able to move to Fastly.

We need to see how the CDN copes with large amounts of users before switching to it.

Please be aware that http://fastly.linuxmint.io is a temporary domain name, set up for this test.

If/when we eventually switch to Fastly we'll make http://packages.linuxmint.com point to Fastly CDN directly.

Many thanks to all of you in advance.

@clefebvre clefebvre self-assigned this Apr 8, 2024
@GAJansen
Copy link

GAJansen commented Apr 9, 2024

Hi @clefebvre,
I am in to try and test this repo. But as this is a temporary set up, how will testers be notified when the test is over and switch back to the original repo's?

@oleg-indeez
Copy link

hello. Just changed as it stated in post. Cert error:

$ apt update
Сущ:2 http://pub.freerdp.com/repositories/deb/jammy freerdp-nightly InRelease                                                                
Сущ:3 http://ppa.launchpad.net/phoerious/keepassxc/ubuntu jammy InRelease                                                                    
Игн:1 https://fastly.linuxmint.com virginia InRelease                                                                                        
Сущ:4 http://ppa.launchpad.net/unit193/inxi/ubuntu jammy InRelease                                                                           
Сущ:5 http://archive.ubuntu.com/ubuntu jammy InRelease                                                                                       
Сущ:6 https://repo.skype.com/deb stable InRelease                                                                                            
Сущ:7 http://security.ubuntu.com/ubuntu jammy-security InRelease                                                                             
Сущ:8 http://archive.ubuntu.com/ubuntu jammy-updates InRelease                                                                               
Сущ:9 http://archive.ubuntu.com/ubuntu jammy-backports InRelease                                           
Сущ:10 https://download.sublimetext.com apt/stable/ InRelease                     
Игн:1 https://fastly.linuxmint.com virginia InRelease
Игн:1 https://fastly.linuxmint.com virginia InRelease
Ошб:1 https://fastly.linuxmint.com virginia InRelease
  Certificate verification failed: The certificate is NOT trusted. The name in the certificate does not match the expected.  Could not handshake: Error in the certificate verification. [IP: 192.124.249.53 443]
Чтение списков пакетов… Готово
Построение дерева зависимостей… Готово
Чтение информации о состоянии… Готово         
Может быть обновлено 5 пакетов. Запустите «apt list --upgradable» для их показа.
W: Не удалось получить http://fastly.linuxmint.com/dists/virginia/InRelease  Certificate verification failed: The certificate is NOT trusted. The name in the certificate does not match the expected.  Could not handshake: Error in the certificate verification. [IP: 192.124.249.53 443]
W: Некоторые индексные файлы скачать не удалось. Они были проигнорированы, или вместо них были использованы старые версии.

no difference whether romeo enabled or not

@EnlightenedBacon
Copy link

hello. Just changed as it stated in post. Cert error:

fastly.linuxmint.io not .com

@karhima
Copy link

karhima commented Apr 9, 2024

Screenshot from 2024-04-09 11-16-14
The https site is giving me this error, http://fastly.linuxmint.io is working fine.

@oleg-indeez
Copy link

oleg-indeez commented Apr 9, 2024

hello. Just changed as it stated in post. Cert error:

fastly.linuxmint.io not .com

thank you for correction - my fault by neglection. Now it works perfect

@sat-hub
Copy link

sat-hub commented Apr 9, 2024

I started testing https://fastly.linuxmint.io.

🚀

@clefebvre
Copy link
Member Author

Screenshot from 2024-04-09 11-16-14 The https site is giving me this error, http://fastly.linuxmint.io is working fine.

Does apt update work? Do you get any warning/error?

@Cautious-C
Copy link

🚀

@clefebvre
Copy link
Member Author

clefebvre commented Apr 9, 2024

Hi @clefebvre, I am in to try and test this repo. But as this is a temporary set up, how will testers be notified when the test is over and switch back to the original repo's?

When the test is over we'll close this issue and/or make announcements.

@karhima
Copy link

karhima commented Apr 9, 2024

apt update did not give me any errors or warnings

@rcork
Copy link

rcork commented Apr 9, 2024

🚀

@sardine-antics
Copy link

🚀

@ReyVago
Copy link

ReyVago commented Apr 9, 2024

I made the change of repositories, and everything seems to work fine.
Captura de pantalla de 2024-04-09 08-53-08
Captura de pantalla de 2024-04-09 08-54-09

@juglanshub
Copy link

🚀 https://fastly.linuxmint.io

@ajay6915
Copy link

ajay6915 commented Apr 9, 2024

Worked with https://fastly.linuxmint.io. No issues.

@dream-eddie
Copy link

dream-eddie commented Apr 9, 2024

Switched over to https://fastly.linuxmint.io/ and works fine and is fast.

@myself42
Copy link

myself42 commented Apr 9, 2024

http://fastly.linuxmint.io @ Una is working OK (I didn't notice a difference compared to the local server) so 🚀

@rebelxt
Copy link

rebelxt commented Apr 9, 2024

Made the change in a Mint Cinnamon 21.3 test bed under VirtualBox. Worked without error. It wasn't slow. But, I never change the Main mirror anyway, only the Base. So I don't have any idea if it is helping.

@HeidiKabel
Copy link

I also get an error message with the https - it says the mirror is unavailable:

grafik

@HeidiKabel
Copy link

And the http site gives me the same error:

grafik

@anaximeno
Copy link

anaximeno commented Apr 9, 2024

@HeidiKabel what is the version of mint you are currently on? Also, the issue persists after clicking to reload?

@bhilmers
Copy link

bhilmers commented Apr 9, 2024

🚀 I am in Chicago and think the CDN was maybe slightly faster, but that's just a feeling.

@Condobloke
Copy link

Condobloke commented Apr 9, 2024

image

Arrived prior to being available on default settings (2nd PC)
All of the updates downloaded, installed and finished in under 10 seconds
Location: Australia, Eastern Coast.

@clefebvre
Copy link
Member Author

clefebvre commented Apr 9, 2024

@karhima @HeidiKabel two questions...

  • Does the issue persist and always happen when you click Refresh in Mintupdate?
  • Can you paste the output of curl -i https://fastly.linuxmint.io/db/version?

@JerryF1257
Copy link

🚀

@andrewille
Copy link

Works fine for me. First, I downloaded spotify-client which was pretty slow (~1MB/s). The second time, right after, it was very fast. The caching seems to work really well.

@bencastan
Copy link

🚀

All good from Sydney Australia

@haggen88
Copy link

haggen88 commented Apr 10, 2024

h2gn@h2gn:~$ apt update
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Ign:3 http://fastly.linuxmint.io virginia InRelease
Get:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Get:5 http://fastly.linuxmint.io virginia Release [24,1 kB]
Get:6 http://fastly.linuxmint.io virginia Release.gpg [833 B]
Hit:7 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Get:8 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages [609 kB]
Get:9 http://fastly.linuxmint.io virginia/main i386 Packages [17,9 kB]
Get:10 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1.558 kB]
Get:11 http://fastly.linuxmint.io virginia/main amd64 Packages [18,5 kB]
Get:12 http://archive.ubuntu.com/ubuntu jammy-updates/universe i386 Packages [698 kB]
Get:13 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1.060 kB]
Get:14 http://fastly.linuxmint.io virginia/upstream i386 Packages [14,6 kB]
Get:15 http://fastly.linuxmint.io virginia/upstream amd64 Packages [48,8 kB]
Get:16 http://fastly.linuxmint.io virginia/import amd64 Packages [8.338 B]
Get:17 http://fastly.linuxmint.io virginia/import i386 Packages [3.678 B]
Get:18 http://fastly.linuxmint.io virginia/backport amd64 Packages [54,9 kB]
Get:19 http://fastly.linuxmint.io virginia/backport i386 Packages [8.307 B]
Fetched 4.355 kB in 5s (899 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

🚀 no problems at the moment

@biicwlim
Copy link

biicwlim commented Apr 10, 2024

http working fine here, https did not. Also, I had to disconnect from my VPN, but that has often been true on the default mirror; others I've tried have usually let me connect over VPN with no problem.

@carlosmintfan
Copy link

carlosmintfan commented Apr 22, 2024

Unfortunatedly, I don't get the error. @enrico3 could you enter sudo xed /usr/lib/linuxmint/mintUpdate/mintUpdate.py, then press Ctrl+I, then enter 1224, and then add the following lines below (indentation is important):

                    print(mint_timestamp)
                    print(mirror_timestamp)

so it should look like this:

                    # Only perform up-to-date checks when refreshing from the UI (keep the load lower on servers)
                    mint_timestamp = self.get_url_last_modified("http://packages.linuxmint.com/db/version")
                    mirror_timestamp = self.get_url_last_modified("%s/db/version" % mirror_url)
                    print(mint_timestamp)
                    print(mirror_timestamp)
                    if mirror_timestamp is None:

then save, close and execute mintupdate in a terminal, refresh and paste all output? Unfortunatedly I'm not surce I can really help here. Can you open fastly.linuxmint.io in your browser? Do you see the website then?

@enrico3
Copy link

enrico3 commented Apr 22, 2024

@carlosmintfan During the refresh I got this additional error (and then the same message as yesterday)
updateMgrErr
The error message as text:
Nicht alle Paketquellenindizes konnten heruntergeladen werden.
Die Anwendungspaketquelle steht möglicherweise nicht mehr zur Verfügung oder ist aufgrund von Netzwerkproblemen nicht erreichbar. Sofern für diese Anwendungspaketquelle noch eine ältere Paketliste verfügbar ist, wird diese verwendet. Anderenfalls wird diese Anwendungspaketquelle gänzlich ignoriert. Bitte überprüfen Sie Ihre Netzwerkverbindung und vergewissern Sie sich ebenfalls, dass die Adresse der Anwendungspaketquelle korrekt in den Einstellungen eingetragen ist.

GPG-Fehler: http://repository.spotify.com stable InRelease: Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY 6224F9941A8AA6D1Das Depot »http://repository.spotify.com stable InRelease« ist nicht signiert.Eine Aktualisierung von solch einem Depot kann nicht auf eine sichere Art durchgeführt werden, daher ist es standardmäßig deaktiviert.Weitere Details zur Erzeugung von Paketdepots sowie zu deren Benutzerkonfiguration finden Sie in der Handbuchseite apt-secure(8).https://repo.skype.com/deb/dists/stable/InRelease: Schlüssel ist im veralteten Schlüsselbund trusted.gpg gespeichert (/etc/apt/trusted.gpg), siehe den Abschnitt MISSBILLIGUNG in apt-key(8) für Details.

Terminal output:

khs@erazermint:~$ /usr/lib/linuxmint/mintUpdate/mintUpdate.py:1381: DeprecationWarning: Gdk.threads_init is deprecated
  Gdk.threads_init()
/usr/lib/linuxmint/mintUpdate/mintUpdate.py:1766: DeprecationWarning: Gdk.threads_enter is deprecated
  Gdk.threads_enter()
/usr/lib/linuxmint/mintUpdate/mintUpdate.py:803: DeprecationWarning: Gdk.threads_leave is deprecated
  Gdk.threads_leave()
Flatpak: done generating updates
(28, 'Resolving timed out after 5001 milliseconds')
1713804854
None
Flatpaks: timed out trying to refresh Command '['/usr/lib/linuxmint/mintUpdate/flatpak-update-worker.py', '--refresh']' timed out after 29.99996774200008 seconds
Flatpak: done generating updates
(28, 'Resolving timed out after 5000 milliseconds')
1713804854
None

I can open the page in the browser just fine. I have quite a slow connection here (16 MBit). Maybe that has to do with it somehow!?

@carlosmintfan
Copy link

Thanks @enrico3! Please open the mintUpdate.py again with the terminal command, press Ctrl+F and search for def get_url, then, change the print (e) which is some lines below def get_url_last_modified(self, url): to print ("error: ", e) (preserving the indentation that was before), save the file, then restart mintUpdate by typing mintupdate in the terminal again, and what I want to know is if the line (28, 'Resolving timed out after 5001 milliseconds') now looks like error: (28, 'Resolving timed out after 5001 milliseconds'). If that's the case, edit the c.setopt(pycurl.CONNECTTIMEOUT, 5) which is somewhere between the lines def get_url_last_modified(self, url): and the print line, and modify the 5 to a – let's say, to a 30. Save the file, run mintupdate in a terminal again, refresh and – is the error away now and the None in the terminal output a number too? It could indeed be that your internet connection is just slow and therefore 5 seconds aren't enough for connecting.

@enrico3
Copy link

enrico3 commented Apr 22, 2024

When I change the timeout to 30 the error message disappears and both timestamps show the same value!
Thank you for your support!

@carlosmintfan
Copy link

So @clefebvre it's just that. Now you have to decide how to deal with it.

@clefebvre
Copy link
Member Author

Well done guys!

@clefebvre
Copy link
Member Author

For those who get the error in mintupdate, can you run this and paste the output?

time curl -si https://fastly.linuxmint.io/db/version

@clefebvre
Copy link
Member Author

New Firefox 125.0.2 going live right now.

Fastly was configured with shielding and stale content delivery.

@midigark
Copy link

Still going strong.
Today's release of Firefox and dependencies - download 8 seconds.
All other updates have worked without errors or delays.

@kubcomputing
Copy link

Firefox 125.0.2~linuxmint1+faye at a possible 5 MB/s (Germany)
https://fastly.linuxmint.io: 2 MB/s
http://packages.linuxmint.com: 1,2 MB/s

@solt87
Copy link

solt87 commented Apr 23, 2024

Get:1 https://fastly.linuxmint.io virginia/upstream amd64 firefox amd64 125.0.2+linuxmint1+virginia [74,5 MB]
Get:2 https://fastly.linuxmint.io virginia/upstream amd64 firefox-locale-en amd64 125.0.2+linuxmint1+virginia [801 kB]
Get:3 https://fastly.linuxmint.io virginia/upstream amd64 firefox-locale-hu amd64 125.0.2+linuxmint1+virginia [573 kB]
Fetched 75,8 MB in 2min 16s (559 kB/s)                                                       

For me, this 559 kB/s was one of the slowest downloads on this machine, with this connection. (As stated in an earlier comment, speeds ten times as high are not uncommon.)

@Wibol
Copy link

Wibol commented Apr 23, 2024

🚀 Descargados 77,3 MB en 3s (25,0 MB/s)

@pucelev
Copy link

pucelev commented Apr 23, 2024

Firefox = 2 seconds download
🚀

@Xenophobe-01
Copy link

Upstate NY, FIOS 100/100 Mb fiber, just got the Firefox 125.0.2 update, download speed 4988 kB/s, 3-4 seconds tops, distinctly better this time. 🚀

@karhima
Copy link

karhima commented Apr 23, 2024

For those who get the error in mintupdate, can you run this and paste the output?

time curl -si https://fastly.linuxmint.io/db/version

~$ time curl -si https://fastly.linuxmint.io/db/version
HTTP/2 200
content-type: application/octet-stream
etag: "1949557024"
last-modified: Tue, 23 Apr 2024 14:57:54 GMT
server: Lighttpd
via: 1.1 varnish, 1.1 varnish
accept-ranges: bytes
date: Tue, 23 Apr 2024 18:58:24 GMT
age: 272
x-served-by: cache-chi-kigq8000075-CHI, cache-ams21080-AMS
x-cache: HIT, HIT
x-cache-hits: 2, 1
x-timer: S1713898705.969759,VS0,VE1
content-length: 31

3.3.2
3.3.0
bdb4.3.29
bdb4.3.0

real 0m0,381s
user 0m0,058s
sys 0m0,004s

@enrico3
Copy link

enrico3 commented Apr 23, 2024

Usually the values are in this range but sometimes the 'real' value jumps to 5s.

time curl -si https://fastly.linuxmint.io/db/version
HTTP/2 200
content-type: application/octet-stream
etag: "1949557024"
last-modified: Tue, 23 Apr 2024 14:57:54 GMT
server: Lighttpd
via: 1.1 varnish, 1.1 varnish
accept-ranges: bytes
date: Tue, 23 Apr 2024 19:34:00 GMT
age: 84
x-served-by: cache-chi-kigq8000075-CHI, cache-fra-etou8220133-FRA
x-cache: HIT, HIT
x-cache-hits: 6, 1
x-timer: S1713900840.471516,VS0,VE1
content-length: 31

3.3.2
3.3.0
bdb4.3.29
bdb4.3.0

real 0m0,220s
user 0m0,047s
sys 0m0,010s

@PDXsailor
Copy link

I'm not sure why the Update Manager shows an Ungoogled-Chromium update available but won't/can't actually download and install it. After authenticating the screen stays on the main update window; no download box appears. This happened with a different app a few days ago (don't remember which one). I repeated the update in both cases several times. It may have nothing to do with Fastly, of course.

@carlosmintfan
Copy link

I'm not sure why the Update Manager shows an Ungoogled-Chromium update available but won't/can't actually download and install it. After authenticating the screen stays on the main update window; no download box appears. This happened with a different app a few days ago (don't remember which one). I repeated the update in both cases several times. It may have nothing to do with Fastly, of course.

Can you run mintupdate from the command line and see if there are any errors in the output? (Besides the deprecation warnings, they don't matter.)

@PDXsailor
Copy link

Please ignore my post - it is a Flatpack app so is not coming through Fastly.

Also, mintupdate doesn't show any errors when attempting to update.

@glassesh2003
Copy link

glassesh2003 commented Apr 24, 2024 via email

@karhima
Copy link

karhima commented Apr 24, 2024

@PDXsailor Ungoogled Chromium explains that here (with steps how to resolve it): https://github.com/flathub/io.github.ungoogled_software.ungoogled_chromium
So yes, that's not Fastly related, package was renamed and now you have to do a flatpak update.

@PDXsailor
Copy link

@karhima Thanks for the info.

@bonsaihorn
Copy link

Done! Working fine...

@wbeebe
Copy link

wbeebe commented Apr 24, 2024

Testing it and happy with it using HTTPS URI 🚀.

@ignacionelson
Copy link

Working great! Thank you

@Sparifankal
Copy link

time curl -si https://fastly.linuxmint.io/db/version
HTTP/2 200
content-type: application/octet-stream
etag: "1042323668"
last-modified: Wed, 24 Apr 2024 17:36:25 GMT
server: Lighttpd
via: 1.1 varnish, 1.1 varnish
accept-ranges: bytes
age: 277
date: Sat, 27 Apr 2024 11:47:45 GMT
x-served-by: cache-chi-kigq8000075-CHI, cache-fra-etou8220144-FRA
x-cache: HIT, HIT
x-cache-hits: 1076, 0
x-timer: S1714218465.134020,VS0,VE1
content-length: 31

3.3.2
3.3.0
bdb4.3.29
bdb4.3.0

real 0m5,159s
user 0m0,087s
sys 0m0,005s

@carlosmintfan
Copy link

time curl -si https://fastly.linuxmint.io/db/version HTTP/2 200 content-type: application/octet-stream etag: "1042323668" last-modified: Wed, 24 Apr 2024 17:36:25 GMT server: Lighttpd via: 1.1 varnish, 1.1 varnish accept-ranges: bytes age: 277 date: Sat, 27 Apr 2024 11:47:45 GMT x-served-by: cache-chi-kigq8000075-CHI, cache-fra-etou8220144-FRA x-cache: HIT, HIT x-cache-hits: 1076, 0 x-timer: S1714218465.134020,VS0,VE1 content-length: 31

3.3.2 3.3.0 bdb4.3.29 bdb4.3.0

real 0m5,159s user 0m0,087s sys 0m0,005s

so here we have a real time that's more than 5 seconds
@clefebvre

@benmpl
Copy link

benmpl commented Apr 28, 2024

I've been using it for a couple of days now, everything works great so far :)

@DeI1ys
Copy link

DeI1ys commented Apr 29, 2024

🚀
I'm from Chicago so I didn't notice any difference.
apt update and update manager work fine.

@Velofil
Copy link

Velofil commented Apr 30, 2024

Working fine from Germany 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests