I have enabled capture signaling traffic in customers auths, but when trying to access it I’m getting a 502 Bad Gateway
looks like nginx misconfiguration
- verify you have configured everything as described here: Call trace storage configuration — Yeti documentation
- provide related
nginxlogs if it does not help
Everything was there as described, but i found it, it’s proxy_pass http://ts; that caused it, although it’s defined at the top of the page
upstream ts {
server 127.0.0.1:80;
}
I commented out and it’s working fine now.
Another question, while in a call and I go to active calls, i can see the call, when i click on the call i get a message
We’re sorry, but something went wrong.
In nginx error.log it says
[error] 1076114#1076114: *3 access forbidden by rule, client: 123.45.678.90, server: domain.com, request: "GET /favicon.ico HTTP/1.1", host: "domain.com", referrer: "https://domain.com/active_calls"
there is no proxy_pass http://ts in documentation Call trace storage configuration — Yeti documentation.
Do not mix everything in same topic. For new issues - create new topic with issue description and yeti-web logs.
1 Like
I did not add it manually, I just followed the documentation to get the server up and running, there are more lines there, I guess I’ll comment everything out and just leave it as described in the documentation.
It is working now, thank you!