Hi Brian,
Is this happening on a new connections only or also with old ones?
Is this only happening with this specific connection? And is this happening from this specific (virtual?) machine, you are running the beta on?
Just to confirm Brians findings.
I have found the same issue, also in 3.0.2, new project, new connection, and it is affecting FTP as well as database connections. Also tried the same on 2 different servers and get the same results as per the video.
Apparently the issue I am having is that Node needs some specific folders created before the FTP will work correctly so basically Wappler works but some manual server config is needed if using node for the connection to function correctly . They are going to produce a guide for that
These are just two different problems.
The blank test connection dialog (reported in this topic initially) is a cosmetic issue in the UI. It happens on all the server models. It does show blank connection dialog but does not affect how your ftp works.
The other question (about the nodejs) is not related. Nodejs server does not use the same folders structure as your regular web server - you can’t just upload all the files in the public_html folder as the nodejs site won’t work.
It needs special setup depending on your control panel cpnanel/plesk. So the steps would be similar to: https://www.a2hosting.com/kb/cpanel/cpanel-software/create-application-with-nodejs-selector
and we will provide a clear guide on how to get your nodejs app uploaded to your remote hosting.