From: bugzilla-daemon@libre-riscv.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 185] Getting 502 Bad Gateway when accessing bugzilla from archive.org
Date: Thu, 02 Apr 2020 17:50:46 +0000
Message-ID: <bug-185-13-I2u38lAOhU@http.bugs.libre-riscv.org/> (raw)
In-Reply-To: <bug-185-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=185
Jacob Lifshay <programmerjake@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|--- |High
Severity|normal |critical
--- Comment #6 from Jacob Lifshay <programmerjake@gmail.com> ---
Now I'm getting 502 Bad Gateway from my local computer:
curl --verbose --ipv6 --no-progress-meter http://libre-riscv.org/ &> curl.log
produces:
* Trying 2a00:1098:82:f::1:80...
* Connected to libre-riscv.org (2a00:1098:82:f::1) port 80 (#0)
> GET / HTTP/1.1
> Host: libre-riscv.org
> User-Agent: curl/7.69.1
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 502 Bad Gateway
< Server: nginx
< Date: Thu, 02 Apr 2020 17:44:04 GMT
< Content-Type: text/html
< Content-Length: 166
< Connection: keep-alive
<
{ [166 bytes data]
* Connection #0 to host libre-riscv.org left intact
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
Either we should fix the server's config or remove the IPv6 DNS entry, since it
works through IPv4.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next parent reply index
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-185-13@http.bugs.libre-riscv.org/>
2020-04-02 17:50 ` bugzilla-daemon [this message]
2020-04-02 18:26 ` [libre-riscv-dev] [Bug 185] Getting 502 Bad Gateway bugzilla-daemon
2020-04-03 18:32 ` bugzilla-daemon
2020-04-03 18:50 ` bugzilla-daemon
2020-04-06 21:32 ` bugzilla-daemon
2020-04-06 21:55 ` bugzilla-daemon
2020-04-07 11:02 ` bugzilla-daemon
2020-04-07 11:21 ` bugzilla-daemon
2020-04-07 11:35 ` bugzilla-daemon
2020-04-07 11:37 ` bugzilla-daemon
2020-04-07 14:58 ` bugzilla-daemon
2020-04-07 15:01 ` bugzilla-daemon
2020-04-07 15:04 ` bugzilla-daemon
2020-04-07 15:31 ` bugzilla-daemon
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-185-13-I2u38lAOhU@http.bugs.libre-riscv.org/ \
--to=bugzilla-daemon@libre-riscv.org \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git