SFTP for Wordpress is connecting but rejecting the username + password

[Lonkle]

I get a no such user found from error when checking the Cloudron SFTP Service Logs. But I only have one user and one password. I'm gonna try a fresh install, but was curious if anyone had run into this error before?

[girish]

@lonk Can you double check that you have the username correct. Note that the username is not your email id or username@domain.com. It is username@app.domain.com. It is displayed in the Access section of the app. This is required because SFTP has no "vhost"/Host header like HTTP1.1 does.

[Lonkle]

@girish Yeah, I've always been able to log in via SFTP via that method. And it acknowledges that there's an SFTP server, but still:

joel@wordpress.example.com: no such user found from [x] to 172.18.0.5:22
UNKNOWN - PASS (hidden)
UNKNOWN - USERAUTH_REQUEST
UNKNOWN USER joel@wordpress.example.com 331
UNKNOWN USERAUTH_REQUEST
SSH2 session closed.

I tried capitalizing the J and changing my password, and I even made a new user, tried changing the Access Control Setting with Groups. I'm gonna try to install a new app, I restore so often I wonder if something got corrupted. But I just checked the box database directly and there's only one user, "joel".

If that doesn't work, I'll just re-install again, just pretty odd it can't find the user.

[msbt]

@lonk are you using port 222 instead of 22?

[Lonkle]

@msbt Yup, if I don't use 222 then Transmit can't find the SFTP server.

I'm gonna see if I can login to a new installation of Wordpress.

[msbt]

@lonk was just curious because your paste said otherwise

[Lonkle]

@msbt Do you mean this line:

to 172.18.0.5:22

This is a copy paste from the internal SFTP Cloudron logs. Port 222 public forwards to 172.18.0.5:22 internal.

[msbt]

@lonk ah ok, my bad

[d19dotca]

I know this is marked as "Solved"... but is it? I have recently run into the same issue but for Surfer instance not WordPress, but same SFTP server obviously that's running the show. I get the following in the SFTP server logs:

2020-12-10T16:59:33.000Z <IpHostnameofClient> UNKNOWN - [10/Dec/2020:16:59:33 +0000] "USER <username@SFTPservername>" 331 -
2020-12-10T16:59:33.000Z 2020-12-10 16:59:33,825 sftp proftpd[3588] sftp (<IpHostnameofClient>): USER <username@SFTPservername>: no such user found from <IpHostnameofClient> to <MyIPAddress>:22

I've verified the username they're using (the username@SFTPServerName) matches what's in the app access panel. The only thing that seems weird is the "22" port but I assume "222" forwards to "22"?

I tried myself with my own user in the same format but of course my own password and it worked fine, and when I purposely tried an incorrect password I actually see "Incorrect password" in the logs, so it seems they're using the right credentials and everything. Never experienced this issue before until today. Well actually it started yesterday but I wasn't notified of it until today. Oddly... Tuesday night I installed the v6 from v5, so I wondered if that had anything to do with it but the rest of my SFTP account access is working so I find it hard to believe, but it is interesting timing...

[girish]

@d19dotca Is the SFTP user a "normal" user or admin user? non-admin users have SFTP disabled by default in Cloudron 6. This is a breaking change. You can enable it back in Services -> SFTP -> Allow non-admins.

[d19dotca]

@girish Ahh..... okay yeah they're a non-admin. That may be it then. Let me check.

[d19dotca]

@girish said in SFTP for Wordpress is connecting but rejecting the username + password:

non-admin users have SFTP disabled by default in Cloudron 6. This is a breaking change.

Ah okay, indeed that was it! Thank you so much for the quick reply there.

I may have missed it, but I didn't see that written anywhere in the release notes when updating to v6... if that's not documented we definitely need to add that. My apologies if I missed it though.

[girish]

@d19dotca Technically, we haven't even announced the release of Cloudron 6 yet. It takes us ~2 weeks to push it out to all our users. And we push the blog post after most Cloudrons have updated. I realize this is a bit different to other software, but I think I mentioned elsewhere our mindset is tuned for auto-updating software (we are changing ourselves slowly...). If we push the blog post, people will rush to update and then we cannot handle the support rush. But this is a topic for another day

[girish]

@d19dotca The docs are here but you won't know about it since it's pushed without the announcement - https://docs.cloudron.io/apps/#non-admin-access

[d19dotca]

@girish Ah okay, yeah that makes sense. FWIW, I'd suggest that any "breaking changes" like that though still be mentioned on the release notes that you see before manually updating Cloudron, but I realize that still may not be too helpful because most will just auto-update anyways. haha. A little bit of a predicament there I guess. All good, I just appreciate the really quick response!

[Lonkle]

@d19dotca @girish Updating to 6.0 fixed the issue completely. I didn't even change any settings in my FTP app and it logged right in, so weird.

[d19dotca]

@lonk Yeah I figured we had the same issue but apparently not, my bad. Didn't mean to hijack the thread earlier. haha. Mine was actually caused by v6.0 due to a breaking change in how SFTP works - by default for admins only, meaning any non-admin users are rejected out of the box. But I think yours was different as you filed it before v6.0.