Alexander Berezin

Any chance this will get reconsidered with the release of NC 22?

@kosli thank you very much for your work! Hope this makes it into the next release.

Thank you for the prompt reply. It seems that when I change `--socket` to `--http-socket` in the current configuration, the HTTP error code changes from 404 to 405. In general,...

Ok, I've switched to `--http` and here is what I get now. ``` >> curl 127.0.0.1:3031 {"message":"version: 0.3.1"} ``` ``` >> curl 127.0.0.1:3031/status 405 Method Not Allowed Method Not Allowed...

Here is what the log shows: `Error | talked | cURL Error (28): Operation timed out after 30001 milliseconds with 0 bytes received`

`https://nc.mydomain.org/talked` (domain redacted) /var/log/syslog only has lines about starting and stopping the service, nothing regarding its functioning.

Hello again. I've set the log level in the systemd service to debug and still haven't noticed anything suspicious that is directly related to Talked.

Oh, I see, sorry for the misunderstanding. Still, the result after the change is the same. This, I think, confirms the idea that the problem is with the connection and...

Yep, that solved the current problem. Now `/recording status` works in chat, but `/recording start` returns "Failed to load the Talk room".

Oops, no 😅 But now that it is, the error changed to "Failed to initiate call" (when a call is ongoing).