Closed Goodsmileduck closed 4 years ago
Hello, this happened to me when the data in db.env was incorrect, and why are you using version v2.28.7 if the official WhatsApp documentation is at 2.27.12?
Hello, this happened to me when the data in db.env was incorrect, and why are you using version v2.28.7 if the official WhatsApp documentation is at 2.27.12?
Are you referring to v2.27.8? The version is only an example and you should refer to the changelog in the documentation for the latest version number. :)
@Goodsmileduck Can you verify if it is the same case as #15 ?
sorry, it's 2.27.8
@mengyiyuan yes, it's almost the same thing when web container can't connect to mysql.
I will try to reproduce it once time again to get more logs from containers.
BTW from docs, it's not clear how to use WA_API_KEY
Deployed v2.27.11
version to dev env. I set for web container WA_API_KEY=1938thwuerfiw3h05thgqiefo87w46yh
, but how I can use it now?
request with --header 'Authorization: Bearer 1938thwuerfiw3h05thgqiefo87w46yh'
return me:
{"meta":{"version":"v2.27.11","api_status":"stable"},"errors":[{"code":1005,"title":"Access denied","details":"Missing or invalid authentication credentials"}]}
ok, looks like I found. I should be
--header 'Authorization: Apikey 1938thwuerfiw3h05thgqiefo87w46yh'
Sorry for the late reply. Glad that you found the solution, I will close this issue now.
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
after that it stays running, and no logs we using
v2.27.8