Wappler 7.3.8, NodeJS, Docker Desktop local docker database on dev server with production server at DigitalOcean. Wappler has lost connections with the database on both the Dev and Prdx svr. I deleted the /app/modules/connection folder and restarted Wappler no joy. Could not find an answer in the community and Claude wants me to delete the .wappler folder. I thought I would check in with the community before I did that. Any guidance would be appreciated. Thanks in advance.
Hi Mark,
Could you please provide more information on the issue with database connectivity? Are you seeing any errors in the dev console? Is the web application running?
1 Like
Looks like users are having lots of issues with latest version of docker. If on v29 try reverting to 28?
1 Like
Thank you guptast, Good questions I should have mentioned there are No errors in the logs. We originally uploaded a legacy database and data into Docker and the Production Server with dbForge. Wappler picked it up on both targets and development proceeded nicely. We are now adding additional tables & data to dbForge but Wappler is not seeing these. We did create a test table in the Wappler Database Manager that Published successfully to the Dev and Prdx servers and was picked up by dbForge.
Besides the /app/modules/connection folder are there any other files/folders that can be deleted so we can create a totally new db Connection? Are there any troubleshooting techniques we could use?
Thank you Hyperbytes, currently running Docker 4.48.0, updating it is worth a try.
Seems that just about every network service attached to Docker is falling over right now. Traefik, Redis, and now MySQL due to the most recent updates. However they can be worked around.
You want to downgrade to a previous version not upgrade. You'll also need to do the same for the remote deployment @mark1
1 Like
Thank you Cheese, Will keep you posted.
Hey Cheese, I was in the process of updating Docker Desktop and Wappler when I read your post. I plan to downgrade Docker Desktop tomorrow if I fail to resolve this. We uploaded a legacy database to the localhost server with dbForge. (Just FYI the new_table was added by me using Wappler's Database manager while troubleshooting)
If I understand this correctly the screen shot demonstrates the tables are in the database but for some reason Wappler can't see them. I've searched the docs, community and Claude.
There has to be a way to delete the db Connection (and data) then re-connect it to the Database with the correct data, but I have yet to find it. Any guidance would be appreciated.
BACKUP everything first Mark.
Your connection should be in:
/app/modules/connections/...
Just open the file in a text editor and make the changes required.
There are also database connections in the Targets too (remember the wappler directory is hidden so if you have not already done so enable show hidden files and folders):
/.wappler/targets/...
Each Target will have a database directory and in there are the database connection files. At the very end of the file below the structure is also a connection string.
I suppose the alternative would be to entirely delete the database connections from within Wappler but this may leave some residual files? I'm sure we had that issue in the past. Even now after years of using Wappler I have no idea why there is an Advanced tab, or why there are multiple database configuration dialogues within Wappler, ie in the main menu on the left, and under Server Connect Globals area...? So if you do make changes within Wappler (and not the manual changes I outline above) make sure to check both sets of configuration details match and are for the working (new) connection.
Also the Project Settings area (under Targets, and specific to each target) has a database configuration (so make sure to make changes there especially if you have selected Docker for the database type).
Once again just BACKUP first so if it all goes Pete Tong you can rollback without too much hassle.
It would be nice if in Wappler 8 there is one area to configure the database connection (per Target of course) rather than multiple database connection entry points as it is just confusing and makes no sense especially to a new User trying to figure it out for the first time...
2 Likes
Which would you take out cheese?
Workflows->Globals->Database connections is needed for server connect
DB Manager connections needed for those who need to set different settings for direct access.
Remove from project settings?
Workflows->Globals->Database connections is needed for server connect
DB Manager connections needed for those who need to set different settings for direct access.
Remove from project settings?
And let Wappler feed the info through to the relevant areas.
Are you saying that setting is not needed????
No, what I mean is that all the required data can be entered in one place.
For those of us familiar with the Wappler way, it doesn’t matter, we know there are three spots to configure a database; newcomers aren’t so lucky.
1 Like