thanks a lot it works 110% perfect.guys please take not on the " eth0
" interface at the end of "route add default gw 192.168.1.1 eth0" step
when assigning a temporary IP addresses cause if you don't it wont work
#thats the mistake that l was doing all along and l could connect to the
I tried to follow this step by step on my AWS Ubuntu instance. But it
didnt work. And now I am unable to login into my instance using my key
pair. Any ideas? I tried to debug it using key pair permission issue but
nothing worked so far. Even FTP doesnt work for the user I created. It
gives me the error "Could not connect Server"
HI, I have tried with a particular folder so on login the user is
directly going to that folder but the user can go back to the root and
go into any other folder and add delete files so the whole purpose of
limited access to a particular folder is defeated. Any inputs will be
One thing that bugged me after
following your guide was that the Message of the Day was missing after
SSHing onto my servers. This is due to commenting out the "UsePAM yes"
You can't uncomment this as it is, as
the config file will error and SSH won't start. This option has to come
before the Subsystem definition, so at Step 8, if you move the
suggested changes to the bottom of the file and leave UsePAM as it is,
things will work as expected and you'll still get the MOTD displaying.
I was setting this up on an AWS EC2 instance, so I had to add the following 2 lines to /etc/vsftpd.conf at Step 3.
pasv_address=[public DNS from the EC2 instance] pasv_addr_resolve=Yes