However, the same account has full access via sftp. This user is in fact chrooted when accessed via a SSH terminal. In fact I got "STFP restriction inactive" when logged as root (not chrooted of course), but "STPF restriction active" when logged as manager of the domain (the account in Domains > mydomain > Acces to the server over SSH). That's pretty unlikely but worth checking, as many do block port 25 by default - as an example.Ĭlick to expand.I did some researches and understood what this command exactly does. Not your Plesk Obsidian Firewall but your Hosting Company's Firewall. You've not stated who your Hosting your VPS with, but the previous post ^^ would definitley be your 1st check anyway but then maybe, just double check that your Hosting Company have not blocked port 21 by default i.e. Is what we do, but with SFTP only as described in the 1st paragraph.Īs you've stated, your intention is to use FTP not SFTP anyway, but those items just FYI, if, for whatever unlikely reason, you decide to give up with FTP. We intentionally, don't use proftp at all (see above) However, this setup is on our own server, not VPS which might make a slight difference. If your Plesk user access rights / SSH /Chroot SFTP / user rights etc are all setup correctly (takes a bit of time and forethought) then you can avoid any of the full access issue that you've mentioned above with SFTP. Only STFP with access only from certain IP addresses and only via Public/Private Keys NOT password (which is disabled).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |