From: Christina O'Donnell <cdo@mutix.org>
To: guix-devel@gnu.org, 68920@debbugs.gnu.org
Subject: bug#68920: Issues with issues.guix.gnu.org (502 Bad Gateway)
Date: Sat, 3 Feb 2024 20:34:37 +0000 [thread overview]
Message-ID: <4dd113ef-8bcf-c48b-548f-29b23b87cfbe@mutix.org> (raw)
Message-ID: <20240203203437.fDIv7xoy-D7YVC4U5UEAY2a5XpsIeWMWxDUCQFR_tMk@z> (raw)
In-Reply-To: <CAJsg1E-WuC29rYVRndnhz8bnUzt34Y76e5_cv=Kfrx_HqZ8AhQ@mail.gmail.com>
Hi Guix,
From my machine[1] connecting to https://issues.guix.gnu.org/ results
in, after 130 seconds[2], a 502 bad gateway. It's been having issues for
over a week, but I only just found a need to test it.
I couldn't see an issue about it on debbugs so I thought it prudent to
raise an issue.
Reproduced with curl, firefox, and ungoogled-chromium on the main page
and on specific issues.
It appears to be under a lot of load.
Kind regards,
- Christina
[1] based in Cambridge, UK, and via my VPS in Dusseldorf, Germany on
2024-02-03 19:30 UTC+0
[2] Rather consistently 130-140 seconds from both UK and Dusseldorf.
Apparently the server is in Berlin.
next prev parent reply other threads:[~2024-02-04 3:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 19:42 issues.guix.gnu.org seems stop updating Andy Tai
2023-12-08 22:12 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-08 22:29 ` Maxim Cournoyer
2023-12-09 0:53 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-09 11:05 ` Ludovic Courtès
2024-02-03 20:34 ` Christina O'Donnell [this message]
2024-02-03 20:34 ` bug#68920: Issues with issues.guix.gnu.org (502 Bad Gateway) Christina O'Donnell
2024-02-04 5:33 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-02-04 10:56 ` Christina O'Donnell
2024-02-04 10:56 ` bug#68920: " Christina O'Donnell
2024-02-06 14:22 ` Maxim Cournoyer
2024-02-06 15:55 ` Andreas Enge
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=4dd113ef-8bcf-c48b-548f-29b23b87cfbe@mutix.org \
--to=cdo@mutix.org \
--cc=68920@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
/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).