From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>, rekado@elephly.net
Cc: guix-sysadmin <guix-sysadmin@gnu.org>,
Altadil <Altadil@protonmail.com>,
65056@debbugs.gnu.org
Subject: bug#65056: https://issues.guix.gnu.org/ cannot be accessed through Tor
Date: Sun, 13 Aug 2023 11:46:52 +0000 [thread overview]
Message-ID: <1504743B-0B78-4D42-AB22-F25CA2D0194D@tobias.gr> (raw)
In-Reply-To: <877cpzbxf4.fsf@gnu.org>
On 13 August 2023 00:25:51 UTC, "Ludovic Courtès" <ludo@gnu.org> wrote:
>I think it’s worse than this. I noticed that ci.guix.gnu.org (same
>machine) would occasionally time out on my side, without Tor, starting
>from this week (I was on vacation before, so I don’t know exactly when
>it started). From a browser, I get this “DoS attack” HTML page:
Oh, wow. This is new to me.
It's frustrating that $IT keeps adding new significant hurdles with apparently 0 communications, and that our only option is often 'ask rekado, again, to ask things, again'. That's not right.
Ricardo, do you think there's a chance this trend will improve (without you burning out)?
Otherwise, I'd like to suggest wireguarding berlin's impressive hardware resources to bayfront or to a new head node not hosted at the MDC, or something similarly provocative. Just give up on hosting public services there, like we already migrated the home page. This isn't meaningful redundancy.
Kind regards,
T G-R
Sent on the go. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2023-08-13 11:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 16:57 bug#65056: https://issues.guix.gnu.org/ cannot be accessed through Tor Altadil via Bug reports for GNU Guix
2023-08-04 19:21 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2023-08-04 19:29 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2023-08-13 0:25 ` Ludovic Courtès
2023-08-13 11:46 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2023-08-14 9:07 ` Ricardo Wurmus
2023-09-08 20:24 ` Ludovic Courtès
2023-09-12 8:02 ` Ricardo Wurmus
2023-09-12 13:06 ` Maxim Cournoyer
2023-09-14 21:25 ` Ludovic Courtès
2023-09-15 7:41 ` Ricardo Wurmus
2023-09-18 9:51 ` Ludovic Courtès
2023-09-20 21:31 ` Giovanni Biscuolo
2023-09-20 22:45 ` Ricardo Wurmus
2023-09-21 6:27 ` Giovanni Biscuolo
2023-10-02 8:48 ` Ludovic Courtès
2023-09-18 20:31 ` bug#65056: https://issues.guix.gnu.org available through Tor again Altadil via Bug reports for GNU Guix
2023-09-21 6:29 ` Giovanni Biscuolo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1504743B-0B78-4D42-AB22-F25CA2D0194D@tobias.gr \
--to=bug-guix@gnu.org \
--cc=65056@debbugs.gnu.org \
--cc=Altadil@protonmail.com \
--cc=guix-sysadmin@gnu.org \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).