diff --git a/doc/forum/git-remote-gcrypt_and_rsyncd/comment_1_34dd343ed75918f5969f6a23dfae3317._comment b/doc/forum/git-remote-gcrypt_and_rsyncd/comment_1_34dd343ed75918f5969f6a23dfae3317._comment
new file mode 100644
index 0000000000..02246cf558
--- /dev/null
+++ b/doc/forum/git-remote-gcrypt_and_rsyncd/comment_1_34dd343ed75918f5969f6a23dfae3317._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2023-11-28T16:06:22Z"
+ content="""
+That is a pretty weird error message! It looks like git-annex may have run
+git but tried to pass it a working directory that does not exist. It would
+be interesting to know what git command, passing --debug would tell you.
+
+But: The gcrypt special remote is documented as needing gitrepo=rsync:// to
+operate over ssh. And git-remote-gcrypt interprets a rsync:// url as rsync
+over ssh (see its man page). Yes, "host::" in rsync indicates direct contact
+to a rsync daemon, not using ssh, but that will not work with git-remote-gcrypt
+to the best of my knowledge.
+"""]]