SFTP access for LAMP app
3246 last edited by girish
Quick question, as I am too daft to figure it out myself by looking through the posts and docu:
Where do I find the password for the SFTP user of the LAMP stack app?
"Password - Cloudron password (password is the same for SFTP access to all apps)" and
"Only Cloudorn admins have SFTP access. To give a specific user access to SFTP of a single app, make them an operator."
Does this suggest it should be the same password as my main admin user?
Also, despite having opened the required port 222, I get a message saying I cannot connect to my app. What's up with that? I've tried using the local IP of my Cloudron box too with the same results.
@3246 In order to connect, you must use the FQDN of the app you are connecting to in your username, shown like below.
So for you, it could be:
(Using your username to kind of fill in blank info)
OK, tried that too but it's just not connecting to 222. I have restarted by routers and canyouseeme.org tells me port 222 is closed. How can I check this on Cloudron?
@3246 For a start, are you able to connect at all or is this an authentication issue (i.e post connection) ?
telnet my.domain.com 222work ? If it does, then atleast firewall etc work.
@girish sadly that's not working, no. The services dashboard shows SFTP running and I can connect via SSH (using my system user login, not Cloudron).
@3246 the SFTP endpoint is using your Cloudron users now the system users. The username will be
cloudronusername@appdomainThe appdomain is required so the system knows to which app you want to connect. That is just a virtual email address and does not need to exist.
@3246 thanks. My understanding is that you have this installed in your house, correct? If so, this is what I would do:
telnet <internal-ip> 222work? If this doesn't work, this is some cloudron related issue. I would also double check here that
telnet <interal-ip> 22works (the ssh port)
- If the above works, then can you double check if your router firewall is allowing incoming port 222 for the public IP and into this VM?
@girish SSH works, 222 does not
Services look normal: