From: 宋文武 <iyzsong@envs.net>
To: "Diederich, Stefan" <Stefan.Diederich@unimedizin-mainz.de>
Cc: "'help-guix@gnu.org'" <help-guix@gnu.org>
Subject: Re: GUIX behind a proxy
Date: Mon, 24 Oct 2022 15:22:14 +0800 [thread overview]
Message-ID: <87czahr8ih.fsf@envs.net> (raw)
In-Reply-To: <f155d011bb7c497598830550396a9e19@unimedizin-mainz.de> (Stefan Diederich's message of "Fri, 21 Oct 2022 11:26:53 +0000")
"Diederich, Stefan" <Stefan.Diederich@unimedizin-mainz.de> writes:
> Dear Sir or Madame,
>
> I installed guix with the installation script provided
>
> sudo sh guix-install.sh
>
> After this I added some the https_proxy and http_proxy to the environment in the file /etc/systemd/system/guix-daemon.service:
>
> # This is a "service unit file" for the systemd init system to launch
> # 'guix-daemon'. Drop it in /etc/systemd/system or similar to have
> # 'guix-daemon' automatically started.
>
> [Unit]
> Description=Build daemon for GNU Guix
>
> [Service]
> ExecStart=/var/guix/profiles/per-user/root/current-guix/bin/guix-daemon --build-users-group=guixbuild
> Environment='GUIX_LOCPATH=/var/guix/profiles/per-user/root/guix-profile/lib/locale' LC_ALL=en_US.utf8
> Environment='https_proxy=https://10.10.6.11:8080'
> Environment='http_proxy=http://10.10.6.11:8080'
> Environment='HTTP_PROXY=http://10.10.6.11:8080'
> Environment='HTTPS_PROXY=https://10.10.6.11:8080'
> [...]
>
> Is there anything I might have missed? Can someone help me with configuring guix behind a proxy?
>
Hello, I think the value of https_proxy should also be
'http://10.10.6.11:8080', not https. Unless you does have the proxy
server listen https, which usually not setup that way.
Hope it help!
prev parent reply other threads:[~2022-10-24 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 11:26 GUIX behind a proxy Diederich, Stefan
2022-10-21 19:26 ` Wojtek Kosior via
2022-10-24 7:22 ` 宋文武 [this message]
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=87czahr8ih.fsf@envs.net \
--to=iyzsong@envs.net \
--cc=Stefan.Diederich@unimedizin-mainz.de \
--cc=help-guix@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.
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).