# "Certificate invalid" problem with SFTP or FTPS RW publishing

**URL:** <https://forums.realmacsoftware.com/t/certificate-invalid-problem-with-sftp-or-ftps-rw-publishing/26617>\
**Category:** RapidWeaver Classic\
**Created:** [May 2, 2019, 4:33pm UTC](https://forums.realmacsoftware.com/t/certificate-invalid-problem-with-sftp-or-ftps-rw-publishing/26617 "2019-05-02T16:33:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rtloon](https://avatars.discourse-cdn.com/v4/letter/r/7ab992/32.png) [@rtloon](https://forums.realmacsoftware.com/u/rtloon)\
**Post date:** [May 2, 2019, 4:33pm UTC](https://forums.realmacsoftware.com/t/certificate-invalid-problem-with-sftp-or-ftps-rw-publishing/26617/1 "2019-05-02T16:33:27Z")

</div>

I have now had the precise same issue on two sites: getting invalid certificate messages when testing connections that work with FTP but not SFTP or FTPS. In both cases I have not had problems connecting via FTPS on Cyberduck.

In the one I am currently working on I had RW SFTP working fine when connecting to sandbox.domain, but when I switched over to another subdomain.domain I got FTP to work, but am getting a certificate invalid messages when testing SFTP (or FTPS), using the same setup as worked for sandbox.domain, except for the new username and password.

I went into the certificate and checked “always trust” wherever I could. Looking into the certificate details I see there is Basic Constraints extension that is critical but “certificate authority” is set to “no”

 ![29%20AM](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/2X/9/9d84a3a3199f55ea63bd661e73d4a91c8a5f7f03.png)

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/system/32/25301_2.png) [@system](https://forums.realmacsoftware.com/u/system)\
**Post date:** [June 2, 2019, 2:33am UTC](https://forums.realmacsoftware.com/t/certificate-invalid-problem-with-sftp-or-ftps-rw-publishing/26617/2 "2019-06-02T02:33:33Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
