Problems with NodeJS in Database Manager

[Jackson_rr]

yes, persists in 3.7.3.

[Dave]

Our issue has resolved itself after a local system reboot/server reboot, and restart of Wappler. Everything is working as it should now. Sorry for any inconvenience.

[Jackson_rr]

I believe there are still some problems when the project is in NodeJS, because when pulling the tables of the DB took about 3 hours … o Table name appeared, plus fields did not.

All tables look like this.

[Dave]

We are just going through server logs for Apache/MySQL our firewall/modsec/Imunify360 configurations to see if we can spot anything. So far nothing but still quite a few lines to look through. If we find anything at all will post it here.

[George]

I don’t thing that it is NodeJS related, Wappler connects directly to the database and fetched the schema.

It is advisable to run more recent MySQL/MariaDb versions as very old one can be slow in schema retrieval and that is why the process timeout eventually if your database have a lot of tables.

[Dave]

Maybe this post could help resolve the issue @Jackson_rr?

Blazingfast hosting

I managed to get it working with the direct connect apposed to the server connect and the error message was for a timeout but it loaded the entire just a moment please pages html from blazing. For anyone else using blazingfast set up remote connections on channel to allow your IP Then set up your target and database connection making sure on database connection you use direct.

[Teodor]

This should now be fixed in Wappler 3.7.4