Please accept all the main ToC changes to reflect this, plus I nitpicked the whole thing, listed it alphabetically, and created new sections where required.
Probably the Tor Browser stuff is another candidate for chopping down to size in the new “Anonymous Browsing” section I created, but lets focus on fixing links first.
Thanks @0brand - linked all your pics and edited Screenshots accordingly. Pity about success message, I thought it stayed there until closed by user (or it used to).
ha ha - I’ll let you work your technical magic and come sniffing later on
If you approve all that, it will be much easier to start fixing all the links from the 3 splits.
Plus, it improves the main ToC which is too chunky in that section I split into browsing, email & messengers, other anonymous services. (plus splitting off dev/license stuff into own section)
If you approve all that, it will be much easier to start fixing all the links from the 3 splits.
Plus, it improves the main ToC which is too chunky in that section I split into browsing, email & messengers, other anonymous services.
Sure. Thanks for letting me know that this blocks things so I will
prioritize it. (Previously I didn’t prioritize since it looked like a
time consuming change.)
Unfortunately the accept revision button is broken perhaps due to recent
changes. Already notified mig5. I’ll review as soon I hear it’s repaired.
Do you happen to know what time you saw this error (maybe UTC or CEST would be useful, to correlate with server time which is CEST, but whatever works for you if you can specify the timezone).
And/or what page you were editing at the time.
A 503 reported by Varnish means it couldn’t get a response from its backend Apache, which is a surprise to me, as that’s an area I didn’t touch recently (and I’ve touched a lot of areas! )
One theory is the logrotate daily cron or something reloaded Apache at just that precise time (e.g a fluke) but knowing what time you experienced this will be useful. Unfortunately Varnish doesn’t really log anything so it’s hard to debug further.
A 503 would also occur if some sort of timeout threshold was tripped between Varnish waiting for Apache to respond - e.g if you’re uploading a very large file that might occur. So a bit of context might help track this down, so far not seeing much in the logs other than a 503 on the ‘Screenshots’ wiki page at 10:11AM CEST or so…
Yes, that was me. I guess it was just a fluke(?) in timing.
Thanks for the education you’re giving everyone too in explaining things, it’s appreciated.
BTW phabricator used to be the real buggy Whonix sub-domain, often reporting some “clustered(?) exception error” (I think), and a refresh was required for the page to present properly.
@torjunkie yeah, the Phabricator issue was due to ‘too many connections’ MySQL errors - a side-effect of its peculiar database design - and we recently saw it even impacts the wiki since they share the same MySQL server. Both issues should not reoccur
The Varnish one remains a mystery, might need to add some logging and attempt to reproduce some other time. Curious if it was instantaneous or whether there was a long timeout first. Anyway, let me know if it occurs again.
OpenPGP Best Practices - riseup.net is nice although they recommend 3072 RSA which I see no reason for if we can easily use maximum key length 4096 RSA.
I’m holding off on edits until the main ToC page is approved i.e. as this prevents me finishing off recent weeks of work (and satisifying my editing OCD).