SFTP for Wordpress is connecting but rejecting the username + password
-
@msbt Do you mean this line:
to 172.18.0.5:22This is a copy paste from the internal SFTP Cloudron logs. Port 222 public forwards to 172.18.0.5:22 internal.
-
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>:22I'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...
--
Dustin Dauncey
www.d19.ca -
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>:22I'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...
-
@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 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.
@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.
--
Dustin Dauncey
www.d19.ca -
@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.
@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 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.
-
@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 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!
--
Dustin Dauncey
www.d19.ca -
@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!
-
@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.
