Why is fdroid down all the time?


#1

Clicking on update repos just spins endlessly with no way to kill it other than force closing the app, which is a separate issue in itself. If you need funds for better hosting, can you please display some goal prominently on the website ?


API version Survey
#2

Happens to me whole day too… It seems when f-droid.org resolves to ‘5.9.48.82’, the initial TCP SYN takes from several seconds to half a minute or even longer (or timeouts)… And it look very overloaded even when 3way handshake is established.

Happens both in F-DROID app and manually on the web from laptop. However now that my browser decided to use other IPv4 address ‘107.150.51.2’ it works just fine.

for example, one of the faster (!) connects look like:

01:26:03.799483 IP 192.168.9.57.43402 > 5.9.48.82.443: Flags [S], seq 4167860780, win 29200, options [mss 1460,sackOK,TS val 83021689 ecr 0,nop,wscale 7], length 0
01:26:04.817402 IP 192.168.9.57.43402 > 5.9.48.82.443: Flags [S], seq 4167860780, win 29200, options [mss 1460,sackOK,TS val 83021944 ecr 0,nop,wscale 7], length 0
01:26:06.833402 IP 192.168.9.57.43402 > 5.9.48.82.443: Flags [S], seq 4167860780, win 29200, options [mss 1460,sackOK,TS val 83022448 ecr 0,nop,wscale 7], length 0
01:26:10.993118 IP 192.168.9.57.43402 > 5.9.48.82.443: Flags [S], seq 4167860780, win 29200, options [mss 1460,sackOK,TS val 83023488 ecr 0,nop,wscale 7], length 0
01:26:11.024943 IP 5.9.48.82.443 > 192.168.9.57.43402: Flags [S.], seq 1329971975, ack 4167860781, win 28960, options [mss 1460,sackOK,TS val 115574504 ecr 83023488,nop,wscale 7], length 0
01:26:11.025040 IP 192.168.9.57.43402 > 5.9.48.82.443: Flags [.], ack 1, win 229, options [nop,nop,TS val 83023495 ecr 115574504], length 0
01:26:11.025425 IP 192.168.9.57.43402 > 5.9.48.82.443: Flags [P.], seq 1:207, ack 1, win 229, options [nop,nop,TS val 83023496 ecr 115574504], length 206
01:26:11.071037 IP 5.9.48.82.443 > 192.168.9.57.43402: Flags [.], ack 207, win 235, options [nop,nop,TS val 115574512 ecr 83023496], length 0

I’ve e-mail the f-droid team so hopefully someone will notice and resolve problem (tried IRC, but due to DDoS they don’t give voice to unregistered users :frowning: )


#3

Why is fdroid down all the time?

It was rarely “down”, but I do see it being “slow” to respond.

Ping @hans


#4

Try adding a mirror:


#5

@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.


#6

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


#7

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


#8

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.)


#9

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


#10

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


#11

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


#12

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!


#13

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


#14

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.


#15

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 ?


#16

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


#17

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.


#18

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


#19

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.


#20

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