How to handle SFTP clients after disabling root user

You don’t need to activate root to do that.

In Transmit check these settings: Protocol: choose SFTP Server: your full domain name or IP user name: your sudo username (not root)

Port: only enter somthing here if you changed the default port 22 to something else

Once you start modifying files on your server via Transmit you may run into permission issues. If you do connect via SSH to your server and type this into the command line:

chown -R demouser. /var/www/html

• change “demouser” to your name (keep the dot at the end)
• change “/var/www/html” to whatever your folder structure is you need to change

You don’t need to activate root to do that.

In Transmit check these settings: Protocol: choose SFTP Server: your full domain name or IP user name: your sudo username (not root)

Port: only enter somthing here if you changed the default port 22 to something else

Once you start modifying files on your server via Transmit you may run into permission issues. If you do connect via SSH to your server and type this into the command line:

chown -R demouser. /var/www/html

• change “demouser” to your name (keep the dot at the end)
• change “/var/www/html” to whatever your folder structure is you need to change

Hi. For those of you, who is still facing the problem with Transmit working with encrypted keys. Maybe, before chowning on the server you’ll find it helpful just to put your passphrase (the local password you chose when encrypted the keys) to the password field of Transmit app. As Transmit app developer recommends here: If you’ve specified an encrypted key for use with this server in your config file, you can leave the key button alone and put the passphrase in Transmit’s password field.

Spent some time… Helped me a lot.

Sugarhill thanks for the additional input. Also, for work related large file transfers I’d take a look at Innorix DS.

@sugarhill chown -R someUser. /some/folder worked fine.

Quick question, I have multiple sites inside the “www” folder (/var/www), do you see a problem if I give a user write access to the entire “www” folder instead of doing one by one?

chown -R demouser. /var/www

Is this good practice?

Thanks

I don’t get this. I had

 chown -R apache. /var/www 

So Joomla can install files and update configuration. But I also want to be able to add/delete/change files via sFtp. However when I do the other chown than apache cant write and Joomla stops working (instaal,change config, etc).

Thanks a lot.