Your f-droid repo is down

[haverholm]

Describe the bug The microG repo is not available from F-droid app or browser.

To Reproduce Steps to reproduce the behavior:

1. Update repos in F-droid app or
2. Navigate to repo URL in browser
3. See error

Do I need to fill out expected behaviour, etc?

[Wojtaz0w]

It works for me in Poland

[haverholm]

And it's back up in Sweden as well. Weird.

I wouldn't have posted the issue if it hadn't given error messages twice in a row in the app, which then made me test the repo in a browser. This looks like intermittent connection failure, but probably worth looking into never the less?

[Sapiosenses]

And it's back up in Sweden as well. Weird.

I wouldn't have posted the issue if it hadn't given error messages twice in a row in the app, which then made me test the repo in a browser. This looks like intermittent connection failure, but probably worth looking into never the less?

The entire microg.org website went down a few days ago.

I cannot get it to respond properly right now. (I'm in the USA)

Nor can I figure out the best place to report this, especially since the website is down.

(Though at this point many others must have reported it)

[mar-v-in]

There have been some network issues on the server recently, but those should be solved since Dec 5. So if you still see any connection issues, please double-check it's not on your end

[Sapiosenses]

There have been some network issues on the server recently, but those should be solved since Dec 5. So if you still see any connection issues, please double-check it's not on your end

Hi Marvin,

Here in San Francisco CA USA I have tried a variety of browsers from every major browser platform (Chromium, Mozilla, Webkit/Safari) on various OS's from Linux, macOS, Windows, Android and iOS on a variety of different internet providers and they are all giving a 404 for either "microg.org" or "www.microg.org" since probably Monday or so. (It's possible it was working at some point in between those days but that's the range of time I know of.)

A user reported it in my microG support group on Monday.

Perhaps your hosting provider's web accelerator or a CDN is caching a bad copy of the page, and it's only routing traffic from that cache to certain regions or something?

FYI both of those hostnames resolve here to 109.230.233.131 and that netblock is registered to you.

[Sapiosenses]

BTW pings to 109.230.233.131 are working fine from here, latency is ~180ms. (I have a slow local last hop of about 30-35ms)

[mar-v-in]

There is not web accelerator or CDN involved in the microg.org website. If anything, there is DDoS protection at ISP level, but that wouldn't be able to intercept TLS.

A 404 would be very weird. Even at the times of network issues, the server would've never returned 404 for the main page.

Does it happen when you access the website with or without TLS?

[Sapiosenses]

I'm just entering the simple hostname, it shows up as a non-encrypted page and 404

[Sapiosenses]

If you'd like to give me another good internal URL to test on that server I can try that

[Sapiosenses]

OK, if I explicitly enter it as a SSL URL it is working here.

[Sapiosenses]

So perhaps an issue with SSL forwarding or something. (Or whatever they call it when an incoming request does not request SSL and the server rewrites it with "https://" prefix)

[Sapiosenses]

However if I try that explilcit SSL tactic with Fennec Android, it complains that it does not trust the certificate for "https://www.microg.org".

[Sapiosenses]

Qualys SSL tester reports that there is a certificate name mismatch:

https://www.ssllabs.com/ssltest/analyze.html?d=www.microg.org&ignoreMismatch=on&latest

[Sapiosenses]

Using explicit SSL on Safari /macOS shows this error:

[Sapiosenses]

As the Qualys test implies, apparently Chrome doesn't care about that mismatch but Mozilla, Apple, Java and Windows do.

[Sapiosenses]

And a Chromium based browser on Android (Vivaldi) when loading via explicit SSL doesn't care, loads the page with no complaint.

Same with Bromite. 404 with plain or non-SSL url, no complaints at all using explicit SSL URL.