Can't create a new project - multiple issues

Wappler Version : 6.0.3
Operating System : 13.5.1
Server Model: PHP
Database Type: MySQL
Hosting Type: Docker

Expected behavior

What do you think should happen?

Create a new project using docker, and docker it set up.

Actual behavior

What actually happens?

Create a new project and docker fails to create the image.

How to reproduce

Create a new php project using docker as server type. The following error occurs. I hit deploy and the same error occurs.

I was able to get docker set up by going to Targets and clicking save. It then set up the docker image.

Yes for php docker projects we now use directly the native docker images, so just a regular project options save should be enough.

Will make sure this happens also for new php docker projects.

1 Like

@George here’s another issue with creating new project. I don’t recall PHP setting the root to /www before but it’s doing that now and when I go to change it, it throws an error. The project.json file doesn’t get updated on save either. I have to change the root folder manually. The routing also seems affected but I haven’t had time to thoroughly test that yet.

When I change the webRootFolder manually and then go to save the project settings I get these alerts.

And lastly, the db connection fails. I try to set it up with third party software I use often for wappler projects and it fails to connect as if the password showing in the target settings is not the correct one.


I was going to open a bug report for this as I didn’t see anything about it on announcements, but I found a post of George saying there were working on implementing it.

What about moving manually? :thinking:

@franse I’m about to try creating a new project using that files from last project I successfully set up and finished in Wapper (finished it just yesterday). I’m going through and manually changing all the connection and .json files with the new setttings and then I’m going to open Wappler and see what happens. I’ll keep you posted.

You don’t have to set it as this is the new default for some time now. It is required and also more convenient to have all your php files in a web root folder for example www and packaging tools and Wappler extensions outside of it.

Eventually the www folder is uploaded to your live site root so it doesn’t matter

1 Like

@George, got it. Thanks for the clarification. Cloning my last project and changing the settings seemed to work for setting up the project, however the issue still remains that I can’t set up my third party software database connection. Never had this issue before with wappler/docker.


Screenshot 2023-12-16 at 7.28.03 AM

Not sure why the error says 192.168.65.1

The db connection worked fine until I went to targets and resaved the info. Then got the error. Something is definitely going haywire in this latest version haha.

I need to use the third party software to import some tables that I use on all my projects, unless there is a way to import using Wappler that I’m missing.

Quiting Wappler and then reopening, makes the DB connection again inside wappler, but still doesn’t connect from my third party software. The need to quit wappler after changes to setttings to be a common issue across a lot of settings in this version.

Ok last observation, the db_user works in the third party software, the root doesn’t. I’ll investigate that, probably a setting in one of the wappler files somewhere.

These issues should now be fixed in Wappler 6.0.4

This topic was automatically closed after 46 hours. New replies are no longer allowed.