Open megapearl opened 1 year ago
Heya I've been struggling to install, and got the same fwconsole error That's how I ended up here
So far here's what I found out
--volume freepbx-data:/data
--volume /synologydisk1/docker/freepbx/data:/data
results in the failures you describe with a "[freepbx] Can't seem to locate /usr/sbin/fwconsole.. exiting"
[INFO] ** [freepbx] New install detected - please wait while we fetch FreePBX - will take up to 30 minutes!
[NOTICE] ** [freepbx] Starting Asterisk 17.9.3 for the first time
[NOTICE] ** [freepbx] Installing FreePBX 15.0.16.56 source code
[ERROR] ** [freepbx] Can't seem to locate /usr/sbin/fwconsole.. exiting
[cont-init.d] 10-freepbx: exited 1.
[cont-init.d] 15-socat: executing...
[cont-init.d] 15-socat: exited 0.
[cont-init.d] 99-container: executing...
**********************************************************************************************************************
**********************************************************************************************************************
**** ****
**** ERROR - Some initialization scripts haven't completed - All services are now halted ****
**** - The following scripts in '/etc/cont-init.d' did not pass their completion check ****
**** ****
**********************************************************************************************************************
**********************************************************************************************************************
10-freepbx
- I am now fiddling around to find a way to make it read properly the SSL certificates which are generated by acme.sh on the host, and are sitting in a specific directory mounted. Currently trying with this in the docker run:
--volume freepbx-data:/data \ --volume /synologydisk1/docker/freepbx/certs:/certs \
EDIT: yep that part works.
Not sure if that helps, but it seems easier to setup using a mount volume, avoiding potential permission errors.
Just set up a new container, but can't get it to install. It looks like it is not connecting to the database, but I can connect to it from within the container just fine.
What I tried so far:
Tried it on another server (hardware) and other database host (Virtual Machine). Started over using the 14, 15, and develop branch. Connecting to the local ip (In my case 10.0.1.44) instead of the mariadb hostname. Using a simple password with just letters and numbers. Tested using root user and password of MariaDB. Using mysqlcheck --repair --all-databases and mysqlcheck reported no errors.
Still giving the SQLSTATE[HY000] [2002] error.
What could be wrong, how to troubleshoot/debug? My setup is:
docker-compose:
logs:
When I shell into the container I can connect to the mariadb container just fine.