From: Felix Lechner via <help-guix@gnu.org>
To: "dabbede@gmail.com" <dabbede@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Connection refused to Guix-hosted SSH
Date: Fri, 14 Oct 2022 10:06:11 -0700 [thread overview]
Message-ID: <CAFHYt56Jia-VA0_G-wdvZJN0SEejiTkhZc7u5JKreeS=pfKtOA@mail.gmail.com> (raw)
In-Reply-To: <CAEwYQ4TZhq2+9PBHRuKV1B=FMzmchw+1Dx1vwQ9Se4MfaJEENA@mail.gmail.com>
Hi,
On Fri, Oct 14, 2022 at 1:54 AM dabbede@gmail.com <dabbede@gmail.com> wrote:
>
> Finally, I also tried to manually start sshd on port 2222
I think that is a fabulous idea, especially if you can prevent
daemonization with -d (or -D).
> this is the output /etc/ssh/sshd_config: No such file or directory
The sshd_config is in /gnu/store. It is generated by 'guix system
reconfigure'. You can see all available versions with
ls -ld /gnu/store/*sshd-config
In a bind, I would pick one that should work and pass it via -f.
To find the version that is actually used by your current system
generation and corresponds to your latest config.scm would require
some sleuthing. You may have to examine the symbolic links in the
system profile and, possibly, in /gnu/store. You may be able to get
better advice about that in #guix on IRC.
Either way, please do not make any manual changes to /gnu/store,
however tempting it may appear.
Kind regards
Felix Lechner
next prev parent reply other threads:[~2022-10-14 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 20:22 Connection refused to Guix-hosted SSH dabbede
2022-10-13 5:30 ` Oleg Pykhalov
2022-10-14 8:27 ` dabbede
2022-10-13 21:04 ` Felix Lechner via
2022-10-14 8:54 ` dabbede
2022-10-14 17:06 ` Felix Lechner via [this message]
2022-10-14 20:01 ` dabbede
2022-10-14 20:18 ` Felix Lechner via
2022-10-19 18:54 ` Efraim Flashner
2022-10-19 19:39 ` dabbede
2022-10-15 6:01 ` Oleg Pykhalov
2022-10-16 7:53 ` dabbede
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='CAFHYt56Jia-VA0_G-wdvZJN0SEejiTkhZc7u5JKreeS=pfKtOA@mail.gmail.com' \
--to=help-guix@gnu.org \
--cc=dabbede@gmail.com \
--cc=felix.lechner@lease-up.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.