Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

I am using a Macbook SSH terminal and generated RSA key pairs and uploaded remote id_rsa.pub with approved permissions. I can connect with remote Apache web server. I can create, open, move, modify and on preliminary inspection can manage files on the web server, no problem ... and generate no error messages.

Surprisingly I can not scp a folder nor document from my desktop to the remote server. Nor can I scp a folder or document from the remote server to my desktop. Each time I receive the error message:

stdin: is not a tty

The scp command to or from the remote web server does not work with either absolute or relative file location references.

My standard syntax looks like this:

From local host:

scp -rp ~/Desktop/foldername username@secureremoteserver.com:~/public_html

From remote host:

scp -rp username@secureremoteserver.com:~/public_html/foldername ~/Desktop/

It appears to be an issue with the stdin: is not a tty error message.

What's going on?

If this error is preventing the file transfers, how do I resolve the stdin: is not a tty?

share|improve this question
    
Yes I tried full path and every permutation, same error with rsync. –  user2217265 Mar 29 '13 at 17:18
    
Server does not recognize my local desktop for these commands ... I assume the 'stdin: is not a tty' error message is definitely at the root of the problem. -- thanks, cb –  user2217265 Mar 29 '13 at 17:20
    
please edit your post to include that information. –  strugee Nov 18 '13 at 7:02
    
Please try scp -v (verbose mode) and post its output. –  n.st Dec 25 '13 at 15:36
    
Oops, this one's old! My suggestion still applies, though, if you haven't found a solution yet. –  n.st Dec 25 '13 at 15:37
show 1 more comment

1 Answer

I am not sure if it matters on OSX sshd implementation but on some systems, when you don't have a tty, the implied home directory with ~/ convention, may not expand and you may get some unexpected results. I know it is not a sure thing but please try with full path names, instead of ~/ construct.

share|improve this answer
    
It seems that even providing a full path, the remote server does not recognize the location of the local directory and file and oddly offers a reference to being unable to locate the local directory and file ... giving a url that refers to the 'remote' root. Weird and frustrating. –  user2217265 Apr 2 '13 at 1:13
    
Does not seem to work with absolute url. Remote server gives error essentially unable to locate the local directory and file to copy. –  user2217265 Apr 2 '13 at 2:00
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.