Fatal error: Certificate verification: Not trusted

Feature Request
1

Of late, I am getting this error message when trying to publish a project:

Executing Upload Synchronization ...
Uploading restart.txt to restart the NodeJS server ...
cd: Fatal error: Certificate verification: Not trusted (70:3F:15:7E:00:83:28:32:BB:EE:14:CD:45:47:77:6C:DA:62:3A:6D)

As it stands and under this circumstance, I cannot use Wappler to publish a project.

I get the same error message when using FileZilla, but here I tick the “Always trust this certificate in future sessions” box and all is well.

Please add a similar checkbox for the Wappler client so that I do not have to use FileZilla.

2

Are you using ftps or so and is the certificate valid?

4

The certificate itself is valid.

From what I can see, this appears to be a server‑side issue rather than anything related to Wappler. My host has been aware of the problem for almost a week now, but the fix still hasn’t been applied.

I’m able to work around it in FileZilla by choosing to trust the certificate manually, but it’s definitely inconvenient. It would be very helpful if Wappler could offer the same “always trust this certificate” option so that publishing isn’t blocked when the server presents a certificate that can’t be fully verified.