diff --git a/doc/bugs/assistant_cannot_set_up_remote_repo_via_an_ssh_alias_or_an_ip_address.mdwn b/doc/bugs/assistant_cannot_set_up_remote_repo_via_an_ssh_alias_or_an_ip_address.mdwn
new file mode 100644
index 0000000000..68e4180230
--- /dev/null
+++ b/doc/bugs/assistant_cannot_set_up_remote_repo_via_an_ssh_alias_or_an_ip_address.mdwn
@@ -0,0 +1,22 @@
+What steps will reproduce the problem?
+
+Using the assistant, create an SSH remote.  Try to use an alias as the name of the remote (e.g. I have a server which I have aliased to "homeworld" in my .ssh/config.  When I'm at home, that is an alias for 192.168.1.253.  When I'm not at home, I edit .ssh/config so that "homeworld" becomes an alias for a hostname at no-ip.com.)  Despite the fact that "homeworld" is a viable ssh target because of the alias, the assistant doesn't recognize it as a valid host to ssh to.
+
+I had trouble with an ip address the first time I tried it but just tried it again and it worked fine, so please disregard that part of the title of this bug report.
+
+
+What is the expected output? What do you see instead?
+
+expected output = move to the "create a repository -- rsync or regular" page.
+observed output = "cannot resolve host name"
+
+
+What version of git-annex are you using? On what operating system?
+
+ Version: 3.20130102 OS X Lion
+
+
+Please provide any additional information below.
+
+I realize this is kind of a power user whine.  Using an ssh alias which does not correspond to an actual resolvable hostname (and cannot, because it's supposed to be a layer of indirection over the hostname) is not an everyday problem for an average user.
+