Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
Forum Thread Details
  • Replies 5 replies
  • Subscribers 665 subscribers
  • Views 667 views
  • Users 0 members are here
Related

FTP pi

gam3t3ch

Trying to ftp into my pi

 

I get this:

STATUS:>    Connecting to 192.168.1.24

STATUS:>    Socket connected. Waiting for welcome message...

    SSH-2.0-OpenSSH_6.7p1 Raspbian-5+deb8u3

 

then that's about it.

 

using my pi login info and tried root as well same result. as well as on port 22.

 

Sure I am pretty sleepy at the moment and still at work so having a huge brain fart anyone able to lead me into the right direction

 

image

 

I am able to ssh into the pi tho.

 

Any help would be great.  have the pi setup as a webserver at the moment. just would like to use ftp for building a site and testing on the pi.

Parents

  • Hi Wesley,

     

    You seem to be connecting to the SSH port, the one numbered 22.

     

    That port is used to gain shell access to the pi. FTP is an old fashioned protocol that works on port 21.

     

    Now when you have shell access you can run a program on both ends and transfer files like that. That's what SFTP, SCP and RSYNC all do.

     

    So if you're using an old FTP program but adjusting the port number to that of SSH, the program and the server-program will be talking different protocols. That can't work. You could use something like "sftp" or "scp" to copy files across.


    To be honest: I prefer "rsync" (even though it is not installed by default on the pi). When nothing special is going on, I'm just typing two letters more than scp. But when for example a big transfer needs to be stopped and restarted, rsync is way better. The most common case is when I tell rsync to copy a bunch of data but it then starts copying data that don't need copying or can wait for later. So then I abort the transfer and restart while excluding the non-needed data. That's much more efficient when you're using rsync.

Reply

  • Hi Wesley,

     

    You seem to be connecting to the SSH port, the one numbered 22.

     

    That port is used to gain shell access to the pi. FTP is an old fashioned protocol that works on port 21.

     

    Now when you have shell access you can run a program on both ends and transfer files like that. That's what SFTP, SCP and RSYNC all do.

     

    So if you're using an old FTP program but adjusting the port number to that of SSH, the program and the server-program will be talking different protocols. That can't work. You could use something like "sftp" or "scp" to copy files across.


    To be honest: I prefer "rsync" (even though it is not installed by default on the pi). When nothing special is going on, I'm just typing two letters more than scp. But when for example a big transfer needs to be stopped and restarted, rsync is way better. The most common case is when I tell rsync to copy a bunch of data but it then starts copying data that don't need copying or can wait for later. So then I abort the transfer and restart while excluding the non-needed data. That's much more efficient when you're using rsync.

Children
  • in reply to rew

    cool will look into rsync.   ya I thought it would have been a good time to get the pi server back up and was more wanting to ftp into it vs ssh just what am use to for my workflow for webdesign.  hopefully will be up and running again today tho after the distro update breaking my image.