Closed patrick-zimmermann closed 4 years ago
@patrick-zimmermann this may be related to what was reported in #24, for now to solve it, try to use WA_DB_ENGINE=mysql
instead of WA_DB_ENGINE=MYSQL
when you start the container.
The SSL settings should be picked up this way. We've already made the fix which will be included in the next release.
Let me know if this temporary fix works, thanks!
@mengyiyuan Thanks for your quick response. Changing the parameter to lowercase did indeed solved the issue.
As far as I can tell, you only need to change it in the webapp. The master and core can be left uppercase, right?
@mengyiyuan Thanks for your quick response. Changing the parameter to lowercase did indeed solved the issue.
As far as I can tell, you only need to change it in the webapp. The master and core can be left uppercase, right?
That's right. Only in webapp.
Perfect, thanks a lot!
Hello ,
I was created the whole setup at that time I got the same error, but at the next second I was fixed the same. Mainly because of 2 reasons you may get the URL not found errors.
Containers are not up (db, coreapp, webapp). You might be calling the wrong URL. Please check the below link if do you want any clarity. https://youtu.be/hYO32rQQ9Pc
I try to setup the WhatsApp Business API with an external MySQL database (Azure Database for MySQL). That database requires SSL (see here).
I already followed the instructions from the official documentation (see here). However, it looks like that the whatsapp-web component ignores the defined environment variables. I uploaded the certificates to the defined path (/usr/local/waent/data/certs). The connection via terminal to the database works. Also, if I disable the SSL setting on the MySQL database the connection works as well.
The error message I see in the logs: SSL connection is required. Please specify SSL options and retry
Could you please provide an dedicated example for enabled SSL configuration.
whatsapp-web env:
The defined path above (/usr/local/waent/data) is mounted as a persistent volume on the kubernetes system.
The error log from the pod.
We are using the latest version
2.27.12
.