オンプレミスAPIを終了します。詳細と次世代クラウドAPIへの移行方法については、オンプレミスAPIの終了のドキュメントを参照してください。
This covers how to troubleshoot issues that may arise with the on-premise WhatsApp API.
Users using AWS using the template can see issue where webapp failed to create db.
Fix:
Users using Azure kubernetes templates will see the issue where webapp fail to communicate with the coreapp.
Affected version:
Fix:
Users using v2.47 series will not be getting notifications about changes in phone number even if they have this setting enabled.
Affected version:
Fix:
Businesses in Cuba, Iran, North Korea, Syria, and three sanctioned regions in Ukraine (Crimea, Donetsk, Luhansk) are not eligible to use the WhatsApp Business Platform.
WhatsApp Messenger (WhatsApp) and WhatsApp Business app users in Cuba, Iran, North Korea, Syria, and three sanctioned regions in Ukraine (Crimea, Donetsk, Luhansk) are not eligible to receive messages sent via the WhatsApp Business Platform.
Messages with emojies might fail with QSqlError("1366", "QMYSQL: Unable to execute query", "Incorrect string value: '...' for column 'data' at row 1")
Affected Versions:
Possible fix:
Affected Versions:
Possible Fixes (any of the following):
/opt/whatsapp/bin/launch_within_docker.sh
as the execution path / CMD.Affected Versions:
This can happen if the ipv6 networking stack is completely disabled in your environment.
Fix:
ENABLE_IPV6
to false
on the webapp container.Follow these steps:
If you are not able to create a certificate for your phone number, and you see this error in the Whatsapp Manager, it is because the phone number is already in use:
Once a number has been registered with an API client, it cannot be deleted then re-added.
If you believe that this is an error and the phone number has not actually been registered, please contact support.
The quickest solution would be to add a new, previously unregistered phone number.
If your phone number status is showing as "Offline" in WABA, but it was not flagged for quality, it is likely that your docker instance has stopped running due to insufficient resources. You will need to restart your docker containers. Additionally, you should ensure that your container configuration has the minimum recommended core parameters.
Use the WADebug command line tool to help find any potential issues with the WhatsApp Business API setup and to make requesting help from WhatsApp support more effective.
Collect logs from all containers
~/biz $ docker-compose -f docker-compose.yml -f network-waent.yml logs > debug_output.txt
waweb
or wacore
) to the docker-compose logs
command:~/biz $ docker-compose -f docker-compose.yml -f network-waent.yml logs waweb > debug_output.txt
You can find the logs in the debug_output.txt
file in the current directory.
While trying to upload media by URL using the /media
endpoint, or trying to send a media message using the link
param, you may receive the following error message via webhooks:
{ "statuses": [ { "errors": [ { "code": 500, "title": "Media upload error (Connection closed)" } ], "id": "gBEGkZdCkJYlAgloe7nahJW35zc", "recipient_id": "16315555555", "status": "failed", "timestamp": "1617349703" } ] }
If you get that error, it may be because:
Curl
request from within the container:docker exec <webapp-container-id> curl -X GET <url-of-file> > file.pdf
For webhooks, you can have self signed certificates and use the /certificates/webhooks/ca
endpoint to upload the certificates. For media, the certificates need to have a proper chain and cannot be self-signed.
If you are unable to upload or download media or if your webhooks are not being delivered to your call back URL, you may see some of the following messages in your log entries:
If you get these errors, it may be because:
/media
endpoint.curl -X POST -H 'Content-type: application/json' --data '{"text":"Hello World!"}' --cacert <CERTIFICATE_PEM_FILE> <WEBHOOK_URL>
. The certificate file should be the same that was uploaded to the Enterprise Client. You can download the certificate from Enterprise Client by following the steps here.
openssl verify -verbose cert.pem
WhatsApp Business API v2.35 includes more extensive logging around media upload and download issues. On v2.35 you can look for the following entries in your logs: "MediaUploader: Found %d ssl errors"
and "MediaDownloader: Found %d ssl errors"
.