# Ssh to nest not working

**URL:** <https://discourse.pijul.org/t/ssh-to-nest-not-working/1267>\
**Category:** Question\
**Created:** [February 19, 2025, 9:27pm UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267 "2025-02-19T21:27:47Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![19aklopf84](https://avatars.discourse-cdn.com/v4/letter/1/bc8723/32.png) [@19aklopf84](https://discourse.pijul.org/u/19aklopf84)\
**Post date:** [February 19, 2025, 9:27pm UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/1 "2025-02-19T21:27:47Z")

</div>

authentication works, but then it hangs

---

<div class="post-metadata">

**Author:** ![tankf33der](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/tankf33der/32/289_2.png) [@tankf33der](https://discourse.pijul.org/u/tankf33der)\
**Post date:** [February 20, 2025, 7:30am UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/2 "2025-02-20T07:30:11Z")

</div>

> [@Unable to push to the Nest](https://discourse.pijul.org/t/unable-to-push-to-the-nest/1214/10):
>
> The server-side has moved forward, while pijul remains stagnant. This can be easily fixed with a dirty hack at your own risk. cd pijul pijul remote I5GEGWCQIJKTINCFGJEEIVZXKU: https://nest.pijul.com/pijul/pijul pijul reset --force cargo update cd pijul-remote vi Cargo.toml # change thrussh = "0.34" to "0.35.6" cargo update cd .. cargo build --release cd pijul clone tankf33der@nest.pijul.com:tankf33der/picolisp # cloned cd picolisp # change something pijul rec -am"." pijul push -a # pushed P…

---

<div class="post-metadata">

**Author:** ![19aklopf84](https://avatars.discourse-cdn.com/v4/letter/1/bc8723/32.png) [@19aklopf84](https://discourse.pijul.org/u/19aklopf84)\
**Post date:** [February 22, 2025, 8:14pm UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/3 "2025-02-22T20:14:28Z")

</div>

I don’t have a pijul directory now. because ssh do not work…

---

<div class="post-metadata">

**Author:** ![tankf33der](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/tankf33der/32/289_2.png) [@tankf33der](https://discourse.pijul.org/u/tankf33der)\
**Post date:** [February 22, 2025, 8:33pm UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/4 "2025-02-22T20:33:52Z")

</div>

did you install pijul beta9 from crates first ?

---

<div class="post-metadata">

**Author:** ![19aklopf84](https://avatars.discourse-cdn.com/v4/letter/1/bc8723/32.png) [@19aklopf84](https://discourse.pijul.org/u/19aklopf84)\
**Post date:** [February 22, 2025, 8:47pm UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/5 "2025-02-22T20:47:29Z")

</div>

Beta9 with some package Manager in Windows…

---

<div class="post-metadata">

**Author:** ![tankf33der](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/tankf33der/32/289_2.png) [@tankf33der](https://discourse.pijul.org/u/tankf33der)\
**Post date:** [February 22, 2025, 8:49pm UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/6 "2025-02-22T20:49:46Z")

</div>

now clone pijul from nest via https and build pijul from nest

---

<div class="post-metadata">

**Author:** ![19aklopf84](https://avatars.discourse-cdn.com/v4/letter/1/bc8723/32.png) [@19aklopf84](https://discourse.pijul.org/u/19aklopf84)\
**Post date:** [February 22, 2025, 9:56pm UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/7 "2025-02-22T21:56:55Z")

</div>

i could clone and build. but when i try:  
ssh -T [nest.pijul.com](http://nest.pijul.com)  
…  
Authenticated to [nest.pijul.com](http://nest.pijul.com) ([3.254.166.252]:22) using “publickey”.  
debug1: channel 0: new session [client-session] (inactive timeout: 0)  
debug1: Entering interactive session.  
debug1: pledge: filesystem  
and then it stucks

---

<div class="post-metadata">

**Author:** ![tankf33der](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/tankf33der/32/289_2.png) [@tankf33der](https://discourse.pijul.org/u/tankf33der)\
**Post date:** [February 23, 2025, 6:46am UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/8 "2025-02-23T06:46:23Z")

</div>

why? Why? you do `ssh -T` against nest? 🙂 Do this for github.

At least do something useful. Do you have any questions about Pijul?

---

<div class="post-metadata">

**Author:** ![19aklopf84](https://avatars.discourse-cdn.com/v4/letter/1/bc8723/32.png) [@19aklopf84](https://discourse.pijul.org/u/19aklopf84)\
**Post date:** [February 23, 2025, 8:18am UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/9 "2025-02-23T08:18:22Z")

</div>

Because If use Clone with ssh, IT still ASK me for Passwort and it doesn’t work…

---

<div class="post-metadata">

**Author:** ![tankf33der](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/tankf33der/32/289_2.png) [@tankf33der](https://discourse.pijul.org/u/tankf33der)\
**Post date:** [February 23, 2025, 10:04am UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/10 "2025-02-23T10:04:24Z")

</div>

did you upload ssh pub key to nest ?

---

<div class="post-metadata">

**Author:** ![19aklopf84](https://avatars.discourse-cdn.com/v4/letter/1/bc8723/32.png) [@19aklopf84](https://discourse.pijul.org/u/19aklopf84)\
**Post date:** [February 23, 2025, 10:24am UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/11 "2025-02-23T10:24:40Z")

</div>

Yes, i don’t know why IT doesen’t Work…

---

<div class="post-metadata">

**Author:** ![tankf33der](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/tankf33der/32/289_2.png) [@tankf33der](https://discourse.pijul.org/u/tankf33der)\
**Post date:** [February 23, 2025, 10:47am UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/12 "2025-02-23T10:47:51Z")

</div>

perfect, we move fast to destination.  
now go and read how to fix it in link i post 3 days ago.

---

<div class="post-metadata">

**Author:** ![19aklopf84](https://avatars.discourse-cdn.com/v4/letter/1/bc8723/32.png) [@19aklopf84](https://discourse.pijul.org/u/19aklopf84)\
**Post date:** [February 23, 2025, 11:27am UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/13 "2025-02-23T11:27:38Z")

</div>

> pijul remote I5GEGWCQIJKTINCFGJEEIVZXKU: [pijul/pijul](https://nest.pijul.com/pijul/pijul) pijul  
> error: unrecognized subcommand ‘I5GEGWCQIJKTINCFGJEEIVZXKU:’

Usage: pijul remote [OPTIONS] [COMMAND]

For more information, try ‘–help’.

---

<div class="post-metadata">

**Author:** ![tankf33der](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/tankf33der/32/289_2.png) [@tankf33der](https://discourse.pijul.org/u/tankf33der)\
**Post date:** [February 23, 2025, 11:38am UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/14 "2025-02-23T11:38:49Z")

</div>

`pijul remote` is just command all next is output from it

---

<div class="post-metadata">

**Author:** ![19aklopf84](https://avatars.discourse-cdn.com/v4/letter/1/bc8723/32.png) [@19aklopf84](https://discourse.pijul.org/u/19aklopf84)\
**Post date:** [February 23, 2025, 12:58pm UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/15 "2025-02-23T12:58:13Z")

</div>

C:\Users\alexa\pijul\pijul\>cd pijul-remote

C:\Users\alexa\pijul\pijul\pijul-remote\>notepad Cargo.toml

C:\Users\alexa\pijul\pijul\pijul-remote\>cargo update  
Updating [crates.io](http://crates.io) index  
Locking 1 package to latest compatible version  
Updating thrussh v0.34.1 → v0.35.6  
Removing thrussh-libsodium v0.3.0  
note: pass `--verbose` to see 40 unchanged dependencies behind latest

C:\Users\alexa\pijul\pijul\pijul-remote\>cd …

C:\Users\alexa\pijul\pijul\>cargo build --release  
warning: C:\Users\alexa\pijul\pijul\pijul-remote\Cargo.toml: `default_features` is deprecated in favor of `default-features` and will not work in the 2024 edition  
(in the `keyring` dependency)  
Compiling libpijul v1.0.0-beta.10 (C:\Users\alexa\pijul\pijul\libpijul)  
warning: unexpected `cfg` condition value: `deterministic_hash`  
 → libpijul\src\lib.rs:79:7  
|  
79 | #[cfg(feature = “deterministic\_hash”)]  
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  
|  
= note: expected values for `feature` are: `canonical-path`, `default`, `flate2`, `ignore`, `lru-cache`, `mmap`, `ondisk-repos`, `path-slash`, `tar`, `tarball`, `tempfile`, `text-changes`, `zstd`, and `zstd-seekable`  
= help: consider adding `deterministic_hash` as a feature in `Cargo.toml`  
= note: see [https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html](https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html) for more information about checking conditional configuration  
= note: `#[warn(unexpected_cfgs)]` on by default

warning: unexpected `cfg` condition value: `deterministic_hash`  
 → libpijul\src\lib.rs:81:11  
|  
81 | #[cfg(not(feature = “deterministic\_hash”))]  
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  
|  
= note: expected values for `feature` are: `canonical-path`, `default`, `flate2`, `ignore`, `lru-cache`, `mmap`, `ondisk-repos`, `path-slash`, `tar`, `tarball`, `tempfile`, `text-changes`, `zstd`, and `zstd-seekable`  
= help: consider adding `deterministic_hash` as a feature in `Cargo.toml`  
= note: see [https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html](https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html) for more information about checking conditional configuration

warning: field `is_cyclic` is never read  
 → libpijul\src\diff\diff.rs:80:9  
|  
75 | pub struct Replacement {  
| ----------- field in this struct  
…  
80 | pub is\_cyclic: bool,  
| ^^^^^^^^^  
|  
= note: `Replacement` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis  
= note: `#[warn(dead_code)]` on by default

warning: field `conflict_type` is never read  
 → libpijul\src\diff\vertex\_buffer.rs:23:9  
|  
20 | pub struct Conflict {  
| -------- field in this struct  
…  
23 | pub conflict\_type: ConflictType,  
| ^^^^^^^^^^^^^  
|  
= note: `Conflict` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis

warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item  
 → libpijul\src\text\_encoding.rs:68:9  
|  
64 | / fn deserialize(deserializer: D) → Result\<Self, D::Error\>  
65 | | where  
66 | | D: serde::Deserializer\<'de\>,  
| |\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_- move the `impl` block outside of this associated function `deserialize`  
67 | {  
68 | impl\<'de\> Visitor\<'de\> for EncodingVisitor {  
| ^^^^^^^^^^-------^^^^^^^^^^---------------  
| | |  
| | `EncodingVisitor` is not local  
| `Visitor` is not local  
|  
= note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`  
= note: `#[warn(non_local_definitions)]` on by default

Compiling pijul-repository v0.0.1 (C:\Users\alexa\pijul\pijul\pijul-repository)  
Compiling pijul-identity v0.0.1 (C:\Users\alexa\pijul\pijul\pijul-identity)  
Compiling pijul-remote v1.0.0-beta.6 (C:\Users\alexa\pijul\pijul\pijul-remote)  
warning: `libpijul` (lib) generated 5 warnings  
Compiling pijul v1.0.0-beta.9 (C:\Users\alexa\pijul\pijul\pijul)  
warning: use of deprecated type alias `std::panic::PanicInfo`: use `PanicHookInfo` instead  
 → pijul\src\main.rs:149:5  
|  
149 | setup\_panic!();  
| ^^^^^^^^^^^^^^  
|  
= note: `#[warn(deprecated)]` on by default  
= note: this warning originates in the macro `$crate::setup_panic` which comes from the expansion of the macro `setup_panic` (in Nightly builds, run with -Z macro-backtrace for more info)

warning: use of deprecated type alias `std::panic::PanicInfo`: use `PanicHookInfo` instead  
 → pijul\src\main.rs:149:5  
|  
149 | setup\_panic!();  
| ^^^^^^^^^^^^^^  
|  
= note: this warning originates in the macro `$crate::setup_panic` which comes from the expansion of the macro `setup_panic` (in Nightly builds, run with -Z macro-backtrace for more info)

warning: use of deprecated associated function `chrono::NaiveDateTime::from_timestamp_opt`: use `DateTime::from_timestamp` instead  
 → pijul\src\commands\record.rs:268:44  
|  
268 | chrono::NaiveDateTime::from\_timestamp\_opt(t, 0).unwrap(),  
| ^^^^^^^^^^^^^^^^^^

warning: use of deprecated associated function `chrono::NaiveDateTime::from_timestamp_opt`: use `DateTime::from_timestamp` instead  
 → pijul\src\commands\tag.rs:291:40  
|  
291 | chrono::NaiveDateTime::from\_timestamp\_opt(t, 0).unwrap(),  
| ^^^^^^^^^^^^^^^^^^

warning: `pijul` (bin “pijul”) generated 4 warnings  
Finished `release` profile [optimized] target(s) in 1m 03s

C:\Users\alexa\pijul\pijul\>cd  
C:\Users\alexa\pijul\pijul

C:\Users\alexa\pijul\pijul\>pijul clone 19aklopf84@nest.pijul.com:19aklopf84/mynewproject  
Warning: Unable to automatically authenticate with server. Please make sure your SSH keys have been uploaded to the Nest.  
For more information, please visit [Uploading public keys - The Pijul manual](https://pijul.org/manual/the_nest/public_keys.html#ssh-public-keys)  
Error: Not authenticated. Please check your credentials and try again.

C:\Users\alexa\pijul\pijul\>

---

<div class="post-metadata">

**Author:** ![19aklopf84](https://avatars.discourse-cdn.com/v4/letter/1/bc8723/32.png) [@19aklopf84](https://discourse.pijul.org/u/19aklopf84)\
**Post date:** [February 23, 2025, 1:00pm UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/16 "2025-02-23T13:00:40Z")

</div>

my ssh config:

# Pijul Nest SSH-Zugang

Host [nest.pijul.com](http://nest.pijul.com)  
User 19aklopf84  
IdentityFile C:\Users\alexa.ssh\id\_ed25119  
IdentitiesOnly yes  
PreferredAuthentications publickey  
LogLevel DEBUG

---

<div class="post-metadata">

**Author:** ![tankf33der](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/tankf33der/32/289_2.png) [@tankf33der](https://discourse.pijul.org/u/tankf33der)\
**Post date:** [February 23, 2025, 3:09pm UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/17 "2025-02-23T15:09:07Z")

</div>

pijul not using ssh config.

---

<div class="post-metadata">

**Author:** ![19aklopf84](https://avatars.discourse-cdn.com/v4/letter/1/bc8723/32.png) [@19aklopf84](https://discourse.pijul.org/u/19aklopf84)\
**Post date:** [February 23, 2025, 3:31pm UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/18 "2025-02-23T15:31:00Z")

</div>

ok i gave ssh config away. if i want to clone, it asks me for password.

---

<div class="post-metadata">

**Author:** ![tankf33der](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/tankf33der/32/289_2.png) [@tankf33der](https://discourse.pijul.org/u/tankf33der)\
**Post date:** [February 23, 2025, 3:51pm UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/19 "2025-02-23T15:51:17Z")

</div>

did you upload _correct_ key to nest?

---

<div class="post-metadata">

**Author:** ![19aklopf84](https://avatars.discourse-cdn.com/v4/letter/1/bc8723/32.png) [@19aklopf84](https://discourse.pijul.org/u/19aklopf84)\
**Post date:** [February 23, 2025, 4:05pm UTC](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267/20 "2025-02-23T16:05:54Z")

</div>

yes i uploaded correct key

[Next page](https://discourse.pijul.org/t/ssh-to-nest-not-working/1267.md?page=2)