Cannot access live calls

Yeti-Switch
1

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.

YetiActiveCalls
YetiActiveCalls736×252 5.57 KB

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"

Where are the yeti-web logs located? /var/log/yeti/ is a empty directory

There is no default in /etc/nginx/sites-enabled/

2
3

The checks are fine.

I did journalctl -u yeti-web -f and tested going into an active call, i got the following error:

[8d98cb31-22b8-4f35-92b5-da1f63214717] Completed 200 OK in 316ms (Views: 141.1ms | ActiveRecord: 40.1ms (34 queries, 10 cached) | GC: 5.6ms)
 [4b1f7d78-ec61-44c5-bd96-3ac250defb31] Started GET "/active_calls/1*1-0793F847-682D21E9000DE230-CF4F86C0" for 123.45.678.90 at 2025-05-20 20:44:52 -0400
 [4b1f7d78-ec61-44c5-bd96-3ac250defb31] Processing by ActiveCallsController#show as HTML
 [4b1f7d78-ec61-44c5-bd96-3ac250defb31] Parameters: {"id"=>"1*1-0793F847-682D21E9000DE230-CF4F86C0"}
 [4b1f7d78-ec61-44c5-bd96-3ac250defb31] Completed 500 Internal Server Error in 69ms (GC: 0.0ms)
 [4b1f7d78-ec61-44c5-bd96-3ac250defb31] [4b1f7d78-ec61-44c5-bd96-3ac250defb31] ArgumentError (When assigning attributes, you must pass a hash as an argument, Array passed.):
                                           [4b1f7d78-ec61-44c5-bd96-3ac250defb31]
                                           [4b1f7d78-ec61-44c5-bd96-3ac250defb31] app/models/concerns/with_associations.rb:11:in `initialize'
                                           [4b1f7d78-ec61-44c5-bd96-3ac250defb31] app/models/node.rb:125:in `new'
                                           [4b1f7d78-ec61-44c5-bd96-3ac250defb31] app/models/node.rb:125:in `active_call'
                                           [4b1f7d78-ec61-44c5-bd96-3ac250defb31] app/models/realtime_data/active_call.rb:10:in `query_builder_find'
                                           [4b1f7d78-ec61-44c5-bd96-3ac250defb31] app/lib/query_builder/proxy.rb:23:in `find_record'
                                           [4b1f7d78-ec61-44c5-bd96-3ac250defb31] app/lib/query_builder/base.rb:65:in `find'
                                           [4b1f7d78-ec61-44c5-bd96-3ac250defb31] app/admin/realtime_data/active_calls.rb:109:in `show'
                                           [4b1f7d78-ec61-44c5-bd96-3ac250defb31] config/initializers/instrumentation_notification.rb:33:in `block in process_action'
                                           [4b1f7d78-ec61-44c5-bd96-3ac250defb31] config/initializers/instrumentation_notification.rb:32:in `process_action'
4

it looks like bug. GET /active_calls/<id> exception · Issue #1750 · yeti-switch/yeti-web · GitHub

5

And what about yeti-web logs, is it supposed to be only in journal or is something not properly setup on my server?

6

I sent you link do documentation because it explains how to check logs.

journalctl -u yeti-web

so it is supposed to be only in journald

1 Like