# NO SUCCESS setting up with REMOTE-MYSQL.YML
**URL:** https://community.xibo.org.uk/t/no-success-setting-up-with-remote-mysql-yml/22437
**Category:** CMS Installation
**Created:** [March 30, 2020, 5:47am UTC](https://community.xibo.org.uk/t/no-success-setting-up-with-remote-mysql-yml/22437 "2020-03-30T05:47:50Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@aponkye](https://community.xibo.org.uk/u/aponkye)
#### Post date: [March 30, 2020, 5:47am UTC](https://community.xibo.org.uk/t/no-success-setting-up-with-remote-mysql-yml/22437/1 "2020-03-30T05:47:51Z")
hello members, i have been playing around with all options for xibo docker install. I want to test xibo install using an external database, a MARIADB which on the same server. but i get an error no matter what i do…below is the error:
Attaching to anansemedia\_cms-web\_1, anansemedia\_cms-xmr\_1, anansemedia\_cms-quickchart\_1
cms-quickchart\_1 | yarn run v1.19.1
cms-quickchart\_1 | $ node index.js
cms-quickchart\_1 | 2020-03-30T05:10:57.819Z - info: Loaded 1 keys from API keyfile
cms-quickchart\_1 | 2020-03-30T05:10:58.002Z - info: Telemetry is enabled
cms-quickchart\_1 | Mon, 30 Mar 2020 05:10:58 GMT body-parser deprecated undefined extended: provide extended option at index.js:33:17
cms-quickchart\_1 | 2020-03-30T05:10:58.619Z - info: Setting request timeout: 1000 ms
cms-quickchart\_1 | 2020-03-30T05:10:58.619Z - info: NODE\_ENV: production
cms-quickchart\_1 | 2020-03-30T05:10:58.619Z - info: Listening on port 3400
cms-web\_1 | Waiting for MySQL to start - max 300 seconds
waiting for MySQL to start…when i check in the database, its empty. WITHOUT USING REMOTE-MYSQL.YML I can run xibo 2.3.2 without any issues. i am just curious to see how using another database aside from the default database that installs with xibo as you launch the docker yml.
i replaced the default config.env file with that of config.env.template-remote-mysql (renamed it config.env and made necessary changes) while cms\_remote-mysql.yml also exist, i bring up the containers with sudo docker-compose -f cms\_remote-mysql.yml up -d. containers start fine, but then i am not able to start xibo and login page…
what am i doing wrong?
---
### Author:  [@DanBW](https://community.xibo.org.uk/u/DanBW)
#### Post date: [March 30, 2020, 8:34am UTC](https://community.xibo.org.uk/t/no-success-setting-up-with-remote-mysql-yml/22437/2 "2020-03-30T08:34:28Z")
Hi aponkye,
Can you confirm what command you are running when you get this message?
Many Thanks.
---
### Author:  [@alex](https://community.xibo.org.uk/u/alex)
#### Post date: [March 30, 2020, 1:20pm UTC](https://community.xibo.org.uk/t/no-success-setting-up-with-remote-mysql-yml/22437/3 "2020-03-30T13:20:42Z")
The Docker containers running the CMS need to be able to connect to your MySQL server, so you’ll need to ensure you’ve enabled your MySQL server to accept connections over the network (and then firewalled that off appropriately), and then created a user and database for Xibo to use.
You then put those details in config.env. Note you can’t use “localhost” as the server name, it will need to be the IP address of a non-loopback interface (eg your LAN interface) and you’ll need to ensure your firewall allows access to that.
There’s really no benefit to using a local MySQL server separate to the one Xibo runs itself. We provide remote MySQL for people who want to use a separate server to run MySQL on really.
---
### Author:  [@aponkye](https://community.xibo.org.uk/u/aponkye)
#### Post date: [March 31, 2020, 4:37am UTC](https://community.xibo.org.uk/t/no-success-setting-up-with-remote-mysql-yml/22437/4 "2020-03-31T04:37:56Z")
sudo docker-compose logs
Attaching to anansemedia\_cms-web\_1, anansemedia\_cms-xmr\_1, anansemedia\_cms-quickchart\_1
cms-quickchart\_1 | yarn run v1.19.1
cms-quickchart\_1 | $ node index.js
cms-quickchart\_1 | 2020-03-30T07:59:03.479Z - info: Loaded 1 keys from API keyfile
cms-quickchart\_1 | 2020-03-30T07:59:03.656Z - info: Telemetry is enabled
cms-web\_1 | Waiting for MySQL to start - max 300 seconds
cms-quickchart\_1 | Mon, 30 Mar 2020 07:59:04 GMT body-parser deprecated undefined extended: provide extended option at index.js:33:17
cms-quickchart\_1 | 2020-03-30T07:59:04.257Z - info: Setting request timeout: 1000 ms
cms-quickchart\_1 | 2020-03-30T07:59:04.257Z - info: NODE\_ENV: production
cms-quickchart\_1 | 2020-03-30T07:59:04.257Z - info: Listening on port 3400
cms-quickchart\_1 | 2020-03-31T03:55:13.449Z - info: Received kill signal, shutting down gracefully.
cms-quickchart\_1 | 2020-03-31T03:55:13.453Z - info: Closed out remaining connections.
cms-quickchart\_1 | yarn run v1.19.1
cms-quickchart\_1 | $ node index.js
cms-quickchart\_1 | 2020-03-31T03:59:09.308Z - info: Loaded 1 keys from API keyfile
cms-quickchart\_1 | 2020-03-31T03:59:10.237Z - info: Telemetry is enabled
cms-quickchart\_1 | Tue, 31 Mar 2020 03:59:11 GMT body-parser deprecated undefined extended: provide extended option at index.js:33:17
cms-quickchart\_1 | 2020-03-31T03:59:12.023Z - info: Setting request timeout: 1000 ms
cms-quickchart\_1 | 2020-03-31T03:59:12.024Z - info: NODE\_ENV: production
cms-quickchart\_1 | 2020-03-31T03:59:12.024Z - info: Listening on port 3400
ananse@ghanamedia:/opt/anansemedia$
sudo docker-compose logs
Attaching to anansemedia\_cms-web\_1, anansemedia\_cms-xmr\_1, anansemedia\_cms-quickchart\_1
cms-quickchart\_1 | yarn run v1.19.1
cms-quickchart\_1 | $ node index.js
cms-quickchart\_1 | 2020-03-30T07:59:03.479Z - info: Loaded 1 keys from API keyfile
cms-quickchart\_1 | 2020-03-30T07:59:03.656Z - info: Telemetry is enabled
cms-quickchart\_1 | Mon, 30 Mar 2020 07:59:04 GMT body-parser deprecated undefined extended: provide extended option at index.js:33:17
cms-quickchart\_1 | 2020-03-30T07:59:04.257Z - info: Setting request timeout: 1000 ms
cms-quickchart\_1 | 2020-03-30T07:59:04.257Z - info: NODE\_ENV: production
cms-quickchart\_1 | 2020-03-30T07:59:04.257Z - info: Listening on port 3400
cms-quickchart\_1 | 2020-03-31T03:55:13.449Z - info: Received kill signal, shutting down gracefully.
cms-quickchart\_1 | 2020-03-31T03:55:13.453Z - info: Closed out remaining connections.
cms-quickchart\_1 | yarn run v1.19.1
cms-quickchart\_1 | $ node index.js
cms-quickchart\_1 | 2020-03-31T03:59:09.308Z - info: Loaded 1 keys from API keyfile
cms-quickchart\_1 | 2020-03-31T03:59:10.237Z - info: Telemetry is enabled
cms-quickchart\_1 | Tue, 31 Mar 2020 03:59:11 GMT body-parser deprecated undefined extended: provide extended option at index.js:33:17
cms-quickchart\_1 | 2020-03-31T03:59:12.023Z - info: Setting request timeout: 1000 ms
cms-quickchart\_1 | 2020-03-31T03:59:12.024Z - info: NODE\_ENV: production
cms-quickchart\_1 | 2020-03-31T03:59:12.024Z - info: Listening on port 3400
cms-web\_1 | Waiting for MySQL to start - max 300 seconds
this is how far i can get…
that is the output fron compose logs…i still cant launch xibo
---
### Author:  [@aponkye](https://community.xibo.org.uk/u/aponkye)
#### Post date: [March 31, 2020, 4:40am UTC](https://community.xibo.org.uk/t/no-success-setting-up-with-remote-mysql-yml/22437/5 "2020-03-31T04:40:24Z")
MySQL started
cms-web\_1 | Updating settings.php
cms-web\_1 | ERROR 2002 (HY000): Can’t connect to MySQL server on ‘135.23.77.250’ (115)
cms-web\_1 | New install
cms-web\_1 | Provisioning Database
cms-web\_1 | ERROR 2002 (HY000): Can’t connect to MySQL server on ‘135.23.77.250’ (115)
cms-web\_1 | Phinx by CakePHP - [https://phinx.org](https://phinx.org). 0.9.2
cms-web\_1 |
cms-web\_1 | using config file .varwwwcmsphinx.php
cms-web\_1 | using config parser php
cms-web\_1 | using migration paths
cms-web\_1 | - /var/www/cms/db/migrations
cms-web\_1 | warning no environment specified, defaulting to: production
cms-web\_1 | using adapter mysql
cms-web\_1 | using database media
cms-web\_1 |
cms-web\_1 | In MysqlAdapter.php line 115:
cms-web\_1 |
cms-web\_1 | There was a problem connecting to the database: SQLSTATE[HY000] [2002] Conn
cms-web\_1 | ection refused
cms-web\_1 |
cms-web\_1 |
cms-web\_1 | migrate [-c|–configuration CONFIGURATION] [-p|–parser PARSER] [-e|–environment ENVIRONMENT] [-t|–target TARGET] [-d|–date DATE] [-x|–dry-run]
cms-web\_1 |
cms-web\_1 | Configuring Database Settings
cms-web\_1 | ERROR 2002 (HY000): Can’t connect to MySQL server on ‘135.23.77.250’ (115)
cms-web\_1 | ERROR 2002 (HY000): Can’t connect to MySQL server on ‘135.23.77.250’ (115)
cms-web\_1 | ERROR 2002 (HY000): Can’t connect to MySQL server on ‘135.23.77.250’ (115)
cms-web\_1 | ERROR 2002 (HY000): Can’t connect to MySQL server on ‘135.23.77.250’ (115)
cms-web\_1 | ERROR 2002 (HY000): Can’t connect to MySQL server on ‘135.23.77.250’ (115)
cms-web\_1 | ERROR 2002 (HY000): Can’t connect to MySQL server on ‘135.23.77.250’ (115)
cms-web\_1 | Setting up Maintenance
cms-web\_1 | Protected Maintenance
cms-web\_1 | ERROR 2002 (HY000): Can’t connect to MySQL server on ‘135.23.77.250’ (115)
cms-web\_1 | ERROR 2002 (HY000): Can’t connect to MySQL server on ‘135.23.77.250’ (115)
cms-web\_1 | Importing ca-certs
cms-web\_1 | cp: can’t stat ‘/var/www/cms/ca-certs/_.pem’: No such file or directory
cms-web\_1 | cp: can’t stat '/var/www/cms/ca-certs/_.crt’: No such file or directory
cms-web\_1 | WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
cms-web\_1 | Setting up Quickchart
cms-web\_1 | ERROR 2002 (HY000): Can’t connect to MySQL server on ‘135.23.77.250’ (115)
cms-web\_1 | Configuring Maintenance
cms-web\_1 | Removing web/install/index.php from production container
cms-web\_1 | Starting cron
cms-web\_1 | Starting webserver
cms-web\_1 | AH00558: httpd: Could not reliably determine the server’s fully qualified domain name, using 172.24.0.3. Set the ‘ServerName’ directive globally to suppress this message
---
### Author:  [@alex](https://community.xibo.org.uk/u/alex)
#### Post date: [March 31, 2020, 8:40am UTC](https://community.xibo.org.uk/t/no-success-setting-up-with-remote-mysql-yml/22437/6 "2020-03-31T08:40:07Z")
Your MySQL server isn’t accepting connections over the network. You need to fix that for it to work.
---
### Author:  [@aponkye](https://community.xibo.org.uk/u/aponkye)
#### Post date: [April 2, 2020, 9:24pm UTC](https://community.xibo.org.uk/t/no-success-setting-up-with-remote-mysql-yml/22437/7 "2020-04-02T21:24:21Z")
docker-compose -f cms\_remote-mysql.yml up -d …I am guessing this installs works best with older MYSQL…I am using the lates version of MARIADB which seem not allow the us passwords.
---
### Author:  [@aponkye](https://community.xibo.org.uk/u/aponkye)
#### Post date: [April 2, 2020, 9:37pm UTC](https://community.xibo.org.uk/t/no-success-setting-up-with-remote-mysql-yml/22437/8 "2020-04-02T21:37:07Z")
I suspect that. but i shifted gears from that. I am now following the steps to us local nginx to redirect traffic to xibo in docker. my nginx is not a dockerized nginx. i have access to xibo unti i put 127.0.0.1 infront of my public port e.i 127.0.0.1:1001:80 in the custom port yml file, I also tried it using docker-compose yml. so far i am learning a lot of reason as to why most xibo users cant get xibo to working using docker. once i get through with being able to launch xibo using remote MYSQL and also none DOCKERIZED NGINX server host to proxy / redirect traffic to docker container…i will write my instructions to help even the most computer illiterate to be able to setup xibo under 30 minutes. i already have an instruction but this was during 1.8.1 xibo…tested same instructions on my guinea pig server over and over and each time, xibo worked right on. …my instructions will be for NGINX and not apache .
---
### Author:  [@system](https://community.xibo.org.uk/u/system)
#### Post date: [July 3, 2020, 3:37am UTC](https://community.xibo.org.uk/t/no-success-setting-up-with-remote-mysql-yml/22437/9 "2020-07-03T03:37:50Z")
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.