Why is fdroid down all the time?

Try adding a mirror:

2 Likes

@hans for the average Joe (uh, unfortunately including me): How does one add a mirror? Like any other repo, and the app automatically recognizes it as mirror for the corresponding repo? In Settings › Repositories I couldn’t find a way to add a mirror to a specific repo.

Click on a mirror URL on your device, send it to F-Droid, click “Add Mirror”

2 Likes

Oh! That was easy (thanks to the QR Code scanner). And now: How can I remove a mirror?

https://www.popularmechanics.com/home/interior-projects/how-to/a2205/4227455/ (I’m sorry, my good friend. Sometimes I can’t stop myself. Forgive me.)

Thanks. I was able to add the mirrors. Btw, the first mirror also seems to be down, at least for me.

The mirror monitor also saw that, but its back up:
https://fdroid.gitlab.io/mirror-monitor

1 Like

Why aren’t those actual repo links there on that page?

because I suck at HTML and that uses a library that directly converts a
Python dict into an HTML table. I’d love it if someone improved it!

1 Like

Is there an issue with the site? It loads exceptionally slow these days :frowning:

Some people are seeing that, I haven’t seen it. It would be useful to troubleshoot it. Today’s index update includes setting 3 official mirrors, so that should hopefully reduce any load on f-droid.org directly.

I’m still seeing occasional issues with catalog not updating despite adding the mirrors. I think it’s less frequent than before, but it still happens, at which point I need to force close the app. Is there an existing bug for the force close issue ?

This continues to be a problem. I don’t think the mirrors are doing much. I don’t know if they are used at all. The client still seems to get stuck on “connecting to f-droid.org”. Additionally, there are several failed to connect messages in the logcat

01-30 09:26:48.286 13006 13064 E ImageLoader: https://f-droid.org/repo/icons-320/io.github.lonamiwebs.stringlate.1007.xml
01-30 09:26:48.286 13006 13064 E ImageLoader: java.io.FileNotFoundException: https://f-droid.org/repo/icons-320/io.github.lonamiwebs.stringlate.1007.xml
01-30 09:26:48.489 13006 13063 E ImageLoader: https://f-droid.org/repo/icons-320/com.termux.66.xml
01-30 09:26:48.489 13006 13063 E ImageLoader: java.io.FileNotFoundException: https://f-droid.org/repo/icons-320/com.termux.66.xml
01-30 09:27:00.414 13006 13063 E ImageLoader: https://f-droid.org/repo/icons-320/com.termux.66.xml
01-30 09:27:00.414 13006 13063 E ImageLoader: java.io.FileNotFoundException: https://f-droid.org/repo/icons-320/com.termux.66.xml
01-30 09:35:32.364 13226 13525 E ImageLoader: failed to connect to f-droid.org/107.150.51.2 (port 443) from /192.168.1.231 (port 46037) after 10000ms
01-30 09:35:32.364 13226 13525 E ImageLoader: java.net.SocketTimeoutException: failed to connect to f-droid.org/107.150.51.2 (port 443) from /192.168.1.231 (port 46037) after 10000ms
01-30 09:35:38.533 13226 13520 E ImageLoader: https://f-droid.org/repo/icons-320/com.iskrembilen.quasseldroid.1096.xml
01-30 09:35:38.533 13226 13520 E ImageLoader: java.io.FileNotFoundException: https://f-droid.org/repo/icons-320/com.iskrembilen.quasseldroid.1096.xml
01-30 09:35:58.143 13226 13515 E ImageLoader: failed to connect to f-droid.org/107.150.51.2 (port 443) from /192.168.1.231 (port 46052) after 10000ms
01-30 09:35:58.143 13226 13515 E ImageLoader: java.net.SocketTimeoutException: failed to connect to f-droid.org/107.150.51.2 (port 443) from /192.168.1.231 (port 46052) after 10000ms
01-30 09:36:08.069 13226 13524 E ImageLoader: https://f-droid.org/repo/icons-320/com.termux.66.xml
01-30 09:36:08.069 13226 13524 E ImageLoader: java.io.FileNotFoundException: https://f-droid.org/repo/icons-320/com.termux.66.xml

Seeing the same (the slowness, didn’t look in logcat yet).

Basically, it takes 1 minute to start the index update, then 5 minutes to start to download whatever app I choose to install. Once started it goes really fast, but the initial part it just sits there, also looking in the network traffic (via NetGuard) in the first 3 minutes the server was not even contacted.

No mirror was ever used.

Guys this may happen sometimes, but honestly i never faced any issues with this website. Maybe it depends on the location too.

We definitely need more info to track this down, things like @boomhauer’s log snippet are definitely helpful. Which version of F-Droid made that log output?

Personally, I have seen slowness but rarely have I seen installs totally fail to download. But mostly, I get updates fully in the background.

This is with 1.5.1. I can also confirm @Licaon_Kter’s general findings. The following points may need to be investigated:

  • Whether this is an ipv6 issue
  • Whether mirrors are useful. Ideally, all of app’s functionality should work if f-droid.org has been blocked at the network level and mirrors have been added.
  • There’s no way to remove mirrors at the moment short of clearing all app data

I’m currently working on making the Android client app more aggressitvely switch to mirrors. If all goes well, there will be an alpha release out within a week that will have a new Expert preference to enable this new behavior.

3 Likes

This also also include switches per mirror to selectively disable:

4 Likes

Guys, can you please get better hosting ? I am more than happy to pay. I don’t know what the situation with mirrors is in 1.6 (I’m having some other trouble with 1.6), but the main f-droid site is rarely usable. F-Droid is down at the moment and I get the “error getting index file” error. f-droid has become so unusable that I have replaced all my f-droid apps with play store versions wherever possible. I only use f-droid for the few apps like adaway that are not on playstore.