WhatsApp / WhatsApp-Business-API-Setup-Scripts

The scripts related to setting up WhatsApp business API
MIT License
423 stars 444 forks source link

wabweb container exit code 1: /opt/whatsapp/bin/web_setup.sh: line 368: WACORE_PORT_6250-6253_TCP: invalid variable name #101

Open ronna opened 2 weeks ago

ronna commented 2 weeks ago

Following the docker compose install and using docker files wabweb container is not starting, see log below

waweb-1 | Uploading certificate to db waweb-1 | Downloading certificate from db waweb-1 | Installed ca cert at /var/lib/whatsapp/ca.pem waweb-1 | Installed server cert at /var/lib/whatsapp/www.cert waweb-1 | Rewrote cert file at /var/lib/whatsapp/server.cert wacore-1 | D 2024-11-04 13:02:44.625 UTC 44 servicemessagestore_p.h:1350] Creating template_rate_limiting_rolling_window_counter table req_id=none wacore-1 | D 2024-11-04 13:02:44.625 UTC 44 datastore.cpp:1587] Creating table "template_rate_limiting_rolling_window_counter" req_id=none wacore-1 | D 2024-11-04 13:02:44.625 UTC 44 datastore.cpp:1647] "CREATE TABLE IF NOT EXISTS template_rate_limiting_rolling_window_counter ( timestamp BIGINT NULL , template_id VARCHAR(512) CHARACTER SET latin1 NOT NULL , pacing_session BIGINT NULL )" req_id=none waweb-1 | SSL Hardened waweb-1 | SSL enabled waweb-1 | Provisioned certificates successfully waweb-1 | Cleaned up staging area wacore-1 | D 2024-11-04 13:02:44.652 UTC 44 datastore.cpp:1497] Creating indexes for "template_rate_limiting_rolling_window_counter" req_id=none waweb-1 | /opt/whatsapp/bin/web_setup.sh: line 368: WACORE_PORT_6250-6253_TCP: invalid variable name

facebook-github-bot commented 2 weeks ago

Hi ronna (https://github.com/ronna/),

Thank you for your comment. This GitHub repo is not actively monitored. If you need help, please check previously asked questions in the WA Business API Developer Community, or raise a Direct support ticket. Meanwhile, we are happy to continue with less time-sensitive discussions in GitHub.

Thanks for your understanding!

RonnieRocket147 commented 2 weeks ago

Same here. So far Direct Support is only telling us it is our fault but it really is a container issue 😭

zerow06 commented 1 week ago

Same issue here using WA_API_VERSION=2.59.2 and latest version of docker-compose file with Docker Desktop 4.35.1 (173168)