Hetzner server is not starting docker

I am trying to deploy my project to production. The first time I tried, it went smoothly, but when it came to creating Traefik, I got this error:

network wappler-compose_proxy declared as external, but could not be found.

I thought I had done something wrong when generating Traefik, so I deleted the server and redid the entire procedure. However, now when I try to start the server without Traefik, just the raw project, I am getting this error. I don't understand why this error is occurring.

Thanks

I saw here that Docker Compose wasn't installed, for some reason it didn't install automatically. I did the manual installation, but now when I try to install Traefik, I get this error:

WARN[0018] a network with name wappler-compose_proxy exists but was not created by compose.
Set `external: true` to use an existing network 
network wappler-compose_proxy was found but has incorrect label com.docker.compose.network set to ""
Error Launching Services!

I don't understand, it was supposed to be all automatic, right? The last time I deployed a project, it was so simple, everything was done automatically for me. Now I'm getting these errors. I don't understand.

How can I resolve this? Has anyone encountered this Traefik error before?

what were the options selected for your production target?

Hi George, so I selected the Hetzner CX42 server, but now it's not going through anymore; it's giving the following error when trying to create the server: Failed to create server: error during placement

George, I don't know what else to do. This is the fifth time I've tried to deploy this project and it keeps giving me an error:

=> [web] exporting to image 1.9s => => exporting layers 1.9s => => writing image sha256

0.0s => => naming to docker.io/library/colmeias__production-web 0.0s [+] Running 1/1 :heavy_check_mark: Network colmeias__production_default Created 0.4s network wappler-compose_proxy declared as external, but could not be found Error Launching Services!

It worked the first time, but I ended up deleting the server and recreating it due to Traefik. Now it keeps showing this error and I don't know how to fix it.

@Cristiano_Barbieri have you tried:

REMEMBER TO BACKUP FIRST! REMEMBER TO BACKUP FIRST!

A search of the Community returns a few Topics along the same lines.

I found where the problem was. When we delete the provider, it doesn't remove the configurations from the folder, so it was using the old configurations and causing these errors.

Here's a suggestion for you: in a future update, when deleting the provider, also delete the configurations in the folder. Otherwise, it pulls everything again and causes these errors.

I deleted the configurations in the folder, redid the whole process, and now everything is working fine.

Thank you very much, everyone.

Here's a tip: if you create a provider once, delete it, and try to set up the server again, check the folder to see if the configurations are still in the .wappler/providers folder.

2 Likes