[BUG] Scheduler and/or Autoconf not connecting to Database about bunkerweb HOT 4 CLOSED

Hi @0FiRE0, thank you for opening this issue, do you have more logs maybe to see if the autoconf managed to write inside the database ?

from bunkerweb.

Hi @0FiRE0, thank you for opening this issue, do you have more logs maybe to see if the autoconf managed to write inside the database ?

Hi @TheophileDiot ,
Yes, after removing the container docker compose down and re-creating it docker compose up -d, it works fine and is able to connect to the database and works normally.

It seems to be a DNS/Hostname resolution issue, because when I log into the container's terminal, and try to ping the database container, it isn't able to resolve the database hostname anymore, even though they are connected with each other under the same bw-docker network.
But after the re-creation of the containers, it is able to resolve it again.

Sometimes, you can get the same error simply by restarting the containers docker compose restart.

from bunkerweb.

@0FiRE0 oh alright, it seems that Docker can be annoying sometimes with the dns resolution of hostnames, I'll have a look and let you know what I can find

from bunkerweb.

Hello @0FiRE0,

It should be fixed in the last 1.5.2 version. Feel free to open a new issue if needed.

from bunkerweb.