From: "Clément Lassieur" <clement@lassieur.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 32233-done@debbugs.gnu.org
Subject: bug#32233: Cuirass: Berlin web API times out
Date: Mon, 23 Jul 2018 13:54:43 +0200 [thread overview]
Message-ID: <87va96tbek.fsf@lassieur.org> (raw)
In-Reply-To: <87lga2tj3d.fsf@gnu.org>
Hello Ludovic,
Ludovic Courtès <ludo@gnu.org> writes:
> Hello,
>
> Clément Lassieur <clement@lassieur.org> skribis:
>
>> https://berlin.guixsd.org:8081/ times out.
>
> Note that Cuirass listens on localhost:8081, so you cannot reach it from
> the outside (and it’s HTTP, too.) There’s nginx that proxies things,
> see guix-maintenance.git.
Ha :-) I had forgotten about it! So it's not a bug at all, closing it.
> Now, with the version currently running, I can tell you that this URL is
> not very interesting:
>
> --8<---------------cut here---------------start------------->8---
> $ wget -O - http://localhost:8081
> --2018-07-23 11:06:22-- http://localhost:8081/
> Resolving localhost (localhost)... 127.0.0.1
> Connecting to localhost (localhost)|127.0.0.1|:8081... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2018-07-23 11:06:22 ERROR 404: Not Found.
> --8<---------------cut here---------------end--------------->8---
>
> :-)
Well yes, I was expecting 404, because even though it's not very
interesting, it shows that the url handler works.
> Is the Web UI already in the current ‘cuirass’ package?
Soon! But I think we should change the NGINX config nonetheless because
the json API is useful.
> If so, what do we need to change in the nginx config?
I guess we could add:
--8<---------------cut here---------------start------------->8---
server {
listen 8081 ssl;
server_name berlin.guixsd.org;
ssl_certificate /etc/letsencrypt/live/berlin.guixsd.org/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/berlin.guixsd.org/privkey.pem;
# Make sure SSL is disabled.
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
# Disable weak cipher suites.
ssl_ciphers HIGH:!aNULL:!MD5;
ssl_prefer_server_ciphers on;
# Use our own DH parameters created with:
# openssl dhparam -out dhparams.pem 2048
# as suggested at <https://weakdh.org/sysadmin.html>.
ssl_dhparam /etc/dhparams.pem;
access_log /var/log/nginx/https.access.log;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Port $server_port;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
location / {
proxy_pass http://localhost:8081;
}
}
--8<---------------cut here---------------end--------------->8---
I can do the commit if you want (and agree with the content), as you
wish.
Clément
next prev parent reply other threads:[~2018-07-23 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 9:29 bug#32233: Cuirass: Berlin web API times out Clément Lassieur
2018-07-23 9:08 ` Ludovic Courtès
2018-07-23 11:54 ` Clément Lassieur [this message]
2018-07-23 14:52 ` Ludovic Courtès
2018-07-23 15:29 ` Clément Lassieur
2018-07-23 20:07 ` Ludovic Courtès
2018-07-23 20:12 ` Clément Lassieur
2018-07-29 23:25 ` Clément Lassieur
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=87va96tbek.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=32233-done@debbugs.gnu.org \
--cc=ludo@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).