Hi
I created a node project and i setup a remote target, but when i test the connection, it fails.
When I provide the same informations with filezilla it works. This is the message
Can someone help me please?
Hi
I created a node project and i setup a remote target, but when i test the connection, it fails.
When I provide the same informations with filezilla it works. This is the message
Can someone help me please?
Hi ben
Thanks for your reply.
The problem is that i can’t connect to the remote folder in ftp.
In another project (php) with the same parameters i can connect.
PHP uses Apache/Nginx as the server. NodeJS has its own server. For more, see
https://docsdev.wappler.io/guides/nodejs-ftp-deploy-on-shared-hosting-with-plesk-and-cpanel
For cases where we see this error, its usually because it tries to run/read the public folder which has not been uploaded yet.
It should still allow you to save the target. Once done, see if you can upload a file or publish the project.
If that works, and your website is live on the remote URL… then if you test the FTP connection, it should connect.
Hi Sid
So I must create a folder and upload files with FileZilla and then try again in wappler?
No, you can upload from Wappler itself too.
Just save the target, even if it shows error on connection. (Be 100% sure that the settings are correct)
Then, select that target, and either hit publish… or select any one file and upload it.
If you see that file in the remote FTP, it means Wappler is able to connect to it.
Then, you can upload the entire website via publish or separately via FTP (much faster in my experience). Start/Create the NodeJS app on the server, if not already running/created.
Run the website on remote URL to verify app is working.
Now, you can try the do test connection in Wappler target settings and it should work.
hi sid
if I publish to remote it fails. Use same credentials in FileZilla works. The folder exist in ftp manager.
In that case you probably have some issue with the Wappler FTP settings. Maybe recheck the remote path, url etc. Credentials might be correct, but other settings might not.
Ok thanks sid