You need to sign in or sign up before continuing #8112
-
Can someone help me to understand why I receive this message when accessing to this address? I have Chatwoot running on docker in my Synology NAS. I think that solving this I will solve my issue when trying to link EVOLUTION API with CHATWOOT. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Hi all, no clue about that? I Haver chat won’t running on docker installation. |
Beta Was this translation helpful? Give feedback.
-
For posterity: I had this same problem. It was caused by nginx dropping the chatwoot/deployment/nginx_chatwoot.conf Line 28 in 4ed1378 |
Beta Was this translation helpful? Give feedback.
-
hi there, our installation of chatwoot (AKS: Azure Kubernetes Service, following the helm indication here) is not working with underscores_in_headers on; parameter in nginx. This is, according to admin console, Chatwoot 3.16.0 Just for our testing purposes we had added below to the nginx configMap and it had helped us:
On our call, instead of sending api_acces_token header, we sent api-acces-token which is catched by $http_api-access-token and before sending to chatwoot we replaced it to api_acces_token. I'm omitting a lot of details, that certainly I won't be able to explain since it was done by our DevOps expert. |
Beta Was this translation helpful? Give feedback.
For posterity: I had this same problem. It was caused by nginx dropping the
api_access_token
header because it uses underscores. The fix was to addunderscores_in_headers on;
in theserver
block in nginx config. See the nginx config in the repo:chatwoot/deployment/nginx_chatwoot.conf
Line 28 in 4ed1378